This section provides an explanation of key requirement concepts
and information for working with requirement artifacts.
Requirements A requirement describes
a condition or capability to which a system must conform; it is either derived
directly from user needs or stated in a contract, standard, specification,
or other formally imposed document.
Requirement projects A Rational RequisitePro project is
used to manage all information and artifacts related to a requirements management
project.
Requirement association workflows These
workflows describe typical scenarios for using the integration of Rational RequisitePro and
the Rational Software Delivery
Platform products.
Requirement attributes A requirement
attribute is a descriptive property associated with a requirement.
Requirement types A requirement
type is a category of requirements and its associated set of descriptive
and operational characteristics. Examples of requirement types include features,
use cases, supplementary requirements, and glossary terms.
Requirement documents You
can use requirement documents to develop textual elaborations
of requirements related to domain elements, use cases, flows of events, special
requirements, and other conditions.
Requirement traceability Requirement
traceability is a relationship between two requirements that implies
the source, derivation, or dependencies between the artifacts.