“You can use an eraser on the

drafting table or a sledgehammer

on the construction site.”
-- Frank Lloyd Wright

Object Oriented Design

Lecture 03
Course Instructor: Dr Usman Nasir
Course Code: SE331
Spring 2020

Ver 1.0 Y2020

Object Oriented Design
— Object-Oriented (OO) design defines the classes
and their relationships that are needed to build
a system that meets the requirements.
— In OO analysis we model the problem domain, while in
OO design we model the solution domain
— Structures created during OO analysis are often
reused/extended by OO design
— The line between OO analysis and OO design is blurry, as
analysis structures will transition into model elements of the
target system.
OO Design concepts
— Objects
— Behaviours & Responsibilities
— Class & it relationships
Object
— An "object" is anything to which a concept applies
— Things drawn from the real life (problem domain etc).
— e.g., a living person, a job role, a software component in the
solution space.

— Object has three things!!

— State: the condition of an object at a certain stage in its
lifetime.
— Behavior: what an object does of capable of doing.
— Identity: what distinguishes it from other objects.
Behaviours & Responsibilities
— Object have behaviours and responsibilities
— Objects perform actions that have an outcome
— Tell us about itself (getters)
— Change it self (change its variables, setters)
— Initiate activities with other objects (uses, message other
objects)
— Have defined services or responsibilities
— contractual obligation
Class
— Class is a collection of objects that share common
properties, attributes, behavior and semantics, in
general.
— A collection of objects with the same attributes (variables)
and behavior (function/operations).
— Instantiation.
— The act of creating an instance of the class.
— An instance is an object created from a Class
— Association represents a general binary relationship
that describes an activity between two classes.

— Relationships Between Classes

— Dependency ("uses")
— Aggregation ("has")
— Inheritance ("is")
Dependency Relationship
— C depends on D: Method of C manipulates objects
of D.

Example: Mailbox depends on Message

— If C doesn't use D, then C can be developed without
knowing about D.
Aggregation
— Aggregation represents an ownership relationship
between two classes.
— Aggregation models the relationship like has-a.
— One class containing objects of another class is also a form of
aggregation (Composition/Containment).

— Example: MessageQueue aggregates Messages.

— MessageQueue has a Message.

— Example: Mailbox aggregates MessageQueue

— Mailbox has a MessageQueue.
Inheritance
— More general class = superclass
— More specialized class = subclass

— Subclass supports all method interfaces of superclass

— Subclass may have added methods, added state
— Subclass inherits from superclass
— Example: ForwardedMessage inherits from Message.
— ForwardMessage is a Message
Object-Oriented Analysis and Design
— Use-case driven
— Use-cases define the behavior of a system
— Each use-case focuses on one business process

— Architecture centric:
— Functional (external) view: focuses on the user’s
perspective.
— Static (structural) view: focuses on attributes, methods,
classes & relationships.
— Dynamic (behavioral) view: focuses on messages between
classes and resulting behaviors.
— Benefits of OOAD
— Break a complex system into smaller, more manageable
modules.
— Work on modules individually.
— See the system more realistically—as the users do.
Object Oriented Design Phase
— Goals:
— Identify classes.
— Identify behavior of classes.
— Identify relationships among classes.
— Artifacts (some of them):
— Textual description of classes and most important
responsibilities (key methods).
— Diagrams of class relationships.
— Diagrams of important usage scenarios.
Many OOD Methods!
— The Booch Method
— The Coad & Yourdon Method
— The Rambaugh Method
— The Wirfs-Brock Method
Identify classes & behaviors
Identifying Classes
— Well-known authors like Booch, Jacobson and others
give recommendations for finding objects and
classes.
The most common and most important one are :
— to use check lists for object candidates and characteristics
of objects
— to perform a grammatical analysis of some requirements
documents,
— to analyse the application domain and
— to start with analysing use cases
Grammatical Analysis
— Grammatical Analysis is to analyse the requirement
text for Nouns and Phrases to identify classes.
— Nouns suggest objects
— Verbs suggest operations
— Example:
“An ATM will allow a customer to withdraw
funds and display their account balance. Account
details are held centrally. An account can be
credited or debited. In addition, the bank can
request for an account to be frozen at anytime.”
— Nouns suggest objects, Verbs suggest operations
“An ATM will allow a customer to withdraw
funds and display their account balance. Account
details are held centrally. An account can be
credited or debited. In addition, the bank can
request for an account to be frozen at anytime.”

— Classes: ATM, Customer, Account, Bank

— ATM: withdraw, display
— Account: credit, debit, freeze
— Grammatical Analysis only provides a starting point
and basis for candidate classes

ATM Customer Account Bank

