Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 7 System Design: Addressing Design Goals

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2 Describe boundary conditions Define subsystems Map subsystems to hardware/ Manage Select a Define access design goals persistent data control policies global Implement subsystems software platform control flow Figure 7-1, The activities of system design.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3 :WebServer myMac:Mac:UnixHost :IExplorer aPC:PC :Database :UnixHost :Safari Figure 7-2, A UML deployment diagram representing the allocation of components to different nodes and the dependencies among components.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4 GET POST HttpRequest URL File WebServer DBQuery DBResult Figure 7-3, Refined view of the WebServer component.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5 RoutingSubsystem PlanningSubsystem :OnBoardComputer :WebServer Figure 7-4, Allocation of MyTrip subsystems to hardware.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6 Trip Location PlanningService Segment Crossing RouteAssistant Direction Destination TripProxy SegmentProxy PlanningSubsystem Message Connection CommunicationSubsystem RoutingSubsystem Figure 7-5, Revised design model for MyTrip.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7 PlanningSubsystem MapDBStoreSubsystem TripFileStoreSubsystem RoutingSubsystem CommunicationSubsystem Figure 7-6, Subsystem decomposition of MyTrip after deciding on the issue of data stores.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 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.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9 Figure 7-9, Dynamic access implemented with a protection Proxy. Portfolio buy() sell() estimateYield() 1 1 * 1 Broker buy() sell() estimateYield() Access isAccessible(op) PortfolioProxy

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10 Legitimate Intruder Server User CC# EXP 8/99 Plaintext message Encrypted message 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.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11 PlanningService ManageDrivers ManageMaps ManageServer Administrator StartServer ShutdownServer ConfigureServer > Figure 7-14, Administration use cases for MyTrip.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12 Figure 7-18, ARENA subsystem decomposition, game organization part.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 13 Figure 7-19, ARENA subsystem decomposition, game playing part.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 14 Figure 7-20, ARENA hardware/software mapping.