As the name implies, features are a

As the name implies, features are an important aspect of FDD. A feature is a small, client-valued function expressed in the form . For example, "Calculate the total of a sale", "Validate the password of a user", and "Authorize the sales transaction of a customer". Features are to FDD as use cases are to the Rational Unified Process (RUP) and user stories are to Scrum - they're a primary source of requirements and the primary input into your planning efforts.

As you see in Figure 1 there are five main activities in FDD that are performed iteratively. The first is Develop An Overall Model, the initial result being a high-level object model and notes. At the start of a project your goal is to identify and understand the fundamentals of the domain that your system is addressing, and throughout the project you will flesh this model out to reflect what you're building. The second step is Build A Features List, grouping them into related sets and subject areas. These first two steps map to the initial envisioning effort of AMDD (see Figure 2). Next you Plan By Feature, the end result being a development, the identification of class owners (more on this in a minute), and the identification of feature set owners. The majority of the effort on an FDD project, roughly 75%, is comprised of the fourth and fifth steps: Design By Feature and Build By Feature. These two activities are exactly what you'd expect, they include tasks such as detailed modeling, programming, testing, and packaging of the system.

Figure 1. The FDD project lifecycle.



Figure 2. The lifecycle of AMDD.



An FDD project starts by performing the first three steps in the equivalent of the DAD's Inception phase or XP's "iteration 0", the goal being to identify the scope of the effort, the initial architecture, and the initial high-level plan. Construction efforts occur in two-week (or less) iterations, similar to XP or DAD teams, with the team iteratively working through all five steps as needed. As with other agile software development processes, systems are delivered incrementally by FDD teams.

There are six primary roles on an FDD project: Project Manager, Chief Architect, Development Manager, Chief Programmer, Class Owner, and Domain Expert. An individual will take on one or more roles on a project as you would expect. The concept of a class owner is where FDD differs from XP. XP includes a practice called Collective Ownership the idea of which is that any developer can update any artifact, including source code, as required. FDD takes a different approach in that it assigns classes to individual developers, so if a feature requires changes to several classes then the owners of those classes must work together as a feature team to implement it. Just like programming pairs will model storm to think something through before they code it, so will feature teams.


FDD also defines a collection of supporting roles, including:

Domain Manager
Release Manager
Language Guru
Build Engineer
Toolsmith
System Administrator
Tester
Deployer
Technical Writer
FDD's five steps are supported by several best practices. The first is domain object modeling, the creation of a high-level class diagram and supporting artifacts that describes the problem domain. Developing by feature and individual class ownership are also best practices, as is having developers work together in feature teams. Inspections are an important aspect of FDD. FDD also insists on regular builds, similar to XP, and configuration management. Finally, FDD promotes a best practice called reporting/visibility of results, similar to XP and AM's philosophy of open and honest communication.

How would Agile Modeling (AM) be applied on an FDD project? The principles and practices can be clearly applied to FDD's two modeling-oriented steps - develop an overall model and design by feature. The only apparent mismatch between the two processes is FDD's practice of class ownership and AM's practice of collective ownership, but I would argue that this isn't the case. FDD's practice pertains to coding but does not to modeling, on a FDD project people work together in teams to model, along the lines of AM's model with others practice, and therefore several people will be working on your shared collection of modeling artifacts.

- See more at: http://www.agilemodeling.com/essays/fdd.htm#sthash.NaSQFESl.dpuf

ผลลัพธ์ (อังกฤษ) 3:

As the, name implies features are an important aspect of FDD. A feature is, a small client-valued function expressed in The form < action > < result > < Object >. For example, "Calculate the total of a sale", "Validate the password of a user", and "Authorize the sales transaction of a customer."Features are to FDD as use cases are to the Rational Unified Process (RUP) and user stories are to Scrum - they 're a primary Source of requirements and the primary input into your planning efforts.

As you see in Figure 1 there are five main activities In FDD that are performed iteratively. The first is Develop An Overall Model the initial, result being a high-level object Model and notesAt the start of a project your goal is to identify and understand the fundamentals of the domain that your system, is addressing And throughout the project you will flesh this model out to reflect what you 're building. The second step is Build A Features List grouping them, into related sets and subject areas. These first two steps map to the initial envisioning effort of AMDD (see Figure 2)Next you Plan By Feature the end, result being a development the identification, of class owners (more on this in a minute), And the identification of feature set owners. The majority of the effort on an FDD project roughly 75% is comprised of,, The fourth and fifth steps: Design By Feature and Build By Feature. These two activities are exactly what you ', d expectThey include tasks such as detailed modeling programming testing,,, packaging and of the system.

Figure 1. The FDD project Lifecycle.



Figure 2. The lifecycle of AMDD.



An FDD project starts by performing the first three steps in the equivalent Of the DAD 's Inception phase or XP' s "iteration 0", the goal being to identify the scope of the effort the initial architecture,And the initial high-level plan. Construction efforts occur in two-week (or less), iterations similar to XP or, DAD teams With the team iteratively working through all five steps as needed. As with other agile software, development processes Systems are delivered incrementally by FDD teams.

There are six primary roles on an FDD project: Project Manager Chief, Architect Development Manager,Programmer Chief, Owner Class, Domain and Expert. An individual will take on one or more roles on a project as you would Expect. The concept of a class owner is where FDD differs from XP. XP includes a practice called Collective Ownership the Idea of which is that any developer can update any artifact including code as, source, requiredFDD takes a different approach in that it assigns classes to individual developers so if, a feature requires changes to Several classes then the owners of those classes must work together as a feature team to implement it. Just like programming Pairs will model storm to think something through before they code it so will, feature teams.


FDD also defines a collection Of, supporting rolesIncluding:



Domain Manager Release Manager Language Guru


, Build Engineer Toolsmith System Administrator



Tester Deployer Technical Writer FDD 's five steps are supported by several best practices. The first is domain Object modeling the creation, of a high-level class diagram and supporting artifacts that describes the problem domainDeveloping by feature and individual class ownership are also best practices as is, having developers work together in Feature teams. Inspections are an important aspect of FDD. FDD also insists on regular builds similar to XP and configuration,, Management. Finally FDD promotes, a best practice called reporting / visibility, of resultsSimilar to XP and AM 's philosophy of open and honest communication.

How would Agile Modeling (AM) be applied on an FDD Project? The principles and practices can be clearly applied to FDD 's two modeling-oriented steps - develop an overall model And design by featureThe only apparent mismatch between the two processes is FDD 's practice of class ownership and AM' s practice of collective Ownership but I, would argue that this isn 't the case. FDD' s practice pertains to coding but does not to modeling on a, FDD project people work together in teams to model along the, lines of AM 's model with, others practiceAnd therefore several people will be working on your shared collection of modeling artifacts.

- See more at: http: / / www.agilemodeling.com / essays / fdd.htm # sthash.NaSQFESl.dpuf