软件需求课件刘艳霞课件2 chap 9-iteration 2--more grasp.pptVIP

* Indirection Problem: Where to assign a responsibility, to avoid direct coupling between two (or more) things? How to de-couple objects so that low coupling is supported and reuse potential remains higher? Solution: Assign the responsibility to an intermediate object to mediate between other components or services, so that they are not directly coupled. * Example1 : PersistentStorage The Pure fabrication example of de-coupling the Sale from the relational database services through the introduction of a PersistentStorage is also an example of assigning responsibilities to support Indirection. The PersistentStorage acts as a intermediary between the Sale and database Example2: TaxCalculatorAdapter * Indirection : Example3 Consider a CreditAuthorizationService class that needs to use a Modem Bad approach: Put low-level calls to the Modem API directly in the methods of the CreditAuthorizationClass Better approach: Add an intermediate Modem class that insulates CreditAuthorizationClass from the Modem API * * Indirection : Example3 CreditAuthorization Service Modem 1:dial(phoneNum) authorize(payment) * Indirection Low coupling Promotes reusability Protected Variation Problem: How do we design objects and systems so that instability in them does not have undesirable effects on other elements? Instability here doesn’t mean “crashy”. It means prone to change or evolve. Solution: Identify points of predicted instability (variation) and assign responsibilities to create a stable interface around them * Key Concept Example: ITaxCalculatorAdapter Instability or variation different interfaces or APIs of external tax calculators. integrate with many existing tax calculator systems, and also with future third-party calculators not yet in existence. By adding a level of indirection, an interface, and using polymorphism with various ITaxCalculatorAdapter implementations, protection within the system from variations in external APIs is achieved. Internal obj