Enhancing Reusability and Simplifying the OO Development with the Use of Events and Object Environment

  • Krista Rizman
  • Ivan Rozman
Conference paper


Object-oriented(OO) software development enhances reusability. But reuse and object composition are not straightforward. Only compatible components, which conform to the same client-server protocol, can be composed. In this paper we propose an event-driven approach to OO software development which enhances reusability by increasing the openness of objects and provides a simple composition principle. It bases on concepts of events and object environment. Object environment serves as a mediator among independent objects. It consists of agents that monitor and respond to object notifications of events that occur through the life-cycle of each object. Events enhance object openness and so reusability and allow uncoupled programming style. Uncoupled programming style together with a simple composition principle provided by the use of the object environment allow easy production of powerful building blocks and simple construction of the complex software from powerful building blocks.


Software Development Object Environment Instance Method Software Community Event Message 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    B. Henderson-Sellers, J. M. Edwards, “The object oriented system life-cycle”, Communication on the ACM, vol 33, no. 9, Sept. 1990.Google Scholar
  2. 2.
    K. Rizman, I. Rozman, A computer aided prototyping methodology, ACM SIGSOFT SOFTWARE ENGENERING NOTES, Vol 14., No. 6, 68–72 (1989).CrossRefGoogle Scholar
  3. 3.
    R. Wirfs-Broock, Object-Oriented Design: A Responsibility-Driven Approach“, OOPSLA’89 Proceedings, 71–75 (1989).Google Scholar
  4. 4.
    R. Wirfs-Brock, B. Wilkerson, L. Wiener, “Designing Object Oriented Software”, Prentice Hall, 1990.Google Scholar
  5. 5.
    R. Helm, I.M. Holland, D. Gangopadhyay, “Contracts: Specifying Behavioral Compositions in Object-Oriented Systems”, ECOOP/OPSLA’90 Proceedings, October, 1990, pp. 169–180.Google Scholar
  6. 6.
    B. Meyer, Reusability: The Case for Object-Oriented Design, IEEE Software, March 1987, 50–64 (1987).CrossRefGoogle Scholar
  7. 7.
    S. Gibs, D. Tsichritzis, E. Casias, O. Niersatz, X. Bintando: Class Management for Software Communities, Communications of the ACM, vol. 33, no. 9, September 1990, 90–103 (1990).CrossRefGoogle Scholar
  8. 8.
    G. Booch, Object-Oriented Design, The Benjamin Cummings Publishing Company Inc., (1991).Google Scholar
  9. 9.
    P. Coad, E. Yourdon: Object-Oriented Analysis, Yourdon Press, Prentice Hall, 1990.Google Scholar
  10. 10.
    A. Goldberg, D.Robson, Smalltalk-80: The Language and its Implementation, Addison-Wesley, 1983.MATHGoogle Scholar
  11. 11.
    W. LaLonde, J. Pugh: Designing is Hard: Object-Oriented Software Is Different!, Journal on Object Oriented Programming, March/April 1989, 46–55 (1989).Google Scholar
  12. 12.
    D. Teanzer, M. Ganti, S. Padar, “Object-oriented Software Reuse: The Yoyo Problem”, Journal on Object Oriented Programming, Sept./Oct. 1989, 30–35 (1989).Google Scholar

Copyright information

© Springer-Verlag/Wien 1992

Authors and Affiliations

  • Krista Rizman
    • 1
  • Ivan Rozman
    • 1
  1. 1.Faculty of Technical SciencesUniversity of MariborMariborSlovenia, Europe

Personalised recommendations