Feature-Driven Development - About Peter Coad
Feature-Driven Development - About Peter Coad
Feature-Driven Development - About Peter Coad
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
198 ▼ Java Modeling in Color with UML<br />
components<br />
Develop<br />
an<br />
Overall<br />
Model<br />
10% initial<br />
4% ongoing<br />
Build<br />
a<br />
<strong>Feature</strong>s<br />
List<br />
4% initial<br />
1% ongoing<br />
Plan<br />
by<br />
<strong>Feature</strong><br />
components<br />
shape sequences<br />
2% initial<br />
2% ongoing<br />
Again, the percentages are useful guidelines (not absolutes).<br />
The initial “develop an overall model, build a features list, and plan<br />
by feature” sequence consumes 16% of project schedule. The ongoing iterations<br />
of those front-end activities grab another 7%.<br />
It’s the other 77% we’re concerned about in this section, the time<br />
spent in the many “design by feature, build by feature” iterations.<br />
DBF/BBF consists of six little processes and corresponding schedulepercentage<br />
guidelines (Figure 6-6):<br />
■ DBF<br />
■ BBF<br />
Design<br />
by<br />
<strong>Feature</strong><br />
FIGURE 6-5. ▲ FDD processes with schedule percentages.<br />
DBF BBF<br />
Walk<br />
Through<br />
the<br />
Domain<br />
Design<br />
Inspect<br />
the<br />
Design<br />
Build<br />
by<br />
<strong>Feature</strong><br />
77%<br />
cycle time: every two weeks<br />
Code<br />
Inspect<br />
the<br />
Code<br />
1% 40% 3% 45% 10%<br />
44%<br />
56%<br />
FIGURE 6-6. ▲ DBF/BBF milestone with schedule percentages.<br />
Walk through the domain. 1%<br />
Design. 40%<br />
Inspect the design. 3%<br />
Code/test. 45%<br />
Inspect the code. 10%<br />
Promote to build. 1%<br />
Promote<br />
to<br />
Build<br />
1%