FDD Process Model

Develop an Overall Model Build a Feature List Plan By Feature Design By Feature Build by Feature
Entry Criteria Entry Criteria Entry Criteria Entry Criteria Entry Criteria
The feature list team has successfully The planning team has successfully completed process 3: The feature team has successfully completed process 4:
Domain Experts, Chief Programmers, and the Chief The modeling team has successfully completed process 1:
completed process 2: Build a Feature List Plan By Feature Design By Feature for each of the selected features.
Architect have been selected for the project. Develop an Overall Model

Tasks Tasks Tasks

Tasks Tasks

Determine the Implement Classes Conduct a Code

Form the Planning Form a Feature Conduct a Domain and Methods Inspection
Form the Feature List Development
Team Team Walkthrough (Feature Team) (Feature Team)
Team Sequence
Form the Modeling Conduct a Domain (Project Manager. (Project Manager) (Chief Programmer) (Domain Expert)
(Planning Team)
Team Walkthrough Development Manager)
(Project Manager) (Project Manager)

Study the Develop The

Reference Sequence
Assign Feature Sets to Assign Classes to Documents Diagram(s) Promote to the Build
Chief Programmers Unit Test
Developersr (Feature Team) (Feature Team) (Chief Programmer,
Develop Small (Feature Team)
(Planning Team) (Planning Team) Feature Team)
Study Documents Group Models
Build the Feature List
(Modeling Team) (Modeling Team in
(Feature List Team)
Small Groups)
Refine the Object Write Class and
Model Method Prologue
(Chief Programmer) (Feature Team)
Verification
Refine the Overall
Verification
Develop a Team Oject Model
Model Verification
(Chief Architect, Code Inspection and
(Modeling Team) Modeling Team) Self Assessment
Design Inspection Unit Test
Internal and External (Planning Team, Project
(Feature Team) (Chief Programmer,
Assessment Manager)
Feature Team)
(Feature List Team,
Business)
Write Model Notes Exit Criteria Verification Exit Criteria
(Chief Architect,
Chief Programmer) Exit Criteria The planning team must produce the development plan The feature team must complete the development of
The feature list team must produce the features list to the to the satisfaction of the Project Manager and one or more features (client- valued functions). To do
satisfaction of the Project Manager. The feature list consists of: Development Manager. The development plan consists Design Inspection
this, it must have promoted to the build the set of new
a list of major feature sets (areas), a list of features within each of: feature sets with completion dates, Chief (Feature Team)
and enhanced classes that support those features,
feature set. Programmers assigned to feature sets, a list of classes and those classes must have been successfully code
Verification and the developers that own them. inspected and unit tested.

Internal and External Exit Criteria

Assessment
The feature team must produce a successfully inspected
(Modeling Team,
Business) design package. The design package comprises: a
covering memo that integrates and describes the design
package, the referenced requirements (if any) in the form
of documents, memos and supporting documentation,
Exit Criteria design alternatives (if any), the latest object model, the
class and method prologues (pseudo code) created
The modeling team must develop an object model during the process and a to-do task list on affected
to the satisfaction of the Chief Architect. The classes for each team member.
model consists of: class diagrams, sequence
diagrams (if any) and explanatory notes.

Repeated for each feature

Note: Gray shaded tasks are optional Source: "A Practical Guide to Feature Driven Development" by Palmer, Stephen R and Felsing, John M., Copyright © 2002 by Togethersoft Corporation