Software Engineering-3（英文版）.ppt

Review: Subsystems and Interfaces Are a “cross between” a package (can contain other model elements) and a class (has behavior) Realizes one or more interfaces that define its behavior Subsystems and Interfaces (cont.) Subsystems : Completely encapsulate behavior Represent an independent capability with clear interfaces (potential for reuse) Model multiple implementation variants Packages versus Subsystems Subsystems Provide behavior Completely encapsulate their contents Are easily replaced Subsystem Usage Subsystems can be used to partition the system into parts that can be independently: ordered, configured, or delivered developed, as long as the interfaces remain unchanged deployed across a set of distributed computational nodes changed without breaking other parts of the systems Subsystems can also be used to: partition the system into units which can provide restricted security over key resources represent existing products or external systems in the design (e.g. components) Identifying Subsystems Hints Look at object collaborations. Look for optionality. Look to the user interface of the system. Look to the actors. Look for coupling and cohesion between classes. Look at substitution. Look at distribution. Look at volatility. Candidate Subsystems Analysis classes which may evolve into subsystems: Classes providing complex services and/or utilities Boundary classes (user interfaces and external system interfaces) Existing products or external systems in the design (e.g., components): Communication software Database access support Types and data structures Common utilities Application-specific products Identifying Subsystems Identifying Interfaces Purpose To identify the interfaces of the subsystems based on their responsibilities Steps Identify a set of candidate interfaces for all subsystems. Look for similarities between interfaces. Define interface dependencies. Map the interfaces to subsystems. Define the behavior specified b