Modern Systems Analysis

and Design
Third Edition

Jeffrey A. Hoffer
Joey F. George
Joseph S. Valacich

Chapter 16
Designing Distributed and
Internet Systems

16.1
Copyright 2002 Prentice-Hall, Inc.
 Learning Objectives
Define key terms
 Client/server architecture
 Local area network
 Distributed database
 Middleware
Distinguish between file server and
client/server environments
Describe alternative designs for
distributed systems and their tradeoffs
16.2
 Learning Objectives
Describe how standards shape the
design of Internet-based systems
Describe options for assuring Internet
design consistency
Describe how site management issues
can influence customer loyalty as well
as system security

16.3
 Learning Objectives
Discuss issues related to managing on-
line data
 Context development
 On-line transaction processing
 Online analytical processing
 Data warehousing

16.4
 The Process of Designing
Distributed and Internet Systems
Similar to designing single-location systems
Due to multi-location deployment, numerous
design issues must be considered
More opportunity for failure due to number of
components
Understanding characteristics of commonly
used architectures is key to successful design

16.5
 The Process of Designing
Distributed and Internet Systems

Deliverables and Outcome

 Document that consolidates system design
information
 Description of each site
 Description of data usage for each site
 Description of business process for each site
 Contrasts of alternative IS architectures for
site, data and processing needs of each site

16.6
 Designing Distributed
Systems
Designing systems for local area networks
(LAN)
 LAN supports a network of personal computers
that share common devices and software attached
to the LAN
 File Servers
 A device that manages file operations
 Shared by each client PC attached to the LAN
 DBMS Applications
 One copy of DBMS on file server and concurrently running
copies on client PCs
 All data manipulation is performed on the client PC
16.7
 Designing Distributed
Systems
Designing systems for local area
networks (LAN)
 File Servers (continued)
 Limitations
 Excessive data movement
 Need for powerful client workstation
 Decentralized data control

16.8
 Designing Distributed
Systems
Designing systems for a Client Server
Architecture
 Application processing is divided between
client and server
 Client manages the user interface
 Database server is responsible for data
storage and query processing
 Database engine

16.9
 Designing Distributed
Systems
Designing systems for a Client Server
Architecture
 Advantages
 Allows companies to leverage the benefits of
microcomputer technology
 Allows processing to be performed close to the source of
data
 Improves response time
 Reduces network traffic
 Facilitates the use of graphical user interfaces (GUIs)
 Encourages the acceptance of open systems
 Disadvantages
 Server must be more powerful than server in file server
environment
16.10
 Choosing Between File Server
and Client/Server Architecture
File server architecture
 Supports only the distribution of data
 Entire programs and databases must be
transferred to clients when accessing
system
 Most appropriate for small applications with
little or no concurrent data access

16.11
 Choosing Between File Server
and Client/Server Architecture
Client/Server Architecture
 Client and server share processing
workload
 Excellent choice for systems with large
amounts of data and concurrent access
needs
Table 16-1 highlights differences
between both architectures
16.12
 Advanced Forms of
Client/Server Architecture
Three-tiered client/server
 Three logical and distinct applications
 Data management
 Presentation
 Analysis
 Middleware
 Combination of hardware, software and communication
technologies that bring together three distinct
applications into one environment
 Application Server
 Server where data analysis functions are performed

16.13
 Advanced Forms of
Client/Server Architecture
Three-tiered client/server
 Advantages
 Applications can be partitioned in a way that
best fits the organizational computing need
 Easier customization
 Easier maintenance

16.14
 Approaches to Designing
Client/Server Architectures
Distributed Presentation
Remote Presentation
Remote Data Management
Distributed Function
Distributed Database
Distributed Processing

16.15
 Designing Internet Systems
Standards
 Design is simpler due to standards
 Naming
 BIND
 Translation
 Hypertext Transfer Protocol (HTTP)
 Formatting
 Hypertext Markup Language (HTML)

16.16
 Designing Internet Systems
Separating Content and Display
 HTML has limitations due to format orientation of
tags
 Extensible Markup Language (XML) has been
developed to separate content from display
 Ability to create custom languages

Future Evolution
 Move from desktop PCs to thin clients
 Most processing and data storage occurs on the server

16.17
 Designing Internet Systems
Aids to Site Consistency
 Cascading Style Sheets
 A set of style rules that tells a Web browser
how to present a document
 Extensible Style Language (XSL)
 Specification for separating style from content
when generating HTML documents

16.18
 Designing Internet Systems
Design Issues Related to Site
Management
 Customer Loyalty and Trustworthiness
 Conveyed by
 Design quality
 Up-front disclosure
 Comprehensive, correct and current content
 Connected to the rest of the Web
 Data security
 Personalization

16.19
 Designing Internet Systems
Design Issues Related to Site
Management
 Web Pages Must Live Forever
 Customer Bookmarks
 Links from Other Sites
 Search Engine Referrals
 Old Content Adds Value
 System Security

16.20
 Managing On-line Data
Effective design in the result of understanding
how a system fits within the context of an
organization
 Context Development
Integration Depth
 Measurement of how far into the existing
technology infrastructure a system penetrates
Organizational Breadth
 A measurement that tracks the core business
functions affected by a system
16.21
 Managing On-line Data
On-line Transaction Processing (OLTP)
 Refers to immediate automated responses
to the requests of users
 Designed to handle multiple concurrent
transactions
 Plays a large role in electronic commerce
applications

16.22
 Managing On-line Data
On-line Analytical Processing (OLAP)
 Refers to graphical software tools that
provide complex analysis of data stored in
a database.
 OLAP server is the chief component
 Good for time series and trend analysis
 Enables user to “drill-down” into the data

16.23
 Managing On-line Data
Comparison of Operational and
Informational Systems
 Operational
 Interact with customers and run a business in
real time
 Informational
 Designed to support decision making based on
historical data

16.24
 Managing On-line Data
Data Warehousing
 Subject-oriented
 Organized around key subjects
 Integrated
 Data are collected from many operational systems and
made to conform to standards
 Time-variant
 Data contains a time dimension
 Nonvolatile
 Data cannot be updated by users

16.25
 Managing On-line Data
Data Warehousing
 Two primary architectures
 Two-level
 Data warehouse and decision support environment
 Three-level
 Operational systems
 Enterprise data warehouse
 Centralized, integrated data warehouse

 Control point and single source of all data made

available to end users

 Data marts
 A data warehouse that is limited in scope based upon

aggregation and selection

16.26
 Summary
Local Area Network-based Architectures
 File server
 Client/Server
Evolution of distributed systems
 Three-tiered client/server architecture
Internet Design
 Standardization
 Consistent look and feel
 Cascading Style Sheets
 eXtensible Style Sheet language

16.27
 Summary
Internet Design
 XML
On-line Transaction Processing (OLTP)
On-line Analytical Processing (OLAP)
Data Warehouses
 Two-tier versus three-tier
Electronic commerce application

16.28