Ordering actions in sequence diagrams of UML

Cardoso, Janétte; Sibertin-Blanc, Christophe

doi:10.1109/iti.2001.937990

Cited by 24 publications

(14 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To obtain a finite automaton, possible traces that contain the same set of events are identified. An SD has also been translated to a Petri net (e.g., [Cardoso and Sibertin-Blanc 2001;Eichner et al 2005;Fernandes et al 2007]) and abstract state machines (e.g., [Cavarra and Küster-Filipe 2004;Kohlmeyer and Guttmann 2010;Xiang and Shao 2009]). Refinement is not considered [Cardoso and Sibertin-Blanc 2001;Cavarra and Küster-Filipe 2004;Eichner et al 2005;Fernandes et al 2007;Hammal 2006;Kohlmeyer and Guttmann 2010;Whittle and Schumann 2000;Ziadi et al 2004;Xiang and Shao 2009].…”

Section: Translation To Automata and Process Calculimentioning

confidence: 99%

See 1 more Smart Citation

Required behavior of sequence diagrams

Kim

2014

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Many reusable software artifacts such as design patterns and design aspects make use of UML sequence diagrams to describe interaction behaviors. When a pattern or an aspect is reused in an application, it is important to ensure that the sequence diagrams for the application conform to the corresponding sequence diagrams for the pattern or aspect. Reasoning about conformance relationship between sequence diagrams has not been addressed adequately in literature. In this article, we focus on required behaviors specified by a UML sequence diagram and provide a semantic-based formalization of conformance relationships between sequence diagrams. A novel trace semantics is first given that captures precisely required behaviors. A refinement relation between sequence diagrams is then defined based on the semantics. The refinement relation allows a sequence diagram to be refined by changing its structure so long as its required behaviors are preserved. A conformance relation between sequence diagrams is finally given that includes the refinement relation as a special case. It allows one to introduce and rename lifelines, messages, and system variables when reusing sequence diagrams. Properties of the semantics, refinement, and conformance relations are studied. Two case studies are provided to illustrate the efficacy of semantic-based conformance reasoning. ACM Reference Format:Lunjin Lu and Dae-Kyoo Kim. 2014. Required behavior of sequence diagrams: Semantics and conformance.

show abstract

Section: Translation To Automata and Process Calculimentioning

confidence: 99%

“…A simple sequence diagram which does not have any combined fragment has been modeled as a partial order on event occurrences [Cardoso and Sibertin-Blanc 2001]. Intuitively, e 1 ; e 2 indicates that e 1 occurs no later than e 2 .…”

Section: Abstract Syntaxmentioning

confidence: 99%

Required behavior of sequence diagrams

Kim

2014

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…One way of analyzing specifications given through semiformal UML notation is to formally define an operational semantics for the UML dynamic diagrams based on a formal notation, which shows how these diagrams are executed in real-time and which allows one to analyze qualitatively and quantitatively real-time UML specifications (Cardoso and Sibertin-Blanc, 2001). In this paper, semantics improvement is given by combining UML with Petri nets.…”

Section: Real-time Systems Modeling Based On Uml Diagramsmentioning

confidence: 99%

Real-time scheduling of batch systems using Petri nets and linear logic

Soares

Julia

Vrancken

2008

Journal of Systems and Software

View full text Add to dashboard Cite

“…The latest version is UML 2.0 from the acceptance of UML1.1 by OMG (Object Management Group) in 1997. UML has proven successful in the modeling of many large and complex systems [6][7][8][9][10][11][12][13][14][15][16]. Figure 3 shows the packages that are part of the VSNNetMDS UML software model, as well as dependencies between the packages.…”

Section: Software Modelmentioning

confidence: 99%

Web-based remote monitoring and fault diagnosis system

Chen

et al. 2005

Int J Adv Manuf Technol

View full text Add to dashboard Cite

This paper proposes an approved Web-based multilayer distributed software architecture solution for remote monitoring and fault diagnosis. To tightly integrate legacy monitor systems, a component framework model based on COM has been proposed, which is very suitable for remote monitoring and fault diagnosis applications. This system has the potential for exchanging a data acquisition system by using wrapper service components. A mixed thick Web client architecture is proposed to implement real-time remote monitoring. A Web-based remote monitoring and fault diagnosis system is developed by using modeling technology, Web application technology, component technology and VME extension for instrumentation (VXI) bus technology, which publishes a fault diagnosis algorithm package, a basic monitoring package and an advanced analysis package on the Internet. This system provides authorized users with an effective and instant way to access new monitoring and diagnosis component packages in time. This paper gives researchers a paradigm to accomplish similar systems. The technique developed may be used for other fields, such as power engineering, manufacture and transportation system.

show abstract

Ordering actions in sequence diagrams of UML

Cited by 24 publications

References 2 publications

Required behavior of sequence diagrams

Required behavior of sequence diagrams

Real-time scheduling of batch systems using Petri nets and linear logic

Web-based remote monitoring and fault diagnosis system

Contact Info

Product

Resources

About