Using a more functional approach instead of a process-oriented approach, the feature tree allows requirements and work to be categorized in a feature tree.
A feature tree can be configured freely. For instance, the feature tree can have various applications defined at the top-level, with modules and sub-modules, bundling the requirements and work in features at the lowest level. The granularity and the depth are completely up to the analysts.
The work and requirements are shared between the business processes, features and iterations.
When adding a new node in the tree, the type of node will be determined by the node that was selected.
- When a feature node was selected, a new feature node will be created.
- When a requirement node was selected, a requirement node will be created.
- When a work node was selected, a work node will be created.
The new node will be placed next to the previously selected node by default, with the same parent and at the same level.
Alternatively, new child nodes at a certain location can be added via the Sub-features, Linked requirements or Linked work tab.
When work is linked to a requirement, repositioning the requirement will also reposition the work. However, the work can be placed at a different location in the feature tree while retaining its link with the requirement. The work will receive a different icon and a task will be available to move the work to the same location in the feature tree as its requirement.
|The work is not linked to a requirement, placed freely in the feature tree|
|The work is linked to a requirement and is in sync when it comes to positioning in the feature tree|
|The work is linked to a requirement but is manually placed elsewhere in the feature tree|
To supplement the description of features, attachments can be added. These attachments will be stored in the database.
Linked requirements and linked work
The Linked requirements and Linked work details show the requirements and the work that is directly linked to the feature.
The Impact analysis tab can be used to get an overview of all underlying requirements and all underlying work for a certain feature. These overviews differ from the Linked requirements and Linked work details as they also include the requirements and work of all sub-features.
The arrow () can be used to navigate to the selected requirement or the selected work in the feature tree.
To find out which business processes and iterations share the same underlying requirements and/or underlying work, the Related business processes and Related iterations details can be used in the Impact analysis tab.
The arrow () can be used to navigate to the node in the business process or iteration tree, respectively.
To quickly and freely categorize features, tags are available.
The Unassigned node is used to group requirements and work that have not yet been assigned to a feature.
Drag-drop can be used to reposition nodes. The dragged node will be positioned as a child of the drop target node.
The progress of the features is aggregated using the status of the underlying requirements and work.
For more information, see the documentation on requirements and work.