CSIT111 Programming Fundamentals

Object Oriented Programming

Concept

1
 Focus of this subject

• This subject is not only about Java

• If you know a programming language and you know how
to use computers, it does not mean that you can develop
software systems
If you know alphabet and you
can type quickly, this may not
be enough to write a novel

To become a programmer
- you need to be familiar with advanced software
development concepts
- you need to know how to efficiently utilize these
concepts using appropriate programming languages
2
 Software development challenge
Software development has unique challenges which are
not common for other industries
• When you design a car you can foresee how it will look like when it is made
• Reverse engineering can reproduce car design documents (identical to original ones)

However…
• When a program is executed, it How to design
is a sequence of invisible electrical programs
signals which represent binary when you can't
microprocessor instructions see the final
• It is practically impossible to product?
reproduce the original program
3
code from binary instructions
 Imperative Programming Concept
The oldest concept where a program consists of a
sequence of commands for the microprocessor to execute
Example: Assembly language is a symbolic representation of
microprocessor instructions with one-to-one mapping
pushl %ebp 11010011
movl %esp, %ebp 01010010
addl 8(%ebp), %eax 10000011

How to increase
productivity of software
development?

• When you virtually have to 'live in the microprocessor' and think like a
machine to write even a simple program, you cannot be productive
• It is close to impossible to reuse assembly code. You need to start every
new project practically from scratch
4
 How to find an efficient design methodology ?

We could try to borrow ideas from other industries

Can software be built

from pre-designed
pre-tested parts too?

• Cars are made of preassembled parts

• To build a new car you don't need to design every part from
scratch – some parts can be reused from previous models,
or be purchased from new suppliers without making any
changes in their internal structure
5
 How to find an efficient design methodology ?

We could try to borrow ideas from other industries

Can software modules

be designed with
clearly defined
interface to simplify
their integration?

• To assemble a home theatre you can buy modules from different

manufacturers according to your needs
• They can be easily plugged together as their interfaces are standardized
6
 How to find an efficient design methodology ?

Other examples:

From transistors to integrated circuits

From bricks to pre-fabricated panels

• Transition to pre-fabricated generic reusable modules with well defined

interface components has been a common trend for all industries
• To increase productivity, computer programming had to follow the same
trend
• Research on efficient programming concepts led to development of the
Object Oriented Design methodology in the late 60th
7
 Objects
• Object Oriented Design methodology introduces the
concept of objects
• Like mechanical and electrical parts in other industries,
objects become major software building blocks
• Rather than think about commands and microprocessor
instructions, you need to think about objects, their
properties, their behaviors and how their interaction can
implement your program functionality
• In general, objects can receive messages from other
objects and provide responses. To use them, you don’t
need to worry about their internal structure. It is hidden.
Message Object Result

8
 Evolution of OOD languages
• The OOD methodology has substantially evolved since it was
introduced in the 60th
• Evolution of OOD programming languages reflects the evolution of
OOD programming concepts
1967 1980 1983 1995 2000

Simula Smalltalk C++ Java C#

Created a basis Significant Implemented Supports only Originated from
for all following revision of latest concepts practically Java, however
OO languages. Simula. of OOD. Very proven OOD deviated
It had some Development efficient concepts with substantially
shortcomings environment compiler. the focus on over years.
related to with tools Standardised by Internet and Works on MS
debugging and commonly used ISO. platform .NET platform.
support of now: debugger, independent
Standardised by
multiple code editor, applications.
ISO.
hardware class library
platforms

9
 Object Based Design
• The main purpose of any program is to process data
• The major task of OOD is how to split system's data and
behaviour into a set of interacting objects
A functional view of the program An OOD view of the program

Main
Data processing object
methods

Object2 Object1

Data to be
processed Object4
Object3

10
 What can an object do ?
• When you describe your program as a collection of
interacting objects, you need to have a clear idea what role
the objects will play in your application
• An object may play just one role, or several typical roles

Role Stereotypes
Collect, store and Provide services
provide data and computing
(data provider) (service provider)

An object

Generate other Make decisions

objects and maintain (controller)
relationship between
them (constructor) Analyse events and delegate
11
tasks to others (coordinator)
 Internal structure of objects
• Each object implements a certain part of the system functionality.
Thus, it should contain data and methods to process this set of data
Object
Data
How can objects interact?
Data processing
methods

Object
• To interact with other objects, they Data
also include interface methods
• Interaction between objects is Interface Data
possible only through interface methods processing
methods methods

12
 What does an object look like?
