Software Engineering Fundamentals CSC-2073: Lecture No. 33

Software Engineering
Fundamentals
CSC-2073
Lecture No. 33
Dr. Muhammad Adeel
Department of Computer Science
National Textile University
dr.muhammad.adeel.ntu@gmail.com
Last Lecture Review
 Design Principles
– Information Hiding
– Incremental Development
o Fan-in
o Fan-out
– Abstraction
o Functional Abstraction
o Data Abstraction
– Generality
2 Software Engineering - CSC2073

Agenda – What will you Learn Today?
Object Oriented Design

Function Oriented vs. OO Design

Function Oriented Design
 Data is decomposed according to functionality

requirements
 Decomposition revolves around function
F1 F2 F3 F4
DS1 DS2 DS3 DS4

Object-Oriented Design
 OO paradigm focuses both on the

functionality and the data at the same time

Why Object Oriented Design?
 Object-Oriented technology helps in software

modeling of real life objects in a direct and
explicit fashion
 Encapsulate data and processes related to a

real life object or process in a single software
entity

Why Object Oriented Design?
 It also provides a mechanism so that the

object can inherit properties from their
ancestors, just like real-life objects
 An Object-Oriented software system consists

of objects which are:
‒ Hierarchical
‒ Highly Cohesive
‒ Loosely Coupled

OO Design Components

What is Object?
 An object can be defined as a tangible entity

that exhibits some well defined behavior
 An object has:
Identity
State All of the properties of the object and their
current values
Behavior How an object acts and reacts in terms of
its state changes and message passing

What is Class?
 A representation of a type of object
 A class is the blueprint from which the

individual objects are created
 Class is composed of three things:

- Name
- Attributes
- Operations

What is Class?
 A class specifies an interface and defines an

implementation
 The interface consists of the declaration of all

the operations applicable to instances of this
class
 The implementation of a class consists of the

implementation of all the operations

Class vs. Object
Class
Objects

What is Class - UML Notation
Attributes Class Name
Student
Visibly - Name:string
+ public Return Type
- Discipline:string
- private - CGPA:float
# protected + takeClasses():Integer
~ package + getCourseRegister():String
+ prepareNotes():String

Abstract Classes
 An abstract class Abstract Class

Name
implements an abstract
concept
 Main purpose is to be Attributes Vehicle
inherited by other classes - Color
+ Accelerate()
 An abstract class cannot be
instantiated
 If any class contains any Methods
abstract functions, then that

class is also abstract
Abstract Classes
Vehicle
- Color
- Model
+ Accelerate()
+ ApplyBrakes()
Car Bus Truck

Abstract Classes
Shape
+ Draw()
Line Circle Triangle
+ Draw() + Draw() + Draw()

Interfaces
 Interfaces are much like abstract

Interface
classes Name
 Interface is a contract - a class
that implements it is required to <<interface>>
implement all of the methods IDoor
and properties + Open()
 No instances of interfaces can
be created Method
 In interfaces the definition of the
method is not allowed
Why We Need Interfaces?
Vehicle
+ Door()
+ FillFuel()
Car
+ Reverse()

?
??
Vehicle
gn
si
de
+ Door()
t
+ FillFuel()
ec
rr
co
it
Is
Car Motorcycle
+ Reverse() + TurnAround()

Vehicle
<<interface>>
IDoor
+ Door()
+ Open() + FillFuel()
Car Motorcycle
+ Reverse() + TurnAround()

Abstract Class vs. Interface
What is the difference between an interface and an

abstract class?
<<interface>> SomeVehicle
Door
+ Open() + drive()
+ open()
Interface
Abstract class
Non of them can be instantiated
Cannot contain implementation Can (but need not to) contain

implementation

Recap
 Function Oriented vs. OO Design

 OO Design Components
‒ Class vs. Object
‒ Abstract Classes
‒ Interfaces

Last Lecture Review
 Function Oriented vs. OO Design

 OO Design Components
‒ Class vs. Object
‒ Abstract Classes
‒ Interfaces

Object Oriented Design

Relationship Among Classes

Relationships Among Classes
 Association
 Aggregation
 Composition
 Inheritance

Association
 It represents a linkage between two classes
 Associations are bi-directional i.e. both

classes are involved in a relationship
 The line is drawn from the containing to the

contained class

Association - Example
Teacher Course
teaches
+ Salary():int * * + Salary():int
+ Leaves():int + Leaves():int
+ Medical():int + Medical():int

Aggregation
 The relationship between the container and

the contained object is called aggregation
 Aggregation is “has - a” relationship
 A weak Association
 Aggregate object can exist independently

Aggregation - Example
Car Wheel
4

Word
Processing
Document
* * Picture
*
Folder

Tables
1..6 White Board

Chair * Class
1
Multimedia

Composition
 The relationship between the “part” objects

and the “whole” object is known as
Composition
 It’s a strong association
 It contains Objects that live and die together
 It is represented by a filled diamond shape

from child to parent class with association
Composition
 The child class's instance lifecycle is

dependent on the parent class's instance
lifecycle
 The part class can only be related to one

instance of the parent class

Composition - Example
Company Department
1 ..
*

Building
Room

Head
2 Person 2 Leg
Arm
1
Body

Inheritance
 It implies the functionality of data sharing

between Base and Derived class
 All the data members and methods of base

class are available for use in derived class but
not vice-versa
 Derive class extends the functionality of super

class to use the base class methods

Inheritance - Example
Person
- Name
- Age
- Gender
+ EatFood()
+ Walk()
Student Teacher
- Program - Designation
- StudyYear - Salary
+ Study() + TakeClasses()
+ HeldExam() + takeExam

