Building a Requirements Model

A requirements model contains a set of requirements, which can be displayed and manipulated in any number of requirements views. You can differentiate views by selecting requirements, customizing columns, or changing the traceability matrix type.

There are three types of views in a requirements model:

• Creating a Requirement View
  You can create a requirement view in an existing RQM from the Browser or the toolbar.
• RQM Objects
  PowerDesigner lets you create requirements and other related objects to build your RQM.
• 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. Groups are teams of users (e.g. a QA team) 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 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.