0
Chapter 12: Architecture
Objectives <ul><li>Understand the different physical architecture components. </li></ul><ul><li>Understand server-based, c...
Introduction <ul><li>Most modern systems span two or more networked computers </li></ul><ul><li>The physical architecture ...
ELEMENTS OF THE PHYSICAL ARCHITECTURE LAYER
Architectural Components <ul><li>Software components </li></ul><ul><ul><li>Data storage </li></ul></ul><ul><ul><li>Data ac...
Server-Based Architectures <ul><li>The server performs all four application functions </li></ul><ul><li>The client only ne...
Client-Based Architectures <ul><li>All logic resides on the client computer </li></ul><ul><li>A separate computer may hold...
Client-Server Architectures <ul><li>Balance processing between client and server </li></ul><ul><li>Predominant architectur...
Client-Server Tiers <ul><li>Client server architectures can have two or more tiers depending on application logic partitio...
Distributed Objects Computing <ul><li>Next generation of client-server computing </li></ul><ul><li>The client need not kno...
Selecting a Physical Architecture <ul><li>Cost of infrastructure </li></ul><ul><li>Cost of development </li></ul><ul><li>E...
Architecture Characteristics Server-Based Client-Based Client-Server Cost of infrastructure Very high Medium Low Cost of d...
INFRASTRUCTURE DESIGN
Deployment Diagram <ul><li>Represent relationships between hardware components of an information system </li></ul><ul><li>...
Sample Deployment Diagram
Network Model <ul><li>Shows the major components of the information system and their geographic locations throughout the o...
Sample Network Model
NONFUNCTIONAL REQUIREMENTS
Nonfunctional Requirement Types <ul><li>Operational </li></ul><ul><li>Performance </li></ul><ul><li>Security </li></ul><ul...
Operational Requirements
Performance Requirements
Security Requirements
Cultural & Political Requirements
Summary <ul><li>Elements of the Physical Architecture Layer </li></ul><ul><li>Infrastructure Design </li></ul><ul><li>Nonf...
Upcoming SlideShare
Loading in...5
×

Ch12

774

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
774
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Ch12"

  1. 1. Chapter 12: Architecture
  2. 2. Objectives <ul><li>Understand the different physical architecture components. </li></ul><ul><li>Understand server-based, client-based, and client–server physical architectures. </li></ul><ul><li>Be familiar with distributed objects computing. </li></ul><ul><li>Be able to create a network model using a deployment diagram. </li></ul><ul><li>Understand how operational, performance, security, cultural, and political requirements affect the design of the physical architecture layer. </li></ul><ul><li>Be familiar with how to create a hardware and software specification. </li></ul>
  3. 3. Introduction <ul><li>Most modern systems span two or more networked computers </li></ul><ul><li>The physical architecture layer design specifies </li></ul><ul><ul><li>How the system will be distributed across the computers </li></ul></ul><ul><ul><li>What hardware and software will be used </li></ul></ul><ul><li>Most systems’ design is constrained by existing systems and networks </li></ul>
  4. 4. ELEMENTS OF THE PHYSICAL ARCHITECTURE LAYER
  5. 5. Architectural Components <ul><li>Software components </li></ul><ul><ul><li>Data storage </li></ul></ul><ul><ul><li>Data access logic </li></ul></ul><ul><ul><li>Application logic </li></ul></ul><ul><ul><li>Presentation logic </li></ul></ul><ul><li>Hardware components </li></ul><ul><ul><li>Computers (clients, servers) </li></ul></ul><ul><ul><li>Networks </li></ul></ul>
  6. 6. Server-Based Architectures <ul><li>The server performs all four application functions </li></ul><ul><li>The client only needed a monitor, a keyboard, and a communications device (e.g. modem) </li></ul>Data Storage Data Access Logic Application Logic Presentation Logic
  7. 7. Client-Based Architectures <ul><li>All logic resides on the client computer </li></ul><ul><li>A separate computer may hold the data </li></ul><ul><li>Simple to develop, but difficult to maintain </li></ul>Data Storage Data Access Logic Application Logic Presentation Logic
  8. 8. Client-Server Architectures <ul><li>Balance processing between client and server </li></ul><ul><li>Predominant architecture in modern systems </li></ul><ul><li>Amount of client processing varies </li></ul><ul><ul><li>Thin clients do only presentation logic </li></ul></ul><ul><ul><li>Thick clients do presentation and application </li></ul></ul>Application Logic Presentation Logic Data Storage Data Access Logic
  9. 9. Client-Server Tiers <ul><li>Client server architectures can have two or more tiers depending on application logic partitioning </li></ul><ul><ul><li>2-tier: all application and data logic on one server </li></ul></ul><ul><ul><li>3-tier: application logic on one server, data logic on another </li></ul></ul><ul><ul><li>4-tier: application logic split among two servers, data logic on another </li></ul></ul><ul><li>Sometimes called an n -tier architecture </li></ul>
  10. 10. Distributed Objects Computing <ul><li>Next generation of client-server computing </li></ul><ul><li>The client need not know which server to call </li></ul><ul><li>Middleware intercepts the client request and sends it to the appropriate server </li></ul><ul><li>Three competing approaches </li></ul><ul><ul><li>CORBA </li></ul></ul><ul><ul><li>Enterprise Java Beans </li></ul></ul><ul><ul><li>.NET </li></ul></ul>
  11. 11. Selecting a Physical Architecture <ul><li>Cost of infrastructure </li></ul><ul><li>Cost of development </li></ul><ul><li>Ease of development </li></ul><ul><li>Interface capabilities </li></ul><ul><li>Control and security </li></ul><ul><li>Scalability </li></ul>
  12. 12. Architecture Characteristics 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
  13. 13. INFRASTRUCTURE DESIGN
  14. 14. Deployment Diagram <ul><li>Represent relationships between hardware components of an information system </li></ul><ul><li>Elements of a deployment diagram </li></ul><ul><ul><li>Nodes : a computational resource </li></ul></ul><ul><ul><li>Artifacts : a piece of the information system which will be installed on a node </li></ul></ul><ul><ul><li>Communication paths : a communication link such as a network connection or a USB cable </li></ul></ul>
  15. 15. Sample Deployment Diagram
  16. 16. Network Model <ul><li>Shows the major components of the information system and their geographic locations throughout the organization </li></ul><ul><li>Purposes of the network model: </li></ul><ul><ul><li>To convey the complexity of the system </li></ul></ul><ul><ul><li>To show how the system’s software components will fit together </li></ul></ul>
  17. 17. Sample Network Model
  18. 18. NONFUNCTIONAL REQUIREMENTS
  19. 19. Nonfunctional Requirement Types <ul><li>Operational </li></ul><ul><li>Performance </li></ul><ul><li>Security </li></ul><ul><li>Cultural and Political </li></ul>
  20. 20. Operational Requirements
  21. 21. Performance Requirements
  22. 22. Security Requirements
  23. 23. Cultural & Political Requirements
  24. 24. Summary <ul><li>Elements of the Physical Architecture Layer </li></ul><ul><li>Infrastructure Design </li></ul><ul><li>Nonfunctional Requirements </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×