fdd process model diagram

2
FDD Process Model Source: "A Practical Guide to Feature Driven Development" by Palmer, Stephen R and Felsing, John M., Copyright © 2002 by Togethersoft Corporat ion Note: Gray shaded tasks are optional Develop an Overall Model Entry Criteria Tasks Verification Exit Criteria Form the Modeling Team (Project Manager) Conduct a Domain Walkthrough (Project Manager) Study Documents (Modeling Team) Develop Small Group Models (Modeling Team in Small Groups) Develop a Team Model (Modeling Team) Refine the Overall Oject Model (ChiefArchitect, Modeling Team) Write Model Notes (Chief Architect, Chief Programmer) Internal and External Assessment (Modeling Team, Business) Domain Experts, Chief Programmers, and the Chief Architect have been selected for the project. The modeling team must develop an object model to the satisfaction of the Chief Architect. The model consists of: class diagrams, sequence diagrams (if any) and explanatory notes. Repeated for each feature The planning team has successfully completed process 3: Plan By Feature Form a Feature Team (Chief Programmer) Conduct a Domain Walkthrough (Domain Expert) Study the Reference Documents (Feature Team) Develop The Sequence Diagram(s) (Feature Team) Refine the Object Model (Chief Programmer) Write Class and Method Prologue (Feature Team) Design Inspection (Feature Team) Design Inspection (Feature Team) The feature team must produce a successfull y inspected 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, design alternatives (if any), the latest object model, the class and method prologues (pseudo code) created during the process and a to-do task list on affected classes for each team member. Design By Feature Entry Criteria Tasks Verification Exit Criteria The feature team has successfully completed process 4: Design By Feature for each of the selected features. Implement Classes and Methods (Feature Team) Conduct a Code Inspection (Feature Team) Unit Test (Feature Team) Promote to the Build (Chief Programmer, Feature Team) Code Inspection and Unit Test (Chief Programmer, Feature Team) The feature team must complete the development of one or more features (client- valued functions). To do this, it must have promoted to the build the set of new and enhanced classes that support those features, and those classes must have been successfully code inspected and unit tested. Build by Feature Entry Criteria Tasks Verification Exit Criteria The modeling team has successfully completed process 1: Develop an Overall Model Form the Feature List Team (Project Manager. Development Manager) Build the Feature List (Feature List Team) Internal and External Assessment (Feature List Team, Business) The feature list team must produce the features list to the satisfaction of the Project Manager. The feature list consists of: a list of major feature sets (areas), a list of features within each feature set. Build a Feature List Entry Criteria Tasks Verification Exit Criteria The feature list team has successfully completed process 2: Build a Feature List Form the Planning Team (Project Manager) Determine the Development Sequence (Planning Team) Assign Feature Sets to Chief Programmers (Planning Team) Assign Classes to Developersr (Planning Team) Self Assessment (Planning Team, Project Manager) The planning team must produce the development plan to the satisfaction of the Project Manager and Development Manager. The development plan consists of: feature sets with completion dates, Chief Programmers assigned to feature sets, a list of classes and the developers that own them. Plan By Feature Entry Criteria Tasks Verification Exit Criteria

Upload: nizarkhoja3470

Post on 10-Apr-2018

219 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: FDD Process Model Diagram

8/8/2019 FDD Process Model Diagram

http://slidepdf.com/reader/full/fdd-process-model-diagram 1/1

FDD Process Model

Source: "A Practical Guide to Feature Driven Development" by Palmer, Stephen R and Felsing, John M., CNote: Gray shaded tasks are optional

Develop an Overall Model

Entry Criteria

Tasks

Verification

Exit Criteria

Form the ModelingTeam

(Project Manager)

Conduct a DomainWalkthrough

(Project Manager)

Study Documents

(Modeling Team)

Develop SmallGroup Models

(Modeling Team inSmall Groups)

Develop a TeamModel

(Modeling Team)

Refine the Overall

Oject Model(Chief Architect,Modeling Team)

Write Model Notes(Chief Architect,

Chief Programmer)

Internal and External

Assessment(Modeling Team,

Business)

Domain Experts, Chief Programmers, and the ChiefArchitect have been selected for the project.

The modeling team must develop an object model

to the satisfaction of the Chief Architect. Themodel consists of: class diagrams, sequence

diagrams (if any) and explanatory notes.

Repeated for each

The planning team has successfully completed process 3:Plan By Feature

Form a FeatureTeam

(Chief Programmer)

Conduct a DomainWalkthrough

(Domain Expert)

Study theReference

Documents(Feature Team)

Develop TheSequence

Diagram(s)(Feature Team)

Refine the Object

Model(Chief Programmer)

Write Class and

Method Prologue(Feature Team)

Design Inspection(Feature Team)

Design Inspection(Feature Team)

The feature team must produce a successfully inspected

design package. The design package comprises: acovering memo that integrates and describes the designpackage, the referenced requirements (if any) in the form

of documents, memos and supporting documentation,design alternatives (if any), the latest object model, the

class and method prologues (pseudo code) createdduring the process and a to-do task list on affected

classes for each team member.

Design By Feature

Entry Criteria

Tasks

Verification

Exit Criteria

The feature teaDesign By Fe

Implement and Met

(Feature T

Unit T

(Feature T

The feature one or more

this, it must and enhanc

and those cl

The modeling team has successfully completed process 1:Develop an Overall Model

Form the Feature ListTeam

(Project Manager.

Development Manager)

Build the Feature List(Feature List Team)

Internal and ExternalAssessment

(Feature List Team,Business)

The feature list team must produce the features list to the

satisfaction of the Project Manager. The feature list consists of:a list of major feature sets (areas), a list of features within each

feature set.

Build a Feature List

Entry Criteria

Tasks

Verification

Exit Criteria

The feature list team has successfullycompleted process 2: Build a Feature List

Form the PlanningTeam

(Project Manager)

Determine the

DevelopmentSequence

(Planning Team)

Assign Feature Sets to

Chief Programmers(Planning Team)

Assign Classes toDevelopersr

(Planning Team)

Self Assessment(Planning Team, Project

Manager)

The planning team must produce the development planto the satisfaction of the Project Manager and

Development Manager. The development plan consists

of: feature sets with completion dates, ChiefProgrammers assigned to feature sets, a list of classes

and the developers that own them.

Plan By Feature

Entry Criteria

Tasks

Verification

Exit Criteria