Anupkumar M Bongale

 To explain how a software design may be

represented as a set of interacting objects
that manage their own state and operations
 To describe the activities in the object-

oriented design process

 To introduce various models that describe an

object-oriented design
 To show how the UML may be used to

represent these models

 An object-oriented design process
◦ Weather Station Case Study

 Design evolution
 Several different notations for describing
object-oriented designs were proposed in the
1980s and 1990s
 The Unified Modeling Language is an
integration of these notations
 It describes notations for a number of

different models that may be produced

during OO analysis and design
 It is now a de facto standard for OO

modelling
 Employee
name: string
address: string
dateOfBirth: Date
employeeNo: integer
socialSecurityNo: string
department: Dept
ma nager: Employee
salary: integer
status: {current, left, retired}
taxCode: integer
. ..
join ()
leave ()
retire ()
changeDetails ()
 Conceptually, objects communicate by
message passing.
 Messages
◦ The name of the service requested by the calling
object.
◦ Copies of the information required to execute the
service and the name of a holder for the result of
the service.
 In practice, messages are often implemented
by procedure calls
◦ Name = procedure name.
◦ Information = parameter list.
// Call a method associated with a buffer
// object that returns the next value
// in the buffer
v = circularBuffer.Get () ;

// Call the method associated with a

// thermostat object that sets the
// temperature to be maintained
thermostat.setTemp (20) ;
 Objects are members of classes which define
attribute types and operations

 Classes may be arranged in a class hierarchy

where one class (a super-class) is a generalisation of
one or more other classes (sub-classes)

 A sub-class inherits the attributes and

operations from its super class and may add
new methods or attributes of its own

 Generalisation in the UML is implemented as inheritance

in OO programming languages
 Employee

Ma nager Programmer

budgetsControlled project
progLanguage
dateAppointed

Project De pt. Strategic

Ma nag er Ma nager Ma nag er
projects dept responsibilities
 It is an abstraction mechanism which may be
used to classify entities

 It is a reuse mechanism at both the design

and the programming level

 The inheritance graph is a source of

organisational knowledge about domains and
systems
 Object classes are not self-contained. they cannot
be understood without reference to their super-
classes

 Designers have a tendency to reuse the inheritance

graph created during analysis. Can lead to
significant inefficiency

 The inheritance graphs of analysis, design and

implementation have different functions and
should be separately maintained
 Define the context and modes of use of the
system
 Design the system architecture
 Identify the principal system objects
 Develop design models
 Specify object interfaces
A weather data collection system is required to generate weather maps on a
regular basis using data collected from remote, unattended weather stations
and other data sources such as weather observers, balloons and satellites.
Weather stations transmit their data to the area computer in response to a
request from that machine.

The area computer validates the collected data and integrates it with the
data from different sources. The integrated data is archived and, using data
from this archive and a digitised map database a set of local weather maps
is created. Maps may be printed for distribution on a special-purpose map
printer or may be displayed in a number of different formats.
A weather station is a package of software controlled instruments
which collects data, performs some data processing and transmits
this data for further processing. The instruments include air and
ground thermometers, an anemometer, a wind vane, a barometer
and a rain gauge. Data is collected every five minutes.

When a command is issued to transmit the weather data, the

weather station processes and summarises the collected data. The
summarised data is transmitted to the mapping computer when a
request is received.
 Data display layer where objects are
«subsystem» concerned with preparing and
Da ta display presenting the data in a human-
readable form

Data archiving layer where objects

«subsystem» are concerned with storing the data
Da ta archiving for future processing

Data processing layer where objects

«subsystem» are concerned with checking and
Da ta processing integrating the collected data

Data collection layer where objects

«subsystem» are concerned with acquiring data
Da ta collection from remote sources
 Develop an understanding of the
relationships between the software being
designed and its external environment
 System context
◦ A static model that describes other systems in the
environment. Use a subsystem model to show other
systems. Following slide shows the systems around
the weather station system.
 Model of system use
◦ A dynamic model that describes how the system
interacts with its environment. Use use-cases to
show interactions
«subsystem»
Da ta collection «subsystem»
Da ta display

Observer Satellite
User Ma p
Co mms interface display

Weather Ma p
Balloon Ma p printer
station

«subsystem» «subsystem»
Da ta processing Da ta archiving

Da ta
Da ta Da ta storage
checking integration
Ma p store Da ta store
Startup

Shutdown

Re port

Ca librate

Test
System Weather station
Use-case Report
Actors Weather data collection system, Weather station
Data The weather station sends a summary of the weather data that has been
collected from the instruments in the collection period to the weather data
collection system. The data sent are the maximum minimum and average
ground and air temperatures, the maximum, minimum and average air
pressures, the maximum, minimum and average wind speeds, the total
rainfall and the wind direction as sampled at 5 minute intervals.
Stimulus The weather data collection system establishes a modem link with the
weather station and requests transmission of the data.
Response The summarised data is sent to the weather data collection system
Comments Weather stations are usually asked to report once per hour but this
frequency may differ from one station to the other and may be modified in
future.
 Once interactions between the system and its
environment have been understood, you use
this information for designing the system
architecture
 Layered architecture is appropriate for the
