The subType enumeration classifies Design Requirements by engineering discipline. This classification enables filtered views in powersheet configurations and drives cascade mappings to FMEA occurrence ratings.
Enumeration Values
| ID | Display Name | Description | ISO Standard |
|---|
electrical | Electrical | Circuit design, power systems, and electrical safety requirements | IEC 60601-1 (Electrical safety) |
labeling | Labeling | Labels, markings, symbols, and Instructions for Use (IFU) | IEC 60601-1 Clause 7 |
mechanical | Mechanical | Physical structure, enclosures, and mechanical safety | IEC 60601-1 Clause 9 |
software | Software | Firmware, application software, and software safety | IEC 62304 |
usability | Useability | Human factors, user interface, and usability engineering | IEC 62366-1 |
The display name uses the British English variant “Useability” rather than the standard “Usability.” This is intentional in the configuration and does not affect functionality.
Configuration Details
| Property | Value |
|---|
| Field ID | subType |
| Used by | Design Requirement work item type |
| Source file | .polarion/tracker/fields/designRequirement-subType-enum.xml |
Cascade Mapping to FMEA Occurrence
The subType field participates in a cascade mapping defined in mappings.xml that filters valid FMEA occurrence values based on the design discipline. This mapping (subType_-__fmOccurrence) enables the risksheet to present contextually appropriate occurrence ratings when evaluating failure modes related to specific design disciplines.
| SubType | Cascades to fmOccurrence |
|---|
operation | Multiple occurrence levels |
software | Multiple occurrence levels |
design | Multiple occurrence levels |
use | Multiple occurrence levels |
system | Multiple occurrence levels |
process | Multiple occurrence levels |
The cascade mapping references sub-type values (operation, design, use, system, process) that differ from the values defined in this enumeration. These may reference a legacy or alternative enum configuration. The five values defined above (electrical, labeling, mechanical, software, usability) are the current active values.
Usage in the Solution
- DFMEA analysis — Design requirement sub-types inform the failure mode analysis by categorizing which engineering discipline a requirement belongs to. See DFMEA Risksheet Configuration.
- Filtered views — PowerSheet configurations can filter design requirements by sub-type to focus on a specific discipline (e.g., showing only software requirements).
- Traceability — Sub-type classification supports discipline-specific traceability from design requirements to verification test cases. See Link Roles.
