Feature-Driven Development

Topics: Feature Driven Development, Project management, Agile software development Pages: 3 (1093 words) Published: March 1, 2013
Feature Driven Development
Feature-Driven Development is a form of Agile Methodology used primarily in software development. It is a model-driven method that is both incremental and iterative and it primarily focuses on client-valued functions, or features. The project is built based on required specific features rather than adding them on later. FDD is most effective with larger projects that use complex business logic, whereas small, simple projects cannot properly use the methodology. The FDD process is broken down into five basic steps: Develop the Overall Model, Build Feature List, Plan by Feature, Design by Feature, and Build by Feature. The first step involves starting with a walkthrough of the context and scope of each domain in the entire project in order to create a broad model. The model does not contain any specific attributes or methods involved, but instead focuses on the general shape of each part of the project and culminates in a total picture. It is an iterative and collaborative process that involves the entire team as well as the clients/stakeholders to come up with the model. The second step consists of identifying and listing all of the specific features required to meet the project requirements. It is imperative to use the terminology of the business domain so that the client would be able to understand each feature and reduce the chances of miscommunication. Often times poor communication leads to problems in development, so a common language must be used to clear up any confusion. With FDD, every aspect is described as a feature, which is defined as <action> the <result> by/for/to an <object> (e.g., calculate the total for a sale). Along with this description, features also include a timeline, typically less than two weeks each. The definition of each feature ensures that both clients and project team members are on the same page in terms of requirements and minimizes risk of miscommunication. The third...
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Paragraph Development Essay
  • Test Driven Development Essay
  • Feature Essay
  • Features Research Paper
  • Features of Private Payers and Consumer Driven Health Plans Essay
  • Features of Private Payer & Consumer Driven Health Plans Essay
  • Event driven program key features P1 Essay
  • Features of Private Payer and Consumer-Driven Health Plans Essay

Become a StudyMode Member

Sign Up - It's Free