|
|
|
|
|
|
|
|
|
|
- Overview
- Assigning dependencies to requirements
- Overview
- Assigning dependencies
- Monitoring requirements
- Window for managing the requirements
Assigning dependencies to requirements
The following steps must be performed to implement the requirements: - Creating a list of requirements. This list can group the necessary requirements for a new software version.
- Creating the requirements.
- Assigning dependencies to requirements (tasks, business rules, ...).
- Monitoring the requirements.
Assigning dependencies to requirements Overview A requirement is the description of a feature. To implement this feature, dependencies must be associated with this requirement. These dependencies can be tasks to perform, bugs to correct or business rules to implement. In a development team, the dependencies are added by the project manager. The project contributors see new tasks being added to their task list, and they can modify the duration assigned to the task. Assigning dependencies The dependencies are added from the window for managing the requirements, via the following toolbar:
These icons allow you to: - Link a new task or an existing task to the requirement. This task can be a development task, a test task or a documentation task.
The simple creation of a task enables you to create a task linked to the selected requirement.
The multiple creation allows you to create a set of tasks linked to the selected requirement. A development task, a test task and a documentation tasks are proposed by default.
The assignment of an existing task enables you to list all the tasks belonging to a contributor in order to select the requested task. - Link a new incident or an existing incident to the requirement. If the incident already exists (via user feedback for example), you have the ability to find the incidents per application.
- Link a new business rule or an existing business rule to the incident. If the business rule already exists, a search window enables you to quickly select the requested business rule.
As soon as the different dependencies are entered, the window for managing requirements is automatically refreshed. Various information is displayed: - The general state of the requirement and its dependencies: a requirement can be, for example, "Unplanned", "In progress", "Blocked", ... The general state of the requirement is deduced from the state of its dependencies.
- The status of the different types of action (development, documentation and test)
- The contributors. The list of contributor is deduced from the contributors linked to the requirement dependencies.
- The availability date is calculated according to the task list assigned to the different contributors.
- The rate for task completion, the rate for rule validation and the rate for fixing the incidents associated with the requirement.
Window for managing the requirements The window for managing the requirements gives the manager a global view of the progress of a requirement or set of requirements. Several filters are used to select the requirements to display. The "Historial" tab provides an overview of the progress and quality of a list of requirements. This tab is used to get: - A view of the impact of requirements: Various arrays and graphs show the number of requirements broken down by service, by person and by status.
- A view of the impact of tasks: Various graphs show the number of tasks affected by requirements and their progression.
- A view of the impact of incidents: Various graphs show the number of incidents affected by the requirements and their progression.
- Project elements: The list of project elements affected by the requirements (e.g. business rules).
The first three visions can be displayed according to different modes (General, Development, Test and Documentation) and they can take various complexity coefficients into account.
Esta página también está disponible para…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|