3/16/06: System Architecture
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

3/16/06: System Architecture

on

  • 433 views

 

Statistics

Views

Total Views
433
Views on SlideShare
432
Embed Views
1

Actions

Likes
0
Downloads
6
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

3/16/06: System Architecture Presentation Transcript

  • 1. System Architecture & Hardware Configurations Dr. D. Bilal IS 582 Spring 2006
  • 2. System Architecture
    • Two major system architectures:
      • Hierarchical
      • Client/Server
  • 3. Hierarchical Architecture
    • Processing and activities are controlled by the host system
    • Remote computers connected to host system have limited functions
    • (input/output)
  • 4. Hierarchical Architecture
    • Remote computers connected to the host system emulate “dumb” terminals in communicating with the host system.
    • “Dumb” terminals have no or limited processing capabilities.
  • 5. Client/Server Architecture
    • Client: a user’s computer
    • Server: a dedicated computer in a network shared by multiple users
      • More than one server can exist in this architecture (e.g., database server, Web server, application server, e-mail server)
  • 6. Client/Server Architecture
    • A computing architecture in a LAN or WAN environment
      • Clients on network perform certain processing functions when requesting information from a server in the network
  • 7. Client/Server Architecture
    • TCP/IP to establish communications between clients and servers
    • Clients handle the user interface
      • screen formatting, display of results, input/output
      • make requests and send them to the application server
  • 8. Client/Server Architecture
    • Server searches for requested information and sends results to the client(s)
    • Server performs database management, information retrieval, transaction and processing tasks.
    • Server delivers access to files, applications, and network communications.
  • 9. File Server Architecture
    • User requests information from a server
    • Entire database file is downloaded in the computer making the request
      • results in slow communication between the user’s computer and the server.
  • 10. File Server Architecture
    • Software programs are loaded onto the server only.
    • Installing updates are done in server
    • Updates take less time to install than those in client/server architecture
  • 11. Client/Server Architecture
    • One client may connect to one or more servers: OPAC server, Webmail server, and other servers
    • One server may connect to multiple clients concurrently.
  • 12. Client/Server Architecture
    • Each client that is connected in a client/server network must have part of the automation software (e.g., user interface) loaded onto its hard disk that allows it to perform certain application tasks.
  • 13. Client/Server Architecture
    • If all OPACs in a network must have access to the Web, all clients must have a Web browser.
    • If all clients must provide access to e-mail, they must have the e-mail client software loaded on them.
  • 14. Client/Server Architecture
    • Servers may be large scale computers, mid-range computers, or high speed microcomputers.
    • True client/server means that the application was originally designed to run on a network (LAN or WAN).
  • 15. Types of Client/Server: Two-Tier
    • Database processing tasks are done in the server.
    • Application processing tasks are done in the client requesting the information.
      • A request is generated in the client and transmitted to the server. The Database Management System that resides on the server searches for the desired information and transmits the results of the request to the client.
  • 16. Types of Client/Server: Three-Tier
    • Used when applications are in high demand.
    • An additional server is used for application processing tasks.
    • Both the client and the additional server perform application processing tasks.
    • The other server performs the database management tasks (searching, retrieval, etc.).
  • 17. Types of Client/Server: Thin Clients
    • Computer terminals rather than desktop computers.
    • Do little or no data processing tasks.
    • Process information (input/output).
    • Used to lower PCs and Macs cost used in a network.
  • 18. Types of Client/Server: Thin Clients
    • May be used as e-mail stations, Web access stations, and/or OPACs stations.
    • Can co-exist with thick or fat clients in a network.
  • 19. Client/Server Architecture
    • Benefits
      • See Bilal, 2002, pp. 33-34.
    • Disadvantages
      • See Bilal, 2002, p. 34.
    • See client/server software architecture at
    • http:// www.sei.cmu.edu/str/descriptions/clientserver.html
  • 20. Options for Hardware Configurations
    • Non-networked (a.k.a. stand-alone)
      • Advantages
      • Disadvantages
    • Difference between stand-alone hardware configuration and stand-alone software configuration.
  • 21. Options for Hardware Configurations
    • Networked: LAN-based
      • Advantages
      • Disadvantages
    • Networked: WAN-based
      • Advantages
      • Disadvantages
  • 22. ASP Model
    • ASP (Access Service Provider)
    • To outsource network maintenance and troubleshooting to a vendor
    • Vendor does database installation and update
    • Fee-based service