Supporting UML Sequence Diagrams with a Processor Net Approach

Staines, Tony Spiteri

doi:10.4304/jsw.2.2.64-73

Cited by 3 publications

(4 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A UML sequence diagram (SD) specifies scenarios of the processing of operations because of their clear graphical layout, but the semantics presented in the OMG specification for SD only give a basic idea of how the SD should work [11]. Indeed, the SD, as a semiformal model, is ambiguous and lacks precise semantics for its notations [11,20,21]. As a result, this chart should be initially converted to an appropriate formal model to prevent different understandings and decipher a unique meaning.…”

Section: Related Workmentioning

confidence: 99%

Early reliability assessment of component-based software system using colored petri net

Hosseinzadeh-Mokarram¹,

Isazadeh²,

Izadkhah³

2019

Turk J Elec Eng & Comp Sci

View full text Add to dashboard Cite

Assessment of reliability in the early stages of software development from architectural models is one of the major challenges that many studies have addressed in this field in the last decade. The main drawbacks of existing methods are the following: 1) considering equal impact for all parts of the software architecture on system reliability, and 2) inability to determine the contribution of each part of the software in the system failure. This paper introduces the extended version of the colored petri net as an underlying verifiable model to evaluate the reliability of a software system. The proposed model enhances reliability assessment of the software system by measuring the density of failure for each part of the software system, predicting the reliability during execution of a scenario, and estimating the reliability of every structural part of a program, such as loops and conditions. These innovations enable software architects to cost-effectively identify and correct the vulnerable parts of a system in the early stages of software development. The high-level model of the scenario is taken as a UML sequence diagram. Synthesis of the formal model is conducted using an introduced graph called a fragments dependency graph. The practicality of the suggested approach is illustrated by a case study.

show abstract

Section: Related Workmentioning

confidence: 99%

Early reliability assessment of component-based software system using colored petri net

Hosseinzadeh-Mokarram¹,

Isazadeh²,

Izadkhah³

2019

Turk J Elec Eng & Comp Sci

View full text Add to dashboard Cite

show abstract

“…Tony Spiteri [18] takes a case study, transform it into UML diagrams, and then implement the specifications into formal method languages, then apply optimization methods to minimize the computing resources; total time and total cost. in [19]- [21] z notations based schemas are applied in some real life examples and case studies, furthermore, the authors also uses z/eves tool for formal model check as well as z schemas verification.…”

Section: Related Workmentioning

confidence: 99%

An Integration of UML Sequence Diagram with Formal Specification Methods—A Formal Solution Based on Z

Minhas

Qazi²,

Shahzadi³

et al. 2015

JSEA

View full text Add to dashboard Cite

UML Diagrams are considered as a main component in requirement engineering process and these become an industry standard in many organizations. UML diagrams are useful to show an interaction, behavior and structure of the system. Similarly, in requirement engineering, formal specification methods are also being used in crucial systems where precise information is required. It is necessary to integrate System Models with such formal methods to overcome the requirements errors i.e. contradiction, ambiguities, vagueness, incompleteness and mixed values of abstraction. Our objective is to integrate the Formal Specification Language (Z) with UML Sequence diagram, as sequence diagram is an interaction diagram which shows the interaction and proper sequence of components (Methods, procedures etc.) of the system. In this paper, we focus on components of UML Sequence diagram and then implement these components in formal specification language Z. And the results of this research papers are complete integrated components of Sequence diagram with Z schemas, which are verified by using tools and model based testing technique of Formal Specifications. Results can be more improved by integrating remaining components of Sequence and other UML diagrams into Formal Specification Language.

show abstract

“…4, which transfers the root node of a SeqD to the root of CSP model: Listing 1 consists of a matching-template (lines 1-7) and a constructing-template (lines [8][9][10][11][12][13][14][15]. A path expression (lines 2-3) searches for an ownedBehavior element with property @xmi:type='uml:Interaction', and owned by a Collaboration packagedElement.…”

Section: Implementation and Examplementioning

confidence: 99%

“…A model driven approach is used in [1] to create Petri Net from UML2.0 SeqD. The work of [11] shows how UML SeqD can be converted to a processor net and analyzed. This paper is clearly inspired by the above mentioned contributions.…”

Section: Implementation and Examplementioning

confidence: 99%

QVT Based Model Transformation from Sequence Diagram to CSP

2010

2010 15th IEEE International Conference on Engineering of Complex Computer Systems

View full text Add to dashboard Cite

In a model driven software development paradigm, UML sequence diagrams are used for modeling the interaction view of the software. For an application with high demanding of dependability, formal verification and analysis need to be performed on the sequence diagrams. This is usually done by transforming the sequence diagrams to a well studied formalism that has effective tool support to verification and analysis. In this paper, we propose an approach for transformations from sequence diagrams to CSP processes. The transformations are implemented by using the model driven software engineering standards, such as MOF, QVT, and XSLT. For this, we design the metamodels for sequence diagrams and CSP, and a set of transformation rules are specified using the QVT graphical syntax. The transformation rules are implemented as XSLT rule-based style templates. An XSLT engine reads the XMI file of a sequence diagram produced by an UML CASE tool, and then executes the XSLT templates, outputs the CSP model as an XML file. The XML file of the CSP processes can be translated into the input of a CSP checker for verification.

show abstract

Supporting UML Sequence Diagrams with a Processor Net Approach

Cited by 3 publications

References 20 publications

Early reliability assessment of component-based software system using colored petri net

Early reliability assessment of component-based software system using colored petri net

An Integration of UML Sequence Diagram with Formal Specification Methods—A Formal Solution Based on Z

QVT Based Model Transformation from Sequence Diagram to CSP

Contact Info

Product

Resources

About