Publication detail

Specification of UML Classes by Object Oriented Petri Nets

KOČÍ, R. JANOUŠEK, V.

Original Title

Specification of UML Classes by Object Oriented Petri Nets

English Title

Specification of UML Classes by Object Oriented Petri Nets

Type

conference paper

Language

en

Original Abstract

The UML class diagram defines a basic architectonic model of the system. Its behavior is then usually described by other UML diagrams, such as activity diagrams, sequence diagrams, etc. These models serve for the design purposes and are automatically or manually transformed in the next development stages, typically to the models with formal basis or to implementation (production) environment. There is no backward step allowing to investigate the system structure and its behavior with the designed models. On the other hand, there are approaches to system design combining design, testing, and implementing stages into one development technique. One of them uses Object Oriented Petri Nets (OOPN) as basic modeling formalism. Nevertheless, OOPN lacks for advisable architectonic view of modeled systems as it is offered by UML class diagram. The paper is aimed at using UML class diagrams for system architecture description and the OOPN formalism for description of classes behavior. Since UML classes and OOPN classes partially differs, we define formal transformation between UML classes and OOPN classes.

English abstract

The UML class diagram defines a basic architectonic model of the system. Its behavior is then usually described by other UML diagrams, such as activity diagrams, sequence diagrams, etc. These models serve for the design purposes and are automatically or manually transformed in the next development stages, typically to the models with formal basis or to implementation (production) environment. There is no backward step allowing to investigate the system structure and its behavior with the designed models. On the other hand, there are approaches to system design combining design, testing, and implementing stages into one development technique. One of them uses Object Oriented Petri Nets (OOPN) as basic modeling formalism. Nevertheless, OOPN lacks for advisable architectonic view of modeled systems as it is offered by UML class diagram. The paper is aimed at using UML class diagrams for system architecture description and the OOPN formalism for description of classes behavior. Since UML classes and OOPN classes partially differs, we define formal transformation between UML classes and OOPN classes.

Keywords

Class diagram, Object-Oriented Petri Nets, UML, transformation

RIV year

2012

Released

10.09.2012

Publisher

Xpert Publishing Services

Location

Lisbon

ISBN

978-1-61208-230-1

Book

ICSEA 2012, The Seventh International Conference on Software Engineering Advances

Edition

NEUVEDEN

Edition number

NEUVEDEN

Pages from

361

Pages to

366

Pages count

6

URL

BibTex


@inproceedings{BUT97037,
  author="Radek {Kočí} and Vladimír {Janoušek}",
  title="Specification of UML Classes by Object Oriented Petri Nets",
  annote="The UML class diagram defines a basic architectonic model of the system. Its
behavior is then usually described by other UML diagrams, such as activity
diagrams, sequence diagrams, etc. These models serve for the design purposes and
are automatically or manually transformed in the next development stages,
typically to the models with formal basis or to implementation (production)
environment. There is no backward step allowing to investigate the system
structure and its behavior with the designed models. On the other hand, there are
approaches to system design combining design, testing, and implementing stages
into one development technique. One of them uses Object Oriented Petri Nets
(OOPN) as basic modeling formalism. Nevertheless, OOPN lacks for advisable
architectonic view of modeled systems as it is offered by UML class diagram. The
paper is aimed at using UML class diagrams for system architecture description
and the OOPN formalism for description of classes behavior. Since UML classes and
OOPN classes partially differs, we define formal transformation between UML
classes and OOPN classes.",
  address="Xpert Publishing Services",
  booktitle="ICSEA 2012, The Seventh International Conference on Software Engineering Advances",
  chapter="97037",
  edition="NEUVEDEN",
  howpublished="print",
  institution="Xpert Publishing Services",
  year="2012",
  month="september",
  pages="361--366",
  publisher="Xpert Publishing Services",
  type="conference paper"
}