EXample: Incorporating RMI (continued) Application <<layer>> Business services Application Registration Package d (from Application) University Artifacts ( from Business Services) <<layer> Business Middleware Services Java rmI Java.io Naming Server (from java rmi) <<interface>> <<laver>> Serializable UnicastRemote Middleware (from java. io) <<interface>> Object remote (from Server (from java rmi
16 Example: Incorporating RMI (continued) <<layer>> Business Services <<layer>> Middleware <<layer>> Application Middleware <<layer>> Application <<layer>> Business Services <<layer>> java.rmi <<interface>> remote (from java.rmi) Naming (from java.rmi) UnicastRemote Object (from Server) Server <<interface>> Serializable (from java.io) Java.io Registration Package (from Application) University Artifacts (from Business Services)
Use-Case Design Steps Describe interaction among design objects ★◆ Simplify sequence diagrams using subsystems Describe persistence-related behavior Refine the flow of events description Unify classes and subsystems M
17
Guidelines: Encapsulating Subsystem Interactions Subsystems should be represented by their interfaces on interaction diagrams Messages to subsystems are modeled as messages to the subsystem interface Messages to subsystems correspond to operations of the subsystem interface Interactions within subsystems are modeled in Subsystem Design <interface: ≤< subsystem>> My Subsystem InterfaceA op10 op10 H
18
Advantages of Encapsulating Subsystem Interactions Use-case realizations Are less cluttered Can be created before the internal designs of subsystems are created (parallel development Are more generic and easier to change (Subsystems can be substituted. H-
19
Use-Case Design Steps Describe interaction among design objects Simplify sequence diagrams using subsystems ★◆ Describe persistence- related behavior Refine the flow of events description Unify classes and subsystems BM
20