Submitted to:

Professor Nouman Shakir

Submitted by:
(4224) Raza ul Mustafa
(4247) Waseem Abbas
(4222) Muhammad Umar Darraz
(4246) Ahsan Sajjad
Course/Degree:
BS Software Engineering
Subject:
Introduction to Software Engineering
Presentation Topic:
Architecture Design and Patterns
1. Architecture Designs and Design Decisions
2. Architecture Views
3. Architecture Patters
 Model-View-Controller
 Layered Architecture

4. Architecture Patters
 Client-Server Architecture
 Pipe and Filter Architecture
 Architecture Designs and Decision Designs
(Presented by 4224 Raza Ul Mustafa)
Architectural Design
Architectural design is a process for identifying the sub-systems making up a
system and the framework for sub-system control and communication. The
output of this design process is a description of the software architecture.
Architectural design is an early stage of the system design process. It represents
the link between specification and design processes and is often carried out in
parallel with some specification activities. It involves identifying major system
components and their communications.
Software architectures can be designed at two levels of abstraction:

 Architecture in the small is concerned with the architecture of individual

programs. At this level, we are concerned with the way that an individual
program is decomposed into components.
 Architecture in the large is concerned with the architecture of complex
enterprise systems that include other systems, programs, and program
components. These enterprise systems are distributed over different
computers, which may be owned and managed by different companies.

Three advantages of explicitly designing and documenting software architecture:

 Stakeholder communication: Architecture may be used as a focus of

discussion by system stakeholders.
 System analysis: Well-documented architecture enables the analysis of
whether the system can meet its non-functional requirements.
 Large-scale reuse: The architecture may be reusable across a range of
systems or entire lines of products.

Software architecture is most often represented using simple, informal block

diagrams showing entities and relationships. Pros: simple, useful for
communication with stakeholders, great for project planning. Cons: lack of
semantics, types of relationships between entities, visible properties of entities in
the architecture.
Uses of architectural models:
As a way of facilitating discussion about the system design:
A high-level architectural view of a system is useful for communication with
system stakeholders and project planning because it is not cluttered with
detail. Stakeholders can relate to it and understand an abstract view of the
system. They can then discuss the system as a whole without being
confused by detail.
As a way of documenting an architecture that has been designed:
The aim here is to produce a complete system model that shows the different
components in a system, their interfaces and their connections.

Architectural design decisions:

Design Decision encompass every aspect of system under development

 System Structure
 Functional Behaviour
 Interaction
 Non-Functional
 Implement
 Architecture Views
(Presented by 4247 Waseem Abbas)

Architectural views:
Dictionary Meaning : manner of looking at something , , ,
In architecture first of all we will discuss about what is views??
For better understanding and managing multi dimensional view must be taken for
any complex entity,multiple parameters involved.
For Example In civil what are view of building…..
Room layout, front Elevation drawing; 3D view of building /room ; Electrical
diagram Plumbing diagram; security alarm diagram; AC duct diagram etc…..
Architecture view in SE
Each view address a set of system concern , following the conventions of its
viewpoint Actually Viewpoint _ A position or direction
So,a view of a system is a repsentation of the system from the perspective of a
viewpoint.
Example of SW Views
A logical view(top/overall/bird eye view)
In logical view we explain all function and organizations,
Implemention View
In implemention view technology(HW and networking)
Module sequence
Development view
Front end
Back end
Database connectivity
Process (Deployment) view
Module and function,
Their interaction
Control points
Non functional requirements
Security view
User id / password
Graphical password
Transactional password
Architecture views
It is impossible to represent all relevant information about a system architecture
in a single architecture model as each model only shows one view or prospective
of the system.
You usually need to present multiple views of the software architecture.
Multiple perspective are necessary to capture the complete behavior and
development of a software system.
 Architecture Patterns
(MVC and Layered Architecture)
(Presented by 4222 Muhammad Umar Darraz)

Architectural patterns:
Patterns are a means of representing, sharing and reusing knowledge. An
architectural pattern is a stylized description of a good design practice, which has
been tried and tested in different environments. Patterns should include
information about when they are and when the are not useful. Patterns may be
represented using tabular and graphical descriptions.

Model-View-Controller:
 Serves as a basis of interaction management in many web-based
systems.
 Decouples three major interconnected components:
o The model is the central component of the pattern that directly
manages the data, logic and rules of the application. It is the
application's dynamic data structure, independent of the user
interface.
o A view can be any output representation of information, such as a
chart or a diagram. Multiple views of the same information are
possible.
o The controller accepts input and converts it to commands for the
model or view.
 Supported by most language frameworks.
Pattern name Model-View-Controller (MVC)

Separates presentation and interaction from the system data.

The system is structured into three logical components that
interact with each other. The Model component manages the
system data and associated operations on that data. The View
Description
component defines and manages how the data is presented to
the user. The Controller component manages user interaction
(e.g., key presses, mouse clicks, etc.) and passes these
interactions to the View and the Model.

