Skip to main content
Source file: rtm.yaml

​
Entity Types

The model defines five entity types, each mapped to a Polarion work item type (or document type):
EntityPolarion TypeNavigable PropertiesPurpose
Document(default module type)type, subsystemContainer for TARA analysis modules
Chapterheading(none)Structural headings — excluded from analysis
SystemElementsystemElementoutlineNumber, descriptionSystem/subsystem/component being analyzed
RequirementsysReqdescription, classificationCybersecurity and system requirements
TestCasetestCase(none)Verification evidence leaf node

​
Entity Details

​
Document

The root entity in the RTM model. Represents a container document (e.g., a TARA Risk Specification module). 
- name: Document
  properties:
    - type
    - subsystem
  • type — Classifies the document kind (e.g., riskSpecification). Used to filter TARA documents from other document types.
  • subsystem — Scopes analysis to a specific system component. References a systemElement work item ID.
Document has no polarionType mapping in this model. It maps to the default Polarion document/module type. The RTM engine treats it as the implicit root of any expansion path.

​
Chapter

Structural heading entity used to organize modules into sections. 
- name: Chapter
  polarionType: heading
  properties: []
Chapters are excluded from coverage calculations and Risksheet/PowerSheet analysis rows. They are purely structural elements.

​
SystemElement

Represents a system component being analyzed in the TARA (e.g., an ECU, software component, or hardware module). 
- name: SystemElement
  polarionType: systemElement
  properties:
    - outlineNumber
    - description
  • outlineNumber — Provides hierarchical position in the document (e.g., “1.2.3”)
  • description — Provides context for display in PowerSheet columns
SystemElement anchors the TARA scope. Each element represents a component within the system boundary being analyzed for cybersecurity threats. See System Element (systemElement) for the full work item type reference.

​
Requirement

Represents a system requirement, mapped to the sysReq Polarion work item type. 
- name: Requirement
  polarionType: sysReq
  properties:
    - description
    - classification
  • description — Requirement text
  • classification — Categorizes requirements (e.g., cybersecurity, functional). Used by the Cybersecurity Case Dashboard to filter cybersecurity-specific requirements.

​
TestCase

Verification leaf node in the traceability chain. 
- name: TestCase
  polarionType: testCase
  properties: []
TestCase has no navigable properties in the RTM model. Its primary role is as a link target — coverage dashboards compute the ratio of Requirements linked to at least one TestCase via the verifies link role.

​
Relationships

relationships: []
The RTM model defines no explicit relationships between entity types. This is architecturally significant:
  • Link traversal paths for PowerSheet expansion are derived from Polarion link role definitions directly (see Link Roles)
  • Sheet configurations must define their own expansion paths using Polarion link role IDs
  • This differs from more complete RTM models that define named relationships like “refines”, “verifies”, “assesses”
                        RTM Model (rtm.yaml)
                        Declares entity types + properties
                              |
                              v
+------------------+    +------------------+    +------------------+
| Document         |    | SystemElement    |    | Requirement      |
| (type, subsystem)|    | (outlineNumber,  |    | (description,    |
|                  |    |  description)    |    |  classification) |
+------------------+    +------------------+    +------------------+
                              |
                              v
                        +------------------+
                        | TestCase         |
                        | (no properties)  |
                        +------------------+

Relationships defined by Polarion link roles, NOT by this model:
  taraRecord --hasCybersecurityGoal--> cybersecurityGoal
  sysReq --derivesRequirement--> cybersecurityGoal
  riskControl --mitigates--> taraRecord
  testCase --verifies--> sysReq

​
TARA-Specific Types Not in RTM

The following work item types are used extensively in the TARA solution but are not declared in the RTM model:
TypePurposeConfiguration Source
taraRecordCore TARA analysis recordCustom fields, Risksheet
cybersecurityGoalCybersecurity objectives with CALCustom fields
threatScenarioReusable threat catalog entriesRisksheet item links
stakeholderImpact scope entitiesRisksheet item links
riskControlConcrete countermeasuresCustom fields, link roles
These types are implemented through native Polarion configuration (types, link roles, custom fields, enums) and referenced directly in Risksheet configurations without RTM model abstraction.
Source: .polarion/nextedy/models/rtm.yaml