On the Integration of UML and Petri Nets in Software Development

Campos, Jocileide Sales; Merseguer, José

doi:10.1007/11767589_2

Cited by 23 publications

(10 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Merseguer et al have done important work ( [4] gives an overview) on translating the UML to labeled generalized stochastic Petri nets (LGSPN) for performance analysis purposes. Tool support is provided through the ArgoSPE tool set and the model checker GreatSPN.…”

Section: Related Workmentioning

confidence: 99%

UML behavioral consistency checking using instantiable Petri nets

Thierry-Mieg¹,

Hillah²

2008

Innovations Syst Softw Eng

View full text Add to dashboard Cite

Model-driven engineering (MDE) development methods are gaining increasing attention from industry. In MDE, the model is the primary artifact and serves several goals, including code generation, requirements traceability, and model-based testing. MDE thus enables cost-effective building of models versus direct coding of an application. Thus model-based formal verification of behavioral consistency is desirable as it helps improve model quality. Our approach is based on translation of a UML model to instantiable Petri nets (IPN). This formalism is based on the semantics of Petri nets, but introduces the concepts of type and instance. This allows one to accurately capture these concepts in UML models. IPN support hierarchical descriptions natively, and use the notion of transition synchronization for composition of behaviors. This is a general and powerful mechanism borrowed from process algebra. We show that IPN allow one to adequately address the challenges of translation from UML for analysis purposes. The approach has been implemented and experimental results are presented.

show abstract

Section: Related Workmentioning

confidence: 99%

UML behavioral consistency checking using instantiable Petri nets

Thierry-Mieg¹,

Hillah²

2008

Innovations Syst Softw Eng

View full text Add to dashboard Cite

show abstract

“…In this paper Sequence Diagrams are used as the modelling language for describing the behaviour of a system. Sequence Diagrams are a UML 2.1 version of Message Sequence Charts [13] and they are widely used in Software Engineering [14]. Sequence Diagrams can be used in modelling complex Enterprise Systems as they provide a sequential listing of events and are also able to model parallelism and conflicts.…”

Section: Uml Sequence Diagramsmentioning

confidence: 99%

Model interoperability via Model Driven Development

Ameedeen

Bordbar

Anane

2011

Journal of Computer and System Sciences

View full text Add to dashboard Cite

Model Driven Development Model interoperability Software development UML Petri NetsAmong the factors that contribute to the inherent complexity of the software development process is the gap between the design and the formal analysis domains. Software design is often considered a human oriented task while the analysis phase draws on formal representation and mathematical foundations. An example of this dichotomy is the use of UML for the software design phase and Petri Nets for the analysis; a separation of concerns that leads to the creation of heterogeneous models. Although UML is widely accepted as a language that can be used to model the structural and behavioural aspects of a system, its lack of mathematical foundations is seen as a serious impediment to rigorous analysis. Petri Nets on the other hand have a strong mathematical basis that are well suited for formal analysis; they lack however the appeal and the ease-of-use of UML. A pressing concern for software developers is how to bridge the gap between these domains and allow for model interoperability and the integration of different toolsets across them, and thus reduce the complexity of the software development process. The aim of this paper is to present a Model Driven Development (MDD) model transformation which supports a seamless transition between UML and Petri Nets. This is achieved by model interoperability from UML Sequence Diagrams to Petri Nets and supported by tool integration. The model transformation framework allows a software system to be designed in terms of UML Sequence Diagrams and subjected to formal analysis by taking advantage of the strong mathematical framework of Petri Nets. The behaviour of a Personal Area Network will be used to illustrate the proposed approach and to highlight model interoperability and tool integration through the design, the transformation and the analysis phases.

show abstract

“…In this manuscript, the main general goal is to devise scenario-based modeling techniques that can be translatable to a PN model, so here we focus on previous works that address the (more generic) transformation of scenario-based models into state-based models. Campos and Merseguer integrate performance modeling within software development process, based on the translation of almost all UML behavioral models into Generalized Stochastic PNs [1]. They explain how to obtain from sequence diagrams and statecharts a performance model representing an execution of the system.…”

Section: Specification With Colored Petri Netsmentioning

confidence: 99%

Scenario-Based Modeling in Industrial Information Systems

Machado

Fernandes

Barros

et al. 2010

Distributed, Parallel and Biologically Inspired Systems

View full text Add to dashboard Cite

Abstract. This manuscript addresses the creation of scenario-based models to reason about the behavior of existing industrial information systems. In our approach the system behavior is modeled in two steps that gradually introduce detail and formality. This manuscript addresses the first step, where text-based descriptions, in the form of structured rules, are used to specify how the system is or should be regulated. Those rules can be used to create behavioral snapshots, which are collections of scenario-based descriptions that represent different instances of the system behavior. Snapshots are specified in an intuitive and graphical notation that considers the elements from the problem domain and permit designers to discuss and validate the externally observable behavior, together with the domain experts. In the second step (not fully covered in this manuscript), the system behavior is formalized with an executable model. This formal model, which in our approach is specified using the Colored Petri Net (CP-nets) language, allows the system internal behavior to be animated, simulated, and optimized. The insights gained by experimenting with the formal model can be subsequently used for reengineering the existing system.

show abstract

On the Integration of UML and Petri Nets in Software Development

Cited by 23 publications

References 28 publications

UML behavioral consistency checking using instantiable Petri nets

UML behavioral consistency checking using instantiable Petri nets

Model interoperability via Model Driven Development

Scenario-Based Modeling in Industrial Information Systems

Contact Info

Product

Resources

About