Problem The display presented to the user frequently changes over time
description in response to input or computation. Different users have
different needs for how they want to view the program.s
information. The system needs to reflect data changes to all
 users in the way that they want to view them, while making it
easy to make changes to the user interface.

This involves separating the data being manipulated from the

manipulation logic and the details of display using three
Solution components: Model (a problem-domain component with data
description and operations, independent of the user interface), View (a data
display component), and Controller (a component that receives
and acts on user input).

Advantages: views and controllers can be easily be added,

removed, or changed; views can be added or changed during
execution; user interface components can be changed, even at
runtime. Disadvantages: views and controller are often hard to
Consequences
separate; frequent updates may slow data display and degrade
user interface performance; the MVC style makes user interface
components (views, controllers) highly dependent on model
components.

Layered architecture:
 Used to model the interfacing of sub-systems.
 Organizes the system into a set of layers (or abstract machines) each of
which provide a set of services.
 Supports the incremental development of sub-systems in different
layers. When a layer interface changes, only the adjacent layer is
affected.
 However, often artificial to structure systems in this way.
Name Layered architecture

Organizes the system into layers with related functionality associated with
each layer. A layer provides services to the layer above it so the lowest-level
Description
layers represent core services that are likely to be used throughout the
system.

Used when building new facilities on top of existing systems; when the
When used development is spread across several teams with each team responsibility for
a layer of functionality; when there is a requirement for multi-level security.

Allows replacement of entire layers so long as the interface is maintained.

Advantages Redundant facilities (e.g., authentication) can be provided in each layer to
increase the dependability of the system.

In practice, providing a clean separation between layers is often difficult and

a high-level layer may have to interact directly with lower-level layers rather
Disadvantages than through the layer immediately below it. Performance can be a problem
because of multiple levels of interpretation of a service request as it is
processed at each layer.
 Architecture Patterns
(Client Server and Pipe and Filter
Architecture)
(Presented by 4246 Ahsan Sajjad)
Repository architecture:
 Sub-systems must exchange data. This may be done in two ways:
o Shared data is held in a central database or repository and may be
accessed by all sub-systems;
o Each sub-system maintains its own database and passes data
explicitly to other sub-systems.
 When large amounts of data are to be shared, the repository model of
sharing is most commonly used a this is an efficient data sharing
mechanism.
Name Repository

All data in a system is managed in a central repository that is

Description accessible to all system components. Components do not interact
directly, only through the repository.

You should use this pattern when you have a system in which
large volumes of information are generated that has to be stored
When used
for a long time. You may also use it in data-driven systems where
the inclusion of data in the repository triggers an action or tool.

Components can be independent--they do not need to know of

the existence of other components. Changes made by one
Advantages component can be propagated to all components. All data can be
managed consistently (e.g., backups done at the same time) as it
is all in one place.

The repository is a single point of failure so problems in the

Disadvantage repository affect the whole system. May be inefficiencies in
s organizing all communication through the repository. Distributing
the repository across several computers may be difficult.

Client-server architecture:
  Distributed system model which shows how data and processing is
distributed across a range of components, but can also be implemented
on a single computer.
 Set of stand-alone servers which provide specific services such as
printing, data management, etc.
 Set of clients which call on these services.

Network which allows clients to access servers

Name Client-server

In a client-server architecture, the functionality of the system is

organized into services, with each service delivered from a
Description
separate server. Clients are users of these services and access
servers to make use of them.

Used when data in a shared database has to be accessed from a

When used range of locations. Because servers can be replicated, may also be
used when the load on a system is variable.

The principal advantage of this model is that servers can be

distributed across a network. General functionality (e.g., a printing
Advantages
service) can be available to all clients and does not need to be
implemented by all services.

Each service is a single point of failure so susceptible to denial of

service attacks or server failure. Performance may be
Disadvantage
unpredictable because it depends on the network as well as the
s
system. May be management problems if servers are owned by
different organizations.
Pipe and filter architecture:
 Functional transformations process their inputs to produce outputs.
 May be referred to as a pipe and filter model (as in UNIX shell).
 Variants of this approach are very common. When transformations are
sequential, this is a batch sequential model which is extensively used in
data processing systems.
 Not really suitable for interactive systems.

Name Pipe and filter

The processing of the data in a system is organized so that each

processing component (filter) is discrete and carries out one type
Description
of data transformation. The data flows (as in a pipe) from one
component to another for processing.
 Commonly used in data processing applications (both batch- and
When used transaction-based) where inputs are processed in separate stages
to generate related outputs.

Easy to understand and supports transformation reuse. Workflow

style matches the structure of many business processes. Evolution
Advantages
by adding transformations is straightforward. Can be
implemented as either a sequential or concurrent system.

The format for data transfer has to be agreed upon between

communicating transformations. Each transformation must parse
Disadvantage
its input and unparse its output to the agreed form. This increases
s
system overhead and may mean that it is impossible to reuse
functional transformations that use incompatible data structures.