Use a Controlled Vocabulary

[odungern]

Among the concepts offered by UML/SysML we will select those deemed relevant for overarching system modeling. Different modeling languages use their own terminology - but share many concepts. The final goal is to put system information from difference sources into a common context.

A common terminology is essential in all those cases.

[odungern]

Two ways to add meaning to weakly defined model-elements are proposed, see example:

• by stereotype: In the example given, two classes have a stereotype of an imported profile 'RFLP' defining four levels of system specification, namely Requirement, Function, Logical and Physical. In the example it is just used as an additional information/definition as a value of property typed dcterms:type.
• by generalization: Both concrete model elements (in fact 'instances') specialize a class named with an ontology term. As a consequence they are not an instance of uml:Class, but of IREB:Requirement resp. FMC:Actor.