Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Agile Houston Meeting - Jan 17th, "Evolutionary Database Design" w/ Pramodkumar Sadalage (updated with abstract)

0 views
Skip to first unread message

jsa...@gmail.com

unread,
Dec 12, 2007, 2:12:21 PM12/12/07
to agilehouston-announce
Title: Evolutionary Database Design

Abstract:

"For years the norm for object developers was to work in an
evolutionary (iterative and incremental) manner but for database
developers to work in a more serial manner. The predominance of
evolutionary development methodologies such as Extreme Programming
(XP), Feature Driven Development (FDD) make it clear that the two
groups need to work in the same manner to be productive as a team.

Pramod will present material from the 2007 Jolt Productivity Award
winning book "Refactoring Databases : Evolutionary Database Design" on
how to go about doing evolutionary database development, how to apply
all the agile practices to database development and will talk about
the following techniques:

Database refactoring: Evolve an existing database schema a small bit
at a time to improve the quality of its design without changing its
semantics.

Continous Integtration: Why not test you database creation and
migration scripts as part of Continous Integration and apply the same
rigor to the database artifacts that you apply to the application
code. You should fail the build when the developer/dba makes a mistake
doing a database change

Evolutionary data modeling: Model the data aspects of a system
iteratively and incrementally, just like all other aspects of a
system, to ensure that the database schema evolves in step with the
application code.

Database regression testing: Ensure that the database schema actually
works.

Configuration management of database assets: Your data models,
database tests, test data, and so on are important project artifacts
which should be managed just like any other artifact.

Database Schema Deployment: Ensure that the scripts used to build
development environments are the exact same as the used in QA, UAT and
production. Ensure deployment to production is not a surprise and not
a project in itself.


http://agilehouston.org/Main/EvolutionaryDatabaseDesign
January 17th 2008 - 6:30pm
3100 Main St, Suite 900
Directions and Parking: http://agilehouston.org/Main/PROS
Sponsored by PROS: http://www.prospricing.com

About The Speaker:

Pramod Sadalage is a Author and Consultant for ThoughtWorks, an
enterprise application development and integration company. He first
pioneered the practices and processes of evolutionary database design
and database refactoring in 1999 while working on a large J2EE
application using the Extreme Programming (XP) methodology. Pramod
writes and speaks about database administration on evolutionary
projects, the adoption of evolutionary processes with regard to
databases, and evolutionary practices impact upon database
administration, in order to make it easy for everyone to use
evolutionary design in regards to databases. When he is not working,
you can find him spending time with his family and trying to improve
his running.

jsa...@gmail.com

unread,
Dec 17, 2007, 12:07:50 PM12/17/07
to agilehouston-announce
The presenter had a conflict, so this has been moved to Jan 15th...
same time.
Reply all
Reply to author
Forward
0 new messages