Course Title: Software Component Design

Course code:-SWEG3093

Muleta Taye (MSc)

College of Mechanical and Electrical Engineering
Department of Software Engineering
E-mail:-tayemuleta09@yahoo.com
Target Dept.:-Software Engineering(IV)

January 11, 2020

Objective Of the Course

Apply a wide variety of software designing techniques and tools.

Understanding the different design patterns.
Perform object-oriented design and programming with a high level of
proficiency.
Analyze software in order to improve its efficiency, reliability, and
maintainability.
Course Content

Chapter 1 : Introduction to Low-Level Software Design and Constn

Chapter 2 : Design Pattern
Chapter 3 : Refactoring
Chapter 4 : Thread and Thread Synchronization
Chapter 5 : Inter-Thread and Process communication
Chapter 6 : Disciplined Approaches to Design Change using XP
Teaching Methods and Assessment:

Lectures Assesment Method Weight

Assignment I 10%
Laboratory Assignment II 5%
project works Project Work 10%
Test- I 10%
Assignment and Test II 15%
Final Exam 50%
Exams
 CHAPTER ONE
Introduction to Low-Level Software Design
Where is the Component design ?
Software Development Life Cycle
Object-Oriented based analysis and Design
Component-Based Engineering
Introduction

Definitions
Program : is A set of statements used to instruct a Machine.
Software: Is basically set of programs along with Libraries,
Documentation and related aspect devised for some specific activity.
Software Engineering: Is an engineering discipline that is concerend with
all aspect of software production.

Software Process : set of related activities that take to the production of

Software Product.
Development might be new or Extension of the existing
Software process must include
1 Specification : Functionality and Constriants
2 Design and Implementation : Producing the Software.
3 Validation: Ensure whether it meets the customer needs.
4 Evolution : evolving to meets the changing customer need.
Introduction

Definitions
Program : is A set of statements used to instruct a Machine.
Software: Is basically set of programs along with Libraries,
Documentation and related aspect devised for some specific activity.
Software Engineering: Is an engineering discipline that is concerend with
all aspect of software production.

Software Process : set of related activities that take to the production of

Software Product.
Development might be new or Extension of the existing
Software process must include
1 Specification : Functionality and Constriants
2 Design and Implementation : Producing the Software.
3 Validation: Ensure whether it meets the customer needs.
4 Evolution : evolving to meets the changing customer need.
Introduction

Definitions
Program : is A set of statements used to instruct a Machine.
Software: Is basically set of programs along with Libraries,
Documentation and related aspect devised for some specific activity.
Software Engineering: Is an engineering discipline that is concerend with
all aspect of software production.

Software Process : set of related activities that take to the production of

Software Product.
Development might be new or Extension of the existing
Software process must include
1 Specification : Functionality and Constriants
2 Design and Implementation : Producing the Software.
3 Validation: Ensure whether it meets the customer needs.
4 Evolution : evolving to meets the changing customer need.
Introduction

Definitions
Program : is A set of statements used to instruct a Machine.
Software: Is basically set of programs along with Libraries,
Documentation and related aspect devised for some specific activity.
Software Engineering: Is an engineering discipline that is concerend with
all aspect of software production.

Software Process : set of related activities that take to the production of

Software Product.
Development might be new or Extension of the existing
Software process must include
1 Specification : Functionality and Constriants
2 Design and Implementation : Producing the Software.
3 Validation: Ensure whether it meets the customer needs.
4 Evolution : evolving to meets the changing customer need.
Introduction

Definitions
Program : is A set of statements used to instruct a Machine.
Software: Is basically set of programs along with Libraries,
Documentation and related aspect devised for some specific activity.
Software Engineering: Is an engineering discipline that is concerend with
all aspect of software production.

Software Process : set of related activities that take to the production of

Software Product.
Development might be new or Extension of the existing
Software process must include
1 Specification : Functionality and Constriants
2 Design and Implementation : Producing the Software.
3 Validation: Ensure whether it meets the customer needs.
4 Evolution : evolving to meets the changing customer need.
Introduction ..

1 Software Specification: refers the Requirement Engineering defining

Service Requirement : that is Functionality of the system
Constriants Identification in the Operation and Dev’t
Goal? Poduction of well-defined Documents considering two level details:
End User and Customer need high-level detail
Activities in Specification include :
Feasibility Study: It is a kind of assesment study
Requirement elicitation and Analysis : involves Gathering requirement
Requirement specification : Gathered information → Document
Reqirement Validation: checking for realism, Consistency and Completeness
2 Software design and Implementation
It Involves 2 Process
Implementation : is the actual software development process where System
Specification is Converted into Exeutable system.
Design: Describe the Structure of the System including;
Data Model and Structure, Algorithm, The Component Design And
Interfaces between system Component.
Introduction ..

1 Software Specification: refers the Requirement Engineering defining

Service Requirement : that is Functionality of the system
Constriants Identification in the Operation and Dev’t
Goal? Poduction of well-defined Documents considering two level details:
End User and Customer need high-level detail
Activities in Specification include :
Feasibility Study: It is a kind of assesment study
Requirement elicitation and Analysis : involves Gathering requirement
Requirement specification : Gathered information → Document
Reqirement Validation: checking for realism, Consistency and Completeness
2 Software design and Implementation
It Involves 2 Process
Implementation : is the actual software development process where System
Specification is Converted into Exeutable system.
Design: Describe the Structure of the System including;
Data Model and Structure, Algorithm, The Component Design And
Interfaces between system Component.
Introduction ..

1 Software Specification: refers the Requirement Engineering defining

Service Requirement : that is Functionality of the system
Constriants Identification in the Operation and Dev’t
Goal? Poduction of well-defined Documents considering two level details:
End User and Customer need high-level detail
Activities in Specification include :
Feasibility Study: It is a kind of assesment study
Requirement elicitation and Analysis : involves Gathering requirement
Requirement specification : Gathered information → Document
Reqirement Validation: checking for realism, Consistency and Completeness
2 Software design and Implementation
It Involves 2 Process
Implementation : is the actual software development process where System
Specification is Converted into Exeutable system.
Design: Describe the Structure of the System including;
Data Model and Structure, Algorithm, The Component Design And
Interfaces between system Component.
Introduction ..

1 Software Specification: refers the Requirement Engineering defining

Service Requirement : that is Functionality of the system
Constriants Identification in the Operation and Dev’t
Goal? Poduction of well-defined Documents considering two level details:
End User and Customer need high-level detail
Activities in Specification include :
Feasibility Study: It is a kind of assesment study
Requirement elicitation and Analysis : involves Gathering requirement
Requirement specification : Gathered information → Document
Reqirement Validation: checking for realism, Consistency and Completeness
2 Software design and Implementation
It Involves 2 Process
Implementation : is the actual software development process where System
Specification is Converted into Exeutable system.
Design: Describe the Structure of the System including;
Data Model and Structure, Algorithm, The Component Design And
Interfaces between system Component.
Introduction ..

1 Software Specification: refers the Requirement Engineering defining

