MARTE_ — The dependency between NFP and VSL is not necessary

Currently the domain view and the UML representation of NFP rely on VSL constructs which specialize UML ones (ValueSpecification, Datatype). This dependency is a limitation to the modularity of MARTE (e.g. one might be willing to use NFP with another expression language). Proposed resolution: 1) In the domain model, replace references to MARTE::VSL::ValueSpecification by UML::ValueSpecification (starting by page 35). 2) In the domain model, replace references to MARTE::VSL::TupleType by UML::DataType (starting by page 38) 3) In the UML representation, remove the generalization link between TupleType and NFPType (starting by page 38) 4) In the chapter overview, remove the dependency link between NFP and VSL

The dependency of Domain Models on the VSL Domain Model does not affect
the modularity of MARTE. On contrast, having a cohesive integration of Value
Specification concepts from VSL with the other chapters is a must regarding the
comprehensibility of MARTE. The only design constraint in MARTE was to do
VSL independent of other MARTE specific chapter, because we had in mind to
use VSL together with other profiles (e.g., SysML). This level of dependency has
been achieved as VSL doesn’t import other MARTE packages.
Note that there are many MARTE chapters that reuse VSL concepts:
CoreElements, Time, RSM, and having also NFP importing VSL is not a real
problem.
For these reasons, we propose to close this issue without change.
Disposition: Closed No Change