Person
- Name
- Age
- Gender
+ EatFood()
+ Walk()
Student Teacher

Person Doctor
- Name - Designation
- Age - Salary
- Gender
+ CheckUp()
+ EatFood()
+ Prescribe()
+ Walk()
Student Teacher

Person
- Name
- Age
- Gender
+ EatFood()
+ Walk()
Student Doctor Teacher

- Program - Designation - Designation
- StudyYear - Salary - Salary
+ Study() + CheckUp() + TakeClasses()
+ HeldExam() + Prescribe() + takeExam

Recap
 Relationship among Classes

1) Association
2) Aggregation
3) Composition
4) Inheritance

Questions

Last Lecture Review
 Relationship among Classes

1) Association
2) Aggregation
3) Composition
4) Inheritance

Abbot’s Textual Analysis Sequence Diagrams

Announcement
 7th July 2021 (SRS)

 14th July 2021
(Design Document)
 28st July 2021
(Test Document)
Course Project Submission

Abbot’s Textual Analysis

 “Textual Analysis” is a working technique used

to extract model element information from
unstructured information systematically.”
 It was initially developed by Abbot and then
extended by Graham and others
 In this technique different parts of speech are

identified within the text of the specification
and these parts are modeled using different
components
1) A common noun in the informal strategy

suggests a data type
2) A proper noun suggests an object
3) A verb, attribute, predicate, or descriptive

expression suggests an operator
4) The control structures are implied in a

straightforward way by the English
Part of Speech Model Component Example
Proper Noun Instance, Object Ahmad
Common Noun Class, Type, Role Student, Teacher
Doing Verb Operation buy
Being Verb Classification is a horse, is a book
Having Verb Composition Fan has wings
Adjective Phrase Association, The customer with
Operation children.
The customer who
bought the Kite.
Intransitive Verb Exception or Event depend

Abbot’s Textual Analysis - Example
 The customer enters the store to buy a toy. He

has to be a toy that his daughter likes and it
must cost less than 50 Euros. He tries a video
game, which uses a data glove and a head-
mounted display. He likes it. An assistant helps
him. The suitability of the game depends on the
age of the child. His daughter is only 3 years
old. The assistant recommends another type of
toy, namely the board game “Monopoly".

Example Part Of Speech UML Model

Component
“Monopoly” proper noun object
toy improper noun class
buy doing verb operation
recommend doing verb operation
is-a being verb inheritance
has-a having verb aggregation
must be modal verb constraint
dangerous adjective attribute
enter transitive verb operation
depends on intransitive verb constraint,
association

Customer Store
+ enter()
Daughter
- age
Videogame
suitable
Toy
- price
Boardgame +buy()
+ like()

Interaction Diagrams

Interaction Diagrams
 Interaction Diagrams depict the dynamic

behavior of the system
 A set of messages exchanged among a set of

objects
 Often used to model the way a use case is

realized through a sequence of messages
between objects

Purpose of Interaction Diagrams
 Model interactions between objects
 Assist in understanding how a system (a use

case) actually works
 Verify that a use case description can be

supported by the existing classes
 Identify responsibilities/operations and assign

them to classes

Software Engineering Fundamentals CSC-2073: Lecture No. 33

Uploaded by

Copyright:

Available Formats

Software Engineering Fundamentals CSC-2073: Lecture No. 33

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Engineering Fundamentals CSC-2073: Lecture No. 33

Uploaded by

Copyright:

Available Formats

Software Engineering

2 Software Engineering - CSC2073

Object Oriented Design

3 Software Engineering - CSC2073

4 Software Engineering - CSC2073

 Data is decomposed according to functionality

DS1 DS2 DS3 DS4

5 Software Engineering - CSC2073

 OO paradigm focuses both on the

6 Software Engineering - CSC2073

 Object-Oriented technology helps in software

 Encapsulate data and processes related to a

7 Software Engineering - CSC2073

 It also provides a mechanism so that the

 An Object-Oriented software system consists

8 Software Engineering - CSC2073

9 Software Engineering - CSC2073

 An object can be defined as a tangible entity

10 Software Engineering - CSC2073

 A representation of a type of object

 A class is the blueprint from which the

 Class is composed of three things:

11 Software Engineering - CSC2073

 A class specifies an interface and defines an

 The interface consists of the declaration of all

 The implementation of a class consists of the

12 Software Engineering - CSC2073

13 Software Engineering - CSC2073

14 Software Engineering - CSC2073

 An abstract class Abstract Class

abstract functions, then that

Car Bus Truck

16 Software Engineering - CSC2073

Line Circle Triangle

+ Draw() + Draw() + Draw()

17 Software Engineering - CSC2073

 Interfaces are much like abstract

19 Software Engineering - CSC2073

20 Software Engineering - CSC2073

21 Software Engineering - CSC2073

What is the difference between an interface and an

Non of them can be instantiated

Cannot contain implementation Can (but need not to) contain

22 Software Engineering - CSC2073

 Function Oriented vs. OO Design

23 Software Engineering - CSC2073

 Function Oriented vs. OO Design

24 Software Engineering - CSC2073

Object Oriented Design

25 Software Engineering - CSC2073

26 Software Engineering - CSC2073

27 Software Engineering - CSC2073

 It represents a linkage between two classes

 Associations are bi-directional i.e. both

 The line is drawn from the containing to the

28 Software Engineering - CSC2073

29 Software Engineering - CSC2073

 The relationship between the container and

 Aggregation is “has - a” relationship