Service Requirement : that is Functionality of the system
Constriants Identification in the Operation and Dev’t
Goal? Poduction of well-defined Documents considering two level details:
End User and Customer need high-level detail
Activities in Specification include :
Feasibility Study: It is a kind of assesment study
Requirement elicitation and Analysis : involves Gathering requirement
Requirement specification : Gathered information → Document
Reqirement Validation: checking for realism, Consistency and Completeness
2 Software design and Implementation
It Involves 2 Process
Implementation : is the actual software development process where System
Specification is Converted into Exeutable system.
Design: Describe the Structure of the System including;
Data Model and Structure, Algorithm, The Component Design And
Interfaces between system Component.
Introduction ..

1 Software Specification: refers the Requirement Engineering defining

Service Requirement : that is Functionality of the system
Constriants Identification in the Operation and Dev’t
Goal? Poduction of well-defined Documents considering two level details:
End User and Customer need high-level detail
Activities in Specification include :
Feasibility Study: It is a kind of assesment study
Requirement elicitation and Analysis : involves Gathering requirement
Requirement specification : Gathered information → Document
Reqirement Validation: checking for realism, Consistency and Completeness
2 Software design and Implementation
It Involves 2 Process
Implementation : is the actual software development process where System
Specification is Converted into Exeutable system.
Design: Describe the Structure of the System including;
Data Model and Structure, Algorithm, The Component Design And
Interfaces between system Component.
Introduction ..

1 Software Specification: refers the Requirement Engineering defining

Service Requirement : that is Functionality of the system
Constriants Identification in the Operation and Dev’t
Goal? Poduction of well-defined Documents considering two level details:
End User and Customer need high-level detail
Activities in Specification include :
Feasibility Study: It is a kind of assesment study
Requirement elicitation and Analysis : involves Gathering requirement
Requirement specification : Gathered information → Document
Reqirement Validation: checking for realism, Consistency and Completeness
2 Software design and Implementation
It Involves 2 Process
Implementation : is the actual software development process where System
Specification is Converted into Exeutable system.
Design: Describe the Structure of the System including;
Data Model and Structure, Algorithm, The Component Design And
Interfaces between system Component.
Introduction ..

1 Software Specification: refers the Requirement Engineering defining

Service Requirement : that is Functionality of the system
Constriants Identification in the Operation and Dev’t
Goal? Poduction of well-defined Documents considering two level details:
End User and Customer need high-level detail
Activities in Specification include :
Feasibility Study: It is a kind of assesment study
Requirement elicitation and Analysis : involves Gathering requirement
Requirement specification : Gathered information → Document
Reqirement Validation: checking for realism, Consistency and Completeness
2 Software design and Implementation
It Involves 2 Process
Implementation : is the actual software development process where System
Specification is Converted into Exeutable system.
Design: Describe the Structure of the System including;
Data Model and Structure, Algorithm, The Component Design And
Interfaces between system Component.
Introduction ..

1 Software Specification: refers the Requirement Engineering defining

Service Requirement : that is Functionality of the system
Constriants Identification in the Operation and Dev’t
Goal? Poduction of well-defined Documents considering two level details:
End User and Customer need high-level detail
Activities in Specification include :
Feasibility Study: It is a kind of assesment study
Requirement elicitation and Analysis : involves Gathering requirement
Requirement specification : Gathered information → Document
Reqirement Validation: checking for realism, Consistency and Completeness
2 Software design and Implementation
It Involves 2 Process
Implementation : is the actual software development process where System
Specification is Converted into Exeutable system.
Design: Describe the Structure of the System including;
Data Model and Structure, Algorithm, The Component Design And
Interfaces between system Component.
Introduction ..

Figure: General Model for Design process

Design process involves :

High-level design (Architectural Design):
Interface Design:
Database Design:
Component Design(Low-level design):
Introduction ..

1 High-level design (Architectural Design):

Identify the Overall Structure of the System inlcuding Major Components,
their relashionship and Distribution logic.
2 Interface Design:
a clearly and unambigiously the interfaces between system component is
defined.
3 Database Design:
Design the System Data structure and how system data is represented in
database.
4 Component Design(Low-level design)
Taking each Major Component and design in detail how they operate.
Software Development Roadmap

Software Development life cycle(SDLC): Series of steps where product

goes via.
Do You think Life Cycle of product is the Same?: Nop it is Different
A number of LC models:
Build-and-Fix Model
The Waterfall Model
The Rapid-Prototyping Model
Boehm’s Spiral Model
Incremental Model
Synchronize-and-Stablize model

1 Build-and-Fix Model
There is NO specification or design attempt in this model.
The Engineers build the SW by reworking as many times as necessary to
satisfy customer.
Un-Satisfactory Model
Software Development Roadmap

Software Development life cycle(SDLC): Series of steps where product

goes via.
Do You think Life Cycle of product is the Same?: Nop it is Different
A number of LC models:
Build-and-Fix Model
The Waterfall Model
The Rapid-Prototyping Model
Boehm’s Spiral Model
Incremental Model
Synchronize-and-Stablize model

1 Build-and-Fix Model
There is NO specification or design attempt in this model.
The Engineers build the SW by reworking as many times as necessary to
satisfy customer.
Un-Satisfactory Model
Software Development Roadmap...

2 Waterfall Model
The First published Model and classical model in SDLC
Widely used in government projects and in many major companies
Is Plan-Driven-Process - ??
Must be Planned and scheduled every process activities before moving to the
work
Two versions :
Pure Waterfall Model : There is Overlapping phases. starts @ System
Requirement → Analysis → Design → Implemenation → Maintenance → Retire
Modified Waterfall Model : Enables the phases to overlap when needed
2 Rapid Prototyping Model
Is a working model functionally equivalent to the subset of the products.
The first Step is to Rapid Prototype let the clients and users interact and
experiemetn with the prototype.
If the Client is OK → Specification is drawn
Software Development Roadmap...

2 Waterfall Model
The First published Model and classical model in SDLC
Widely used in government projects and in many major companies
Is Plan-Driven-Process - ??
Must be Planned and scheduled every process activities before moving to the
work
Two versions :
Pure Waterfall Model : There is Overlapping phases. starts @ System
Requirement → Analysis → Design → Implemenation → Maintenance → Retire
Modified Waterfall Model : Enables the phases to overlap when needed
2 Rapid Prototyping Model
Is a working model functionally equivalent to the subset of the products.
The first Step is to Rapid Prototype let the clients and users interact and
experiemetn with the prototype.
If the Client is OK → Specification is drawn
Software Development Roadmap...

2 Waterfall Model
The First published Model and classical model in SDLC
Widely used in government projects and in many major companies
Is Plan-Driven-Process - ??
Must be Planned and scheduled every process activities before moving to the
work
Two versions :
Pure Waterfall Model : There is Overlapping phases. starts @ System
Requirement → Analysis → Design → Implemenation → Maintenance → Retire
Modified Waterfall Model : Enables the phases to overlap when needed
2 Rapid Prototyping Model
Is a working model functionally equivalent to the subset of the products.
The first Step is to Rapid Prototype let the clients and users interact and
experiemetn with the prototype.
If the Client is OK → Specification is drawn
Software Development Roadmap...

Figure: Build-and-Fix
Figure: Rapid Protoyping
Model Figure: Waterfall Model
Model
Recall the issues on the other SDLC Model ....
Software Development Roadmap...

