ITSC 2132 OBJECT ORIENTED PROGRAMING

INTRODUCTION
LECTURE ONE
OUTLINE

• From problem to code

• Three different phases of software development
• Paradigms of programing
• Why object oriented
• Benefits of OOP
• Concepts of object and class
FROM PROBLEM TO CODE

• Software development process has three phases

• Analysis
• Design
• Implementation

• Development of software is a simple linear progression of these phases

• Successful software products evolve over time
• Implementation experience suggest an improved design where new requirement are added that force
another iteration through analysis and design
• Object oriented design can lead software's that facilitate evolution better than traditional methods
THE ANALYSIS PHASE

• A vague understanding of the problem is transformed into a precise description of the tasks that a
software system need to carry out
• Result : - functional specification that have the following characteristics :
• It completely defines that tasks to be performed
• Free from internal contradiction
• Readable by both expert in the problem domain and developer
• Reviewable by diverse interested parties
• Can be tested against reality
• The analysis phase concern itself with description of what need to be done ,not how
• Common method used : textual description and use case [behavior of the system]
THE DESIGN PHASE

• The solution to the problem is proposed and specified

• The major goal of the design phase are :
• Identify the classes
• Identify the responsibilities of these classes
• Identify the relationship between these classes
• It is possible to map an object oriented design to a Non OOP language but the process is unpleasant
• The discovery of classes is an iterative process
• The result of design phase :
• Textual description of classes and there most important responsibilities
• Diagrams of relationship among classes
• Diagrams of important usage scenario
• State diagrams of object whose behavior is highly state dependent
THE IMPLANTATION PHASE

• Classes and methods are coded ,tested and deployed

• Object oriented development encourage gradual growth of a program by attaching more
working class cluster and repeated testing
• Object oriented design is suitable for prototyping
• Prototyping can extremely help in influencing the design or even the analysis where
problem is incompletely understood
• Give more insight into the solutions that are desired
 PARADIGMS OF PROGRAMING

• The two major paradigms

• Structural
• programs could be developed in more sensible blocks
• understandable and maintainable
• Object oriented
• Model instructions with the data they manipulate and store this components together
• Reusability
 STRUCTURAL PARADIGM

Scenario 1
• Assume you undertake the following activities on a daily basis. Arrange this list into a sensible order then split this list into
three blocks of related activities and give each block a heading to summaries the activities carried out in that block.
 Get out of bed
 Eat breakfast
 Park the car
 Get dressed
 Get the car out of the garage
 Drive to work
 Find out what your boss wants you to do today
 Feedback to the boss on today’s results
 Do what the boss wants you to do
STRUCTURAL PARADIGM( CONTINUED …)

• You should have been able to organize these into groups of related activities and give
each group a title that summarizes those activities.
 Get up :- Get out of bed, Get dressed, Eat breakfast
 Go to Work :- Get the car out of the garage, Drive to work ,Park the car
 Do your job :- Find out what your boss wants you to do today ,Do what the boss
wants you to do ,Feedback to the boss on today’s results.
STRUCTURAL PARADIGM( CONTINUED …)

• We can change and improve one section of the instructions without changing the other parts.
For example we could improve the instructions for going to work….
• Listen to the local traffic and weather report, Decide whether to go by bus or by car, If
going by car, get the car and drive to work. Else walk to the bus station and catch the bus
• We can do this without worrying about any potential impact this may have on ‘getting up’ or
‘doing your job’.
• In the same way structuring computer programs can make each part more understandable
and make large programs easier to maintain.
OBJECT ORIENTED PARADIGM

• One of the major issue addressed here is reusability

Scenario 2
• Imagine a personal address book with some data stored about your friends Name,
Address, Telephone Number.
 List three things that you may do to this address book.
 Next identify someone else who may use an identical address book for some purpose other
than storing a list of friends.
OBJECT ORIENTED PARADIGM( CONTINUED …)

• With an address book we would want to be able to perform the following actions :- find out details of a
friend i.e. their telephone number, add an address to the address book and, of course, delete an address.
• We can create a simple software component to store the data in the address book (i.e. list of names etc)
and the operations we can perform (i.e add address, find telephone number etc).
• By creating a simple software component to store and manage addresses of friends we can reuse this in
another software system i.e. it could be used by a business manager to store and find details of
customers. It could also become part of a library system to be used by a librarian to store and retrieve
details of the users of the library.
• Thus in object oriented programming we can create re-usable software components (in this case an
address book).
WHY WE USE THE OBJECT ORIENTATION
PARADIGM?
• The major problem of software arises due to :
 Poor analysis and design: the computer system we create doesn’t do the right thing.
 Poor maintainability: the system is hard to understand and revise when, as is
