Building a Requirements Model

A requirements model represents a detailed and structured list of actions that must be implemented during a development process. A diagram, showing a structure of interconnected symbols, is not the best way to represent a numbered list of requirements. Document, traceability or user allocation views are grids that enumerate a list of requirements with respectively a set of attributes, traceability links or user allocations.

There are three types of views in a requirements model:

Requirements document views – list requirements in a hierarchy
Traceability matrix views - display the links between requirements and design objects (objects from other types of models), external files or other requirements
User allocation matrix views – display the links between requirements and the users and groups who will fulfill them

A requirements model can have as many views as necessary. You can differentiate views by selecting requirements, customizing columns, changing the traceability matrix type.

Creating a Requirement View
You can create a requirement view in an existing RQM in any of the following ways:
Navigating Between Requirement Views
You can navigate between requirement views in a simplified hierarchy via the View menu.
RQM Objects
You can create the following objects in an RQM:
Requirements Views Properties
You can display a requirements view property sheet using one of the following methods:
Requirements Document Views
A requirements document view displays a list of written requirements in a hierarchic grid.
Traceability Matrix Views
A traceability matrix view displays the links between requirements and objects from other types of models, external files or other requirements.
User Allocation Matrix Views
A user allocation matrix view displays the links between requirements and the users and groups who will fulfill them.
Requirements (RQM)
A requirement is a clear and precise description of an action that must be implemented during a development process.
Users and Groups (RQM)
Users are all the people concerned by at least one requirement defined in a requirements model.
Glossary Terms (RQM)
Glossary terms are clearly defined words used to avoid misinterpretations in a requirements model. Use the Description tab, in the Notes tab of a glossary term property sheet, to give a full and precise description of a glossary term.
Design Objects (RQM)
Design objects are objects defined in other types of PowerDesigner models:
Business Rules (RQM)
A business rule is a rule that your business follows. It is a written statement specifying what an information system must do or how it must be structured. It could be a government-imposed law, a customer requirement, or an internal guideline.