12th European Conference on Object-Oriented Programming Brussels, Belgium, July 20 - 24, 1998
	Tutorial T10

Disciplined Object-Oriented Analysis

Analysis is a user domain activity, based on requirements described in use cases. The analysis step is critical to the development of a software system because it identifies the cumulative demand on objects and facilitates reuse of objects and responsibilities at the domain level. We base decisions about the level and scope of analysis on the shared model, a mental model in the mind of the various users of the system. The shared model corresponds to users understanding of what the software system must do. The objects and collaborations of the analysis object model are discovered using CRC cards and transcribed using UML sequence diagrams. The shared model provides clear guidance about when to stop the analysis "chase". This tutorial focuses on the role of analysis in object-oriented software engineering. We present the shared model concept and how it guides us on what we should and should not do during the analysis step. We present the techniques used during the analysis chase by way of a detailed example.

1. Introduction: (20 minutes)
   • What is OO? Why do we use OO?
   • Why is analysis important?
2. The Shared Model to set the level & scope of analysis (20 minutes)
3. Building the Object-Oriented Analysis Model: (110 minutes)
   • Use Case-Driven Analysis
   • CRC with Jacobson object types
   • In-class exercise (combined with the break)
   • The complete analysis model & sequence diagrams
4. Summary and Discussion (30 minutes)
   • The shared model and use cases
   • The shared model and analysis
   • The analysis model and design