c
c



 
 
 
§ System modelling helps the analyst to
understand the functionality of the system
and models are used to communicate with
customers.

§ Different models present the system from

different perspectives
± Structural perspective showing the system or
data architecture;
± Behavioural perspective showing the behaviour
of the system;
± External perspective showing the system¶s
context or environment.
 c
c 
 

§ Building a model of an application domain

and then adding implementation details to it.

§ Following four stages:-

stages:-
± Analysis;
± System Design;
± Object Design;
± Implementation.
 ×

§ Object Model ± describes the static
structure of objects in the system and
their relationships.
§ Dynamic Model ± describes the aspect
of the system that change over time,
i.e. interaction among objects.
§ Functional Model ± describes data
value transformation in the system.
 c



§ Describes the structure of objects in

a system
system--
- Identity
- Relationship to other objects
- Their attributes
- And their operations.
 ~ 
 
§ Describes
those aspects of the
system concerned with time and
sequencing of operations-
operations-

§ Events that make change

§ Sequence of events

§ States that define context of events

§ And organization of events and

states.
 M 
 
§ Describes
those aspects of the system
concerned with transformation of
values--
values
§Functions
§ Mappings
§ Constraints
§ Functional dependencies

§ Is
represented with Data Flow
Diagrams.
 c
 
 

§ The UML is a standard representation
devised by the developers of widely used
object--oriented analysis and design
object
methods.

§ It has become an effective standard for

object--oriented modelling.
object
 c

 

Employee
± Object classes are
name: string
rectangles with address: string
dateOfBirth: Date
the name at the employeeNo: integer
top, attributes in socialSecurityNo: string
department: Dept
the middle section manager: Employee
salary: integer
and operations in status: {current, left, retired}
taxCode: integer
the bottom ...
section; join ()
leave ()
retire ()
changeDetails ()
c

 
 
± Relationships between object classes
(known as associations) are shown as
lines linking objects

Employee Department
is-member-of

is-managed-by

manages
Manager
’ 
 
§ Connection between objects
§ Solid line
± Direction optional
± Arrowhead depends on meaning
§ Name (optional)
§ Multiplicities (optional)

§ Visibility (optional)
 ’





 ’ 

§ Visibility
§ Name (only required element)
§ Type
§ Multiplicity
§ Default value
§ Properties
§ Example:
{






 
’  

§ Instance attributes
± Each object of the class has its own
attribute
± Changing the value of the attribute
affects only the containing object
§ Class attributes
± Only one instance of the attributes for
all objects of the class
± Changing the value of the attribute
affects all objects of the class
± Underline the attribute
’  
  








 c
  
§ An aggregation model shows how
classes that are collections are
composed of other classes.

§ Aggregation models are similar to

the part-
part-of relationship in semantic
data models.
c
  
 w

§ Models the concept of inheritance

§ Subclasses inherit the attributes and
operations of all their superclasses
§ Objects of a subclass should be
substitutable for objects of their
superclasses
§ Uses hollow triangle arrowhead on
superclass
w
w

Employee

Manager Programmer

budgetsControlled project
progLanguage
dateAppointed

Project Dept. Strategic

Manager Manager Manager
projects dept responsibilities
 


§ A restriction in the design
§ Documented inside curly braces {}
attached to any diagram element
’



A
  !"#

$ A

 % "#


$ 

’



A
  !"#

 $ A

 % "#


$ 
‰  ‰
 
 ’




§ Used to hold common operations and data
§ Used in inheritance hierarchy
± Derived (child) classes provide
implementations
§ Documented with class name in ?
?
± Can also use {abstract} property

 
A
#
&'
&
$' A
#
& ($' A
#
 c
 '  

§A behavioural model shows the

interactions between objects to
produce some particular system
behaviour that is specified as a use-
use-
case.

§ Sequence diagrams (or collaboration

diagrams) in the UML are used to
model interaction between objects.
©



Ê~) 

:CommsController :WeatherStation :WeatherData

request (report)

acknowledge ()
report ()
summarise ()

send (report)
reply (report)

acknowledge ()
 

cc~
§ Objects are abstractions of real-
real-world or
system entities and manage themselves

§ Objects are independent and encapsulate

state and representation information.

§ System functionality is expressed in

terms of object services


cc~ 
§ Shared data areas are eliminated
± Objects communicate by message
passing

§ Objects may be distributed

§ Objects may execute sequentially or in

parallel
 ’ ' 
cc~
§ Easier
maintenance. Objects may be
understood as stand-
stand-alone entities

§ Objects
are appropriate reusable
components

§ Forsome systems, there may be an

obvious mapping from real world
entities to system objects