IT Architecture Design: Client-Server and Cloud Computing, Study notes of Business Statistics

Download IT Architecture Design: Client-Server and Cloud Computing and more Study notes Business Statistics in PDF only on Docsity!

Architecture Design

CORRESPONDING TO CHAPTER 8 OF “SYSTEMS ANALYSIS AND DESIGN,” BY DENNIS, WIXOM, AND ROTH

Learning Objectives

 (^) Describe the fundamental components of an information system.  (^) Describe client–server, server-based, and mobile application architectures.  (^) Describe how cloud computing can be incorporated as a system architecture component.  (^) Explain how operational, performance, security, cultural, and political requirements affect the architecture design.  (^) Create a hardware and software specification.

Elements of an

Architecture Design

ASSIGNING SOFTWARE COMPONENTS TO HARDWARE

Objective of Architecture Design

 Assign the software components of the information

system to the hardware devices of the system in the most

advantageous way.

 The major architectural components of any system are

the software and the hardware.

Architectural Components (cont’d)

The three primary hardware components:

o (^) Client computers: Input-output devices employed by users (e.g., PCs, laptops, handheld and mobile devices, smart phones) o (^) Servers: Larger multi-user computers used to store software and data. o (^) Network: Connects the computers.

Client-Server Architectures

 (^) Client-server architectures balance the processing between client devices and one or more server devices.  (^) Generally, clients are responsible for the presentation logic, and  (^) The server(s) are responsible for the data access logic and data storage.  (^) Application logic location varies depending on the C-S configuration chosen.

Client-Server Tiers

 (^) There are many ways in which the application logic can be partitioned between the client side and the server side. 8- 10

Two-Tiered Client-Server Architecture o (^) Thick client – most of application logic on the client side (shown here) o (^) Thin client – little application logic on the client side; most shifted to server side

n-Tiered Client- Server Architecture o (^) Adds “specialized” servers – one for Web-related business logic; one for application logic; one for data base tasks

Server-Based Architecture Zero-client used today in virtual desktop infrastructure (VDI)

Mobile Application Architecture

 (^) Rich client – involves processing on the mobile device using its resources. Presentation logic, application logic, and data access logic on the client side.  (^) Thin Web-based client – application and data access logic on the server side; always connected to server.  (^) Rich Internet application – browser-based; uses some technologies on client device to provide a rich user interface (e.g., Flash).

Mobile Application Options

 (^) Native app – written to run on specific device with specific operating system.  (^) Cross-platform frameworks – develop in web-based technologies and use framework to deploy to multiple devices.  (^) Mobile Web app – browser-based; platform independent. Most limited user experience.

Advances in Architecture Configurations

 (^) Advances in hardware, software, and networking have given rise to a number of new architecture options. o (^) Virtualization: Creation of a virtual device or resource. o (^) Cloud computing: Computing resources obtained as a service.

Virtualization

 (^) Server virtualization involves partitioning a physical server into smaller virtual servers.  (^) Storage virtualization involves combining multiple network storage devices into what appears to be single storage unit.