-
Key: RAAML-55
-
Status: closed
-
Source: Object Management Group ( Mr. Juergen Boldt)
-
Summary:
In figure 10.12 there is a note against ‘solution’ that states a solution could also be some artefact of the system. The GSN standard is clear that a solution presents a reference to evidence. It is not understood how this can be an artefact of the system. Similarly a statement in the note attached to ‘contexturalStatement’ states that context can be either context statement or some artifact of the system; this distorts the definition in the GSN standard which states that the <context statement> can be either an a reference to contextual information, or a statement. This implies that there is not a direct relationship between the modelling in RAAML and the GSN standard.
-
Reported: RAAML 1.0b1 — Tue, 11 May 2021 18:32 GMT
-
Disposition: Resolved — RAAML 1.0
-
Disposition Summary:
*Remove note from figure 10.12 solution *
We should remove the ability to directly substitute a GSN solution with a SysML element because the result is not a valid GSN model. However, what we should allow is for GSN solution to be able to reference a SysML element. We need to decide whether that is by a tag reference property, or by a «trace» relationship, or a dedicated relationship.
-
Updated: Thu, 31 Mar 2022 19:32 GMT
-
Attachments:
- 10.12.png 43 kB (image/png)
RAAML — Inappropriate notes in figure
- Key: RAAML-55
- OMG Task Force: Risk Analysis and Assessment Modeling Language (RAAML) 1.0 FTF