9-1 © Prentice Hall, 2004 Chapter 9, Part II: System Behavior - Interactions (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer

Chapter © Prentice Hall, 2004 Outline - Analysis Class Diagram (Fully Fledged Class Diagram; read skill) - Interactions by Sequence Diagram (read & write skill) - Interactions by Collaboration Diagram - (read skill)

Chapter © Prentice Hall, 2004 Goal: Get to a Fully Fledged Class Diagram 

Chapter © Prentice Hall, 2004 Analyze System’s Processes (Use Case Diagrams/Descriptions, Data Flow Diagrams) Analyze System’s Processes (Use Case Diagrams/Descriptions, Data Flow Diagrams) Represent System’s Data (Conceptual Data Model- Partial Class Diagram; Object-Relational Notation) Represent System’s Data (Conceptual Data Model- Partial Class Diagram; Object-Relational Notation) Represent System’s Logic (Activity Diagram, Decision Tables) Represent System’s Logic (Activity Diagram, Decision Tables) Represent System’s Interactions (Sequence Diagram, Collaboration Diagram) Represent System’s Interactions (Sequence Diagram, Collaboration Diagram) Finalize Class Diagram Activity Diagram of Analyzing Information Systems

Chapter © Prentice Hall, 2004 Categorizing (Stereotyping) Classes (Analysis Classes) Corresponds to conceptual data model classes – Data Connections between actors and use cases – User Interface, other interfaces Performs behaviors associated with inner workings of use cases – Managing transactions, logic, business rules

Chapter © Prentice Hall, 2004

Chapter © Prentice Hall, 2004 Sequence Diagram A UML diagram that shows the interaction between objects to perform critical pieces of use case behavior in a time-ordered manner Interactions are in the form of messages Behavioral responsibilities are assigned to message recipients

Chapter © Prentice Hall, 2004 Symbols in a Sequence Diagram Object: Box or class stereotype symbol Object’s lifetime: Dotted vertical line Focus of Control: Thin bars; periods of time when object is behaving (fulfilling responsibilities). Message: Labeled horizontal arrows between objects. Run one or both ways (message-response).

Chapter © Prentice Hall, 2004

Chapter © Prentice Hall, 2004 Typically, actors interact with boundary classes, which in turn interact with control classes (if exist), which in turn interact with entity classes.

Chapter © Prentice Hall, 2004

Chapter © Prentice Hall, 2004 Collaboration Diagram A UML diagram that shows the interactions between objects to perform critical pieces of the use case behavior Unlike sequence diagrams, collaboration diagrams have no spatial representation of time; sequences of messages are shown by numbering.

Chapter © Prentice Hall, 2004

Chapter © Prentice Hall, 2004 Operations (behaviors) are specified at the bottom of a class box. Operations fulfill the classes’ responsibilities. Analysis Class Diagram Fully fledged Class Diagram with both data and operations (methods, responsibilities).