• Physically, it consists of binary data and Program memory layout
microprocessor instructions which occupy Object 1
a reserved block of memory
( its actual layout is system dependent )
Object 3
• Links between objects can be established
at the compilation time, or dynamically at System.out
run time
System.out is the standard output object that
• Logically, it must be declared in allows Java applications to display data
your program
• When an objects is declared it is class HelloWorldApp {
given a unique name public static void main(String[] args) {
// Display “Hello!"
• Looking through a program code, System.out.println(“Hello!");
you can see all objects declared }
there and follow the logical }
relationship between them
13
 How can objects be created ?
Parts of mechanical systems Objects of a software system
are made based upon their are generated based upon their
description – blueprints description – classes
public class Circle {
public float x, y, r;
public Circle(float r) { this(0.0, 0.0, r); }
public float getArea() { return 3.14*r*r; }
}

Instantiation

circle1 circle2 circle3

• A class is an abstraction defined by a programmer

• An object is an instance generated and placed in computer memory
(many similar objects can be generated from one class)
14
 Classes
• Classes can be interpret as blueprints, or
prototypes for objects
• Objects are not necessarily clones even when they
are created from the same class
For example: a class Polygon can be used to create
triangles and rectangles as instances (objects) public class Polygon {
• To generate different objects, we may specify }
. . . . .

different properties such as number of sides, the

lengths of those sides, their colors
• The object behaviour are things which require
actions - how the area, or the circumference are
calculated, how the object is displayed, etc

15
 Object intrinsic features
1. Identity
– Correct interaction between objects may not possible without
reliable identification of objects
– Each object has a unique identifier that is used to recognize it
public class Polygon {
. . . . .
Instantiation of objects presumes }
that all objects will be given
unique identifiers

ID: triangle1 ID: squareA ID: triangle2 ID: rhombus1

Identity (a unique name) of an object can be:

• specified by a programmer
• assigned by another object that takes a role of structurer
16
 Object intrinsic features
2. State
• Object-Oriented concept presumes that objects store data
• Unless an object is a garbage bin, all data are stored with the purpose
to reflect properties (or attributes) of objects
Example properties of a circle: (x,y) coordinates of the center, r radius
properties of a bill: due date, amount to pay
• A set of actual values stored in an object is referred as an object state
ID: Circle1 ID: Circle2
Some attributes
Object x: 25.0 x: 0.0 cannot be
properties y: 10.2 Object state y: 0.0 changed.
(or attributes) r: 7.5 r: 5.5 They are called
pi: 3.141 pi: 3.141 constants

• Objects instantiated from the same class have the same attributes,
but may have different states ( object IDs have to be different )
17
 Object intrinsic features
3. Behaviour
• Instantiated objects are expected to act and react according to their
roles ( collect and store data, make decisions, provide services, etc )
• A set of supported actions defines object behaviour (what it does)
• Actions in OOD are called methods

ID: Circle1
• Some methods can change the
x: 3.0
object state (changeRadius, …).
y: 1.0
These methods are called mutators
r: 7.5
Methods • Some other methods can only
changeRadius() provide a value of an attribute
Determine
changeCoordinate() without changing the object state
what the
getMyRadius() object does (getMyRadius, …) These methods
getMyCoordinates() are called accessors.
calculateArea()

18
 Fundamental OOD concepts
Encapsulation
• Some industrial products are sealed to prevent access to their
internal components. They can be used through external terminals
• OOD stipulates that to prevent unauthorized access to the most
critical object attributes and methods, they need to be placed into a
protective wrapper inside the object to make sure that:
- well designed and tested objects cannot be alternated or corrupted by
other poorly designed objects
- hidden components can be modified without affecting object interaction
( providing that interface methods are not affected by modifications)
• Attributes and Methods which are
specified as private are hidden inside private
objects and cannot be accessed from Attributes
outside public
methods private
• Methods specified as public can be Methods
used for interaction with other objects
19
 Fundamental OOD concepts
Encapsulation
• According to OOD, interaction between objects can take place only
through public methods
• In general, all attributes should be specified as private. If they need to be
accessed from outside, this should be possible only through a limited set
of public methods ( accessors, or mutators )
• Methods which are irrelevant to object interaction also should be private
• If a private attribute, or a private method can be accessed directly from
outside, this indicates a serious design oversight (a safety bug)
Bank account
Internet Banking money
getBalance()
User interface transaction() payBill() Account
transfer() management
methods

20
 Quiz
You need to implement an object Clock that
- counts time
- provides the current time on request
- can change on request the output format from 24hrs to AM/PM
- can set alarm
- can make beeping sound when alarm is on

ID: Clock1 1. Which methods should be

hours: 12 public and which ones should be
minutes: 25 private ?
seconds: 34
getTime() 2. Which methods are accessors
setOutputFormat() and which ones are mutators?
setAlarm()
countTime()
makeSound()

21
 Fundamental OOD concepts
Static attributes and static methods
Consider EnergyBill objects: EnergyBill1, EnergyBill2, EnergyBill3, . . .
ID: EnergyBill1 ID: EnergyBill2
BillerCode: 41225 BillerCode: 41225 • BillerCode will always
Rate: 0.25 Rate: 0.25 remain the same
energyUsed: 100 energyUsed: 200 therefore this attribute
totalAmount: 25.0 totalAmount: 50.0 should be a constant
dueDate: 10/11/17 dueDate: 15/11/17 • Rate may change, using
changeRate() method.
readEnegyUsed() readEnegyUsed()
This change has to be
calculateTotal() calculateTotal()
done simultaneously for
printBill() printBill()
all EnergyBill objects
changeRate() changeRate()
How to share a private attribute Rate among all objects, so
that if it is changed in one EneryBill, it will simultaneously
affect all other objects ?
22
 Fundamental OOD concepts
Static attributes and static methods
Attributes and methods specified as static are shared
among all objects instances of the same class
ID: EnergyBill1 ID: EnergyBill2
BillerCode: 41225 BillerCode: 41225
static Rate: static Rate:
energyUsed: 100 0.25 energyUsed: 200
totalAmount: 25.0 changeRate() totalAmount: 50.0
dueDate: 10/11/17 dueDate: 15/11/17
readEnegyUsed() readEnegyUsed()
calculateTotal() calculateTotal()
printBill() printBill()
static changeRate() static changeRate()

As static methods are shared among all objects, they cannot

access non-static attributes, or call non-static methods
23
 Fundamental OOD concepts
a boat
Inheritance
• It is common for many real world objects to inherit
properties from other related objects

• To facilitate reusability of objects, OOD

supports inheritance
Mobile
a parent object Boat Phone a motor boat
a yacht

a child object
Motorboat Smartphone
(or derived object)

• Inheritance indicates that objects are related

• The derived object inherits attributes and methods of the parent
object and therefore does not need to implement them again
24
 Fundamental OOD concepts
I need a cat

Polymorphism
• Polymorphism means “many forms”
• Interaction between objects is not always 'hard-wired'
• Polymorphism allows interaction with a virtual object be redirected to
different actual objects depending on the context
an abstract device actual devices

Document Printer Colour

Printer
print()
B&W
Different redirections from an abstract Printer result in Printer
different behaviours when the method print() is executed
Print to
An abstract Printer behaves like a polymorphic device
a File
25
 Fundamental OOD concepts
Polymorphism
playback any stream a virtual object

playbackStream () StreamPlayer

mp3 mpeg4 Mpeg2

Player Player Player

• Polymorphism leads to a generic implementations

• Binding to the right objects is carried out dynamically at
run-time
• Polymorphism is one of the most powerful OOD concepts
supported by Java programming language
26
 Object Oriented Methodology
• OOD is not just a basis for OO programming languages,
but a way of looking at the whole of the software
development process – OO Methodology
• Making a program comprised of interacting objects is a
big design challenge that cannot be done in a hurry
• OOM presumes that a lot of work needs to be done
before you get down to typing your code. OOM
prescribes a formal multistage process
• A program should be formally described using the UML
(Unified Modeling Language) at the system design stage
• A UML description can be implemented using different
OO programming languages

27
 Verbal description, ambiguity, confusion,…

• You may try to describe your program

using a natural language
• Natural languages do not have exact rules for
technical descriptions
• Even a simple natural language description can be
interpreted differently by different listeners (the more
details you provide, the higher chance for misinterpretation)
• A formal modelling language is needed to describe
software designs unambiguously
UML is a formal tool for software systems modelling
28
 What is UML and how can it help?

• UML (Unified Modelling Language) is a consolidation of

research on OO modelling
• UML was accepted by the ISO as an international standard
in 2000
• UML can be used
1. To make sketches when you want to communicate key points of your
program architecture
2. To provide a formal and detailed specification of a software system
3. To generate code directly from UML diagrams if a special tool is
used
• UML models cannot be misinterpreted
• UML is scalable and can be used for small and big projects
• UML facilitates the software development process and
simplifies debugging
29
 UML Class Diagrams
• Class diagrams:
– Contain classes and relations between them
– Specify class attributes sufficient to describe
any state of the object instantiated from a
class
– Specify methods sufficient to implement a
required object behaviour

30
 UML class symbol
• The most basic class symbol is a box with the class name.
It is used when class properties are not important (usually at
initial stages of system design)
• Adding in more details may be needed at later stages
– Attributes, or data members
– Methods Java

class name Person class Person {

lastName: ...
age:
}
attributes
height:
getName() • The level of details depends on
who the diagram is intended for
setName()
methods • Class symbols are the building
getHeight() blocks of class diagrams
getAge()

31
 UML class symbol
• Role stereotypes
• Visibility prefixes

<< Data Provider >>

Role stereotype

Person
- name:
- age: + public attributes and methods
- height: - private attributes and methods
- rate: {read only}
constant
+ getName()
+ setName()
+ getHeight()
+ getAge()
+ setAge()
32
 UML object symbol
<< Data Provider >> A class
Person
- name:
- age:

instantiation

object name class name underline

Jack : Person
Specific values for
name = "Jack Smith" each attribute
age = 21 ( object state )

A simplified UML representation

Jack : Person
when state is not important

33
 Class Relationship

• Class symbols by themselves provide very limited

information about your program architecture
• A model of the system should reflect relationship
between classes
• OOD defines the following types of relationship
between classes:
- association
- composition
- inheritance

34
 Association
• Indicates that one class uses another class
• Association can be described as “has” or “uses”
type of relationship

uses
Lecturer Projector

has
Country Capital City
1
Name: name:

has
User Bank Account
0..*

35
 Composition
• Composition is a special kind of association
• Composition reflects “contains” or “owns” type of
relationship
• Components “live” inside the container with their lifespan
synchronized with the container
• Deletion of the container destroys the component objects
Cube Vertex
8

PC

1..2 1..2 1 1
Processor Monitor Keyboard Mouse

36
 Inheritance
• Inheritance implements an “is a” type of relationship
- Motorboat is a boat
- Smartphone is a mobile phone
• A child class inherits attributes and methods from its parent
class and adds new attributes and methods to implement
new properties and behaviours
Rifle
caliber:
length:
weight: M4 : Automatic Rifle
effective range: caliber = 5.56
instantiation length = 840
is a weight = 3.4
is a
effective range = 500
rate of fire = 950
Sniper Rifle Automatic Rifle
This instantiated object has inherited
telescopic site: rate of fire:
all properties of the parent class

37
 Quiz
• What is the most appropriate relationship between
the following classes:
Table
Desktop
Legs

Table

1 3..4
Desktop Leg

38
 Quiz
• What is the most appropriate relationship between
the following classes:
Passenger
Ticket
Timetable

uses 0..*
Passenger Timetable
has a

1..*

Ticket

39
 Quiz
• What is the most appropriate relationship between
the following classes:
Passenger
Train passenger
Airplane passenger

Passenger

Train passenger Airplane passenger

40
 Quiz
• What is the most appropriate relationship between
the following classes:
Passenger
Airplane passenger
Luggage

Passenger

is a
has
Airplane passenger Luggage

41
 Defining classes

• The problem of defining an appropriate collection

of classes and their relationship for your project
is generally non-trivial
• Although there are some complicated theories
which should help, practically you can mostly
rely on your experience and intuition
• We are going to look at an made-up simple
application scenario to show how to determine
the objects and properties which seem
appropriate

42
 Scenario: A big heavy red cat seats on a mat
• A question we need to answer:
– What objects are needed to implement this scenario
and what are their properties?
• Objects?
– Cat, Mat
• Cat:
– Attributes?
• Big  Size?  Width, Height, Depth?
• Heavy  Weight
• Red  Colour Association
– Methods/Behaviours? uses
• Measure Size Test for “bigness” Cat Mat
• Measure Mass Test for “heaviness”
• Show colour - size: - isSeated:
• Sitting on the mat (interaction) - weight:
+ checkIt()
- color:
• Mat: + seatOn()
– Behaviours? + getSize()
• Can be sat on + getWeight()
+ getColor()
• Classes: Cat, Mat, … ?
43
 UML Design Tools
Enterprise Architect
• One of the most advanced and
most widely used tools in the
industry
• Supports all UML diagrams
• Checks correctness of models
• Dynamic model simulation
• Generation of documentation
and reports in a specified format
• Generation of Java, C++, C#
source code from UML models
• Helps to visualize your
applications by supporting
reverse engineering

44
 Suggested reading

Java: How to Program (Early Objects), 11th Edition

• Chapter 1
1.5 Introduction to object technology

45