Kingdom of Saudi Arabia

Ministry of Higher Education

Al-Imam Muhammad Ibn Saud Islamic University
College of Computer and Information Sciences

Chapter 11:
Architecture
IS 309

Systems Analysis and Design

Information Systems Department

Objectives
• Understand the different physical architecture components.
• Understand server-based, client-based, and client–server
physical architectures.
• Be familiar with cloud computing and Green IT.
• Be able to create a network model using a deployment
diagram.
• Be familiar with how to create a hardware and software
specification.
• Understand how operational, performance, security, cultural,
and political requirements affect the design of the physical
architecture layer.

IS Department 2
Introduction
• Most modern systems span two or more networked
computers
• The physical architecture layer design specifies:
• How the system will be distributed across the computers
• What hardware and software will be used
• Most systems design is constrained by existing systems
and networks
• Physical architecture design is demanding
• Knowledge of key factors is essential
• Nonfunctional requirements play a key role

IS Department 3
Elements of the Physical Architecture
Layer
• Purpose is to decide which applications run on what
hardware
• Process:
• Understand the software and hardware options, then
• Choose from the available alternatives, based on:
• Cost of acquisition
• Cost of development
• Ease of development
• Interface capabilities
• Control & security
• Scalability

IS Department 4
Architectural Components
• Software components
• Data storage
• Data access logic
• Application logic
• Presentation logic
• Hardware components
• Clients (computers, handhelds, cell phones, etc.)
• Servers (mainframes, minis, micros, rack mounted)
• Networks to connect all computers (Dial-up, always-on, medium or
high speed, leased lines)

IS Department 5
Server-Based Architectures
• The server performs all four application functions
• The client (usually a terminal with display and keyboard)
captures keystrokes and sends them to the server for
processing

Data Storage
Data Access Logic
Application Logic
Presentation Logic

IS Department 6
Client-Based Architectures
• Clients are personal computers on a network
• Server is a file server on the same network
• Simple to develop, but quickly overloaded
• All data is downloaded to the client for processing
• Network traffic may become excessive
• Client may not have enough computing power

Data Access Logic Data Storage

Application Logic
Presentation Logic

IS Department 7
Client-Server Architectures
• Balance processing between client and server
• Predominant architecture in modern systems
• Amount of client processing varies
• Thin clients do only presentation logic
• Thick clients do presentation and application
• Highly scalable at incremental cost
• More complex since applications must be written for both
client and server

Application Logic (Thick client) Data Storage

Presentation Logic Data Access Logic
Application Logic
(Thin client)

IS Department 8
Client-Server Tiers
• Client-server architecture tiers are defined based on how
the logic is partitioned:
• 2-tier: one server responsible for data storage and access; client
responsible for application & presentation logic
• 3-tier: data storage and access logic on one server, application
logic on another; client responsible for presentation logic
• n-tier: application logic split among two servers, data logic on
another
• Common in e-commerce applications
• Better load balancing
• More scalable than 2 or 3 tier systems
• Places higher demands on the network

IS Department 9
IS Department 10
Selecting a Physical Architecture
• Cost of infrastructure (initial acquisition and future growth)
• Cost of development
• Ease of development
• Interface capabilities
• Control and security
• Scalability (changes in capacity; upgrades)

IS Department 11
Architecture Characteristics
Server-Based Client-Based Client-Server
Cost of
Very high Medium Low
infrastructure
Cost of
Medium Low High
development
Ease of
Low High Low-Medium
development
Interface
Low High High
capabilities
Control and
High Low Medium
Security
Scalability Low Medium High

IS Department 12
Cloud Computing
• Treat IT as a commodity or utility
• Server is in the “cloud”
• Client is on the desktop
• The “cloud”
• A data center, internal or external; or
• A service provided by a vendor
• An umbrella technology that includes:
• Virtualization
• Service-oriented architectures
• Grid computing

IS Department 13
Green IT
• Anything that reduces the environmental impact of IT
• Topics:
• E-waste (disposal of toxic materials in old computers)
• Energy consumption of data centers and desktops
• The paperless office
• Cloud computing may help to reduce energy consumption
and improve the viability of the paperless office

IS Department 14
Infrastructure Design
• Although possible, few designs are from scratch
• Most designs utilize systems already in place
• Change or improve the existing infrastructure
• Coordination is difficult, but knowledge of elements is essential
• Deployment diagram
• Network model

IS Department 15
Deployment Diagram
• Represent relationships between hardware components
of an information system
• Elements of a deployment diagram
• Nodes: any piece of hardware (e.g. client computers, servers,
networks or network devices)
• Artifacts: a piece of the information system which will be installed
on a node
• Communication paths: a communication link between the nodes

IS Department 16
 IS Department 17

Deployment Diagram Syntax

 IS Department 18

Extended Node Syntax

 IS Department 19

Sample Deployment Diagrams

IS Department 20
Network Model
• A network diagram that depicts the major components and
their geographic locations in the organization
• Purposes of the network model:
• To convey the complexity of the system
• To show how the system’s software components will fit together
• Can serve as an aid for specifying hardware and software

IS Department 21
 IS Department 22

Sample Network Model

 IS Department 23

Diagram With Added Detail

Hardware & Software
Specifications
• Hardware & software needed for the new application is
recorded in a specifications document
• Software requirements:
• Operating system
• Special purpose software (e.g., DBMS)
• Include training needed, maintenance, warranties and licensing
agreements
• Hardware requirements
• Use low level network diagram as a starting point
• Include type & quantity of servers, peripherals, storage & backup devices
• Describe minimum requirements
• Use an alternative matrix to evaluate vendor proposals

IS Department 24
Example

IS Department 25