四川大学软件工程课件 Unit07.pptVIP

* Chapter 11Component-Level Design * What is a Component? Unified Modeling Language defines a component as “… a modular, deployable, and replaceable part of a system that encapsulates implementation and exposes a set of interfaces.” OO view: a component contains a set of collaborating classes Conventional view: the internal data structures that implement the processing logic, and an interface that enables the component to be invoked and data to be passed to it. * OO Component Analysis class Elaborated design class Design component Requirements analysis ? analysis class of PrintJob Architecture design ? component of PrintJob Component-level design: Interfaces: computeJob initiateJob Elaborated design class: to guide implementation Data structure, Algorithmic detail, Interface computeJob initiateJob * Conventional Component Elaborated module Design component Requirements analysis ? data flow diagrams Architecture design ? structure chart Component-level design: Each module in structure chart is elaborated Interface, Data structure, Algorithmic detail, State diagram getJobData module algorithm detail accessCostsDB database * Basic Design Principles The Open-Closed Principle (OCP). “A component should be open for extension but closed for modification. The Liskov Substitution Principle (LSP). “Subclasses should be substitutable for their base classes. Dependency Inversion Principle (DIP). “Depend on abstractions. Do not depend on concretions.” * Basic Design Principles The Interface Segregation Principle (ISP). “Many client-specific interfaces are better than one general purpose interface. The Release Reuse Equivalency Principle (REP). “The granule of reuse is the granule of release.” The Common Closure Principle (CCP). “Classes that change together belong together.” The Common Reuse Principle (CRP). “Classes that aren’t reused together should not be grouped together.” * Design Guidelines Components Naming conventions s