Skip to main content
diagram
This model reference is derived from source code configuration. Verify entity type names and property mappings against your project configuration.

Entity Types

Entity types are declared as a map under domainModelTypes, keyed by type name. Each entry specifies a polarionType mapping and its properties.
Entity TypePolarion TypePurpose
HazardhazardRisk items identified during hazard analysis
RiskControlriskControlMitigation measures applied to reduce risk
RiskAssessmentriskAssessmentEvaluated risk levels combining severity and probability

Property Configuration

Each entity type declares its properties as a map. Property names are used in queries, column bindings, and data display.
domainModelTypes:
  Hazard:
    polarionType: hazard
    properties:
      description:
      severity:
      probability:
      riskLevel:

  RiskControl:
    polarionType: riskControl
    properties:
      description:
      controlType:
      effectiveness:

  RiskAssessment:
    polarionType: riskAssessment
    properties:
      description:
      residualRisk:
      acceptability:
A property set to null (empty after the colon) inherits all default settings. The property name is used as the Polarion field name unless serverName or customFieldName is specified.

Relationships

Relationships define how entity types are connected. Each relationship specifies the Polarion linkRole and navigation property names using direct (forward) and back (reverse) notation.
relationships:
  - from: Hazard
    to: RiskControl
    linkRole: mitigates
    cardinality: one-to-many
    storage: linkedWorkItems
    direct:
      name: riskControls
    back:
      name: hazards

  - from: Hazard
    to: RiskAssessment
    linkRole: has_assessment
    cardinality: one-to-many
    storage: linkedWorkItems
    direct:
      name: riskAssessments
    back:
      name: hazard
PropertyDescription
from / toSource and target entity type names (must match domainModelTypes keys)
linkRolePolarion link role ID implementing this relationship
cardinalityMultiplicity: one-to-many, many-to-one, or many-to-many
storageMust be linkedWorkItems (Polarion native linking)
direct.nameNavigation property on the source entity for forward traversal
back.nameNavigation property on the target entity for reverse traversal

Complete YAML Example

domainModelTypes:
  Hazard:
    polarionType: hazard
    properties:
      description:
      severity:
      probability:
      riskLevel:

  RiskControl:
    polarionType: riskControl
    properties:
      description:
      controlType:
      effectiveness:

  RiskAssessment:
    polarionType: riskAssessment
    properties:
      description:
      residualRisk:
      acceptability:

relationships:
  - from: Hazard
    to: RiskControl
    linkRole: mitigates
    cardinality: one-to-many
    storage: linkedWorkItems
    direct:
      name: riskControls
    back:
      name: hazards

  - from: Hazard
    to: RiskAssessment
    linkRole: has_assessment
    cardinality: one-to-many
    storage: linkedWorkItems
    direct:
      name: riskAssessments
    back:
      name: hazard
Polarion custom field IDs typically use the c_ prefix (e.g., c_probability). Use the customFieldName property when the Powersheet property name differs from the Polarion field ID.

See Also