Software Engineering-5（英文版）.ppt

b) Subsystem Design Distribute subsystem behavior to subsystem elements Document subsystem elements Describe subsystem dependencies Subsystem Responsibilities Subsystem responsibilities defined by interface operations Model interface realizations Interface operations may be realized by Internal class operations Internal subsystem operations Distributing Subsystem Responsibilities Identify new, or reuse existing, design elements (for example, classes and/or subsystems) Allocate subsystem responsibilities to design elements Incorporate applicable mechanisms (for example, persistence, distribution) Document design element collaborations in “interface realizations” One or more interaction diagrams per interface operation Class diagram(s) containing the required design element relationships Revisit “Identify Design Elements” Adjust subsystem boundaries and dependencies, as needed Modeling Convention: Subsystem Interaction Diagrams Example: CourseCatalogSystem Subsystem in Context Review: Incorporating JDBC: Steps Provide access to the class libraries needed to implement JDBC Provide java.sql package Create the necessary DBClasses One DBClass per persistent class Course Offering persistent class = DBCourseOffering Review: Incorporating JDBC: Steps (cont.) Incorporate DBClasses into the design Allocate to package/layer DBCourseOffering placed in CourseCatalogSystem subsystem Add relationships from persistency clients Persistency clients are the CourseCatalogSystem subsystem clients Create/Update interaction diagrams that describe: Database initialization Persistent class access: Create, Read, Update, Delete Example: Local CourseCatalogSystem Subsystem Interaction Example: Billing System Subsystem In Context Example: Local BillingSystem Subsystem Interaction Example: CourseCatalogSystem Subsystem Elements Example: Billing System Subsystem Elements Subsystem Dependencies: Guidelines Subsystem dependency on a subsystem Subsystem dependency on a package Example: CourseCa