credit
withdraw debit
display freeze
Exercise: Identify Classes and methods
Whenever new patient are seen for the first time, they
complete a patient information form that asks their
name, address, phone number and insurance carrier,
which are stored in the patient information file.
Patients can be signed up with only one carrier, but
they must be signed up to be seen by a doctor. Each
time a patient visits the doctor, an insurance claim is
sent to the carrier for payment. The claim must
contain information about the visit, such as the date,
purpose, and cost. It would be possible for a patient to
submit two claims on the same day.
— However, grammatical analysis has its flaws and can
become confusing at times..
Class's responsibilities
— Responsibility is an obligation of a class in terms of
its behavior.
— Two types
— knowing responsibility
— doing responsibility

— Knowing responsibility
— What must a class “know”?
— Private encapsulated data
— Its Related objects
— Things it can derive or calculate
— Doing responsibility
— What must a class “do”?
— Take action (create an object, do a calculation)
— Initiate action in other objects
— Control/coordinate actions in other objects

— OO Principle: Every operation is the responsibility

of a single class.
— Example: Add message to mailbox
— Who is responsible: Message or Mailbox?
Identifying Class relationships
CRC Modelling
— Class-Responsibility-Collaborator (CRC) modelling
provides a simple mechanism for identifying classes
and their relationship even organizing classes
— Low-tech “brainstorming” tool for doing OO design
— Developed by Kent Beck and Ward Cunningham

— CRC model contains a collection of “index cards”

about a class.
— Cards are created from use-case scenarios, based on the
system requirements.
— Index card has detail of
— Class name
— Responsibilities, i.e. attributes & operations
— Collaborations, i.e. where interaction with other classes is
required

— CRC cards are used as part of a role-play that can

help identification and validation of class selection.
Class name:

SuperClasses:

SubClasses

Responsibility Collaborator
— class (top)
— responsibilities (left)
— collaborators (right)
Making CRC Cards!!!
— Make a group of five or six people
— developers, domain experts etc..

— Step 1: Identify the classes in the problem domain.

— Step 2: Take at least one card per person.
— Step 3: Add the class name and add responsibilities
— Step 4: Walk-through a scenario and work on
card(s).
— Repeat Step 4 for all use case scenarios
— Recording a Responsibility:
— List the responsibilities briefly.
— know, maintain, compute, calculate, display, prompt, read,
provide etc).
— A class should not have a large number of responsibilities.
— If the identified responsibilities do not fit in one card re-
think the design.
— Avoid
— too much detail
— too many things
— already listed for the super class
— Recording a Collaborator:
— A class has some data and knows other classes that have
the rest to fulfill a responsibility.
— The other classes are identified as collaborators.
— From a class’ perspective, the philosophy is “What I
know” and “Who I know” to fulfill a responsibility.
CRC Example
— The example application is a Vending Machine that
allows users to buy snack items.
— A Vending machine holds a number of snack items and
displays the list of snack items and their prices through an
user interface with a display screen and buttons for
making selections. In addition, the vending machine has a
slot for money and an item dispenser.
— A user can make a selection and query for the number of
calories of a snack item. The calories are displayed on
pressing a button. A user can place the money in the slot
and select an item.
Nouns are in blue and the verbs are in green.

AVending machine holds a number of snack items and

displays the list of snack items and their prices
through an user interface with a display screen and
buttons for making selections. In addition, the
vending machine has a slot for money and an item
dispenser.

A user can make a selection and query for the number

of calories of a snack item. The calories are displayed
on pressing a button. A user can place the money in
the slot and select an item.
— Nouns = objects/classes.
— Some are attributes of these classes.
— Verbs are actions that can be attached to these
objects.
— Focus on the problem-domain objects and ignore
presentation-specific (user-interface related)
object/classes
— Problem-specific classes:
— Vending Machine
— Snack item
— Price
— Calories
— Selection
— User
 Class name: SnackItem

Responsibility Collaborator

Knows its price and calories

Class name: VendingMachine

Responsibility Collaborator
Maintains a collection of SnackItems. SnackItem
Allows addition and removal of SnackItems
Exercise
A cinema has multiple theatres, each theatre has seats
arranged in rows. There can be a different number of
seats in every row.
Customers can reserve seats, and are given a row
number and a seat number. They may request bookings
of several adjoining seats. Each booking is for a
particular show (that is a movie at a certain time).
Shows are at an assigned date, time, and price, and are
scheduled in a theatre.
The system stores the customer’s name and telephone
number for reservation.
— Discover candidate classes
— Make CRC cards for each of your candidate class.
— Scenario 1: Making a reservation
— Customer come to the CinemaSite (the system) and
wants to reserve two seats to watch a movie at 8 pm.
— Using the CRC cards, play through the scenario
— How does the system find the show?
— Now write responsibilities' and collaborators in CRC
cards.
Thank you!!!
— A laboratory for teaching object oriented thinking by
Kent Beck and Ward Cunningham, OOPSLA 1989.
— http://c2.com/doc/oopsla89/paper.html
— Online tool for CRC Card Making
— https://echeung.me/crcmaker/

— Bring CRC Cards for CinemaSite