slide 1 chapter 13 physical architecture layer design
Post on 15-Jan-2016
231 views
TRANSCRIPT
Slide 1
Chapter 13Physical Architecture Layer Design
Slide 2
ObjectivesUnderstand the different physical architecture components.Understand server-based, client-based, and client server physical architectures.Be familiar with distributed objects computing.Be able to create a network model using a deployment diagram.Understand how operational, performance, security, cultural, and political requirements affect the design of the physical architecture layer.Be familiar with how to create a hardware and software specification.
Slide 3
Physical Architecture
Software ComponentsData StorageData Access LogicApplication logicPresentation logic
Hardware ComponentsClient computersServersConnecting network
Slide 4
Server Based Architecture
Client is a terminalServer has functions of
Presentation logicApplication logicData access logicData storage
Slide 5
Server Based Architecture
Slide 6
Client-Server Architectures
Thin Client/Fat ServerClient is little more than a terminalServer handles all processing
Fat Client/Thin ServerClient does all processingServer may just store data
Slide 7
Thick Client
Slide 8
Server has Data2-Tiered Architecture
Slide 9
Client has Presentation Logic
3-tiered Architecture
Slide 10
N-tiered Architecture
Slide 11
Client-Server Benefits
ScalableSupport multiple clients and serversUsing Internet Standards Presentation logic can be separatedMultiple servers make for a generally more reliable network
Slide 12
MiddlewareMiddleware is a type of system software designed to translate between different vendors’ software. Middleware is installed on both the client computer and the server computer. The client software communicates with the middleware that can reformat the message into a standard language that can be understood by the middleware that assists the server software
Slide 13
Client-Server Limitations
ComplexityUpdating the network computers is more complex
Slide 14
Distributed Objects Computing
This is commonly called middlewareDOC allows the developer to simply concentrate on the users, objects, and methods of an application instead of worrying about whichserver contains which set of objects. The client object simply requests the “network” to locate and execute the server object’s method.
Slide 15
Competing ApproachesObject Management Group
Common Object Request Broker Architecture (CORBA)
SunEnterprise JavaBeans (EJB) Java 2 Enterprise Edition (J2EE)
Microsoft Distributed Component Object Model (DCOM) .net initiative
Slide 16
Selecting a Physical Architecture
Cost of InfrastructureCost of DevelopmentEase of DevelopmentInterface CapabilitiesControl and SecurityScalability
Slide 17
Characteristics
Slide 18
Deployment Diagram Components
NodesAny piece of hardware in the model
ArtifactsPiece of the information system such as software component, database table, …
Communication pathsLinks between nodes of the network
Slide 19
Deployment Diagram
Slide 20
Deployment Diagram (cont.)
Slide 21
Diagram Examples
Slide 22
The Network Model
The network model is a diagram that shows the major components of the information system (e.g., servers, communication lines, networks) and their geographic locations throughout the organization.
Slide 23
Network Model Example
Slide 24
NonFunctional Requirements
Operational Specify the operating environment
Technical EnvironmentType of hardware and software
System Integration Interaction with other systems
Portability Response to changing environments
MaintainabilityExpected business requirement changes
Slide 25
Performance Requirements
SpeedResponse time of the systemTransaction update time
CapacityNumber of users Volume of data
Availability and ReliabilitySpecify available timesPermissible failure rate
SecurityProtect from disruption and data loss
Slide 26
Security
Slide 27
Cultural and Political
MultilingualCustomizationMaking unstated norms explicitLegal requirements
Slide 28
Cultural and Political Rqrts.
Slide 29
Synopsis
Slide 30
Sample Specifications
Slide 31
CD System –Op. Rqrts.
Slide 32
CD Systems - Performance
Slide 33
CD Systems – Security/Cultural
Slide 34
SummaryPhysical Architecture Layer
Choose server vs. client-serverMiddlewareAssess strengths and weaknesses
Infrastructure designVarious clientsNetwork equipment
Nonfunctional RequirementsOperationalPerformanceSecurity
Hardware and software specification