Home > Store

Practical Guide to Feature-Driven Development, A

Register your product to gain access to bonus material or receive a coupon.

Practical Guide to Feature-Driven Development, A

Book

  • Sorry, this book is no longer in print.
Not for Sale

Description

  • Copyright 2002
  • Dimensions: 7" x 9-1/4"
  • Pages: 304
  • Edition: 1st
  • Book
  • ISBN-10: 0-13-067615-2
  • ISBN-13: 978-0-13-067615-3

Feature Driven Development (FDD), created by Peter Coad and Jeff de Luca, combines the compelling advantages of agile methodologies with model-driven techniques that scale to the largest teams and projects. This book demonstrates FDD at work in real-world projects, giving project leaders all the information they need to successfully apply it in their own organizations. The authors begin by introducing FDD's goals and rationale, and the compelling advantages of its model-driven, short-iteration approach to software development. You'll discover which types of projects FDD is best suited for; and understand FDD's roles, artifacts, goals, and timelines. The book includes practical, hands-on coverage of all five key FDD activities: developing an overall model, building a feature list, "plan by feature," "design by feature," and "build by feature." The book also offers specific guidance on adapting FDD to many different types of projects.

Sample Content

Online Sample Chapter

Feature-Driven Development: Best Practices

Table of Contents



Acknowledgments.


Foreword.


Preface.


Introduction.

I. FEATURE-DRIVEN DEVELOPMENT—CONCEPTS.

1. Process Pride: The Pain and Relief.

Process Pride. The Search. Communication, Communication, and Communication. Complexity. Quality. Process Pain and Relief. Summary.

2. Feature-Driven Development—Projects and People.

The Big Three. Process and People. The Roles People Play in FDD. Summary.

3. Feature-Driven Development—Practices.

Integrating Best Practices. Domain Object Modeling. Developing by Feature. Class (Code) Ownership. Feature Teams. Inspections. Regular Build Schedule. Configuration Management. Reporting/Visibility of Results. Summary.

4. Feature-Driven Development—Processes.

The Scope of Feature-Driven Development (FDD). FDD in Four Sentences. FDD in a Nutshell. FDD in Detail. Summary.

5. Feature-Driven Development—Progress.

Time: A Scarce Resource. Estimating Progress. Track by Feature. Reporting to the Development Team. Reporting to the Chief Programmers and Project Manager. Reporting to Sponsors and Upper Management. Chief Programmer Plans. Feature Kills. Summary.

6. Feature-Driven Development—Packages.

Chief Programmer Work Packages. When You Have to Produce a Mountain of Paper. Summary.

II. FEATURE-DRIVEN DEVELOPMENT—THE FIVE PROCESSES IN PRACTICE.

7. Develop an Overall Object Model.

The Form the Modeling Team Task. The Conduct a Domain Walkthrough Task. The Study Documents Task. The Develop Small Group Models Task. The Develop a Team Model Task. The Refine the Overall Object Model Task. The Write Model Notes Task. Verification. Exit Criteria.

8. Feature-Driven Development—Build a Features List.

The Form the Features List Team Task. The Build the Features List Task. Verification. Exit Criteria.

9. Feature-Driven Development—Planning Feature Development.

The Form the Planning Team Task. The Determine the Development Sequence Task. The Assign Feature Sets to Chief Programmers Task. The Assign Classes to Developers Task. Verification. Exit Criteria.

10. Feature-Driven Development—Designing by Feature.

The Form a Feature Team Task. The Conduct a Domain Walkthrough Task. The Study the Referenced Documents Task. The Develop the Sequence Diagram(s) Task. The Refine the Object Model Task. The Write Class and Method Prologue Task. Verification: Design Inspection. Exit Criteria.

11. Feature-Driven Development—Build by Feature.

The Implement Classes and Methods Task. The Conduct a Code Inspection Task. The Unit Test Task. The Promote to the Build Task. Verification. Exit Criteria.

