1 / 11

INFS 6225 Object-Oriented Systems Analysis & Design

INFS 6225 Object-Oriented Systems Analysis & Design. Chapter 11: Physical Architecture Layer Design. Architecture Design. Plan for Hardware, Software, & Infrastructure Part of the System Architecture Layer Designed based on business needs specified in the Analysis Phase.

milton
Download Presentation

INFS 6225 Object-Oriented Systems Analysis & Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INFS 6225 Object-Oriented Systems Analysis & Design Chapter 11: Physical Architecture Layer Design

  2. Architecture Design • Plan for Hardware, Software, & Infrastructure • Part of the System Architecture Layer • Designed based on business needs specified in the Analysis Phase

  3. Three Main Designs • Server-Based – all functions performed on server (e.g., Mainframe configuration) • Client-Based – data stored on server, all other functions performed on local PC • Client-Server – data & data access on server, application & presentation performed on local PC • Fat Client – more application logic on local PC • Thin Client – less application logic on local PC

  4. Tiered Architecture • All Client PCs count as one tier • Each Server PC counts as one tier Four-tier client-server architecture >>

  5. Network Models • Shows major components (e.g., servers, communication lines, networks) & their geographic location • Show complexity of system • Show how components fit together • No standards for creating Network Models

  6. Nonfunctional Requirements • Operational – specifies operating environment • Performance – response time, capacity, & reliability • Security – protection from disruption & data loss • Cultural & Political –specific requirements of host countries

  7. Nonfunctional RequirementsContinued • Operational • Technical – HW, SW, & NW specifications • System Integration – interface w/ other systems • Portability – operation in other environments • Maintainability – adapting to changing business requirements

  8. Nonfunctional RequirementsContinued • Performance • Speed – response time • Capacity – volume of data & users (total & peak) • Reliability – operational vs. not operational

  9. Nonfunctional RequirementsContinued • Security • System Value – estimated value of system & data • Access Control – who can access what • Encryption/Authentication – protection of data across networks/Internet • Virus Control – control spread of viruses

  10. Nonfunctional RequirementsContinued • Cultural & Political • Multilingual – language(s) of host country • Customization – user-defined fields & formats • Unstated Norms – use of local date, currency, measurement formats & labels • Legal – abiding by host country(s) laws

  11. System Specification • Document that describes the HW & SW needed to support the system • Three main steps to create: • List all HW needed • Describe minimum requirements for each piece of HW • List SW to run on each piece of HW

More Related