weather station
◦ Interface layer for handling communications
◦ Data collection layer for managing instruments
◦ Instruments layer for collecting data
 There should be no more than 7 entities in an
architectural model
Weather station

Manages all
«subsystem» external
Interface communications

Collects and
«subsystem» summarises
Da ta collection weather data

«subsystem» Package of
instruments for raw
Instruments data collections
 Identifying objects (or object classes) is the
most difficult part of object oriented design

 There is no 'magic formula' for object

identification. It relies on the skill, experience

and domain knowledge of system designers

 Object identification is an iterative process.

You are unlikely to get it right first time
 Use a grammatical approach based on a
natural language description of the system
(used in Hood method)
 Base the identification on tangible things in
the application domain
 Use a behavioural approach and identify
objects based on what participates in what
behaviour
 Use a scenario-based analysis. The objects,
attributes and methods in each scenario are
identified
 Ground thermometer, Anemometer,
Barometer
◦ Application domain objects that are ‘hardware’
objects related to the instruments in the system
 Weather station
◦ The basic interface of the weather station to its
environment. It therefore reflects the interactions
identified in the use-case model
 Weather data
◦ Encapsulates the summarised data from the
instruments
 WeatherStation WeatherData
identifier airTemperatures
groundTemperatures
reportWeather () win dSpeeds
calibrate (instruments) win dDirections
test () pressures
startup (instruments) rainfall
shutdown (instruments)
collect ()
summarise ()

Ground Anemometer Ba rom eter

the rmometer pressure
win dSpeed
temperature win dDirection height
test () test ()
calibrate () test ()
calibrate ()
 Use domain knowledge to identify more
objects and operations
◦ Weather stations should have a unique identifier
◦ Weather stations are remotely situated so
instrument failures have to be reported
automatically. Therefore attributes and operations
for self-checking are required
 Active or passive objects
◦ In this case, objects are passive and collect data on
request rather than autonomously. This introduces
flexibility at the expense of controller processing
time
 Design models show the objects and object
classes and relationships between these
entities
 Static models describe the static structure of

the system in terms of object classes and

relationships
 Dynamic models describe the dynamic

interactions between objects.

 Sub-system models that show logical
groupings of objects into coherent
subsystems
 Sequence models that show the sequence of
object interactions
 State machine models that show how
individual objects change their state in
response to events
 Other models include use-case models,
aggregation models, generalisation
models,etc.
 Shows how the design is organised into
logically related groups of objects
 In the UML, these are shown using packages

- an encapsulation construct. This is a logical

model. The actual organisation of objects in
the system may be different.
«subsystem» «subsystem»
Interface Da ta collection

Co mmsCo ntroller WeatherData

Instrument
WeatherStation Status

«subsystem»
Instruments

Air
thermometer Ra inGauge Anemometer

Ground
thermometer Barometer Wind Vane
 Sequence models show the sequence of
object interactions that take place
◦ Objects are arranged horizontally across the top
◦ Time is represented vertically so models are read
top to bottom
◦ Interactions are represented by labelled arrows,
Different styles of arrow represent different types
of interaction
◦ A thin rectangle in an object lifeline represents the
time when the object is the controlling object in the
system
 :CommsController :WeatherStation :WeatherData

request (report)

acknowledge ()
report ()
summarise ()

send (report)
reply (report)

acknowledge ()
 Show how objects respond to different service
requests and the state transitions triggered by
these requests
◦ If object state is Shutdown then it responds to a Startup()
message
◦ In the waiting state the object is waiting for further
messages
◦ If reportWeather () then system moves to summarising
state
◦ If calibrate () the system moves to a calibrating state
◦ A collecting state is entered when a clock signal is
received
 Operation calibrate () Calibrating

calibration OK
startup () Waiting test () Testing
Shutdown

shutdown () transmission done test complete

Transmitting
clock collection
done reportWeather ()
weather summary
Summarising complete
Collecting
 Hiding information inside objects means that
changes made to an object do not affect other
objects in an unpredictable way
 Assume pollution monitoring facilities are to be
added to weather stations. These sample the
air and compute the amount of different
pollutants in the atmosphere
 Pollution readings are transmitted with weather
data
 Add an object class called ‘Air quality’ as part
of WeatherStation
 Add an operation reportAirQuality to

WeatherStation. Modify the control software

to collect pollution readings
 Add objects representing pollution

monitoring instruments
 WeatherStation
Air quality
identifier
NO Data
reportWeather () smokeData
reportAirQuality () benzeneData
calibrate (instruments)
test () collect ()
startup (instruments) summarise ()
shutdown (instruments)

Pollution monitoring instruments

NO meter SmokeMeter

BenzeneMeter
 OOD is an approach to design so that design
components have their own private state and
operations
 Objects should have constructor and
inspection operations. They provide services
to other objects
 Objects may be implemented sequentially or
concurrently
 The Unified Modeling Language provides
different notations for defining different
object models
 A range of different models may be produced
during an object-oriented design process.
These include static and dynamic system
models
 Object interfaces should be defined precisely

using e.g. a programming language like Java

 Object-oriented design simplifies system

evolution