This diagram illustrates the Requirements Management domain model. This includes key objects that comprise the requirements management domain, and elaborates on the relationships between those objects.
The following diagram illustrates different types of requirements.
A requirement defines the specific use case and attributes of a new feature.
The domain model defines the following characteristics for requirements:
Any number of requirements may be aggregated into collections.
A requirement can be related to other requirements.
Requirements may be related to any number of test requirements, from the test management system.
Requirements may be related to any number of development change requests, from the development management system.
There may be many types of requirements. Out of the box, a requirement can be classified as a business requirement, a system requirement, a design requirement, or a test requirement.
A collection is a gathering of any number requirements that are all related in some way. A collection may also be aggregated into a document for publishing. A collection may also include requirements that are in a baseline.
A document is a representation of a collection of requirements, with additional structure, formatting, and wording, that may be published out to Microsoft Word format.