Requirement Management Overview
The requirement is a process of documenting, analyzing, tracing, and prioritizing actions and needs to meet certain business objectives.
The purpose of requirements is to make sure that the organization validates and meets the needs of its customers. A Requirement can be created from an Idea, Demand, Portfolio, and Task within a Project.
Requirements are related to demands or portfolios. Demand requirements are copied in the portfolio once the demand is approved.
Requirement Management roles
Idea Manager
The idea manager reviews and classifies the assigned ideas. Once an idea with the type 'Requirement' is accepted, a new requirement is created automatically with all information within the related portfolio. For more details, see Product Roles under Orientation.
Demand Manager
The demand manager creates requirements related to the assigned demands. If demand is approved and classified as 'Portfolio', the requirements are copied into the new portfolio. If the demand is approved and classified as a 'Project', the requirements are copied in the portfolio of the demand. For more details, see Product Roles under Orientation.
Project Manager
The project manager can create a requirement from project tasks, that are within the portfolio. For more details, see Product Roles under Orientation.
Portfolio Manager
A portfolio manager can create new requirements in portfolios where he/she is assigned as Portfolio Manager. For more details, see Product Roles under Orientation.
Project Task User
The project manager can create a requirement from project tasks, that are within the portfolio. For more details, see Product Roles under Orientation.
End-to-end process
The following figure provides an overview of the requirement lifecycle.
The requirement management process consists of the following procedures for handling requirements.
- The user logs in to the Portfolio Management application and creates a new requirement by following the steps in Create a new Requirement.
- The requirement is created in New status. The user detects scope, change, risk, and missing functionality which is not supported, see Viewing-and-updating-requirement-details.
- The user updates the status to In Backlog once the requirement is completely assessed and discussed by following the steps Changing-requirement-statuses.
- The users can create a project task from the requirement, see Creating Requirements and Creating-requirements-from-tasks, the requirement status is updated to In Project automatically and become related to the new task. Note - When projects are created from demands, all demand requirements are copied in the In Project status in the portfolio, and project tasks are created in the Backlog status in the projects and get related to the requirements.
- Once the related project task with the requirement is completed (Done status), the requirement changes to Delivered status automatically. If a related project task is canceled, the requirement moves back to In Backlog status and you can create a project task in future projects.
Requirement Management data access model
The Requirement Management submodule uses row-level security (RLS) to control access to the record and fields. RLS is applied by using Security Labels in BMC Helix Innovation Studio.
The following table describes the Security Labels required for the Requirements:
Security Label name | Description |
|---|---|
Idea Assignee | Access to the Requirement related to a Demand created from an idea, but without the write access. The permission is assigned to the idea manager of the Idea. |
Demand Owner | Access to the Requirement related to Demand. Grants write access to modify the Requirement, provided the Demand is in 'Draft' status. The permission is assigned to the demand submitter. |
Demand Assignee | Access to the Requirement related to Demand. Grants write access to modify the Requirement. The permission is assigned to the demand manager. |
Project Assignee | Access to the Requirement related to a Portfolio, but without write access. The permission is assigned to the project managers of the Projects in the Portfolio. |
Portfolio Assignee | Access to the Requirement. Grants write access to modify the Requirement. If the Requirement is related to a Portfolio, the permission is assigned to the portfolio manager. If the Requirement is related to the Demand, permission is assigned to the portfolio manager to which the Demand belongs. |
Program Assignee | Access to the Requirement. Grants write access to modify the Requirement. If the Requirement is related to a Program, the permission is assigned to the program manager. If the Requirement is related to the Demand, permission is assigned to the program manager to which the Demand belongs. |