Figure: Build-and-Fix
Figure: Rapid Protoyping
Model Figure: Waterfall Model
Model
Recall the issues on the other SDLC Model ....
What is Object-Orientation ..
Is about viewing and modeling the system as a set of interacting and
interrelated objects.
Principles/features of Object-Orientation

Design model : Shows the object / object class in the system and their
relationship between them.
Two Type of deisgn model n OOD :
1 Static model : indicate the static structure of the system using object class
and their relationship.
2 Dynamic model : the dynamic structure of the system and show the
interaction between objects in the system.
What is Object-Orientation ..
Is about viewing and modeling the system as a set of interacting and
interrelated objects.
Principles/features of Object-Orientation

Design model : Shows the object / object class in the system and their
relationship between them.
Two Type of deisgn model n OOD :
1 Static model : indicate the static structure of the system using object class
and their relationship.
2 Dynamic model : the dynamic structure of the system and show the
interaction between objects in the system.
What is Object-Orientation ..
Is about viewing and modeling the system as a set of interacting and
interrelated objects.
Principles/features of Object-Orientation

Design model : Shows the object / object class in the system and their
relationship between them.
Two Type of deisgn model n OOD :
1 Static model : indicate the static structure of the system using object class
and their relationship.
2 Dynamic model : the dynamic structure of the system and show the
interaction between objects in the system.
Object-Oriented based Design (OOAD)

OOAD is semi-formal specification and design technique for the Object

