Executable UML: Difference between revisions

Revision as of 07:38, 5 May 2020

Revision as of 18:07, 4 November 2020

Line 55:

The class and state models by themselves can only provide a static view of the ___domain. In order to have an executable model, there must be a way to create class instances, establish associations, perform operations on attributes, call state events, etc. In Executable UML, this is done using an action language that conforms to the UML Action Semantics.

Action Semantics was added to the UML specification in 2001. The Action Semantics RFP was based on previous work in action languages supporting the [[Shlaer–Mellor method]]. Existing action languages are Object Action Language (OAL), Shlaer–Mellor Action Language (SMALL), Action Specification Language (ASL), Modified Action Specification Language (MASL),<ref name="MASL Source">{{cite web |title=MASL is a Shlaer-Mellor dialect action language and structural modeling language.: xtuml/masl |url=https://github.com/xtuml/masl |publisher=xtUML |accessdate=26 October 2019 |date=27 December 2018}}</ref>, That Action Language (TALL), Starr's Concise Relational Action Language (SCRALL), Platform-independent Action Language (PAL) and PathMATE Action Language (PAL). SCRALL is the only one that is a graphical action language.

===Model testing and execution===