Requirements Views

A requirements model contains a set of requirements and other objects, which can be displayed and manipulated in any number of requirements views.

You can create the following kinds of objects in an RQM:

Object	Description
Requirement	A feature that must be provided by the development process, which should be defined as precisely as possible, and can be assigned to a user or group for implementation (see Requirements (RQM)).
User	A person that is involved in the implementation of one or more requirements (see Users and Groups (RQM)).
Group	A group of users that is involved in the implementation of one or more requirements (see Users and Groups (RQM)).
Glossary term	[deprecated] A word used in a requirements model, which should be defined as precisely as possible to avoid misunderstandings and to set a common vocabulary (see Glossary Terms (RQM - Deprecated)).
Business rule	Written statements describing rules that your business must follow (see Business Rules (RQM)).

You can create requirement views to organize your requirements and other objects from the Browser or the toolbar:

In the requirements view toolbar, select one of the following tools:

Tool	Description
	Create a Requirements Document View - To list requirements in a hierarchy (see Requirements Document Views).
	Create a Traceability Matrix View - To display the links between requirements and design objects (from other types of models), external files or other requirements (see Traceability Matrix Views).
	Create a User Allocation Matrix View - To display the links between requirements and the users and groups who will fulfill them (see User Allocation Matrix Views).

Right-click the model in the Browser and select New > [Type] View.

You can navigate between requirements views in the Browser or by selecting View > Diagram > Select View to open the Select View dialog box, and double-clicking the view to open.

Requirements Document Views
A requirements document view displays a list of written requirements in a hierarchic grid. Multiple views can be created with different filters to display various subsets of requirements.
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. Requirements can have a priority, status, workload, and other properties assigned to them, and can contain sub-requirements.
Packages (RQM)
You can divide your requirements model into packages in order to avoid manipulating the entire set of requirements and to provide views on particular logical subsets of the requirements. You could create packages to represent different tasks, domains, or subject areas.
Users and Groups (RQM)
Users are all the people concerned by at least one requirement defined in a requirements model. Groups are teams of users (e.g. a QA team) concerned by at least one requirement defined in a requirements model.
Glossary Terms (RQM - Deprecated)
Glossary terms are clearly defined words used to avoid misinterpretations in a requirements model. Use the Description sub-tab on the Notes tab of a glossary term property sheet, to give a full and precise description of a glossary term.
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.