Overview
| Property | Value |
|---|---|
| Type ID | sysReq |
| Sort Order | 1 |
| Domain | Requirements (Requirements space) |
| Managed In | System Requirements Specification documents (SRS-SYS-001, SRS-SUB-001..006) |
| ISO Standard | ISO 14971, IEC 62304 |
Custom Fields
System requirement work items have no custom fields. They use only standard Polarion fields.Standard Fields
| Field | Type | Description |
|---|---|---|
title | String | Requirement statement |
description | Rich text | Detailed specification of the system requirement |
status | Enum (status) | Lifecycle state: Draft through Obsolete |
severity | Enum (severity) | General severity classification (exposed in RTM model for risk-based prioritization) |
priority | Enum (priority) | Priority level (Highest through Lowest) |
Link Roles
System requirements are at the center of the V-Model, connecting user needs to design requirements, risk controls, and verification:| Link Role | Direction | Connected Type | Purpose |
|---|---|---|---|
parent | Both | sysReq | Hierarchical nesting (same-type only) |
refines | Forward | userNeed | Traces back to the user need this requirement satisfies |
refines | Reverse (from desReq) | desReq | Design requirements that decompose this system requirement |
implements | Forward | riskControl | Risk controls implemented by this requirement |
verifies | Reverse (from testCase) | testCase | Test cases that verify this requirement |
RTM Domain Model
In the RTM domain model (rtm.yaml), SystemRequirement is a domain entity with type-scoped pick constraints:
| Property | Value |
|---|---|
| Polarion Type | sysReq |
| Exposed Properties | description, severity |
| Pick Constraint | Documents of type systemRequirementsSpecification |
| Relationships | SystemRequirement --[refines]--> UserNeed (many-to-many) |
PowerSheet Views
System requirements appear in multiple powersheet configurations:| Sheet | Role | Column Group |
|---|---|---|
| Whole RTM Config | Linked entity | System Reqs (purple) via refines from user needs |
| Component RTM | Root entity | System Reqs (purple) with upstream User Needs and downstream Design Reqs |
| System Verification Sheet | Root entity | System Reqs (purple) + Verification Tests (orange) + Verification Evidence (red) |
Document Organization
System requirements follow a consistent SYS/SUB pattern:| Document | Space | Document Type | Count |
|---|---|---|---|
| SRS-SYS-001 | Requirements | systemRequirementsSpecification | System-level requirements |
| SRS-SUB-001..006 | Requirements | systemRequirementsSpecification | Subsystem-level requirements |
Related Pages
- Work Item Types — Overview of all 16 work item types
- User Need (userNeed) — Stakeholder needs refined by system requirements
- Design Requirement (desReq) — Technical requirements decomposed from system requirements
- Risk Control (riskControl) — Risk controls implemented by requirements
- V-Model Traceability Chain — End-to-end traceability concept
- Link Roles and Traceability Relationships — Full link role reference