Object-relationship diagrams for object-oriented modeling with concurrency feature

One of the most distinguished features of object-oriented paradigm is the modeling power. It captures real-world entities with a single concept, the object, which combines both the structural aspect and the behavioral aspect of the entities. It provides primarily the concepts of encapsulation and inheritance. Modeling concurrency is very crucial to achieve computational efficiency in case multiple concurrent activities in an application need to be synchronized. The conventional object-oriented modeling lacks the modeling features for concurrency in the sense that it is difficult to separate synchronization from the specification of methods. The separation allows the reusability of a class. In this paper, we propose a modeling technique through a diagrammatical representation of Petri nets, called Object-Relationship Diagram, for object-oriented applications. We first describe structure model and behavior model which describe structural aspect and behavioral aspect of objects, respectively. For behavior modeling, we use the notions of generalization and aggregation to provide users with comprehensibility of the model. We then extend our model to express concurrency and synchronization features to manage concurrent access to objects.

[1]  Michael Kifer,et al.  Deductive and Object-Oriented Databases , 1991 .

[2]  Sukho Lee,et al.  An Object-Oriented Approach to Modelling Relationships and Constraints based on Abstraction Concept , 1990, DEXA.

[3]  C. Tomlinson,et al.  Inheritance and Synchronization with Enabled Sets , 1989, OOPSLA.

[4]  Hirotaka Sakai,et al.  An Object Behavior Modeling Method , 1990, DEXA.

[5]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[6]  James Lyle Peterson,et al.  Petri net theory and the modeling of systems , 1981 .

[7]  Josephine Micallef,et al.  Encapsulation, Reusability and Extensibility in Object-Oriented Programming Languages , 1987 .

[8]  Anne H. H. Ngu Transaction Modeling , 1989, ICDE 1989.

[9]  D. Miller,et al.  Entity Model Clustering: Structuring A Data Model By Abstraction , 1986, Comput. J..

[10]  A. Corradi,et al.  PO: an object model to express parallelism , 1988, OOPSLA/ECOOP '88.

[11]  T. J. Teorey,et al.  A logical design methodology for relational databases using the extended entity-relationship model , 1986, CSUR.

[12]  Eugene Miya,et al.  On "Software engineering" , 1985, SOEN.

[13]  Michael Schrefl,et al.  Object/behavior diagrams , 1991, [1991] Proceedings. Seventh International Conference on Data Engineering.

[14]  Yutaka Kimura,et al.  A View Class Mechanism for Object-Oriented Database Systems , 1991, DASFAA.

[15]  D. Decouchant,et al.  A synchronization mechanism for typed objects in a distributed system , 1988, OOPSLA/ECOOP '88.

[16]  Bruce Martin,et al.  Concurrent programming vs. concurrency control: shared events or shared data , 1988, OOPSLA/ECOOP '88.

[17]  David J. DeWitt,et al.  The Object-Oriented Database System Manifesto , 1994, Building an Object-Oriented Database System, The Story of O2.