软件工程（美国加州大学）4.ppt

ICS 52Introduction to Software Engineering Lecture Notes for Spring Quarter, 2004 André van der Hoek Lecture 5-1 Copyright ?2004, André van der Hoek Duplication of course material for any commercial purpose without the written permission of the lecturer is prohibited. Today’s Lecture USES relation IS-COMPOSED-OF relation COMPRISES diagram USES diagram In Design, We Can Do Anything… …Even when Restricted by Style Fan-in and Fan-out USES Relation Definition Level 0: those modules that do not use any other modules Level i: those modules that use at least one module at level i – 1 and use no modules at level i or greater Use Determine flexibility Determine reuse Determine incremental testability Example Observations The USES relation does not necessarily form a hierarchy An acyclic directed graph is good Cycles generally are bad Indication of high coupling Indication of broken separation of concerns Rules of thumb: allow a to use b… …if it makes a simpler …if b is not only used by a but also by other components Observations Some invocations are not USES Consider a transfer of control Consider a scheduler inside a program Some USES do not involve invocations Consider interrupt handlers Consider global variables Consider a blackboard IS-COMPONENT-OF Relation Definition Module Mi IS-COMPONENT-OF module M if M is realized by aggregating several modules, one of which is Mi The combined set of all modules that exhibit the IS-COMPONENT-OF relation with respect to module M are said to implement module M Use Determine hierarchical decomposition of a component in its subcomponents Abstract details Example Comprises Diagram USES Diagram – Step 1 USES Diagram – Step 2 USES Diagram – Step 3 USES Diagram – Step 4 Observations Why do we identify higher-level modules in the first place? Understanding Abstraction through composition IS-COMPONENT-OF is not is-attribute-of is-inside-of-on-the-screen is-subclass-of is-accessed-through-the-menu-of The Design Pro