Feature-driven development
[1] Its main purpose is to deliver tangible, working software repeatedly in a timely manner in accordance with the Principles behind the agile manifesto.
[2] FDD was initially devised by Jeff De Luca to meet the specific needs of a 15-month, 50-person software development project at a large Singapore bank in 1997.
The description of FDD was first introduced to the world in Chapter 6 of the book Java modelling in Color with UML[1] by Peter Coad, Eric Lefebvre, and Jeff De Luca in 1999.
Later, in Stephen Palmer and Mac Felsing's book A Practical Guide to Feature-Driven Development[2] (published in 2002), a more general description of FDD was given decoupled from Java modelling.
For accurate state reporting and keeping track of the software development project, milestones that mark the progress made on each feature are defined.
Features in this respect are small pieces of client-valued functions expressed in the form "
For accurate state reporting and keeping track of the software development project, it is important to mark the progress made on each feature.
Feature-driven development is built on a core set of software engineering best practices aimed at a client-valued feature perspective.
The left side of the metadata model shows the five basic activities involved in a software development project using FDD.
