-
Key: RAAML-32
-
Status: closed
-
Source: MITRE ( Mr. Robert Martin)
-
Summary:
While a UML profile can provide a mechanism for establishing the primitives and components for capturing the safety and reliability aspects of a system within a MBSE tool, the real goal would appear to be the exchange of MBSE models that include safety and reliability aspects. A metamodel would seem to be a more appropriate mechanism for capturing/conveying the details of what is to be exchanged. Any UML profile necessary could be derived from that metamodel when needed. How does RAAML support the exchange of safety and reliability aspects of a system?
-
Reported: RAAML 1.0b1 — Thu, 29 Apr 2021 21:38 GMT
-
Disposition: Closed; No Change — RAAML 1.0
-
Disposition Summary:
UML XMI used as an exchange format
RAAML WG took a lightweight approach to base RAAML on UML+profiles+libraries to promote exchange of S&R information between tools. This approach has two advantages over having separate metamodel approach. First, any UML-compliant tool (including SysML tools) can load and store these models. A separate metamodel would necessitate a special tool that would need to know how to load and store these models. Second advantage is that connectivity between safety and reliability information and the systems model is easy to achieve for tool vendors that already support UML.
-
Updated: Thu, 31 Mar 2022 19:32 GMT
RAAML — Tool to Tool exchange of safety and reliability aspects of a system
- Key: RAAML-32
- OMG Task Force: Risk Analysis and Assessment Modeling Language (RAAML) 1.0 FTF