Modeling behavioral design patterns of concurrent objects

Abstract

Object-oriented software development practices are being rapidly adopted within increasingly complex systems, including reactive, real-time and concurrent system applications. While data modeling is performed very well under current objectoriented development practices, behavioral modeling necessary to capture critical information in real-time, reactive, and concurrent systems is often lacking. Addressing this deficiency, we offer an approach for modeling and analyzing concurrent object-oriented software designs through the use of behavioral design patterns, allowing us to map stereotyped UML objects to colored Petri net (CPN) representations in the form of reusable templates. The resulting CPNs are then used to model and analyze behavioral properties of the software architecture, applying the results of the analysis to the original software design.

A comparison of executable model based approaches for embedded systems

“…Each of the identified behavioral design patterns then has a corresponding template, represented as a CPN segment, which is paired with the UML object and is instantiated to capture specific behavioral characteristics based on the object specifications [5] …”

“…Two types of CPN template were developed, component templates and connector templates. CPN component templates were developed to support concurrent components with the following behavior patterns: asynchronous (i.e., aperiodic) I/O, periodic I/O, aperiodic algorithm, periodic algorithm, control, etc [5]. An example of a component template is given in Fig.…”

“…2. CPN connector templates were developed to support different types of communication and synchronization between concurrent components, including asynchronous communication, synchronous communication, and mutually exclusive access to passive objects [5]. An example of a connector template is given in Fig.…”

“…This paper is intended to aid designers in their choice of analysis techniques by comparing two different executable model based approaches for designing and validating real-time systems. The approaches include a colored Petri net (CPN) approach [3][4][5] and a state machine based approach [6][7][8][9][10]. Both approaches are compared against seven different comparison criteria and examples are given using a cruise control system case study developed using the COMET UML-based design method for concurrent and real-time systems [6], [7].…”

Scenario-Based Modeling in Industrial Information Systems

“…Collaboration diagrams are used to connect these OPN models and to derive a CP-net model for the considered system, which can be analysed by rigorous techniques or simulated to infer properties some of its behavioral properties. Pettit and Gomaa describe how CP-nets can be integrated with object-oriented designs captured by UML communication diagrams [12]. Their method translates a UML software architecture design into a CP-net model, using pre-defined CPnet templates based on object behavioral roles.…”