This activity addresses:
-
Prioritizing and refining the input to the selection of features and requirements that are to be included in the
current iteration.
-
Defining the set of behavioral scenarios, for one or more Use Cases, that represent some significant central functionality.
-
Defining how traceability will be maintained, including which requirement attributes and traceability relationships
to maintain.
-
Refining the Vision to document the scope of the solution (see Develop Technical Vision)
The scope of a project is defined by the set of requirements allocated to it. Managing project scope to fit the
available resources (time, people, and money) is key to managing successful projects.
The Analyst role is responsible for determining requirements attribute values of
priority, effort, cost, risk values etc., from the appropriate stakeholders, which are collected in the repository of
requirements attributes. These will be used by the Project Manager role when planning each iteration and will enable the Architect
role to identify the architecturally significant scenario's or complete use cases, which will help define the Use-Case
View of the architecture.
|