Skip to main content

​
Purpose

System elements define the scope of the TARA analysis. Each TARA module (risksheet document) is linked to a specific system element via the systemElementId document custom field. The system element hierarchy drives the structure of the entire TARA project: one TARA module per system element that requires threat analysis.

​
Work Item Identity

PropertyValue
Type IDsystemElement
LabelSystem Element
Icontestrun_status_open1.png
Tracker PrefixTR
Form LayoutsystemElement-form-layout.xml

​
Custom Fields

Field IDNameTypeDescription
elementTypeElement Typeenum:systemElementTypeClassifies the element’s position in the system decomposition hierarchy (System, Subsystem, Assembly, Subassembly, or Component).

​
Element Type Enum Values

The systemElementType enumeration defines a 5-level decomposition hierarchy:
Enum IDLabelSort OrderDescription
systemSystem0Top-level system under analysis. The root of the decomposition tree.
subsystemSubsystem1Major functional subdivision of the system.
assemblyAssembly2Physical or logical grouping of components within a subsystem.
subassemblySubassembly3Subdivision of an assembly (e.g., a PCB within a control unit).
componentComponent4Individual hardware or software component. Leaf node of the hierarchy.

​
Example Hierarchy

SYSTEM: ADAS Control System (TR-20524)
+-- SUBSYSTEM: Perception Unit (TR-20525)
|   +-- COMPONENT: Sensor Fusion ECU (TR-20527)
|   +-- COMPONENT: Forward Camera Module (TR-21827)
|   +-- COMPONENT: Front Radar Module (TR-21828)
+-- SUBSYSTEM: Connectivity Gateway (TR-20526)
    +-- COMPONENT: V2X Transceiver (TR-20528)
    +-- COMPONENT: Telematics Control Unit (TCU) (TR-21829)

​
Status Lifecycle

The systemElement-status enumeration extends the general status with an inProgress state:
Enum IDLabelColorSort OrderDescription
draftDraft#3366FF1Initial state for newly created elements.
inProgressIn Progress—2Active work on the element definition.
inReviewIn Review#FFFF994Submitted for peer or stakeholder review.
pendingApprovalPending Approval#FFFF335Review complete, awaiting formal sign-off.
approvedApproved#66FF666Formally approved. Stable for TARA analysis.
rejectedRejected#FF33007Rejected during review. Requires rework.
obsoleteObsolete—8No longer active. Retained for traceability.
Role IDForward LabelTarget TypeDescription
parenthas parentsystemElementHierarchical parent-child relationship (sameType=true). Used to build the system decomposition tree.
Role IDReverse LabelSource TypeDescription
parentis parent ofsystemElementChild elements in the decomposition tree.
allocatedTohas Allocatedfunction, processStepFunctions or process steps allocated to this element.

​
Document Binding

Each TARA module links to a system element through the document-level custom field:
Document FieldTypeDescription
systemElementIdstringThe work item ID of the system element this TARA module analyzes. Set on the riskSpecification document. Displayed in the Risksheet top panel as a breadcrumb.
If systemElementId is not set, the Risksheet top panel displays a warning: “Configuration Required: The System Element custom field is not set.”

​
Additional Document Fields

System elements carry additional context through document-level fields on the linked TARA module:
Document FieldTypeDescription
redAssetsstringIdentifies RED (critical) assets associated with the system element. Part of Item Definition per ISO/SAE 21434 Clause 9.
cybersecurityContexttext/plainDescribes the cybersecurity context for the system element being analyzed.
assumptionstext/plainDocuments assumptions made during the TARA analysis.

​
Storage Location

System elements are stored in the _default/SYSTEM-ELEMENTS module as a flat document with heading items organizing the hierarchy. The parent-child structure is established through Polarion parent link roles, not document nesting.

​
Lucene Queries

type:systemElement
type:systemElement AND elementType:system
type:systemElement AND elementType:component
type:systemElement AND status:approved
type:systemElement AND NOT status:obsolete