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 ensure that the organization validates and meets the needs of its customers. A Requirement can be created from an Idea, Demand, Portfolio, and a 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

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.

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 demand is approved and classified as 'Project', the requirements are copied in the portfolio of the demand.

Project Manager

The project manager can create a requirement from project tasks, that are within the portfolio.

Portfolio Manager

A portfolio manager can create new requirements in portfolios where he/she is assigned as Portfolio Manager.

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 portfolio manager logs in to Portfolio Management application and goes to the Portfolio Console. The portfolio manager opens a Portfolio and creates a new requirement by following the steps to Create a new Requirement.
The requirement is created in 'New' status. The portfolio manager detects scope, change, risk, and missing functionality which is not supported, see Viewing-and-updating-requirement-details.
The portfolio manager updates the status to 'In Backlog' once the requirement is completely assessed and discussed by following steps Changing-requirement-statuses. When the portfolio is created from a demand, all demand requirements are copied into the 'In Backlog' status in the portfolio.
Portfolio managers and project managers assigned to projects in the portfolio can create a project task from the requirement, see Creating-requirements-from-tasks, the requirement status is updated to 'In Project' automatically and related to the new task. 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 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 cancelled, the requirement comes back to "In Backlog" status and can create again 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 which is 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 a demand and grants write access to modify the requirement if the demand is in 'Draft' status. The permission is assigned to the demand submitter.
Demand Assignee	Access to the requirement related to a demand and 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 projects managers of the projects in the portfolio.
Portfolio Assignee	Access to the requirement and grants write access to modify the requirement. If the requirement is related to a portfolio, the permission is assigned to the portfolio manager of the portfolio. If the requirement is related to the demand, the permission is assigned to the portfolio manager of the portfolio under which the demand belongs.
Program Assignee	Access to the requirement and grants write access to modify the requirement. If the requirement is related to a program, the permission is assigned to the program manager for the program. If the requirement is related to the demand, the permission is assigned to the program manager of the program under which the demand belongs.