${taskforce.name} Avatar
  1. OMG Task Force

Risk Analysis and Assessment Modeling Language (RAAML) 1.2 RTF — Open Issues

Create Issue
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
RAAML12-22 Add stereotype for Vulnerability RAAML 1.1 open
RAAML12-23 Add stereotype for Weakness RAAML 1.1 open
RAAML12-18 Add ProcessModel and ControlAlgorithm stereotypes to STPA Profile RAAML 1.1 open
RAAML12-17 Threat should also be a subtype of Limitation-Factor RAAML 1.1 open
RAAML12-16 Threat is not stereotyped as Threat, and must be stereotyped for consistency RAAML 1.1 open

Issues Descriptions

Add stereotype for Vulnerability

  • Key: RAAML12-22
  • Status: open  
  • Source: Ford Motor Company ( Mr. Kyle Post)
  • Summary:

    The Vulnerability element is stereotyped by a generic <<Situation>> stereotype and there is no dedicated <<Vulnerability>> stereotype. To resolve this add a stereotype for Vulnerability. This change should help ensure consistency with Factors and Limitations in the STPA Loss Scenario
  • Reported: RAAML 1.1 — Mon, 13 Apr 2026 12:51 GMT
  • Updated: Mon, 13 Apr 2026 13:03 GMT

Add stereotype for Weakness

  • Key: RAAML12-23
  • Status: open  
  • Source: Ford Motor Company ( Mr. Kyle Post)
  • Summary:

    The Weakness element is stereotyped by a generic <<Situation>> stereotype and there is no dedicated <<Weakness>> stereotype. To resolve this, the ticket calls for adding a stereotype for Weakness. This change should help ensure consistency with Factors and Limitations in the STPA Loss Scenario.
  • Reported: RAAML 1.1 — Mon, 13 Apr 2026 12:58 GMT
  • Updated: Mon, 13 Apr 2026 13:02 GMT

Add ProcessModel and ControlAlgorithm stereotypes to STPA Profile

  • Key: RAAML12-18
  • Status: open   Implementation work Blocked
  • Source: MITRE ( Ms. Mary Tolbert)
  • Summary:

    The issue is that ProcessModel and ControlAlgorithm are not currently stereotypes in the STPA profile, but is required to accurately model a STPA Control Structure.
  • Reported: RAAML 1.1 — Tue, 24 Mar 2026 15:52 GMT
  • Updated: Wed, 8 Apr 2026 15:36 GMT

Threat should also be a subtype of Limitation-Factor

  • Key: RAAML12-17
  • Status: open   Implementation work Blocked
  • Source: MITRE ( Ms. Mary Tolbert)
  • Summary:

    The issue is that Threat is not currently considered as a Limitation-Factor, which is necessary in creating STPA Loss Scenarios. To resolve this, the ticket calls for making Threat a subtype of Limitation.
  • Reported: RAAML 1.1 — Tue, 24 Mar 2026 14:02 GMT
  • Updated: Wed, 8 Apr 2026 15:35 GMT

Threat is not stereotyped as Threat, and must be stereotyped for consistency

  • Key: RAAML12-16
  • Status: open   Implementation work Blocked
  • Source: MITRE ( Ms. Mary Tolbert)
  • Summary:

    The issue is that Threat is not currently stereotyped as Threat, which puts it out of alignment with the other RAAML profile elements. To resolve this, the ticket calls for stereotyping it as Threat.
  • Reported: RAAML 1.1 — Tue, 24 Mar 2026 13:58 GMT
  • Updated: Wed, 8 Apr 2026 15:35 GMT