NATIONAL COLLEGE OF BUISNESSS ADMINISTRATION

&ECONOMICS

Reg no: 2213329

Presented to: PROF Amna
Ilyas
Presented by: Abdullah Ilyas
Object Oriented
Design
Using UML
Diagram
&
Case Diagram
 Object Oriented Analysis
(OOA):
Object oriented analysis is the first technical activity performed
as part of object oriented software engineering.OOA introduce
New concepts to investigate a problem.

• The information domain is modeled.

• Behaviour is presented.
• Function is described.
Object Oriented Design
• An analysis model created using object oriented analysis is
transformed by object oriented design into a design model.

• It works as a plan for software creation.

• OOD results in a design having several different levels of

Modularity.

• The major system components are partitioned into a subsystem

(a system level “Modular”).

• Their manipulation operations are encapsulated into objects

(a modular form that is the building block of an Object Oriented
System).
Concepts :
 Object
 Class
 Attribute
 Operation
 Encapsulation
 Abstraction
 Inheritance
 Subsystem
What is an Object?
 Informally, an object represents an entity, either
physical, conceptual, or software
 All entities involved in design
An object is something that has:
• State
• Behaviour

Example:
person , bank , company etc
What is a Class?

 A class is a description of a group of objects with same properties

(attributes), behavior (operations), relationships, and semantics
Class Compartments
 A class is comprised of three sections
 The first section contains the class name
 The second section shows the structure (attributes)
 The third section shows the behavior (operations)

Class Professor
Name name
Attributes empID
Operations create( )
save( )
delete( )
change( )
 What is an Attribute?
Object
Class

Attribute Attribute Value

:CourseOffering
number = 101
CourseOffering startTime = 900
endTime = 1100
number
startTime :CourseOffering
endTime
number = 104
startTime = 1300
endTime = 1500
What is an Operation?

CourseOffering
Class
addStudent
deleteStudent
Operation getStartTime
getEndTime
Message:
Objects communicate via messages, Messages are
Implemented as procedure or function call.

Abstraction:
Used for handling complexity, removes irrelevant
data and shows only essential data.

Encapsulation:
It is concept of information hiding.
clubs essential information together &
restricts access to the data and method from
outside world
Inheritance:
One class inherits the attributes and methods
from another class.
 UML
(Unified Modeling
Language)

12
 What is UML?

 UML is a standardized Modeling Language

enabling developers to specify
 UML is a language for
 Visualizing
 Specifying
 Constructing
 Documenting
13  Artifacts of a Software system
UML is an important aspect involved in Object Oriented
Development.It uses graphic notation to create visual
Models Of software system.

UML was created by Object Management Group (OMG)

and UML 1.0 specification craft was proposed to the OMG
January 1997.

14
UML is different from the other common Programming
Languages like C++ , JAVA , COBOL etc.

UML is a pictorial language used to make software

Blue prints.

UML has a direct relation with OOA & OOD

CONCEPTUAL MODEL
A Conceptual model can be defined as a model which is
made of concepts and their relationships.
Conceptual model of UML can be mastered
by learning three Major elements

UML Building blocks

Rules to connect the building blocks
Common mechanisms of UML

Object oriented concepts

UML can be described as a successor of
object oriented Analysis and design
 Using
Case Diagrams

19
Contents
 Actors
 Use cases (function/operation)
 Link
 Relationship between two use case
 Use Case Diagrams

 Use Case diagrams show the various activities the users can
perform on the system.
 They model the dynamic aspects of the system.

21
 Use Case Diagrams

 A set of ACTORS : roles users can play in interacting with the

system.
 An actor is used to represent something that users our system.
 A set of USE CASES: each describes a possible kind of
interaction between an actor and the system.
 Uses cases are actions that a user takes on a system
 A number of RELATIONSHIPS between these entities (Actors
and Use Cases).
 Relationships are simply illustrated with a line connecting actors
to use cases.

22
 Use Case Diagrams - Actors

 An actor is a user of the system playing a particular role.

 Actor is shown with a stick figure.

employer employee client

23
 Use Case Diagrams – Use Cases

 Use case is a particular activity a user can do on the system.

 Is represented by an ellipse.
 Following are two use cases for a library system.

24
 Use Case Diagram for Student
Assessment Management System

Grade system

Recor
d
grade
s Student
View grades
Teacher
Distribute
Report cards

Create
report Printing administrator

25 cards
 University Record System (URS)

 A University record system should keep information about its

students and academic staff.
 Records for all university members are to include their id number,
surname, given name, email, address, date of birth, and telephone
number.
 Students and academic staff each have their own unique ID number:
studN (students), acadN (academic employee).
 In addition to the attributes mentioned above:
 Students will also have a list of subjects they are enrolled in. A student
cannot be enrolled in any more than 10 subjects.
 Academic employees will have a salary, and a list of subjects they teach.
An academic can teach no more than 3 subjects.
26
 Some Actions Supported by URS

 The system should be able to handle the following commands.

 Add and remove university members (students, and academic staff)
 Add and Delete subjects
 Assign and Un-assign subjects to students
 Assign and Un-assign subjects to academic staff.

27
 Use Case Diagram - URS System

URS

add
member
system del
user member academic
add subject

del subject

assg subject
unass
subject
enrol subject
student
28 unenrol
subject
THANK YOU