-
Key: MARTE11-110
-
Legacy Issue Number: 14901
-
Status: closed
-
Source: THALES ( Sebastien Demathieu)
-
Summary:
The concept of System in Annex A.2 maps to a concept not defined in the MARTE specification (a SysML concept). However the MARTE profile does not import the SysML profile.
-
Reported: MARTE 1.0 — Thu, 31 Dec 2009 05:00 GMT
-
Disposition: Resolved — MARTE 1.1
-
Disposition Summary:
An AADL system represents an assembly of interacting application software,
execution platform, and system components.
The chosen mapping shall not only be semantically correct, but shall also have
an intuitive name.
MARTE doesn’t address such a generic aspect, and it would not make sense to
add such a concept to MARTE.
UML generic concept “StructuredClasses class” could be use, but this concept
has already been used to represent AADL data. As mappings have always to be
bijectiv, another representation has to be found.
UML “subsystem” concept could be used to represent an “AADL system”, this
mapping is semantically correct, but the name is confusing.
The best solution is to use the SysML “block” concept: the mapping is
semantically correct and the name is sufficiently different to avoid confusion.
This solution needs to import the SysML profile. A prerequisite will be added in
the introduction précising that the SysML profile needs to be importing when
using MARTE to design AADL applications in order to fully address the MARTE
to AADL mapping. -
Updated: Sun, 8 Mar 2015 17:59 GMT
MARTE11 — The concept of System in Annex A.2 maps to a SysML concept
- Key: MARTE11-110
- OMG Task Force: MARTE 1.1 RTF