|
Method Fragment:
Features List |
|
|
|
|
|
|
|
|
Originating Method: FDD |
|
|
List of features that
will support the user requirements. Based on FDD process, Feature List should
be developed after Domain Object Modeling, but in general, FL can be
developed after requirements elicitation (e.g. by interviews, workshops,
etc.) |
|
|
|
|
|
|
|
|
|
Contributes to |
|
|
|
Major Softgoal |
sub softgoal |
Cont.
Value from Fragment |
Study |
Situation |
|
|
|
Better
Planning |
Better Prioritization |
+ |
|
Feature
lists, with the help of interviews and workshops for RE |
|
|
|
Faster
Time to Market |
+ |
|
Earlier
development of high priority features, and sooner coming to a runing
prototype |
|
|
|
Better
Iteration Planning |
+ |
|
Explicit
features clarified the goal of each iteration |
|
|
|
Better Design |
Expandability |
++ |
|
Separation
of Core features from other features helped to the expandability of system
architecture |
|
|
|
|
|
|
|
|
|
|
Improved Collaboration |
Organization of
individuals thoughts |
+ |
|
Individuals
working together around feature lists |
|
|
|
|
|
|
|
|
|
|
Improved Communication |
Better
Understaning of Customer needs |
+ |
|
|
|
|
|
Improved Effectiveness |
Defect Control |
+ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|