inevitable, requests for change arise.

• The Object Oriented programming paradigm aims to help overcome these

problems by
 Helping with the analysis and design tasks during the initial software development phase
 Ensuring software is robust and maintainable
THE BENEFITS OF THE OBJECT ORIENTED

• Before you write the software you must first develop a model of what that software must be
able to do and how it should work.
• Object oriented modelling is based on the ideas of abstraction, encapsulation, inheritance and
polymorphism
• The general proponents of the object oriented approach claims that this model provides:
 Better representation of real world(Founded on the concept of object and class)
 Better abstractions (modelling information and behavior together)
 Better maintainability (more comprehensible, less fragile)
 Better reusability (classes as encapsulated components)
 THE OBJECT AND CLASS CONCEPT

• What is object and class ??

• Objects are entities in computer program that have three characteristics
• State : collection of information held by the object
• Behavior : the operations that the object support
• Identity : differentiate one object from other
• Objects model the real or abstract entities
• A class defines a group of objects
• It defines
• The operations that are allowed on the objects of the class
• The possible states for objects of the class
• Objects that conform to the class description are called instance of the class
THE OBJECT AND CLASS CONCEPT(CONTINUED…)

Scenario 3
• Think of an object you possess. Describe its current state and list two or three things you can do with that
object.
Feedback
• You probably thought about an entirely physical object such as a watch, a pen, or a car.
• Objects have a current status. A watch has a time (represented internally by wheels and cogs or in an
electronic component). A pen has a certain amount of ink in it and has its lid on or off. A car has a current
speed and has a certain amount of fuel inside it.
• Specific behavior can also be associated with each object (things that you can do with it) :- a watch can be
checked to find out its time, its time can also be set. A pen can be used to write with and a car can be driven.
THE OBJECT AND CLASS CONCEPT(CONTINUED…)

What about non physical objects ??

• You can also think of other non physical things as objects :- such as a bank account.
• A bank account is not something that can be physically touched but intellectually we can
consider a bank account to be an object.
• It also has a current status (the amount of money in it) and
• It also has behavior associated with it (most obviously deposit money and withdraw
money).
FINAL THOUGHTS ON OOP

• Object oriented programming it a method of programming that involves the creation of

intellectuals objects that model a business problem we are trying to solve
• E.g. a bank account, a bank customer and a bank manager – could all be objects in a
computerized banking system
• In creating a object oriented program
• we define the properties of a class of objects (e.g. all bank accounts)
• we create individual objects from this class (e.g. your bank account)
FINAL THOUGHTS ON OOP( CONTINUED …)

• Deciding just what classes we should create in our system is not a trivial task as the real
world is complex and messy
• In essence we need to create an abstract model of the real world that focuses on the
essential aspects of a problem and ignores irrelevant complexities
• E.g. in the real world bank account holders sometimes need to borrow money and
occasionally their money may get stolen by a pick pocket. If we were to create a bank account
system
• should we allow customers to borrow money?
• Should we acknowledge that their cash may get stolen and build in some method of them
getting an immediate loan
• Is this an irrelevant detail that would just add complexity to the system and provide no real
benefit to the bank?
FINAL THOUGHTS ON OOP( CONTINUED …)

• Using object oriented analysis and design techniques our job would be
• Look at the real world
• Come up with a simplified abstract model that we could turn into a computer system

• How good our final system is will depend upon how good our software model is
EXERCISE

1. Consider a computer system that will allow items to be reserved from a library.
Imagine one such item that you may like to reserve and list two or three things that a
librarian may want to know about this item.
2. Note that we can consider a reservation to be is an intellectual object (where the
actual item is a physical object). Considering this intellectual object (item reservation)
list two or three actions the librarian may need to perform on this object
3. Considering the most general category of object that can be borrowed from a library, a
‘loan item’, list two or three more specific subcategory of object a library can lend out
ASSIGNMENT ONE

• Describe in detail about the following paradigms

• Imperative programing
• Functional programing
• Procedural programing
• Scripted programing
• Logical programing
• Declarative programing

• Give example programing languages that are under their category [sample code if possible]
• What sort of difference and similarity each have