CO2401: Software Development
Lecture 6
Introduction to Use Case Realisation
1. Purpose
o Use Case Realisation: Involves modelling how a system realizes
each use case scenario by showing how objects interact to achieve
functionality.
o Domain Class Diagrams: Show the static structure of the system,
such as types of things and their relationships, but do not show
object collaboration.
2. Interaction Diagrams
o Interaction diagrams illustrate how objects exchange messages to
coordinate actions. They are crucial for understanding the dynamic
behaviour of the system.
o Types of Interaction Diagrams:
Sequence Diagrams
Communication Diagrams
Sequence Diagrams
1. Overview
o Sequence Diagrams: Capture the dynamic view of a system,
showing interactions among entities over time. They help identify
the behaviour that needs to be implemented in code.
o Key Components:
Participants: Objects involved in the interaction.
Lifelines: Represent the object's existence over time.
Messages: Arrows showing communication between objects.
Activation/Execution Specifications: Rectangles showing
when an object is performing an action.
Lecture 6
Introduction to Use Case Realisation
1. Purpose
o Use Case Realisation: Involves modelling how a system realizes
each use case scenario by showing how objects interact to achieve
functionality.
o Domain Class Diagrams: Show the static structure of the system,
such as types of things and their relationships, but do not show
object collaboration.
2. Interaction Diagrams
o Interaction diagrams illustrate how objects exchange messages to
coordinate actions. They are crucial for understanding the dynamic
behaviour of the system.
o Types of Interaction Diagrams:
Sequence Diagrams
Communication Diagrams
Sequence Diagrams
1. Overview
o Sequence Diagrams: Capture the dynamic view of a system,
showing interactions among entities over time. They help identify
the behaviour that needs to be implemented in code.
o Key Components:
Participants: Objects involved in the interaction.
Lifelines: Represent the object's existence over time.
Messages: Arrows showing communication between objects.
Activation/Execution Specifications: Rectangles showing
when an object is performing an action.
