SOFTWARE

ARCHITECTURE

Client/Server
Architectur
SERVER a process, module,
object or computer that
provides services to another
network
CLIENT a process, module,
object or computer that
requests services from one or
more servers

Client/Server
Architecture is a general
model
of
software
organization and behavior
that can be implemented in
many different ways.

The architectural issues to be

addressed when designing
client/server software are:

Decomposing software into client

and server programs or objects
Determining which clients and
servers will execute on which
computer systems
Designing the communication
protocols and networks that connect
clients and servers

Client
Process or
Object

Client Verification
Service

Credit Data
Store

Client/server architecture advantages:

Location Flexibility
Scalability

Maintainability

Client/server architecture disadvantages:

Additional
complexity
Potential Poor
Performance

Security Issues

Reliability

Three Layer
Architecture

Three Layer Client-Server Architecture

a client/server architecture that divides an application

into view layer, business logic layer, and data layer

View layer
the part of the three-layer architecture that contains

the user interface

Business logic layer or domain layer

the part of a three-layer architecture that contains the

programs that implement the business rules and

processes

Data layer
the part of a three-layer architecture that interacts

with the data

Middleware
Computer software that implements

communication protocols on the

network and helps different systems
communicate

Internet and Web-Based

Approach
Web is complex example of client/server

13

architecture
Web resources are managed by server
processes
Clients are programs that send HTTP
requests to servers
Web protocols HTTP/HTTPS define valid
resource formats and communication
standards
Web protocols are stateless
Web provides Internet access in ordinary
applications

Web-oriented architecture: use of service-oriented

architecture (SOA)

SOA

architecture
that
packages application software
into server software, which can
be managed by and accessed via
a web server. (.net)

Advantages of Web-based
approach
Accessibility
Low-cost Communication
Widely Implemented Standards

Disadvantages of Web-based
approach
Security
Reliability
Throughput
Volatile Standards

NETWORK DESIGN
The key network design issues
Integrating new network needs

within existing infrastructure

Describing local processing activity
and network connectivity
Describing the communication
protocols and middleware
Ensuring that sufficient network
capacity is available

NETWORK
INTEGRATION
Factors impacting network integration
Connections for new servers
Modifying routing and firewall

configuration
Expansion of capacity
New communication protocols
Modified security protocols

Analyst may share or delegate tasks to the

network administrator

NETWORK
DESCRIPTION

USE OF MIDDLEWARE
Middleware
Connects parts of an application
Enables requests and data to pass

among them
Common types of middleware
Teleprocessing monitors
Transaction processing monitors
Object request brokers (ORBs)
Message queues
Each type of middleware has its own set
of protocols