System Architecture Design

The system architecture design consists

of plans for the hardware, software,
communications, security , and global
support for the new application
The designers must decide if processing
will occur in the server (server-based), at
the personal computer (client-based), or
in some combination of these (client-
server based).
Key Definitions
The network model shows major
components of the system, where
they are located and how they will
be connected to one another.
The hardware and software
specifications describe these
components in detail and aid those
responsible for purchase and
acquisition of these products.
Slide 3 PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design
Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.
COMPUTING
ARCHITECTURES
Functions of the
Application System
Data storage
Data access logic
Application logic
Presentation logic
Architectures
Server based
Client based
Client-server based
Alternative Servers
In server based architectures,
the servers do the work and
present the results
Mainframe
Minicomputer
Microcomputer (personal
computer)
Server-Based Computing
Alternative Clients
In client based architectures, clients
do most of the work (except data
storage) and present the results
Terminals
Microcomputer (personal computer)
Special purpose terminals
(ATMs, kiosks, Palm Pilots,
and many others)
Client-Based Computing
Client-Server-Based
Computing (2 Tiers)
Client-Server Attributes
Typical Pros Typical
Compatible with Cons/Limits
web-based system Complexity
design New programming
Scaleable languages and
Work with multiple techniques (stress
vendors/products for personnel)
No central point of More complex to
failure update
Client-Server -- Three
Tiers
Client-Server -- Four Tiers
N-Tiered Client-Server
Attributes
Typical Pros Typical
Separates Cons/Limits
processing to Greater load on
better balance the network
load More difficult to
More scaleable program and
test
Distributed Objects
Computing
Middleware between clients and
servers
Update middleware when changing
client code
May reduce efficiency of the
application
CORBA
DCOM
Slide 17 PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design
Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.
Realities of Infrastructure
Design
Most often the infrastructure
will be in place
Coordination of infrastructure
components is very complex
The application developer will
need to coordinate with
infrastructure specialists
Slide 18 PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design
Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.
Selecting a Computing
Architecture
Server-Based Client-based Client-server

Cost of infrastructure Very high Medium Low

Cost of development Medium Low High

Ease of development Low High Low-medium

Interface capabilities Low High High

Control and security High Low Medium

Scalability Low Medium High

Your Turn
Consider the course registration
system at your university:
What computing architecture does it
use?
What computing architecture would
you use if you were replacing it
today?
INFRASTUCTURE
DESIGN
The Network Model
No standard format
Conveys complexity of the system
and how components fit together
Components are
Clients
Equipment
Connection to external systems or
networks
Top-Level Network Model