This paper presents a pragmatic approach to the specification of functionality of object-oriented applications. The approach relies on event traces, which are used to depict the co-operation between objects. Event traces model the communication between the objects, whereas object models provide a static view of object structures. Together these two notations form the backbone of object modelling, and they can be used consistently throughout the development process. In the analysis phase, event traces provide a black-box view of the system that is to be implemented. Event traces are also used to illustrate how the end user communicates with the user interface. In the design phase event traces illustrate what architectural decisions have been made and how the design objects co-operate with each other. The implementation phase can also be supported by event traces. This paper explains how we use event traces in real software projects. Our approach combines ideas from various object-oriented methods. Our method is called OMT++ and it is being applied in the development of a large network management system with nearly two million lines of C++ code running in the X11 environment.
[1]
Juha-Markus Aalto,et al.
Challenges in Applying Objects to Large Systems
,
1995,
CAiSE.
[2]
Stephen Travis Pope,et al.
A cookbook for using the model-view controller user interface paradigm in Smalltalk-80
,
1988
.
[3]
Chris Dollin,et al.
Object-oriented development: the fusion method
,
1994
.
[4]
Ari Jaaksi,et al.
Object-Oriented Development of Interactive Systems with OMT
,
1994
.
[5]
Ivar Jacobson,et al.
Object-oriented software engineering - a use case driven approach
,
1993,
TOOLS.
[6]
James E. Rumbaugh,et al.
Object-Oriented Modelling and Design
,
1991
.
[7]
James E. Rumbaugh,et al.
OMT: The Dynamic Model
,
1995,
Journal of object-oriented programming.
[8]
Ari Jaaksi,et al.
Object‐oriented specification of user interfaces
,
1995,
Softw. Pract. Exp..