The last requirement of a hierarchy of requirements, or a root requirement without child requirements
See also requirement, composite requirement, root requirement
A written statement specifying what a model must contain or how it must be structured to support business needs. In the case of a requirements model, a business rule acts as a super requirement (a requirement on requirements). It sets a methodology for requirements
Note: Business rules are not active by default, you activate them from an extended model definition attached to the model
A requirement made of other requirements
See also requirement, atomic requirement, root requirement
An object from a design model in PowerDesigner (CDM, PDM, OOM, BPM, XSM, FEM, ILM). The Requirements Model (RQM) allows you to attach design objects to requirements, to import design objects as requirements, or to export requirements as design objects
The Requirement Export Wizard guides you through the creation of design objects from requirements
A term used in a requirements model. You can attach it to requirements via the Related Glossary Terms page of their property sheet. By doing this, you define a common vocabulary for requirements
A group of users to which requirements are allocated. A group can contain other groups
The Requirement Import Wizard guides you through the creation of requirements from design objects selected in a design model open in the workspace
Level of priority attached to a requirement. Values are limited to one decimal, cannot be null or negative
A requirement is a precise description of an action that must be implemented during a development process. Requirements are listed and organized in requirements models, and can be associated with objects in design models (CDM, PDM, OOM, BPM, FEM, XSM, ILM).
See also atomic requirement, composite requirement, root requirement
The requirements document view is a grid in which you create a hierarchy of requirements in rich edit text. Rows, corresponding to requirements, can be moved and resized. Columns, corresponding to requirements attributes, are editable.
Note: The requirements document view is the equivalent of a diagram in design models
Level of risk should a requirement not be satisfied (The list of values is customizable)
The first or only requirement in a hierarchy of requirements. In the Browser tree view, it is directly linked to the model item. In a requirements document view, it has a first level title ID
See also requirement, atomic requirement, composite requirement
Validation level for a requirement (The list of values is customizable)
Sub-classification used to extend the semantics of an object without changing its structure. It can be predefined or user-defined
A link between a requirement and a design object, an external file or another requirement from a different hierarchy
A traceability matrix view is a grid which displays the links between requirements and design objects, external files or other requirements from different hierarchies
The type of requirement from the process point of view (The list of values is customizable)
A user is a person concerned by one or several requirements. You can assign users to requirements (See User Allocations page in requirements property sheet) and check all the requirements assigned to users (See Dependencies page in users property sheet)
A user allocation matrix view is a grid which displays the links between requirements (in rows) and users or groups (in columns) who must meet these requirements during a development process
Test level for a requirement (The list of values is customizable)
| Copyright (C) 2005. Sybase Inc. All rights reserved. | ||