Requirements
IRI: https://w3id.org/altium/cdm/requirements
Models requirements and their revisions, the specifications that group them, baselines approved for execution, change requests, the requirements projects that scope this work, and verification cases that provide evidence against requirements; most of its classes are experimental. It corresponds to requirements management and verification & validation in the Altium 365 Requirements Portal.
In the product
In the API
Requirements in the Altium 365 API reference: the queries, mutations and types of this bounded context.
Entities
| Name | Description |
|---|---|
| Requirements Project | The orchestration space for capturing, evolving, and validating requirements scoped to a product, program increment, or regulatory engagement. |
| Requirement | A single, testable statement of intent or constraint that governs a solution or process outcome. |
| Requirement Baseline | A version-managed release of a specification or subset of requirements approved for execution. In the product this corresponds to a released specification (Release Specification). It is not what the product calls a baseline: in the Requirements & Systems Portal (Legacy), a baseline is a named bookmark for a point in time (e.g. a design review) that is used to compare how requirements and values have changed. |
| Requirement Change Request | Structured workflow item proposing additions, updates, or removals of requirements. |
| Requirement Revision | An immutable snapshot of a requirement statement at a specific revision. |
| Requirement Specification | A curated collection of requirements scoped to a program, domain, or release horizon. |
| Verification Case | A planned verification procedure or test that produces objective evidence against requirements. |
Resources
| Name | Description |
|---|---|
| Requirement Artifact | TBD |