1 / 14

Art for Chapter 7 System Design: Addressing Design Goals

Art for Chapter 7 System Design: Addressing Design Goals. Figure 7-1, The activities of system design. Define. Implement. Define. subsystems. subsystems. design goals. Map subsystems. to hardware/. software platform. Manage. persistent data. Define access. control policies. Select a.

Download Presentation

Art for Chapter 7 System Design: Addressing Design Goals

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. Art for Chapter 7System Design:Addressing Design Goals

  2. Figure 7-1, The activities of system design. Define Implement Define subsystems subsystems design goals Map subsystems to hardware/ software platform Manage persistent data Define access control policies Select a global control flow Describe boundary conditions

  3. :Safari myMac:Mac :UnixHost :WebServer :UnixHost aPC:PC :Database :IExplorer Figure 7-2, A UML deployment diagram representing the allocation of components to different nodes and the dependencies among components.

  4. WebServer GET URL POST DBQuery HttpRequest DBResult File Figure 7-3, Refined view of the WebServer component.

  5. :OnBoardComputer :WebServer PlanningSubsystem RoutingSubsystem Figure 7-4, Allocation of MyTrip subsystems to hardware.

  6. PlanningSubsystem RoutingSubsystem RouteAssistant PlanningService Trip Location Destination TripProxy Direction Crossing SegmentProxy Segment CommunicationSubsystem Message Connection Figure 7-5, Revised design model for MyTrip.

  7. RoutingSubsystem PlanningSubsystem CommunicationSubsystem TripFileStoreSubsystem MapDBStoreSubsystem Figure 7-6, Subsystem decomposition of MyTrip after deciding on the issue of data stores.

  8. Figure 7-8, Packet filtering firewall: a filter, located at the router, allows or denies individual packets based on header information, such as source and destination.

  9. Access isAccessible(op) 1 Broker * PortfolioProxy Portfolio buy() buy() sell() sell() 1 1 estimateYield() estimateYield() Figure 7-9, Dynamic access implemented with a protection Proxy.

  10. Intruder Legitimate User Server Plaintext message CC# 1234 5678 9012 3456 EXP 8/99 Encrypted message XZ<ASL@#34HF*(*A2135SDA*}BKDAWR#%_AS2255 Figure 7-10, Passive attack. Given current technology, it is relatively easy for a passive intruder to listen to all network traffic. To prevent this kind of attack, encryption makes the information an intruder sees difficult to understand.

  11. ManageDrivers <<include>> ManageMaps StartServer PlanningService <<include>> Administrator ManageServer ShutdownServer <<include>> ConfigureServer Figure 7-14, Administration use cases for MyTrip.

  12. Figure 7-18, ARENA subsystem decomposition, game organization part.

  13. Figure 7-19, ARENA subsystem decomposition, game playing part.

  14. Figure 7-20, ARENA hardware/software mapping.

More Related