Oriented Paradigm.
Mainly Involves :
Identifying Objects
Determining Attributes
setting the relationship between Object
OOA involves Three (3) steps :
1 Use-Case Modeling
”Use-case”: describe the Functionality of the product to be constructed.
Provides a generic description of the Overall functionality.
Interaction b/n Classes of the product and and the user of the product
2 Class Modeling
In this Step Classs and Only their attribute extracted and represented in
ER-diagram
What about the methods ? OOD phase
Classes are deduced from the use-case diagram
Class Exraction techniques (Assignment ...
Object-Oriented based Design (OOAD)

OOAD is semi-formal specification and design technique for the Object

Oriented Paradigm.
Mainly Involves :
Identifying Objects
Determining Attributes
setting the relationship between Object
OOA involves Three (3) steps :
1 Use-Case Modeling
”Use-case”: describe the Functionality of the product to be constructed.
Provides a generic description of the Overall functionality.
Interaction b/n Classes of the product and and the user of the product
2 Class Modeling
In this Step Classs and Only their attribute extracted and represented in
ER-diagram
What about the methods ? OOD phase
Classes are deduced from the use-case diagram
Class Exraction techniques (Assignment ...
Object-Oriented based Design (OOAD)

OOAD is semi-formal specification and design technique for the Object

Oriented Paradigm.
Mainly Involves :
Identifying Objects
Determining Attributes
setting the relationship between Object
OOA involves Three (3) steps :
1 Use-Case Modeling
”Use-case”: describe the Functionality of the product to be constructed.
Provides a generic description of the Overall functionality.
Interaction b/n Classes of the product and and the user of the product
2 Class Modeling
In this Step Classs and Only their attribute extracted and represented in
ER-diagram
What about the methods ? OOD phase
Classes are deduced from the use-case diagram
Class Exraction techniques (Assignment ...
Object-Oriented based Design (OOAD)

OOAD is semi-formal specification and design technique for the Object

Oriented Paradigm.
Mainly Involves :
Identifying Objects
Determining Attributes
setting the relationship between Object
OOA involves Three (3) steps :
1 Use-Case Modeling
”Use-case”: describe the Functionality of the product to be constructed.
Provides a generic description of the Overall functionality.
Interaction b/n Classes of the product and and the user of the product
2 Class Modeling
In this Step Classs and Only their attribute extracted and represented in
ER-diagram
What about the methods ? OOD phase
Classes are deduced from the use-case diagram
Class Exraction techniques (Assignment ...
Object-Oriented based analysis and Design (OOAD)..

3 Dynamic Modeling
Determine the actions performed by or to each class or subclass.
Presented in the form of diagram Called State diagram
This step is Action-Oriented Step
For Example :- A product is to be installed to control n elevetors in a building
with m floors. The problem concerns the logic required to move elevetors
between floors according to ff constriants.
1 Each elevetors has setof m buttons one for each floor. These illumnate
when pressed and cause the elevetor to visit the corresponding floor. The
illumination cancelled when the corresponding floor is visited by elevator.
2 Each floor, except the ist floor and the top floor has 2 buttons,One to
request ↑ and other to request ↓
3 When an elevator has no requests,it remains at its current floor with its
doors closed.
Object-Oriented based analysis and Design (OOAD)...

Use-Case Diagram : What ddo you think is the interaction b/n user and
elevator ?
User Press button to get the elevator
User press floor button to request the elevator to stop at specific floor

Figure: Use-case for elevator problem

Go for the Class Modeling and Dynamic Modeling ....

Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
Component Based Engineering

What are Components ?

Are high-level abstraction than Objects which are defined by interfaces OR
Are independent software units that can be composed with other others to
create Software system
Component Based-Software Engineering (CBSE)
is reuse based Approach or
a process of defining, implementing and integrating/composing loosely
coopled, independent components into One big software Product.
CBSE provides good design principle that supoort the construction of
understandable and maintainable SW :
Components Independent: don’t interfere with each other
Allow Components to communicate with well-defined interfaces
The essentials Of CBSE :
1 Independent components are completely specified by interfaces. (Interface
defination and Implementation must be clearly separated)
2 Component Standards:enclosed in Component model employed to facilitate
the Composition of Components.
3 Middleware: provides software support for component integration.
4 Development Process
X-tistics of Components

Component Characteristics Description

Standardaized
Component standardization means that component
used in CBSE has to conform To standard component
model.

Independent
Should be self-contaied possibly be composed and
deployed without requiring other specific component.

Composable
Must able be integrated, All external interaction must
happen via Publicly defined interfaces

Deployable
Self-contained and able to operate as stand-alone
entityon component platform provides implementaion
of the component model.

Documented
Must be fully documented so potential users can
decide whether or not the components meet their
needs.
X-tistics of Components

Component Characteristics Description

Standardaized
Component standardization means that component
used in CBSE has to conform To standard component
model.

Independent
Should be self-contaied possibly be composed and
deployed without requiring other specific component.

Composable
Must able be integrated, All external interaction must
happen via Publicly defined interfaces

Deployable
Self-contained and able to operate as stand-alone
entityon component platform provides implementaion
of the component model.

Documented
Must be fully documented so potential users can
decide whether or not the components meet their
needs.
X-tistics of Components

Component Characteristics Description

Standardaized
Component standardization means that component
used in CBSE has to conform To standard component
model.

Independent
Should be self-contaied possibly be composed and
deployed without requiring other specific component.

Composable
Must able be integrated, All external interaction must
happen via Publicly defined interfaces

Deployable
Self-contained and able to operate as stand-alone
entityon component platform provides implementaion
of the component model.

Documented
Must be fully documented so potential users can
decide whether or not the components meet their
needs.
X-tistics of Components

Component Characteristics Description

Standardaized
Component standardization means that component
used in CBSE has to conform To standard component
model.

Independent
Should be self-contaied possibly be composed and
deployed without requiring other specific component.

Composable
Must able be integrated, All external interaction must
happen via Publicly defined interfaces

Deployable
Self-contained and able to operate as stand-alone
entityon component platform provides implementaion
of the component model.

Documented
Must be fully documented so potential users can
decide whether or not the components meet their
needs.
X-tistics of Components

Component Characteristics Description

Standardaized
Component standardization means that component
used in CBSE has to conform To standard component
model.

Independent
Should be self-contaied possibly be composed and
deployed without requiring other specific component.

Composable
Must able be integrated, All external interaction must
happen via Publicly defined interfaces

Deployable
Self-contained and able to operate as stand-alone
entityon component platform provides implementaion
of the component model.

Documented
Must be fully documented so potential users can
decide whether or not the components meet their
needs.
X-tistics of Components

Component Characteristics Description

Standardaized
Component standardization means that component
used in CBSE has to conform To standard component
model.

Independent
Should be self-contaied possibly be composed and
deployed without requiring other specific component.

Composable
Must able be integrated, All external interaction must
happen via Publicly defined interfaces

Deployable
Self-contained and able to operate as stand-alone
entityon component platform provides implementaion
of the component model.

Documented
Must be fully documented so potential users can
decide whether or not the components meet their
needs.
Component Based Engineering

Better Sometimes to think Components as A provider of one or more

services. → When Systems/Sub-system needs a services.
Such Component Viewing as service provider emphasize 2 X-tiscs of
Reusable components:
1 The component independency as executable entity defined by interfacs.
2 The services provided by components are available via interfaces and the
interaction also via interfaces.
Interfaces are a logical tools where communication amoung components
happen.
Comp. has two interfaces
1 Provides Interface
2 Requires Interface
Component Based Engineering

1 Provides Interface :
Defines the services offered or given by the components.
Basically defines Methods invoked by other components.
In UML Component Diagram represented by circle
2 Requires Interface
Specifies What services must be provided by other components in the
system for proper operation.
Has Methods.
In UML Component Diagram represented by semi-circle/arc

Figure: Component Interfaces

Component Based Engineering

1 Provides Interface :
Defines the services offered or given by the components.
Basically defines Methods invoked by other components.
In UML Component Diagram represented by circle
2 Requires Interface
Specifies What services must be provided by other components in the
system for proper operation.
Has Methods.
In UML Component Diagram represented by semi-circle/arc

Figure: Component Interfaces

Component Based Engineering

1 Provides Interface :
Defines the services offered or given by the components.
Basically defines Methods invoked by other components.
In UML Component Diagram represented by circle
2 Requires Interface
Specifies What services must be provided by other components in the
system for proper operation.
Has Methods.
In UML Component Diagram represented by semi-circle/arc

Figure: Component Interfaces

Component Models (CM)
Component model
Are definition of set of standards for Component implemenation,
documentation and deployement.
is a way to ensure the interoperability of various components.
Many components are available However, Vital Models are WebService
Model, Sun’s Enterprise Java Beans(EJB) and other .
Basic Elements of Component Model are:
1 Interfaces
2 Component Usage
3 Deployement and Use

Figure: Elements of Component Model

Component Models (CM)

1 Interfaces
Used to define components of systems.
CM specifies elements (i.e. Operation names, parameters and exception
logics) of interfaces and how they are defined.
Theoretically, CM also defines the programming language used to define
interfaces.
Specific interfaces defined by the components for composing component
infrastructure. (provides for security and managment purpose)
2 Component Usage
Components must have Unique name: coz might be distributed and
remotely accessed.
Component Meta-data is a data about the components itself. (information
about its interfaces and attributes)
3 Deployement and Use
The CM also defines specification of how components should be packaged
for deployement as independents as wel as executable entities.
Evolution Support: as the requirement changes components will have to to
be changed and replaced.
Component Models (CM)

1 Interfaces
Used to define components of systems.
CM specifies elements (i.e. Operation names, parameters and exception
logics) of interfaces and how they are defined.
Theoretically, CM also defines the programming language used to define
interfaces.
Specific interfaces defined by the components for composing component
infrastructure. (provides for security and managment purpose)
2 Component Usage
Components must have Unique name: coz might be distributed and
remotely accessed.
Component Meta-data is a data about the components itself. (information
about its interfaces and attributes)
3 Deployement and Use
The CM also defines specification of how components should be packaged
for deployement as independents as wel as executable entities.
Evolution Support: as the requirement changes components will have to to
be changed and replaced.
Component Models (CM)

1 Interfaces
Used to define components of systems.
CM specifies elements (i.e. Operation names, parameters and exception
logics) of interfaces and how they are defined.
Theoretically, CM also defines the programming language used to define
interfaces.
Specific interfaces defined by the components for composing component
infrastructure. (provides for security and managment purpose)
2 Component Usage
Components must have Unique name: coz might be distributed and
remotely accessed.
Component Meta-data is a data about the components itself. (information
about its interfaces and attributes)
3 Deployement and Use
The CM also defines specification of how components should be packaged
for deployement as independents as wel as executable entities.
Evolution Support: as the requirement changes components will have to to
be changed and replaced.
Component Models (CM)

Component may be implemented as program unit or as External Service

So that the CM set out the services provided by Middleware for executing
components.
The services offered by a Component model implementation are :
1 Plaform Services
Fundamental services must be available in all Component based System.
Enable Components to communicate and interoperate in distributed fashion.
Services: Addressing, Interface Definition, Exception Mgmt, Component
communication
2 Support Services
Common Services that are likely to be required by other component.
Services: Comp.Mgmt, Transaction Mgmt, Resource Mgmt , Security and
Others
Component Models (CM)

Component may be implemented as program unit or as External Service

So that the CM set out the services provided by Middleware for executing
components.
The services offered by a Component model implementation are :
1 Plaform Services
Fundamental services must be available in all Component based System.
Enable Components to communicate and interoperate in distributed fashion.
Services: Addressing, Interface Definition, Exception Mgmt, Component
communication
2 Support Services
Common Services that are likely to be required by other component.
Services: Comp.Mgmt, Transaction Mgmt, Resource Mgmt , Security and
Others
Component Models (CM)

Component may be implemented as program unit or as External Service

So that the CM set out the services provided by Middleware for executing
components.
The services offered by a Component model implementation are :
1 Plaform Services
Fundamental services must be available in all Component based System.
Enable Components to communicate and interoperate in distributed fashion.
Services: Addressing, Interface Definition, Exception Mgmt, Component
communication
2 Support Services
Common Services that are likely to be required by other component.
Services: Comp.Mgmt, Transaction Mgmt, Resource Mgmt , Security and
Others
Component Composition

Component Composition
is a process/ mechanics of integrating various components with each other
and with specially written glue code for creating system as well as another
components.
Three Flavours:
1 Sequential composition
2 Hierarchical composition
3 Additive composition

1 Sequential composition
is a way of building distnict/new component from two existing components
by calling them sequentially. (Provides interface)
2 Hierarchical composition
Occurs when One component calls directly on the services provided by
another component.
So that the invoked component provides services invoking component.
3 Additive composition
is Combination of two or more components to build new component based
on their functionality.
Component Composition

Component Composition
is a process/ mechanics of integrating various components with each other
and with specially written glue code for creating system as well as another
components.
Three Flavours:
1 Sequential composition
2 Hierarchical composition
3 Additive composition

1 Sequential composition
is a way of building distnict/new component from two existing components
by calling them sequentially. (Provides interface)
2 Hierarchical composition
Occurs when One component calls directly on the services provided by
another component.
So that the invoked component provides services invoking component.
3 Additive composition
is Combination of two or more components to build new component based
on their functionality.
Component Composition

Component Composition
is a process/ mechanics of integrating various components with each other
and with specially written glue code for creating system as well as another
components.
Three Flavours:
1 Sequential composition
2 Hierarchical composition
3 Additive composition

1 Sequential composition
is a way of building distnict/new component from two existing components
by calling them sequentially. (Provides interface)
2 Hierarchical composition
Occurs when One component calls directly on the services provided by
another component.
So that the invoked component provides services invoking component.
3 Additive composition
is Combination of two or more components to build new component based
on their functionality.
Component Models (CM)

Sequential composition

Hierarchical composition

Additive composition
Component Models (CM)

Possibly to use all type of composition But we need ”Glue code” that links
the components.
When Components are are developed independently for reuse :
Incompatability might occur :- Interfaces of the component needs to be
composed might not be the same.
Three type of Incompatability :
1 Parameter Incompatability
Having the same interface name but d/t in parameter number, type
2 Operation Incompatability
The difference of operation in Both interfaces
3 Operation Incompatability
The Provides interface of the component is subset of requires interface of
another component and vice versa
So what is the solution for incompatability ????: ”Adaptors”
Component Models (CM)

Possibly to use all type of composition But we need ”Glue code” that links
the components.
When Components are are developed independently for reuse :
Incompatability might occur :- Interfaces of the component needs to be
composed might not be the same.
Three type of Incompatability :
1 Parameter Incompatability
Having the same interface name but d/t in parameter number, type
2 Operation Incompatability
The difference of operation in Both interfaces
3 Operation Incompatability
The Provides interface of the component is subset of requires interface of
another component and vice versa
So what is the solution for incompatability ????: ”Adaptors”
Component Models (CM)

Possibly to use all type of composition But we need ”Glue code” that links
the components.
When Components are are developed independently for reuse :
Incompatability might occur :- Interfaces of the component needs to be
composed might not be the same.
Three type of Incompatability :
1 Parameter Incompatability
Having the same interface name but d/t in parameter number, type
2 Operation Incompatability
The difference of operation in Both interfaces
3 Operation Incompatability
The Provides interface of the component is subset of requires interface of
another component and vice versa
So what is the solution for incompatability ????: ”Adaptors”
Component Models (CM)

Possibly to use all type of composition But we need ”Glue code” that links
the components.
When Components are are developed independently for reuse :
Incompatability might occur :- Interfaces of the component needs to be
composed might not be the same.
Three type of Incompatability :
1 Parameter Incompatability
Having the same interface name but d/t in parameter number, type
2 Operation Incompatability
The difference of operation in Both interfaces
3 Operation Incompatability
The Provides interface of the component is subset of requires interface of
another component and vice versa
So what is the solution for incompatability ????: ”Adaptors”
Component Models (CM)

Adaptors are a kind of glue code that reconcile the interfaces of

components OR
are components that converts one interface to another.
(provides interface
requires interface)
Example:
911 call for Emergency Services

Adaptor is required to compose the two

components
Assume the Components as a class
callAddress =addressFinder.location(pn);
postCode =
posCodeAdaptor.getPostCode(callAddress);
mapper.displayMap(postCode, scale);
 Chapter Two
Design Patterns

Overview of Design patterns

Types of Design patterns
Applying design patterns
Common design patterns: Singleton, Observer, Iterator
Overiew of Design patterns

Is Software designing is difficult task ?

Of course Yes specially OO principle
Every Engineers might use his own way during implementation→ Problem
Common problem :
How to structure class and their element?
How to instantiate Objects ?
How to let Objects interact ?
How to develop Reusable Codes ?
How to code loosly coopled codes ?
So What is the Solution ? To have standard template
Overiew of Design patterns

Is Software designing is difficult task ?

Of course Yes specially OO principle
Every Engineers might use his own way during implementation→ Problem
Common problem :
How to structure class and their element?
How to instantiate Objects ?
How to let Objects interact ?
How to develop Reusable Codes ?
How to code loosly coopled codes ?
So What is the Solution ? To have standard template
Overiew of Design patterns

Is Software designing is difficult task ?

Of course Yes specially OO principle
Every Engineers might use his own way during implementation→ Problem
Common problem :
How to structure class and their element?
How to instantiate Objects ?
How to let Objects interact ?
How to develop Reusable Codes ?
How to code loosly coopled codes ?
So What is the Solution ? To have standard template
Overiew of Design patterns

Is Software designing is difficult task ?

Of course Yes specially OO principle
Every Engineers might use his own way during implementation→ Problem
Common problem :
How to structure class and their element?
How to instantiate Objects ?
How to let Objects interact ?
How to develop Reusable Codes ?
How to code loosly coopled codes ?
So What is the Solution ? To have standard template
Overiew of Design patterns

A well-defined template for solving common problems.

It is also Industry Standard and Language independent.

Defination
Design pattern is a general repeatable solution to a
commonly occurring problem in software design.
What is Design A design pattern is not a finished design that can be
Patterns In transformed directly into code.
Software It is a description or template for how to solve a problem
that can be used in many different situations.
Engineering?
Christopher Alexander
”A design pattern describes a problem that occurs over and
over again in our environment, and then describes the core of
the solution to that problem, in such a way that you can use
the solution over and over again a million ways, without ever
doing it the same way twice.”
Overiew of Design patterns

A well-defined template for solving common problems.

It is also Industry Standard and Language independent.

Defination
Design pattern is a general repeatable solution to a
commonly occurring problem in software design.
What is Design A design pattern is not a finished design that can be
Patterns In transformed directly into code.
Software It is a description or template for how to solve a problem
that can be used in many different situations.
Engineering?
Christopher Alexander
”A design pattern describes a problem that occurs over and
over again in our environment, and then describes the core of
the solution to that problem, in such a way that you can use
the solution over and over again a million ways, without ever
doing it the same way twice.”
Overiew of Design patterns

A well-defined template for solving common problems.

It is also Industry Standard and Language independent.

Defination
Design pattern is a general repeatable solution to a
commonly occurring problem in software design.
What is Design A design pattern is not a finished design that can be
Patterns In transformed directly into code.
Software It is a description or template for how to solve a problem
that can be used in many different situations.
Engineering?
Christopher Alexander
”A design pattern describes a problem that occurs over and
over again in our environment, and then describes the core of
the solution to that problem, in such a way that you can use
the solution over and over again a million ways, without ever
doing it the same way twice.”
Overiew of Design patterns

A well-defined template for solving common problems.

It is also Industry Standard and Language independent.

Defination
Design pattern is a general repeatable solution to a
commonly occurring problem in software design.
What is Design A design pattern is not a finished design that can be
Patterns In transformed directly into code.
Software It is a description or template for how to solve a problem
that can be used in many different situations.
Engineering?
Christopher Alexander
”A design pattern describes a problem that occurs over and
over again in our environment, and then describes the core of
the solution to that problem, in such a way that you can use
the solution over and over again a million ways, without ever
doing it the same way twice.”
Overiew of Design patterns

There are two core reason for the existence of Design patterns.
1 Design patterns streamlines communication between developers.
It Serve as a common communication language between software developers.
2 They are off-the-shelf solution-forms for common problem-forms.
Help you to identify problems and solve that happened in Off-the-shelf Products.
Benefits of Design patterens:
Highly Maintainable Product
Enhanced Code Reusability
Improve the development of loosely coupled Products
Minimize the Total cost of Ownership
Pattern has four essential elements:
1 Pattern Name:
Describes a design problem, its solutions, and consequences in a word or two.
This is what the pattern will be referred to as → Association
2 The Problem:
This describes the scope of the problem the design pattern is solving.
Describes when to apply the pattern.
Also describe the problem and the application domain/context domain
describe specific design problems
Overiew of Design patterns

3 Solution
Describes the elements that make up the design, their relationships,
responsibilities, and collaborations.
Doesn’t Explain a particular concrete design or implementation,
3 Consequences
are the results and trade-offs of applying the pattern.
The consequences for software often concern space and time trade-offs

20+ design patterens are available.

Categorized in to Three
1 Creational Design patterens
2 Structural Design patterens
3 Behavioural Design patterens
Overiew of Design patterns

3 Solution
Describes the elements that make up the design, their relationships,
responsibilities, and collaborations.
Doesn’t Explain a particular concrete design or implementation,
3 Consequences
are the results and trade-offs of applying the pattern.
The consequences for software often concern space and time trade-offs

20+ design patterens are available.

Categorized in to Three
1 Creational Design patterens
2 Structural Design patterens
3 Behavioural Design patterens
Overiew of Design patterns

3 Solution
Describes the elements that make up the design, their relationships,
responsibilities, and collaborations.
Doesn’t Explain a particular concrete design or implementation,
3 Consequences
are the results and trade-offs of applying the pattern.
The consequences for software often concern space and time trade-offs

20+ design patterens are available.

Categorized in to Three
1 Creational Design patterens
2 Structural Design patterens
3 Behavioural Design patterens
Overiew of Design patterns

3 Solution
Describes the elements that make up the design, their relationships,
responsibilities, and collaborations.
Doesn’t Explain a particular concrete design or implementation,
3 Consequences
are the results and trade-offs of applying the pattern.
The consequences for software often concern space and time trade-offs

20+ design patterens are available.

Categorized in to Three
1 Creational Design patterens
2 Structural Design patterens
3 Behavioural Design patterens
Types of Design patterens

1 Creational Design patterens

A design patterns which abstract the instantiation process.
And also provide a way to create objects while hiding the creation logic,
rather than instantiating objects directly using new operator.
so helps for deciding which objects need to be created for a given use-case.
Two main theme :
1 They all encapsulate knowledge about which concrete classes the system uses.
2 Hide how instances of these classes are created and put together.
Provide more flexibility on what gets created, who created,
how it is created and when the created.

1 Singelton
2 Factory method
5 Creational Design → 3 Abstract Factory
patterns
4 Builder
5 Prototype
Types of Design patterens

1 Creational Design patterens

A design patterns which abstract the instantiation process.
And also provide a way to create objects while hiding the creation logic,
rather than instantiating objects directly using new operator.
so helps for deciding which objects need to be created for a given use-case.
Two main theme :
1 They all encapsulate knowledge about which concrete classes the system uses.
2 Hide how instances of these classes are created and put together.
Provide more flexibility on what gets created, who created,
how it is created and when the created.

1 Singelton
2 Factory method
5 Creational Design → 3 Abstract Factory
patterns
4 Builder
5 Prototype
Types of Design patterens

1 Creational Design patterens

A design patterns which abstract the instantiation process.
And also provide a way to create objects while hiding the creation logic,
rather than instantiating objects directly using new operator.
so helps for deciding which objects need to be created for a given use-case.
Two main theme :
1 They all encapsulate knowledge about which concrete classes the system uses.
2 Hide how instances of these classes are created and put together.
Provide more flexibility on what gets created, who created,
how it is created and when the created.

1 Singelton
2 Factory method
5 Creational Design → 3 Abstract Factory
patterns
4 Builder
5 Prototype
Types of Design patterens

1 Creational Design patterens

A design patterns which abstract the instantiation process.
And also provide a way to create objects while hiding the creation logic,
rather than instantiating objects directly using new operator.
so helps for deciding which objects need to be created for a given use-case.
Two main theme :
1 They all encapsulate knowledge about which concrete classes the system uses.
2 Hide how instances of these classes are created and put together.
Provide more flexibility on what gets created, who created,
how it is created and when the created.

1 Singelton
2 Factory method
5 Creational Design → 3 Abstract Factory
patterns
4 Builder
5 Prototype
Overiew of Design patterns

Singelton Pattern
The most popular pattern which restricts the instantiation of a class.
And ensures that only one instance of the class exists in the JVM.
Is there techniqe to ensure single object exists And the way accessed? Yes
I A global variable makes an object accessible, but it doesn’t keep you from
instantiating multiple objects
II To make the class itself responsible for keeping track of its sole instance
→ By providing a way to access the instance.
→ The class can ensure that no other instance can be created
Applicability :
There is exactly one instance of a class,
It must be accessible to clients from a well-known access point.
When the sole instance should be extensible by subclassing, and clients should be
able to use an extended instance without modifying their code
Implemenation Consideration:
Ensuring a unique instance
Subclassing the Singleton class
Overiew of Design patterns

Singelton Pattern
The most popular pattern which restricts the instantiation of a class.
And ensures that only one instance of the class exists in the JVM.
Is there techniqe to ensure single object exists And the way accessed? Yes
I A global variable makes an object accessible, but it doesn’t keep you from
instantiating multiple objects
II To make the class itself responsible for keeping track of its sole instance
→ By providing a way to access the instance.
→ The class can ensure that no other instance can be created
Applicability :
There is exactly one instance of a class,
It must be accessible to clients from a well-known access point.
When the sole instance should be extensible by subclassing, and clients should be
able to use an extended instance without modifying their code
Implemenation Consideration:
Ensuring a unique instance
Subclassing the Singleton class
Overiew of Design patterns

Singelton Pattern
The most popular pattern which restricts the instantiation of a class.
And ensures that only one instance of the class exists in the JVM.
Is there techniqe to ensure single object exists And the way accessed? Yes
I A global variable makes an object accessible, but it doesn’t keep you from
instantiating multiple objects
II To make the class itself responsible for keeping track of its sole instance
→ By providing a way to access the instance.
→ The class can ensure that no other instance can be created
Applicability :
There is exactly one instance of a class,
It must be accessible to clients from a well-known access point.
When the sole instance should be extensible by subclassing, and clients should be
able to use an extended instance without modifying their code
Implemenation Consideration:
Ensuring a unique instance
Subclassing the Singleton class
Overiew of Design patterns

Singelton Pattern
The most popular pattern which restricts the instantiation of a class.
And ensures that only one instance of the class exists in the JVM.
Is there techniqe to ensure single object exists And the way accessed? Yes
I A global variable makes an object accessible, but it doesn’t keep you from
instantiating multiple objects
II To make the class itself responsible for keeping track of its sole instance
→ By providing a way to access the instance.
→ The class can ensure that no other instance can be created
Applicability :
There is exactly one instance of a class,
It must be accessible to clients from a well-known access point.
When the sole instance should be extensible by subclassing, and clients should be
able to use an extended instance without modifying their code
Implemenation Consideration:
Ensuring a unique instance
Subclassing the Singleton class
Overiew of Design patterns

Singelton Pattern
The most popular pattern which restricts the instantiation of a class.
And ensures that only one instance of the class exists in the JVM.
Is there techniqe to ensure single object exists And the way accessed? Yes
I A global variable makes an object accessible, but it doesn’t keep you from
instantiating multiple objects
II To make the class itself responsible for keeping track of its sole instance
→ By providing a way to access the instance.
→ The class can ensure that no other instance can be created
Applicability :
There is exactly one instance of a class,
It must be accessible to clients from a well-known access point.
When the sole instance should be extensible by subclassing, and clients should be
able to use an extended instance without modifying their code
Implemenation Consideration:
Ensuring a unique instance
Subclassing the Singleton class
Singelton Pattern

Assume simple class diagram for configuration setting

Implementation :
Create the class structure
Create a object of the class
Create the constructor of the class
Get the only object of the class via getInstance
method
Factory Patterns

Define an interface or abstract class for creating an object but let the
subclasses decide which class to instantiate.
Factory pattern is used when we have a super class with multiple
sub-classes and, based on input, we need to return one of the sub-classes.
This pattern removes the responsibility of instantiation of a class from the
client program to the factory class.
Also referred as Virtual Constructor.
When to apply such Patterns ?
When a class doesn’t know what sub-classes will be required to create.
When a class wants that its sub-classes specify the objects to be created.
When the parent classes choose the creation of objects to its sub-classes.
Important points about Factory Design Pattern:
Keep Factory class Singleton or we can keep the method that returns the
subclass as static.
Based on the input parameter, different subclass is created and returned.
Factory Patterns

Define an interface or abstract class for creating an object but let the
subclasses decide which class to instantiate.
Factory pattern is used when we have a super class with multiple
sub-classes and, based on input, we need to return one of the sub-classes.
This pattern removes the responsibility of instantiation of a class from the
client program to the factory class.
Also referred as Virtual Constructor.
When to apply such Patterns ?
When a class doesn’t know what sub-classes will be required to create.
When a class wants that its sub-classes specify the objects to be created.
When the parent classes choose the creation of objects to its sub-classes.
Important points about Factory Design Pattern:
Keep Factory class Singleton or we can keep the method that returns the
subclass as static.
Based on the input parameter, different subclass is created and returned.
Factory Patterns

Define an interface or abstract class for creating an object but let the
subclasses decide which class to instantiate.
Factory pattern is used when we have a super class with multiple
sub-classes and, based on input, we need to return one of the sub-classes.
This pattern removes the responsibility of instantiation of a class from the
client program to the factory class.
Also referred as Virtual Constructor.
When to apply such Patterns ?
When a class doesn’t know what sub-classes will be required to create.
When a class wants that its sub-classes specify the objects to be created.
When the parent classes choose the creation of objects to its sub-classes.
Important points about Factory Design Pattern:
Keep Factory class Singleton or we can keep the method that returns the
subclass as static.
Based on the input parameter, different subclass is created and returned.
Factory Patterns

Define an interface or abstract class for creating an object but let the
subclasses decide which class to instantiate.
Factory pattern is used when we have a super class with multiple
sub-classes and, based on input, we need to return one of the sub-classes.
This pattern removes the responsibility of instantiation of a class from the
client program to the factory class.
Also referred as Virtual Constructor.
When to apply such Patterns ?
When a class doesn’t know what sub-classes will be required to create.
When a class wants that its sub-classes specify the objects to be created.
When the parent classes choose the creation of objects to its sub-classes.
Important points about Factory Design Pattern:
Keep Factory class Singleton or we can keep the method that returns the
subclass as static.
Based on the input parameter, different subclass is created and returned.
Factory Patterns

Define an interface or abstract class for creating an object but let the
subclasses decide which class to instantiate.
Factory pattern is used when we have a super class with multiple
sub-classes and, based on input, we need to return one of the sub-classes.
This pattern removes the responsibility of instantiation of a class from the
client program to the factory class.
Also referred as Virtual Constructor.
When to apply such Patterns ?
When a class doesn’t know what sub-classes will be required to create.
When a class wants that its sub-classes specify the objects to be created.
When the parent classes choose the creation of objects to its sub-classes.
Important points about Factory Design Pattern:
Keep Factory class Singleton or we can keep the method that returns the
subclass as static.
Based on the input parameter, different subclass is created and returned.
Factory Patterns

Define an interface or abstract class for creating an object but let the
subclasses decide which class to instantiate.
Factory pattern is used when we have a super class with multiple
sub-classes and, based on input, we need to return one of the sub-classes.
This pattern removes the responsibility of instantiation of a class from the
client program to the factory class.
Also referred as Virtual Constructor.
When to apply such Patterns ?
When a class doesn’t know what sub-classes will be required to create.
When a class wants that its sub-classes specify the objects to be created.
When the parent classes choose the creation of objects to its sub-classes.
Important points about Factory Design Pattern:
Keep Factory class Singleton or we can keep the method that returns the
subclass as static.
Based on the input parameter, different subclass is created and returned.
Factory Patterns

Define an interface or abstract class for creating an object but let the
subclasses decide which class to instantiate.
Factory pattern is used when we have a super class with multiple
sub-classes and, based on input, we need to return one of the sub-classes.
This pattern removes the responsibility of instantiation of a class from the
client program to the factory class.
Also referred as Virtual Constructor.
When to apply such Patterns ?
When a class doesn’t know what sub-classes will be required to create.
When a class wants that its sub-classes specify the objects to be created.
When the parent classes choose the creation of objects to its sub-classes.
Important points about Factory Design Pattern:
Keep Factory class Singleton or we can keep the method that returns the
subclass as static.
Based on the input parameter, different subclass is created and returned.
Factory Patterns ...

Product: defines the interface of objects the factory method creates.

ConcretePro : which implements the Product interface.
ConcreteProCreator overrides the factory method to return an instance of
a ConcretePro.
ProductMain :
declares the factory method, which returns an object of type Product.
Creator may also define a default implementation of the factory method
that returns a default ConcretePro object.
May call the factory method to create a Product object
Factory Patterns ...

Product: defines the interface of objects the factory method creates.

ConcretePro : which implements the Product interface.
ConcreteProCreator overrides the factory method to return an instance of
a ConcretePro.
ProductMain :
declares the factory method, which returns an object of type Product.
Creator may also define a default implementation of the factory method
that returns a default ConcretePro object.
May call the factory method to create a Product object
Factory Patterns ...

Product: defines the interface of objects the factory method creates.

ConcretePro : which implements the Product interface.
ConcreteProCreator overrides the factory method to return an instance of
a ConcretePro.
ProductMain :
declares the factory method, which returns an object of type Product.
Creator may also define a default implementation of the factory method
that returns a default ConcretePro object.
May call the factory method to create a Product object
Factory Patterns ...

Product: defines the interface of objects the factory method creates.

ConcretePro : which implements the Product interface.
ConcreteProCreator overrides the factory method to return an instance of
a ConcretePro.
ProductMain :
declares the factory method, which returns an object of type Product.
Creator may also define a default implementation of the factory method
that returns a default ConcretePro object.
May call the factory method to create a Product object
Factory Patterns ...

Product: defines the interface of objects the factory method creates.

ConcretePro : which implements the Product interface.
ConcreteProCreator overrides the factory method to return an instance of
a ConcretePro.
ProductMain :
declares the factory method, which returns an object of type Product.
Creator may also define a default implementation of the factory method
that returns a default ConcretePro object.
May call the factory method to create a Product object
Structural Design pattern

2 Structural Design patterns

Are concerned with how classes and objects arecomposed to form larger
structures.
Structural class patterns use inheritance to compose interfaces or
implementations.
So simply explain how to assemble objects and classes into larger structures
while keeping these structures flexible and efficient.

i Adapter
ii proxy
Structural Design → iii Composite
patterns iv Decorator
v Facade
vi Flyweight
Structural Design pattern

2 Structural Design patterns

Are concerned with how classes and objects arecomposed to form larger
structures.
Structural class patterns use inheritance to compose interfaces or
implementations.
So simply explain how to assemble objects and classes into larger structures
while keeping these structures flexible and efficient.

i Adapter
ii proxy
Structural Design → iii Composite
patterns iv Decorator
v Facade
vi Flyweight
Structural Design patterns

i Adapter
also known as Wrappers
Mainly Focus on Converting the interface of a class into another interface
clients expect.
Adapter lets classes work together that couldn’t otherwise because of
incompatible interfaces.

Analogy of Car and

Railwayroad →
Structural Design patterns

Class Structure of Adapter

ClientClass:is a class that contains the existing business logic of the

program
ClientInterface:defines the domain-specific interface that ClientClass uses.
Service: The Service is some useful class that the client can’t use this class
directly because it has an incompatible interface.
AdapterClass:
Is a class that’s able to work with both the clientClass and service
It implements the clientClass interface, while wrapping the service object.
The adapter receives calls from the clientClass via the adapter interface →
them into calls to the wrapped service object in a format it can understand.
Structural Design patterns

Class Structure of Adapter

ClientClass:is a class that contains the existing business logic of the

program
ClientInterface:defines the domain-specific interface that ClientClass uses.
Service: The Service is some useful class that the client can’t use this class
directly because it has an incompatible interface.
AdapterClass:
Is a class that’s able to work with both the clientClass and service
It implements the clientClass interface, while wrapping the service object.
The adapter receives calls from the clientClass via the adapter interface →
them into calls to the wrapped service object in a format it can understand.
Structural Design patterns

Class Structure of Adapter

ClientClass:is a class that contains the existing business logic of the

program
ClientInterface:defines the domain-specific interface that ClientClass uses.
Service: The Service is some useful class that the client can’t use this class
directly because it has an incompatible interface.
AdapterClass:
Is a class that’s able to work with both the clientClass and service
It implements the clientClass interface, while wrapping the service object.
The adapter receives calls from the clientClass via the adapter interface →
them into calls to the wrapped service object in a format it can understand.
Structural Design patterns

Class Structure of Adapter

ClientClass:is a class that contains the existing business logic of the

program
ClientInterface:defines the domain-specific interface that ClientClass uses.
Service: The Service is some useful class that the client can’t use this class
directly because it has an incompatible interface.
AdapterClass:
Is a class that’s able to work with both the clientClass and service
It implements the clientClass interface, while wrapping the service object.
The adapter receives calls from the clientClass via the adapter interface →
them into calls to the wrapped service object in a format it can understand.
Structural Design patterns

Class Structure of Adapter

ClientClass:is a class that contains the existing business logic of the

program
ClientInterface:defines the domain-specific interface that ClientClass uses.
Service: The Service is some useful class that the client can’t use this class
directly because it has an incompatible interface.
AdapterClass:
Is a class that’s able to work with both the clientClass and service
It implements the clientClass interface, while wrapping the service object.
The adapter receives calls from the clientClass via the adapter interface →
them into calls to the wrapped service object in a format it can understand.
Structural Design patterns...

ii Proxy Structural Design pattern

Also referred as Surrogate
Provide a substitute or placeholder for another object.
is class represents functionality of another class.
Application are
Network connection
Large object in memory
File Magmt
Some other resource that is expensive or impossible to duplicate.
Goal: Prevent an object from being accessed directly by its clients
Solution:
Use an additional object, called a proxy
Clients access to protected object only through proxy
Proxy keeps track of status and/or location of protected object
Class Structure and related isssues ....
Behavioral Design patterns

3 Behavioral Design patterns

are concerned with algorithms and the assignment of responsibilities
between objects.
Describe not just patterns of objects or classes but also the patterns of
communication between them.
These patterns characterize complex control flow that’s difficult to follow at
run-time.
They shift yourfocus away from flow of control to let you concentrate just
on the way objects are interconnected.
use inheritance to distribute behaviorbetween classes.

i Observers
ii Itereators
iii Chain of responsibility
Behavioral Design → iv Command
patterns v Interpreter
vi Mediator
vii State
viii Visitor.
Behavioral Design patterns

3 Behavioral Design patterns

are concerned with algorithms and the assignment of responsibilities
between objects.
Describe not just patterns of objects or classes but also the patterns of
communication between them.
These patterns characterize complex control flow that’s difficult to follow at
run-time.
They shift yourfocus away from flow of control to let you concentrate just
on the way objects are interconnected.
use inheritance to distribute behaviorbetween classes.

i Observers
ii Itereators
iii Chain of responsibility
Behavioral Design → iv Command
patterns v Interpreter
vi Mediator
vii State
viii Visitor.
Behavioral Design patterns

i Observers Behavioral Design patterns

Also referred as Dependents, Publish-Subscribe
Define a one-to-many dependency between objects so that when oneobject
changes state, all its dependents are notified and updated automatically.
Use the Observer pattern in any of the following situations:
When an abstraction has two aspects, one dependent on the other.
Encapsulating these aspects in separate objects lets you vary and reuse them
independently.
When a change to one object requires changing others, and you don’t know how
many objects need to be changed.
When an object should be able to notify other objects without making
assumptions about who these objects are.
In other words, you don’t want these objects tightly coupled.
The Observer pattern describes how to establish these relationships.
The key objects in this pattern are subject and observer
Subject : may have any number of dependent observers.
All observers are notified whenever the subject under goesa change in state.
In response, each observer will query the subjectto synchronize its state with the
subject’s state.
Behavioral Design patterns

Analogical Problem :

2 object You and AASTU

Shop
customer wastes time
checking product
availability
the store wastes resources
notifying the wrong
customers.
Design patterns

How to Select a Design Pattern ?

Consider how design patterns solve design problems
Scan the purpose of the design pattern.
Study how patterns interrelate.
compare and select patterns based on the problem.
Examine a cause of redesign.
 Thank you!
Questions + Suggestion ?!