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 attributes
A Rational® RequisitePro® requirement attribute is a descriptive property associated with a requirement.Requirement types
A Rational® RequisitePro® 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.Requirements documents
You can use Rational® RequisitePro® requirements documents to develop textual elaborations of your elements and your use-case descriptions, flows of events, special requirements, and conditions.Requirements projects
A Rational® RequisitePro® project is used to manage all information and artifacts related to a requirements management project.Requirement traceability
Requirement traceability is a relationship between two requirements that implies the source, derivation, or dependencies between the artifacts.Direct associations
A direct association links a model element and a requirement. This link associates the model element and requirement and synchronizes both artifacts so you can manage them as a single, conceptual item.Indirect associations
An indirect association links model elements and requirements through proxy requirements and traceability. Indirect associations are particularly powerful for creating many-to-many relationships with traceability between multiple requirements and a single proxy or between multiple proxies and a single requirement.