|
Contents |
FDD (Feature-driven design)
FDD is a design-oriented agile process developed by Jeff De Luca that follows the belief that a strong design (yet one that allows room for flexibility) will create a process that is better managed and thus more efficient. The project is divided into "features," which are small pieces of the project that possess some customer value. FDD creates design, code, and code inspection schedules that may seem strangely un-agile, but these schedules lack the depth and mounds of paperwork associated with a system completely specified in the requirements phase, instead relying on people and their roles to address the details as needed. The simplified design schedule also serves as an bridge of communication between manager and developer. Perhaps most importantly, the design schedule can be used to establish a baseline for productivity and be used to estimate future product development and serve as an important component of contract negotiation. Books: Peter Coad, Eric Lefebvre, and
Jeff De Luca, Java Modeling in Color with UML: Enterprise
Components and Process, Chapter
6, Prentice Hall, 1999. Palmer, S.R. and J.M. Felsing, A Practical Guide to
Feature-Driven Development, Prentice
Hall, 2002.
Web
Sites/Web Pages: Holonic
Software Development (Granville Miller) Step 10 – A Practical Guide to
Feature-Driven Development Images on
this page taken from the Feature-Driven
Development Community for educational and informational purposes only. |
