Scribd
Upload
33 views

Architectural Styles

This document describes two architectural styles: object-oriented and layered. The object-oriented style uses components that are objects with data and operations. Connectors are message passing and method invocations between objects. The layered style organizes systems hierarchically with each layer exposing an API to above layers and acting as a server or client to adjacent layers. Advantages include evolvability and reuse through standardized interfaces, while disadvantages include performance costs and determining correct abstraction levels.

Uploaded by

sudha_scampy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
33 views

Architectural Styles

This document describes two architectural styles: object-oriented and layered. The object-oriented style uses components that are objects with data and operations. Connectors are message passing and method invocations between objects. The layered style organizes systems hierarchically with each layer exposing an API to above layers and acting as a server or client to adjacent layers. Advantages include evolvability and reuse through standardized interfaces, while disadvantages include performance costs and determining correct abstraction levels.

Uploaded by

sudha_scampy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 5

Architectural Styles

Object-Oriented
Style

Components are objects

Data and associated operations

Connectors are messages and


method invocations

Style invariants

Objects are responsible for their


internal representation integrity

Internal representation is hidden


from other objects

Advantages

Infinite malleability of object


internals

System decomposition into sets


of interacting agents

Disadvantages

Objects must know identities of


servers

Side effects in object method


invocations

Layered Style
Hierarchical system

organization

Multi-level client-server
Each layer exposes an

interface (API) to be used


by above layers
Each layer acts as a

Server: service provider to

layers above
Client: service consumer

of layer(s) below
Connectors are protocols

of layer interaction
Example: operating

systems
Virtual machine style

results from fully opaque


layers

Layered Style
(contd)
Advantages

Increasing abstraction

levels
Evolvability
Changes in a layer affect

at most the adjacent two


layers

Reuse

Different implementations

of layer are allowed as


long as interface is
preserved
Standardized layer

interfaces for libraries and


frameworks

Layered Style
(contd)

Disadvantages
Not universally applicable
Performance

Layers may have to be

skipped

Determining the correct

abstraction level

You might also like