Task: Build Features List
Disciplines: Architecture
Relationships
RolesPrimary Performer: Additional Performers:
Outputs
Main Description

The team shall identify the set of features using the knowledge obtained from process #1. This is simple functional decomposition into subject areas that comes from the partitioning of the domain by the domain experts for their domain area walkthroughs in process #1. It is decomposed into subject areas that comprise business activities that comprise business activity steps (features).

Features are granular functions expressed in client-valued terms using this naming template:
<action> <result> <object>
For example, calculate the total of a sale, calculate the total quantity sold by a retail outlet for an item description Features are granular in accordance with the rule that a feature will take no more than two weeks to complete, but not so granular as to be at the level of getters and setters. Two weeks is an upper limit; most
features take less than this time. When a business activity step looks larger than two weeks, the step is broken into smaller steps that then become features.

Steps
The team shall identify the set of features using the knowledge obtained from process #1.