Requirement Projects
Requirement projects in TESTMETRIX® are used to logically subdivide requirements into different areas or test levels.
They allow requirements to be structured independently of one another and managed clearly.
Typical examples are:
- Integration requirements
- System requirements
- Safety requirements
- Functional requirements
A requirement project always belongs to a verification project and can be linked to an associated test case project.
Purpose of Requirement Projects
In real development projects, there are often different types of requirements originating from different teams, test levels, or system areas.
Without a clear separation, requirements would quickly become confusing and difficult to trace.
Requirement projects therefore enable:
- the separation of different requirement areas
- a clear assignment to test levels
- better traceability
- accurate tracking of requirement coverage
This makes it visible:
- which requirements have already been tested
- which requirements are still open
- which test cases cover which requirements
High-Level and Low-Level Requirements
TESTMETRIX® distinguishes between:
- High-Level Requirements
- Low-Level Requirements
High-Level Requirements
High-level requirements describe overarching functions or system objectives.
Examples:
- Bluetooth Communication
- OTA Update Functionality
- Data Encryption
Low-Level Requirements
Low-level requirements describe concrete technical requirements or behaviors of a system. They are measurable, quantifiable, and therefore testable.
Examples:
- The device must establish a Bluetooth connection within 30 seconds
- OTA updates must be CRC-validated
Only Low-Level Requirements are used for calculating requirement coverage.
References and Traceability
References can be stored for each requirement, for example:
- Documents
- Specifications
- Interviews
- Tickets
- External standards
This ensures traceability of where a requirement originated.
Requirement Status
Requirements have a status. The following values are supported:
| Status | Meaning |
|---|---|
| Draft | Requirement is still being elaborated |
| In Review | Requirement is being reviewed |
| Approved | Requirement has been approved |
This allows requirements to be progressively elaborated and approved.
Requirement Coverage
TESTMETRIX® automatically calculates requirement coverage based on the linked test case executions.
A low-level requirement is considered covered as soon as at least one associated test case execution has been performed.
Example
| Requirement Project | Integration Requirements |
| High-Level Requirement | 001 – Bluetooth Connection |
| Associated Low-Level Requirements | 001-001, 001-002 |
| Covered by Test Cases | 013, 014 |
Creation
Requirement projects are typically created manually via the user interface.
Since they reflect your system's structure, you'll rarely need to create or update them.