FDD Process Model

5 minutes 5 Questions

The FDD Process Model refers to the five-step approach used in Feature Driven Development. The first step is Develop an Overall Model, where a high-level model of the domain is created to establish a shared understanding of the system. The second step is Build a Features List, where features are identified and grouped under subject areas. The third step is Plan by Feature, where a project plan is developed based on feature sets and priorities. The fourth step is Design by Feature, which involves creating detailed design drawings for each feature, including class diagrams and interaction diagrams. The final step is Build by Feature, where developers build and integrate the features following the designs, and ongoing code reviews and inspections are conducted. This iterative process ensures continuous improvement and accurate development according to client requirements.

Guide to FDD Process Model

Feature-Driven Development (FDD) Process Model is crucial because it facilitates complex systems' development by breaking them into smaller, manageable features. These features are worked on and progressively integrated to the larger system.

What is FDD Process Model?
The FDD Process Model is a client-centric, heavyweight methodology used for developing software within the realm of agile project management. It primarily aims at delivering tangible, working software repeatedly in a timely manner.

How does the FDD Process Model work?
The FDD Process involves five stages: Develop an Overall Model, Build a Features List, Plan By Feature, Design By Feature, and Build By Feature. These stages are continuously iterated upon as the development progresses.

Exam Tips: Answering Questions on FDD Process Model
1. Understand and cover all aspects of its five stages in your answer.
2. Highlight its importance and benefits in real-world situations.
3. Mention how FDD promotes quick and continuous delivery of features.
4. Describe how FDD encourages collaboration and communication.
5. Emphasize the iterative nature of FDD.
Remember to use specific examples for better understanding and to make your answer more convincing.

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

Question 1

In an FDD project, customer requirements have changed, leading to the need for new features. What is the appropriate sequence of FDD processes to adapt to this change?

Feature Set Reassessment, Development by Feature, Domain Modeling Development by Feature, Code Inspection, Feature Breakdown Domain Modeling, Building Feature List, Plan by Feature Plan by Feature, Develop by Feature, Feature Breakdown Domain Modeling, Plan by Feature, Development by Feature Code Ownership, Code Inspection, Domain Modeling

Correct Answer: Domain Modeling, Building Feature List, Plan by Feature

When new requirements arise, the correct sequence is to start with Domain Modeling to understand the new features, then Building the Feature List to create a proper list of the new features, and finally Plan by Feature to incorporate them into the project plan.

Question 2

In an FDD project working on medical software, an issue is identified in the prescription report generation feature. Which role is responsible for resolving this?

Subject Matter Expert Chief Programmer Project Manager Class Owner Domain Expert Member of the development team

Correct Answer: Chief Programmer

The role of the Chief Programmer is to lead the resolution of any issues, as they have the most knowledge and experience in the development of the software. The other roles have different responsibilities and focus on other areas of the project.

Question 3

A developed feature doesn't follow the established coding standards. Which FDD process should be followed to correct this?

Domain Modeling Plan by Feature Code Inspection Development by Feature Feature Breakdown Code Ownership

Correct Answer: Code Inspection

Code Inspection is the correct process to ensure that coding standards are met and any deviations are corrected. The other options are either unrelated or other FDD processes that don't address the problem of non-compliance with coding standards.

Go Premium