Risk Management Model - Nextedy Documentation

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 Type	Polarion Type	Purpose
`Hazard`	`hazard`	Risk items identified during hazard analysis
`RiskControl`	`riskControl`	Mitigation measures applied to reduce risk
`RiskAssessment`	`riskAssessment`	Evaluated 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

Property	Description
`from` / `to`	Source and target entity type names (must match `domainModelTypes` keys)
`linkRole`	Polarion link role ID implementing this relationship
`cardinality`	Multiplicity: `one-to-many`, `many-to-one`, or `many-to-many`
`storage`	Must be `linkedWorkItems` (Polarion native linking)
`direct.name`	Navigation property on the source entity for forward traversal
`back.name`	Navigation 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 Nextedy POWERSHEET property name differs from the Polarion field ID.

​Entity Types

​Property Configuration

​Relationships

​Complete YAML Example

​See Also

Entity Types

Property Configuration

Relationships

Complete YAML Example

See Also