Scribd
Upload
28 views

Assignment Part 2

The document discusses several architectural styles: Layered style organizes systems hierarchically with layers providing services to adjacent layers. Most desktop and ecommerce apps use this style. Implicit invocation style uses events to trigger functions. Object oriented style encapsulates data and operations in objects. Pipe and filter style performs independent computations in a defined series. Client server style separates clients, which request services, from servers, which process requests and return information.

Uploaded by

Ehtisham Khattak
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
28 views

Assignment Part 2

The document discusses several architectural styles: Layered style organizes systems hierarchically with layers providing services to adjacent layers. Most desktop and ecommerce apps use this style. Implicit invocation style uses events to trigger functions. Object oriented style encapsulates data and operations in objects. Pipe and filter style performs independent computations in a defined series. Client server style separates clients, which request services, from servers, which process requests and return information.

Uploaded by

Ehtisham Khattak
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Name: Muhammad Ihtisham

GROUP: B

Architectural Styles:
Following are discussed.

Layered Style:
A layered system is organized hierarchically with each layer providing service to the layer above
it and serving as a client to the layer below. In some systems inner layers are hidden from all
except the adjacent outer layer. Connectors are defined by the protocols that determine how
layers will interact. Constraints include limiting interactions to adjacent layers. Layers are the
following in this style. Presentation layer ,Business layer ,Persistence layer ,Database layer

Uses:
Most of the desktop applications and Ecommerce type web applications are developed
using Layered Architecture.
Implicit Invocation Style:
In event-based architectural styles, the fundamental elements in the system are events.
Events are both indicators of change in the system and triggers to functions. Events can
be signals, user inputs, messages, or data from other functions or programs.

Examples:
Implicit invocation systems are used in:
 programming environments to integrate tools.
 user interfaces to separate data from representation.

Object Oriented Style:


Suitable for applications in which a central issue is identifying and protecting related bodies of
information .Data representations and their associated operations are encapsulated in an
abstract data type. Components in this architecture styles are objects, and connectors are
function and procedure invocations (methods).

Uses:
 Objects are responsible for preserving the integrity (e.g., some invariant) of the data
representation.
 The data representation is hidden from other objects.

4.Pipe & Filter Style:

Suitable for applications that require a defined series of independent computations to be


performed on data. A component reads streams of data as input and produces streams of data
as output.
Uses:
Traditional Compilers: Compilation phases are pipelined, though the phases are not always
incremental. The phases in the pipeline include: lexical analysis + parsing + semantic analysis +
code generation

5.Client Server Style:


Each instance of the client software can send data requests to one or more connected servers.
In turn, the servers can accept these requests, process them, and return the requested
information to the client. A server machine is a high-performance host that is running one or
more server programs which share its resources with clients. A client does not share any of its
resources, but requests a server's content or service function.

Uses:
Client examples are Web browsers, email clients and online chat. Server examples are web
servers, ftp servers and database servers.
Comparison of software architecture styles.

You might also like