Considerations and Rationale for a UML System Model

Broy, Manfred; Cengarle, Marı́a Victoria; Grönniger, Hans; Rumpe, Bernhard

doi:10.1002/9780470522622.ch3

Cited by 8 publications

(11 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Roughly, a comorphism corresponds to an encoding of one logic into a another one. The purpose of institution comorphisms is threefold: (1) to provide a means for expressing the dynamic checks (see below) in the institutional framework, (2) to obtain tool support for the various UML diagrams by using comorphisms into toolsupported institutions, and (3) to transform UML diagrams into ACSL specifications and C programs.…”

Section: Towards An Institution For Uml State Machinesmentioning

confidence: 99%

“…This situation leads to a gap between standards' recommendation to apply formal methods, and current industrial practice, which by using the UML lacks the semantic foundations to apply such methods. One common approach to deal with this gap is to define a comprehensive semantics for the UML using a system model, e.g., [2,3]. However, such an approach is a thorny business, as every detail has to be encoded into one, necessarily quite complex semantics.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Towards an Institutional Framework for Heterogeneous Formal Development in UML

Knapp

Mossakowski

Roggenbach

2015

Software, Services, and Systems

View full text Add to dashboard Cite

We present a framework for formal software development with UML. In contrast to previous approaches that equip UML with a formal semantics, we follow an institution based heterogeneous approach. This can express suitable formal semantics of the different UML diagram types directly, without the need to map everything to one specific formalism (let it be first-order logic or graph grammars). We show how different aspects of the formal development process can be coherently formalised, ranging from requirements over design and Hoarestyle conditions on code to the implementation itself. The framework can be used to verify consistency of different UML diagrams both horizontally (e.g., consistency among various requirements) as well as vertically (e.g., correctness of design or implementation w.r.t. the requirements).

show abstract

Section: Towards An Institution For Uml State Machinesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Towards an Institutional Framework for Heterogeneous Formal Development in UML

Knapp

Mossakowski

Roggenbach

2015

Software, Services, and Systems

View full text Add to dashboard Cite

show abstract

“…The System Model is abstract enough to be of general value, but also sufficiently detailed to allow simulation and execution of UML models. Among others, central concepts of the UML have been formalized as theories of the "System Model;" see [30][31][32][33].…”

Section: Uml As a Wholementioning

confidence: 99%

UML formal semantics: lessons learned

Broy

Cengarle

2011

Softw Syst Model

Self Cite

View full text Add to dashboard Cite

show abstract

“…The system model in the form of [6,7] serves as our semantic domain. It characterizes object-based systems by describing their structural, behavioral, and interaction aspects.…”

Section: System Modelmentioning

confidence: 99%

“…For details regarding the rationale behind the system model and the actual definitions please consult [6,7].…”

Section: System Modelmentioning

confidence: 99%

Towards a Semantics of Activity Diagrams with Semantic Variation Points

Grönninger¹,

Reiß²,

Rumpe³

2010

Model Driven Engineering Languages and Systems

Self Cite

View full text Add to dashboard Cite

Abstract. UML activity diagrams have become an established notation to model control and data flow on various levels of abstraction, ranging from fine-grained descriptions of algorithms to high-level workflow models in business applications. A formal semantics has to capture the flexibility of the interpretation of activity diagrams in real systems, which makes it inappropriate to define a fixed formal semantics. In this paper, we define a semantics with semantic variation points that allow for a customizable, application-specific interpretation of activity diagrams. We examine concrete variants of the activity diagram semantics which may also entail variants of the syntax reflecting the intended use at hand.

show abstract

Considerations and Rationale for a UML System Model

Cited by 8 publications

References 30 publications

Towards an Institutional Framework for Heterogeneous Formal Development in UML

Towards an Institutional Framework for Heterogeneous Formal Development in UML

UML formal semantics: lessons learned

Towards a Semantics of Activity Diagrams with Semantic Variation Points

Contact Info

Product

Resources

About