Objectives and Requirements
To assure that evolutions of your organization meet strategic expectations of the enterprise, the main HOPEX concepts can be connected to requirements.
A requirement is a need or expectation explicitly expressed, imposed as a constraint to be met within the context of a project. This project can be a certification project or an organizational project or an information system project.The first task is to inventory objectives involved and requirements imposed, and to connect these to the main organizational and technical components.
An objective is a goal that a company or organization wants to achieve, or is the target set by a process or an operation. An objective allows you to highlight the features in a process or operation that require improvement.Accessing objectives and requirements
To access the objectives tree:
In the Environment desktop, select Regulatory Environment > Objectives.The hierarchy of organization objectives is displayed.
If you expand the folder of an objective, you can display the sub-objectives owned by the current objective.
The list of objectives owned by an objective is accessible in the properties page of the objective, in the Characteristics tab, section-Sub-Objectives.To access the requirements tree:
In the Environment desktop, select Regulatory Environment > Requirements.The hierarchy of organization requirements is displayed.
If you expand the folder of a requirement, you can display the sub-requirements owned by the current requirement.
The list of requirements owned by a requirement is accessible in the properties page of the requirement, in the Characteristics tab, section Sub-Requirements.Objective Characteristics
An objective can be quantitative (directly measurable), or it can be qualitative.
• Reduce order delivery time (quantitative objective)
• Improve product quality (qualitative objective)
• Improve customer satisfaction (qualitative objective)
You can associate an objective with different component types.
Requirement Characteristics
To access characteristics of a requirement:
2. In the page listing requirements, select that which interests you and click Properties.
You can consult or modify the characteristics of the requirement:
According to the 9000 standard, "a requirement is a stated need or expectation, normally implicit, or imposed". Standard ISO 9000 highlights "client expectations" but in the context of a project, other requirements should be considered.Priority can be:
• Low
• Medium
• High
Requirement scope
You can associate a requirement with different object types.
The Object types that can be connected depend on the solution used.To access the objects of a requirement scope:
In the requirement properties dialog box, select the Scope tab.Business and organizational processes, entities and applications appear in the Scope tab in two different sections depending on the role played:
• Constrained Elements: objects that must meet the requirement
The "Segregation of duties" requirement must be met by the "Call for bids management" process.
• Contributing Elements: objects that help meet the requirement.
The "Call for bids" application can automate a control to check the process meets the requirement.
• Incidents: incidents that occurred and for which the requirement has not been met.
• Sub-requirements
Sub-requirements are not used in HOPEX IT Risk Management.Risks and controls
To access risks and controls associated with the requirement:
In the properties of the requirement, expand the Risks and Controls section.