Professional Documents
Culture Documents
6 Software architecture
Avancier
6. Software architecture
Avancier
Plan
10 Migration Planning
Practitioner Migration path
Business case
Delivery Plans
Enterprise
Impressionistic hierarchy
Enterprise
Architecture 10 Business Function Business Function
Solution
1,000 App App
architecture
6. Software architecture
Avancier
6. Software architecture
Basic concepts
Software technologies
Modular design and integration
Service-oriented design
Inter-component coupling
Component structures and patterns
Conceptual framework
Avancier
Delegation
Avancier
Product
Balance
Check
Allocation State
Order
Order
Closure
State
Customer
Credit
Check
Debit
State
Allocation State
Order
One-way dependency
Order
Closure
State Cyclic dependency
Customer
Credit
Check
Debit
State
Stateful component
Avancier
Class diagram
Avancier
Sale Payment
Sequence [an artefact] that shows how UML Object Interaction Diagram
diagram components cooperate at run-
time to enable a process. a:Sale a:Product a:Depot
Customer Product
Sale Payment
Run time is when those components work UML Object Interaction Diagram
and interoperate.
a:Sale a:Product a:Depot
Software technologies
Avancier
6. Software architecture
Basic concepts
Software technologies
Modular design and integration
Service-oriented design
Inter-component coupling
Component structures and patterns
OOP
Avancier
Garbage collection
Avancier
Middleware
Avancier
IDL
Avancier
Web services
Avancier
6. Software architecture
Avancier
6. Software architecture
Basic concepts
Software technologies
Modular design and integration
Service-oriented design
Inter-component coupling
Component structures and patterns
Modular design
Avancier
Modular integration
Avancier
OOD
Avancier
Object- [a technique] a kind of modular design and integration that initially tended
Oriented to assume the following features.
Design
1. a component is an object, an instance of a class, identified by an
object identifier
2. client/sender and server/receiver objects work in the same name
space
3. an object is stateful
4. an object can reuse behaviour by inheriting it from a super type class
5. intelligent domain objects (rather than intelligent process/control
objects)
6. client objects communicate with server objects by request-reply
invocations
7. a server object can accept only one invocation at once (so blocks
others)
DO
Avancier
CBD
Avancier
SOA
Avancier
REST
Avancier
EDA
Avancier
6. Software architecture
Avancier
6. Software architecture
Basic concepts
Software technologies
Modular design and integration
Service-oriented design
Inter-component coupling
Component structures and patterns
SOD
Avancier
Service
Catalogue
Aggregation of services
Avancier
SOD challenges
Avancier
6. Software architecture
Avancier
6. Software architecture
Basic concepts
Software technologies
Modular design and integration
Service-oriented design
Inter-component coupling
Component structures and patterns
Coupling by time
Avancier
Coupling by time
Avancier
Synchronous 1: A request-reply style; a client must wait for a server to reply before
continuing.
2: A blocking style; a server serves one client at a time, turning away
any other client who attempts to request a service. The caller and
responder hold a channel open, blocking others from using it.
Aside: 1: is the usual invocation from one COBOL module to another
or one Java object to another. 2: is the usual invocation style in
CORBA.
Asynchronous 1: A fire-and-forget style in which a client does not wait for a server
to reply, so can carry on to do other things. A call-back mechanism
may be needed.
2: A non-blocking style in which a server can accept requests from
several clients before responding to the first. Typically, the responder
has a queue of incoming messages and releases the channel after a
message is received.
Aside: 1. is the usual style in email conversations. 2. is the usual style
of Web Services.
Location Parties know each others locations. Parties do not know each others locations
Parties exchange complex or strong data Parties exchange only simple or weak data
Data types
types. types.
Client components are disabled when a new Client components are not affected when a
Version
server component version is released new server component version is released
A client must use one protocol to call a A client can use any of several protocols to
Protocol
service. call a service.
Transaction A process involving two parties will ensure A process involving two parties will be
management consistency divided at the expense of consistency
6. Software architecture
Avancier
6. Software architecture
Basic concepts
Software technologies
Modular design and integration
Service-oriented design
Inter-component coupling
Component structures and patterns
Sources include
Network-based architectural styles (after Roy Fielding)
OO design patterns (after the Gang of Four)
Design pattern
Avancier
Server
Server Server
layer
Peer to Peer
Peer-to-peer [a pattern] with no hierarchy,
System
structure meaning that any party can be
Component Component
both a client and server of any
other.
System
Component Component
Cyclic dependency
Avancier
Model
DB
Model
OO design patterns
Avancier
Singleton A component (or class) with only one instance (or object).
Communication
Style
Request-reply Shared
Client Server Data
Event broadcast Space
Communication
4 communication styles Style
Avancier
Connected Disconnected
Component The manner in which components interact (as client and server, or
communication sender and receiver), which can be direct or via intermediaries.
style There are three broad categories:
Point to point
Introduction agent
Mediator (active or passive)
Connected
Communication styles Disconnected
Tightly-coupled Loosely-coupled
Message Message
Broker Bus
Interoperation styles
Communication
Simplified Style
Avancier
Connected
Communication styles Disconnected
Tightly-coupled Loosely-coupled
SOA
Interoperation styles
Communication styles
Tightly-coupled Loosely-coupled
Interoperation styles