III. FEATURE-DRIVEN DEVELOPMENT—ADDITIONAL TOPICS.

12. Feature-Driven Development—Technical Architecture.

Technical Architecture. Technical Architecture in an FDD Project. The PD Layer. The SI Layer. The UI Layer. The DM Layer. Layers and the Build. Reducing Dependencies between Components.

13. Feature-Driven Development—Testing: Failures, Faults, and Fixes.

Kinds of Testing. Failures, Faults, and Fixes. FDD and Unit Testing. FDD and Integration Testing. FDD and System Testing. Customer/User Acceptance Testing. Finding Failures. Reporting Failures. Diagnosing Defects. Fixing Faults. The Defect Board. Summary.

14. Feature-Driven Development—Other Surroundings.

Requirements Change Management. User Documentation. Data Loading and Conversion. Deployment. Summary.

15. Feature-Driven Development—“All Change”.

People and Change. Technology and Change. Process and Change. Last Words.

References.
Index.

Preface

Preface

What FDD Is!

Feature-Driven Development (FDD) is a process designed and proven to deliver frequent, tangible, working results repeatedly. This is the first book to spell out the day-to-day details of using FDD on a real project, giving development team leaders all the information they need to apply FDD successfully to their situations.

FDD is a straightforward approach to producing systems that uses simple, easy-to-understand and easy-to-implement methods; problem-solving techniques; and reporting guidelines providing every stakeholder of a project with the information they need to make sound, timely decisions.

Programmers are provided with the information and supporting infrastructure they need to produce applications. Team leaders and managers get timely information about their teams and projects that allows them to reduce the project risk. Project managers and executive sponsors see the current project status and trouble areas so that they can actually make timely, informed decisions in a controlled, planned manner (no knee-jerk reactions). Reporting becomes easy, relatively painless, timely, and accurate!

Users (customers, sponsors, end users) can actually see areas of their business automated as the project progresses and give early, constructive feedback about the system while it is being developed. At the same time, the development team has the tools and information it needs to control "scope creep!"

What FDD Is Not!

FDD is not yet another process that takes up resources, time, and money but just doesn't produce the needed results. It is not another method whereby administrators, bureaucrats, and process-centric fanatics can focus everyone's time and energy on producing reams of printouts and signatures with nothing to show for it. FDD is not another set of process volumes that will sit on your shelf, collecting dust and impressing your supervisor, co-workers, and significant others with your knowledge of another less-than-useful set of directions for producing systems.

Why Should I Read this Book? (What's in it for Me?)

If any of the following questions apply to you, you will find the answers you are looking for on the following pages:

  • Are you in charge of a group assigned to deliver a critical system with limited resources and short deadlines, and need help to organize the project?
  • Are you tired of filling out so many process forms and reviewing so many documents that you don't have time to do your real work?
  • Are you frustrated at the unfulfilled promises of process initiatives that claim to provide a way to deliver quality results repeatedly?
  • Are you looking for a more efficient way to organize your team to streamline productivity, cut down on unnecessary interruptions, and improve the accuracy of reporting for your projects?
  • Are you currently working on a project that is in trouble because the team has failed to produce a system?
  • Do you want to add to the tools and techniques in your project management or team leader toolbox?
Prego (It's in There!)

Although FDD was first introduced in print in Java Modeling in Color with UML Coad 99, we give a more thorough coverage of the topic. We point out the critical tips for success, as well as the pitfalls that may not be apparent from a cursory glance. Contents include:

  • Who should use FDD
  • The roles, artifacts, goals, and timelines
  • Why FDD includes the practices and techniques that it does
  • The driving forces behind the development of FDD
  • Adapting the use of FDD to different styles of projects

FDD blends a number of industry-recognized best practices used successfully by Peter Coad, Jeff De Luca, and others in their consultancies. These practices are all driven from a client-valued feature perspective. It is the potent combination of these techniques and practices that makes FDD so compelling.

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020