An ASM Semantics for UML Activity Diagrams

Börger, Egon; Cavarra, Alessandra; Riccobene, Elvinia

doi:10.1007/3-540-45499-3_22

Cited by 65 publications

(50 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The ASM ground model and refinement concepts replace the loose character of human-centric UML models and of the links the UML framework offers between descriptions at different system design levels. Starting from the accurate ASM-based semantical definition of the various UML diagrams and related notations (see [32,33,50,51]), this equips UML-based practice with the degree of mathematical precision that distinguishes a scientifically rooted engineering discipline worth its name.…”

Section: Integrating Special Purpose Methodsmentioning

confidence: 99%

See 1 more Smart Citation

The Abstract State Machines Method for High-Level System Design and Analysis

Börger¹

2009

Formal Methods: State of the Art and New Directions

Self Cite

282

518

View full text Add to dashboard Cite

Section: Integrating Special Purpose Methodsmentioning

confidence: 99%

“…Sets of guarded update rules as above in fact constitute a normal form for a class of ASMs which suffice to define every event-B model (see the event-B-model normal form ASMs defined in Sect. 6.1) and to compute every synchronous UML activity diagram [32].…”

Section: Generalizing Fsm Statesmentioning

confidence: 99%

The Abstract State Machines Method for High-Level System Design and Analysis

Börger¹

2009

Formal Methods: State of the Art and New Directions

Self Cite

282

518

View full text Add to dashboard Cite

“…According to the translation rule in Definition 7, the activity diagram  is first translated into the dependency structure td() = ⟨, I, T, S, C, P, F⟩ where  = {0, 1, 2, 3, 4, 5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39, i, f 1, f 2, f 3, f 4, f 5}, I = {{i}}, T = {({i}, {0}), ({0}, {3}), ({0}, {1}), ({1}, {2}), ({2}, {4}), ({2}, {8}), ({4}, {7}), ({7, 8}, {11}), ({3}, {5}), ({5}, {6}), ({6}, {f 1}), ({5}, {9}), ({9}, {10}), ({11}, {12}), ({12}, {13}), ({13}, {f 2}), ({12}, {14}), ({14}, {15}), ({15}, {16}), ({16}, {18}), ({18}, {f 3}), ({16}, {2}), ({15}, {17}), ({17}, {19}), ({10}, {20}), ({19}, {20}), ({20}, {21}), ({20}, {22}), ({21, 22}, {23}), ({23}, {24}), ({24}, {27}), ({27}, {29}),({29}, {30}),({29}, {31}),({30}, {28}),({30}, {25}),({28}, {26}),({26}, {25}), ({25}, {f 4}), ({31}, {20}), ({31}, {32}), ({32}, {33}), ({32}, {36}), ({33}, {34}), ({33}, {35}), ({34, 35}, {37}), ({37}, {38}), ({36}, {39}), ({38}, {39}), ({39}, {f 5})}, S = {{7, 8}, {21, 22}, {34, 35}}, C = {{1, 3}, {6, 9}, {13, 14}, {16, 17}, {25, 28}, {20, 32}, {33, 36}}, P = ∅, and F = {{f 1}, {f 2}, {f 3}, {f 4}, {f 5}}.…”

Section: Figurementioning

confidence: 99%

Decomposition of UML activity diagrams

et al. 2017

View full text Add to dashboard Cite

SummaryIn software engineering, UML activity diagrams in general can be useful for a modeling system functional behavior, ranging from the sequences of activities/actions from business processes within an organization or among organizations down to the detail of an algorithm. The stepwise refinement process makes activity diagrams more and more complex. To guarantee the behavior consistency and correctness under refinement, the activity diagrams must be decomposed according to the divide-and-conquer strategy. Traditional decomposition methods adopt manual techniques and cannot ensure the independence and completeness of the obtained subdiagrams. In this paper, a novel decomposition approach is proposed, which can automatically divide an activity diagram into atomic and correct subdiagrams (subdiagrams without abnormal behavioral problems) at the same level. When such an activity diagram specifies the whole functional behavior of a software system, the approach can in fact decompose a system into multiple atomic subsystems. Every atomic subsystem is a completely independent system. It may be independently developed, independently tested, and independently deployed. The method facilitates the management, development, and maintenance of a software system. With the help of a prototype tool, a case study demonstrates the decomposition method.

show abstract

“…These elements are shared by all ASMs corresponding to UML models 3 . We discuss here on the place of the UML model specific part in the semantics framework (see Fig.…”

Section: Capturing Model Specific Information Through Initializationmentioning

confidence: 99%

“…Some UML formalization efforts using ASM already exist: [3] formalizes UML activity diagrams, by adapting ASM to natively support activity diagrams; [2] formalizes UML state machines by extending the basic ASM, with some new constructs to cover UML state machines specific features; [4] defines an ASM based toolset, focused on the state diagrams. These approaches disconnect state machines /activity diagrams of the rest of the language, and they do not consider all UML concepts (associations, inheritance, etc.…”

Section: Related Effortsmentioning

confidence: 99%

An ASM Semantics of UML Derived from the Meta-model and Incorporating Actions

Ober

2003

Abstract State Machines 2003

View full text Add to dashboard Cite

Abstract. We present an approach towards a formal dynamic semantics for UML using ASM. We aim to remain as close as possible to the standard definition of UML and to cover the operational part of the language with particular attention to the behavior description based on actions. To remain close to the standard UML, we automatically translate the UML metamodel in ASM. This allows to take into account all the concepts and relationships contained in the standard, and to minimize the changes subsequent to the frequent updates of the standard. For the dynamic part, the particularity of our approach is that we focus on actions, as defined in our proposal to the OMG action semantics working group. We deal with concurrency, signal exchange, operation calls, general communication primitives, etc. We do not define the semantics of state machines, but we clearly define their place within the framework of our semantics. We also describe how the ASM domains and functions used in the semantics are built initially from a particular UML model.

show abstract

An ASM Semantics for UML Activity Diagrams

Cited by 65 publications

References 5 publications

The Abstract State Machines Method for High-Level System Design and Analysis

The Abstract State Machines Method for High-Level System Design and Analysis

Decomposition of UML activity diagrams

An ASM Semantics of UML Derived from the Meta-model and Incorporating Actions

Contact Info

Product

Resources

About