Defining Requirements
Different sections are available in the properties of a requirement.
To access requirements, see Accessing Requirements.Code
The code enables unique identification of the requirement.
Parent requirement
This is the requirement to which this requirement is attached.
Regulation framework
A regulation or policy is a set of directives, compulsory or not, defined by a government in a law, by standard bodies as "best practices" or as an internal policy in an organization.
For more details on regulations, see Managing Regulation Frameworks.Priority
Priority can be:
• Low
• Medium
• High
Analysis
• Risk factors
A risk factor is an element which contributes to the occurrence of a risk or which triggers a risk. Several Risks can originate from a same Risk Factor Examples: the use of a hazardous chemical product, the complexity of an application, the size of a project, the number of involved parties, the use of a new technology, the lack of quality assurance, the lack of rigor in requirements definition…• Event type Basel (level 1)
• Event type Basel (level 2)
Responsibilities
HOPEX IRM enables definition of responsibilities of each participant related to a requirement via the RACI matrix.
For more details, see RACI Responsibilities.Scope
The Scope section of requirement properties enables connection of requirements to other objects:
• Business
processes
processes
A business process represents a system that offers products or services to an internal or external client of the company or organization. At the higher levels, a business process represents a structure and a categorization of the business. It can be broken down into other processes. The link with organizational processes will describe the real implementation of the business process in the organization. A business process can also be detailed by a functional view.• Organizational processes
An organizational process describes how to implement all or part of the process required to make a product or handle a flow.• Entities
An entity can be internal or external to the enterprise: an entity represents an organizational element of enterprise structure such as a management, department, or job function. It is defined at a level depending on the degree of detail to be provided on the organization (see org-unit type). Example: financial management, sales management, marketing department, account manager. An external entity represents an organization that exchanges flows with the enterprise, Example: customer, supplier, government office.• Risks
A risk is a hazard of greater or lesser probability to which an organization is exposed.• Risk types
A risk type defines a risk typology standardized within the context of an organization.• Applications
An application is a set of software tools coherent from a software development viewpoint.Sub-requirements
In the properties of a requirement, the Sub-requirements section enables you to define second-level requirements (or sub-requirements).
Milestones and Statuses
In the properties of a requirement, the Milestones and Status page enables to specify:
• Expiration Date-Term of Adjustment: this is the date limit by which the requirement must be fulfilled.
• Creation date: date on which the requirement was created.
• Last Update: this is the date on which the last import was made.
• Official status (from import)
• To be validated
• Validated
• Updated
• Deleted
Regulations and requirements are never deleted automatically. If a regulation/requirement is obsolete, status passes to "Deleted".• Internal status
You can indicate if the requirement:
• is To be assessed
• has already been Assessed
• N/A