DocumentCode
1964662
Title
Emergent database design: liberating database development with agile practices
Author
Harriman, Alan ; Hodgetts, Paul ; Leo, Mike
fYear
2004
fDate
22-26 June 2004
Firstpage
100
Lastpage
105
Abstract
Many agile projects do not apply agile practices to their database development. Common wisdom dictates that the entire data model be carefully designed up front and protected from change thereafter. We believed the common wisdom as well. But the clash of traditional database practices and agile development practices caused us significant pain, and hamstrung our ability to deliver the most business value in each iteration. Once we recognized this pain, we abandoned the conventional wisdom. Incrementally, we applied agile discipline to our database development, eventually reducing up-front design work to just-in-time work that matched our 1 to 2 week development iterations. This paper summarizes our experience.
Keywords
data analysis; data integrity; entity-relationship modelling; object-oriented methods; project management; software prototyping; team working; agile development practices; business value; data model; database development; emergent database design; entity-relationship modelling; Costs; Data models; Design methodology; Lakes; Logic; Pain; Production; Programming profession; Protection; Relational databases;
fLanguage
English
Publisher
ieee
Conference_Titel
Agile Development Conference, 2004
Print_ISBN
0-7695-2248-3
Type
conf
DOI
10.1109/ADEVC.2004.13
Filename
1359802
Link To Document