Escolar Documentos
Profissional Documentos
Cultura Documentos
Agenda
Definition of FDD History of FDD Why FDD? Process of FDD Technical and Financial benefits Future Work Conclusion
2
Quotations
I feel a recipe is only a theme which an intelligent cook can play each time with a variation ( Madame Benoit) The ultimate judgment of progress is this: measurable results in reasonable time (Robert Anthony)
History of FDD
Introduction
Birth of FDD:
Singapore project deemed undoable
2 years 3,500 pages of use case Object model with hundreds of classes Thousands of attributes (but no methods) And NO CODE AT ALL!
Jeff De Luca
Blow schedule
>180days = HIGH RISK! Why?
Business rapidly changing
WHY FDD??
To enable and enforce the repeatable delivery of working software in a timely manner with highly accurate and meaningful information to all key roles inside and outside a project. Many long & complex Projects fail Heavy process approach doesn t work FDD supports Building complex software systems Large development teams
9
What is a Feature?
Definition: small function expressed in clientvalued terms Split into respective domains Features are to be small in the sense they will take no more than two weeks to complete Features that appear to take longer are to be broken up into a set of smaller features Note: Two weeks is the maximum, most features take far less time (1 - 5 days)
10
What is a Feature?
Examples:
Calculate the total of a sale Validate the password of a user Authorize the sales transaction of a customer
11
12
13
FDD Process
Step #1: Develop an Overall Model Step #2: Build a Features List Step #3: Plan By Feature Step #4: Design By Feature Step #5: Build By Feature
14
15
16
Admission System
Reporting
FDD emphasizes the ability to provide accurate, meaningful, and timely progress information to all stakeholders within and outside the project
Feature Milestones
20
21
FUTURE WORK
The future work is to study the usefulness of this methodology in a variety of domains, It is also important to collect cases of feature (or aspect) conflict/subversion, and abstract the resolution pattern for the interworking of features.
References
http://www.wisegeek.com/what-is-featuredriven-development.htm http://www.featuredrivendevelopment.com http://www.nebulon.com http://www.togethersoft.com (http://borland.com) Palmer, Stephen and Fesling, John, A Practical Guide to Feature Driven Development, Prentice-Hall, 2002
24