1 / 31

Jon Grommes

Jon Grommes. Feature Driven Development. Overview. What is Feature Driven Development History of FDD Defining a Feature FDD Roles FDD Reporting FDD Process FDD Quality. What is Feature Driven Development(FDD).

ipo
Download Presentation

Jon Grommes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Jon Grommes Feature Driven Development

  2. Overview • What is Feature Driven Development • History of FDD • Defining a Feature • FDD Roles • FDD Reporting • FDD Process • FDD Quality

  3. What is Feature Driven Development(FDD) • Feature Driven Development is a iterative and incremental software development process • FDD is a software process that was created to deliver frequent, working deployable code repeatedly to the customer. • FDD is considered a straight forward approach to developing software systems that is broken down into five processes. • FDD builds the correct system

  4. The FDD Process • Develop an Overall Model • Build a Feature List • Plan by Feature • Design by Feature • Build by Feature

  5. What is Feature Driven Development Iterative development process (modified for FDD)

  6. History of FDD • First created by Jeff De Luca for a 50 person 15 month project • Luca used the process again, with 250 people 18 month project. • FDD is heavily influenced by Peter Coad and his idea of using a feature list to manage requirements  • Documented in 1999, by when Luca and Coad and Eric Lefebvre wrote a book which was entitled “Java Modeling in Color with UML.”

  7. Defining a Feature • A feature is a “customer-valued function that can be implemented in two weeks or less,” according to COA99.(Coad and colleagues)  • Features are suppose to be small enough so that the customer can describe them exactly. • Should be small enough to implement in one to three days. But if the feature is estimated to take more than ten days to implement then it should be broken down into smaller features.

  8. Naming a Feature • COA99 created a template for defining a feature • <action> the <result> <by | for | of | to> a(n) <object> • Examples • Calculate the total of a Sale • Add a student to the class list

  9. Grouping Features • A feature set is a grouping of business related features. • <action><-ing> a(n) <object> • Example :Making a product Sale • A major feature set is groups of feature sets • <object> management • Example: Product Sales Management

  10. FDD Roles • Project Manager • Responsible for progress reports, budget management, and maintains resources • Chief Architect • Responsible for the creation of the overall design of the system •  Chief Programmers • Responsible for managing programming teams, helping with design of the   system

  11. FDD Roles • Development Managers • Responsible for day-to-day activities • Class Owners • Responsible for creating and testing classes • Domain Experts • Usually the customer, help the class owners build the correct system

  12. Class Owners • Class give to individual developers or two people • Class owner responsible that happen in their class Opposite • Collective Ownership • Any developer can change any line of code

  13. Class Owner Advantages • Sole person is responsible for the class • Expert on every class • Can make changes faster on a class • Owner has something to take pride in • Bring consistency to a class Disadvantages • Possible long waits times to edit other classes • Risk of Lack of knowledge about the class

  14. FDD Reporting Parking Lot Report

  15. FDD Reporting Parking Lot Report

  16. Milestone chart

  17. The FDD Process • Develop an Overall Model • Build a Feature List • Plan by Feature • Design by Feature • Build by Feature

  18. The FDD Process • Upfront Design Activities • Develop an Overall Model • Build a Features List • Plan by Feature • Create systems by Features • Design by Feature • Build by Feature

  19. The FDD Process

  20. 1. Develop an Overall Model • Create overall object model • Domain walk through • Manage scope • Form Modeling Team • Informal Feature List • Model • Only major class and important functions • State relationships between major classes • Sequence Diagram • Displaying complex functional requirements • Review • Notes

  21. 2. Build a Feature List • Features List • Feature List Team • Prioritize the Features • For features: <action> the <result> <by | for | of | to> a(n) <object> • For features sets: <object> management • For major feature sets: <action><-ing> a(n) <object>. • Review

  22. 3. Plan by Feature •  Create Project Milestones • Form the Planning team • Setting Initial Dates • Assigning Class Owners • Review

  23. 4. Design by Feature •  Feature Teams • Class Owners • Domain Walkthrough(optional) • Study Notes(optional) • Develop sequence diagrams • Refine Object Model • Review

  24. 5. Build by Feature •  Implement Classes and Methods • Code Inspection • Promote to Build

  25. FDD Process

  26. FDD Process

  27. FDD Quality • Inspections • Design • Code • Benefits • Knowledge transfer • Standards Conformance • Unit Tests

  28. Summary • Feature Driven Development is a iterative and incremental software development process • FDD is a software process that was created to deliver frequent, working deployable code repeatedly to the customer. • Overall FDD has a lot of good aspects to it that will allow it to be used a lot in the futrue.

  29. References [1]        Stephen Palmer, John Felsing. (2002). A Practical Guide to Feature Driven Development. Upper Saddle River: Prentice Hall. [2]        Pressman, R. (2005). Software Engineering A Practitioner's Approach. Crawfordsville: McGraw-Hill. [3]        Unkown. (2007, 6 17). Feature Driven Development. Retrieved 3 25, 2011, from SCMWise: http://www.scmwise.com/feature-driven-development.html [4]        Palmer, S. (2009, 11 20). An Introduction to Feature-Driven Development. Retrieved 3 25, 2011, from AgileZone: http://agile.dzone.com/articles/introduction-feature-driven [5]        Bauer, M. (2004, 5 27). FDD and Project Managment. Retrieved 3 27, 2011, from martinbauer: http://www.martinbauer.com/Articles/FDD-and-Project-Management [6]        Cause, G. (n.d.). Delivering Real Business Value using FDD. Retrieved 3 26, 2011, from methodsandtools: http://www.methodsandtools.com/archive/archive.php?id=19p3 http://www.featuredrivendevelopment.com/files/fddoverview.pdf

  30. Questions?

  31. http://www.step-10.com/SoftwareDesign/ModellingInColour/

More Related