Chapter 12: Physical Architecture Layer Design

Document Sample
Chapter 12: Physical Architecture Layer Design Powered By Docstoc
					       Chapter 12:
Physical Architecture Layer
          Design
                 Key Definitions
• Physical Architecture Layer Design
  – The plan for the
     •   Hardware
     •   Software
     •   Communications infrastructure
     •   Security
     •   Global support
                Key Definitions
• Must decide on the architecture
  – Server-based
     • Processing built in to the server
  – Client-based
     • Processing done on client PCs
  – Client-server based
     • Processing shared between client and server
             Key Definitions
• Network model
  – Shows major components of the system
  – Where they are located
  – How they will be interconnected
• Hardware and software specification
  – Give details of NW model components
  – Guides purchase and acquisition
               Key Definitions
• Global support and security plan
  – Address global issues of the app.
     • Standards, support, culture, etc.
  – Addresses security
     • Disruption, data corruption, disaster recovery,
       unauthorized access, etc.
ARCHITECTURAL COMPONENTS
             Application Layers
Recall the application Layers:
     1.   Foundation
     2.   System Architecture
     3.   Human-Computer Interaction
     4.   Data Management
     5.   Problem Domain
             Application Functions
•        All applications have four 4 functions
•        The building blocks of all applications
    1.     Data storage
    2.     Data access logic
    3.     Application logic
    4.     Presentation logic
         Application Functions
• Data Storage
  – Part of the data management layer
  – Most application require data storage
     • Simple memo stored to text file
     • Large DB app. recording transactions
  – Data is identified /documented in the CRC cards of
    the structural model
         Application Functions
• Data Access Logic
  – Part of the data management layer
  – Processing needed to access data
     • Most often database queries
     • Also location of distributed data
          Application Functions
• Application Logic
  – Part of the problem domain layer
  – Can be simple or complex
     • Depending on the application
  – Logic documented in use cases and behavioral
    models
     • Sequence, collaboration, statechart diagrams
         Application Functions
• Presentation Logic
  – Part of the human-computer interaction layer
  – Deals with the presentation of information to the
    user
  – And accepting the user's commands
              Architectures
• Server based
• Client based
• Client-server based
Components of the Architectures
• Servers
  – Mainframes, Minis, Micros
• Clients
  – Input/Output HW used by users
  – Terminals, PCs, special purpose HW
• Network
  – HW and SW to connect clients to servers
Server Based Architecture

                          Server Host
 Client/(terminal)   (mainframe computer)




                          Presentation logic
                          Application logic
                          Data access logic
                          Data storage
       Server-Based Computing
• Server does everything
• Client just captures keystrokes and displays
  information
• Server can become overloaded
• Upgrades are
  expensive
Client-Based Computing

      Client               Server
 (microcomputer)      (microcomputer)




 Presentation logic    Data storage
 Application logic
 Data access logic
         Client-Based Computing
•   Client does most of the work
•   Server just stores the data
•   Network traffic can be great
•   All data must travel over the NW for
    processing
    – e.g. DB query
Client-Server-Based Computing
                              Server
                          (microcomputer
          Client           minicomputer
     (microcomputer)        mainframe)




     Presentation logic   Data access logic
     Application logic    Data storage
Advantages of Client-Server-Based
          Computing
• Scalable
  – Easy to increase storage capacity
     • Add another HD or server
  – Easy to increase number of clients
• Supports a variety client types
• More reliable, no
  single point of failure
• Less expensive
Limitations of Client-Server-Based
            Computing
• Complexity
  – Applications have two parts
  – Writing software effectively is hard
            Client-Server Tiers
• Different ways to split application logic
  between client and server
• Previous examples were 2-Tiered
      Two-Tiered Client-Server
• Server is responsible for the data
• Client is responsible for application and
  presentation logic
    Three-Tiered Client-Server
                                            Database Server
                                            (microcomputer
       Client          Application Server    minicomputer
  (microcomputer)       (microcomputer)       mainframe)




  Presentation logic   Application logic    Data access logic
                                            Data storage


Common for Web interface to a DB
n - Tiered Client-Server
          Client         Application Server
     (microcomputer)      (microcomputer)




   Presentation logic            Application logic

   Application Server     Database Server
    (microcomputer)     (micro, mini, mframe)




                          Data access logic
    Application logic
                            Data storage
n - Tiered Client-Server Attributes
• Typical Pros             • Typical Cons/Limits
  – Separates                – Greater load on the
    processing to better       network
    balance load             – More difficult to
  – More scaleable             program and test
         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
INFRASTRUCTURE DESIGN
    Deployment Diagram Components

• Nodes
  – Any piece of hardware in the model
  – A computational resource
  – Labeled by its name
  – Stereotype to label the type of node
• Artifacts
  – Piece of the information system
     • Such as software or a database table
    Deployment Diagram Components

• Node with Deployed Artifact
  – Shows artifact placed on a physical node
  – Good for showing distribution data or software
• Communication paths
  – Links between nodes of the network
   Deployment Diagram

       Node                Artifact




    Node with         Communication Path
Deployment Artifact
Sample Deployment Diagram
          The Network Model
• Shows the major components of the
  information system and their geographic
  locations throughout the organization
• Conveys complexity of the system and how
  components fit together
• Components are
  – Clients / Servers
  – Network equipment
  – Connection to external systems or networks
Sample Network Model
NONFUNCTIONAL REQUIREMENTS
             Nonfunctional Requirements
• Operational
   – Specify the operating environment
       •   Operating system
       •   System software
       •   Information systems
       •   Physical environment
             – Usually only if harsh environment or hardening is required
• Technical Environment
   – Type of hardware and software the system will require
   – Focus on
       • Hardware platforms
             – Intel, Motorola, PDA
       • Operating System
       • Database system
       • System software
          Nonfunctional Requirements
• System Integration
   – Interaction with other systems
   – Both internal and external systems
   – Import/export data formats
• Portability
   – Response to changing environments
   – New platforms
   – New data formats
• Maintainability
   – Expected business requirement changes
   – How easily can the system be updated
             Performance Requirements
• Speed
   – Response time of the system
       • Local action are faster
       • Remote services are slower
   – Transaction update time
       • How long for a change to propagate throughout the system
       • e.g. Inventory updates
• Capacity
   – Number of users
       • Total and simultaneous
       • Affects hardware specification
       • Load balancing?
   – Volume of data
           Performance Requirements

• Availability and Reliability
   – Specify available times
      • When can the users count on the system
      • Work week only?
      • Global usage?
   – Permissible failure rate
      • Be realistic
• Security
   – Protect from disruption and data loss
CUTURAL AND POLITICAL
REQUIREMENTS
      Multilingual Requirements
• Need good translations
  – KFC example
• Concurrent multilingual systems
  – Handle language on the fly
• Discrete multilingual systems
  – Separate parts written for each language
              Customization
• Who has control of the application?
• Can each region make changes to the system
• Can they allow subsidiaries to make changes?
            Unstated Norms
• Make assumptions explicit
• Some examples:
  – Date format
  – Numeric format
  – Name order
  – 24/7 support
          Legal Requirements
• Examples:
  – Montréal’s French language laws
  – France’s WWII laws

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:139
posted:12/4/2011
language:English
pages:44