Modelling Global Behaviour in Object-Oriented Analysis: Scenarios, Use Cases and Interaction Diagrams

Most software development methods define notations for modelling global behaviour. Many of these notations use interaction diagrams to model possible sequences of interactions between a system and its environment, or between the objects of the system. Other methods use structured textual descriptions or regular expressions for specifying use cases or use scenarios. Although many methods use similar notations, there are often substantial differences in their underlying concepts and in the content expressed by the diagrams. On the other hand, completely different notations use sometime the same concepts and show the same aspects of the global behaviour of a system. In this document we investigate the characteristics of different notations. We show what their underlying concepts are and how they relate to each other. Finally, we give an overview of the techniques that are used by some of the current object-oriented analysis methods for modelling global behaviour.

[1]  James E. Rumbaugh,et al.  Object-Oriented Modelling and Design , 1991 .

[2]  Edward V. Berard,et al.  Essays on object-oriented software engineering (vol. 1) , 1993 .

[3]  Dorothea Beringer Limits of Seamlessness in Object Oriented Software Development , 1994, TOOLS.

[4]  Wolfgang Hesse,et al.  Objektorientierte Analyse und Geschäftsvorfallsmodellierung , 1993 .

[5]  David Chenho Kung,et al.  Formal approach to scenario analysis , 1994, IEEE Software.

[6]  Derek Coleman Fusion with Use Cases-Extending Fusion for Requirements Modelling; presentation at the Fusion Users , 1995 .

[7]  Jean-Pierre Corriveau,et al.  Capturing Object Interactions , 1994, TOOLS.

[8]  H. Holbrook,et al.  A scenario-based methodology for conducting requirements elicitation , 1990, SOEN.

[9]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[10]  Randall B. Smith,et al.  Self: The power of simplicity , 1987, OOPSLA 1987.

[11]  G. Dedene,et al.  M.E.R.O.DE.: a model-driven entity-relationship object-oriented Development method , 1994, SOEN.

[12]  Kenneth S. Rubin Object behavior analysis , 1992, CACM.

[13]  Coln Atkinson,et al.  Object-oriented development: The fusion method , 1996 .

[14]  Kent Beck,et al.  A laboratory for teaching object oriented thinking , 1989, OOPSLA 1989.

[15]  Rebecca Wirfs-Brock,et al.  Designing object-oriented software , 1990 .

[16]  W. Stein Objektorientierte Analysemethoden - ein Vergleich , 1993, Inform. Spektrum.

[17]  Jean-Marc Nerson,et al.  Object-Oriented Analysis and Design , 1992, TOOLS.

[18]  Stephen M. McMenamin,et al.  Essential systems analysis , 1984 .

[19]  Andy Pols Requirements engineering: use cases and more , 1997, OOPSLA '97.

[20]  Ian M. Graham Beyond the Use Case: Combining Task Analysis and Scripts in Object-Oriented Requirements Capture and Business Process Re-engineering , 1994, TOOLS.

[21]  Nancy M. Wilkinson Using CRC cards: an informal approach to object-oriented development , 1995 .

[22]  Björn Regnell,et al.  A hierarchical use case model with graphical representation , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

[23]  James Martin,et al.  Object-oriented methods : a foundation , 1995 .

[24]  James E. Rumbaugh,et al.  Getting Started: Using Use Cases to Capture Requirements , 1994, J. Object Oriented Program..

[25]  James Martin,et al.  Object-oriented analysis and design , 1992 .

[26]  Edward Yourdon,et al.  Modern structured analysis , 1989 .

[27]  Australia,et al.  Requirements Modeling , 1997 .

[28]  R. J. A. Buhr,et al.  Use Case Maps: A New Model to Bridge the Gap Between Requirements and Design , 1995 .

[29]  John Daniels,et al.  Designing object systems: object-oriented modelling with Syntropy , 1995 .

[30]  Ian M. Graham Object-oriented methods , 1991 .

[31]  Heinz Züllighoven,et al.  Objektorientierte Anwendungsentwicklung - Konzepte, Strategien, Erfahrungen (2. Aufl.) , 1994 .

[32]  Lorna A. Zorman Requirements Envisaging by Utilizing Scenarios (REBUS). , 1995 .

[33]  Edward V. Berard,et al.  Essays on object-oriented software engineering , 1992 .

[34]  Kim Walden,et al.  Seamless object-oriented software architecture , 1995 .

[35]  Eric Dubois,et al.  O-O Requirements Analysis: an Agent Perspective , 1993, ECOOP.

[36]  Grady Booch,et al.  Object-Oriented Design with Applications , 1990 .

[37]  Todd Cotton Evolutionary fusion: a customer-oriented incremental life cycle for fusion , 1995 .

[38]  Fanny-Michaela Reisin,et al.  Kooperative Gestaltung in partizipativen Softwareprojekten , 1992 .

[39]  Martin Glinz,et al.  An Integrated Formal Model of Scenarios Based on Statecharts , 1995, ESEC.

[40]  Martin S. Feather,et al.  Utilizing Scenarios in the Software Development Process , 1993, Information System Development Process.

[41]  James A. Kowal Behavior models - specifying user's expectations , 1991 .

[42]  Ivar Jacobson,et al.  A Growing Consensus on Use Cases , 1995, Journal of object-oriented programming.