軟件系統(tǒng)設(shè)計(jì)與體系結(jié)構(gòu)：Ch9 Design Patterns(1)

1、 Ch9 Design Patterns(1)Programming to InterfacesOCPSoftware System Design and ArchitectureMain ContentsDesign patternsProgramming to InterfacesOCPWhat is a Design Pattern?A design patternabstracts a recurring design structurecomprises class and/or objectdependencies, structures, interactions, orconv

2、entions distills design experienceElements of Design PatternsDesign patterns have 4 essential elements:Pattern name: increases vocabulary of designersProblem: intent, context, when to apply Solution: UML-like structure, abstract codeConsequences: results and tradeoffsMain ContentsDesign patternsProg

3、ramming to InterfacesOCPProgramming to Interfaces, not Implementations“Connections that address or refer to a module as a whole by its name yield lower coupling than connections referring to the internal elements of another module”Single values VS a collection of valuesTake Care Friend methods and R

4、eferencesShare Data !Iterator PatternIntent Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.Supports multiple traversals of aggregate objects.Provides a uniform interface for traversing different aggregate structures (it support

5、s polymorphic iteration).Abstraction Mechanisms in CLU, Liskov, 1977createIterator( )Iterator PatternStructure/client codeAggregate myList = new ConcreteAggregate( );Iterator itr = myList.createIterator( );Iterator PatternConsequencesProgramming to interfaces and Information HidingIt supports variat

6、ions in the traversal of an aggregate. For example, code generation may traverse the parse tree inorder or preorder. Iterators make it easy to change the traversal. Just replace the iterator instance with a different one.Iterators simplify the Aggregate interface. Iterators traversal interface obvia

7、tes the need for a similar interface in Aggregate.More than one traversal can be pending on an aggregate.11ClientSubjectabstractRequest()RealSubjectRequest()ProxyRequest()refers to-Request()The Proxy Pattern: SolutionThe Proxy PatternThe ProblemProvide a surrogate or placeholder for another object t

8、o control access to itRemote Proxy: provide local representative for object in different address space, may re-code request.Virtual Proxy: creates expensive objects on demand, like in example, may also cache.Protection Proxy: control access to original object, useful when access rights differ.The Pr

9、oxy Pattern ConsequencesThe Proxy pattern introduces a level of indirection when accessing an object:A remote proxy can hide the fact that the object resides in a different address spaceA virtual proxy can perform optimisationsAllow additional housekeepingPrototype PatternClassification Class , Prot

10、otype ClassSpecify the kinds of objects to create using a prototypical instance, and create new objects by copying this prototypePrototype Pattern UMLParticipants: Prototypeo declares an interface for cloning itself. ConcretePrototype o implements an operation for cloning itself. Cliento creates a n

11、ew object by asking a prototype to clone itself.Lets Try!思考題有一個(gè)數(shù)據(jù)列表DataList，其基本類(lèi)型是3維向量ThreeD1）用Java語(yǔ)言實(shí)現(xiàn)該數(shù)據(jù)列表的數(shù)據(jù)結(jié)構(gòu)假設(shè)有三個(gè)外部對(duì)象A,B,C，分別對(duì)其x、y、z維度感興趣，希望訪(fǎng)問(wèn)DataList在相應(yīng)維度的數(shù)據(jù)并進(jìn)行處理2）請(qǐng)定義其對(duì)外的數(shù)據(jù)接口分別使用迭代器與ProxyMain ContentsDesign patternsProgramming to InterfacesOCPOCPFunction of InheritanceIncremental developmentD

12、ata Abstraction and Hierarchy, LiskovModify closed, increment easierOn the Notion of Inheritance，ANTERO TAIVALSAARIAfter 1990s, requirements changed become criticalOCP (depend DIP)Open/Closed Principle (OCP)Software entities should be open for extension, but closed for modificationB. Meyer, 1988 / q

13、uoted by R. Martin, 1996Be open for extensionmodules behavior can be extendedBe closed for modificationsource code for the module must not be changesThere is no 100% OCP!A Simple Example of OCPCopyReadKeyboardWritePrintervoid Copy(ReadKeyboard& r, WritePrinter& w) int c; while (c = r.read () != EOF)

14、 w.write (c);WriteDiskenum OutputDevice printer, disk; void Copy(ReadKeyboard& r, WritePrinter& wp, WriteDisk& wd, OutputDevice dev) int c; while(c = r.read()!= EOF) if(dev = printer) wp.write(c); else wd.write (c);A Simple Example of OCPDiskWriter:Write(c) WriteDisk(c);CopyKeyboardReaderPrinterWrit

15、erDiskWritervoid Copy(ReadKeyboard& r, WritePrinter& w) int c; while (c = r.read () != EOF) w.write (c);思考題Extension:Border( Plain, 3D, Fancy)ScrollBar( Horiz, Vert).VisualComponentdraw()resize()TextViewdraw()resize()SteamedVideoViewdraw()resize()24The Decorator Pattern: ProblemsDecorators expand th

16、e functionality of an instance of a class without changing the class code Add borders or scrollbars to a GUI componentAdding items such as scroll bars as needed provides more flexibility than requiring all windows to have scroll barsAdd headers and footers to an advertisementAdd stream functionality

17、 such as reading a line of input or compressing a file before sending it over the wireMore flexibility than static inheritanceDecorators work behind the scenes, they are transparent to the interfaceThe Decorator Pattern: The SolutionVisualComponentdraw()resize()TextViewdraw()resize()Borderdraw()resi

18、ze()Decoratordraw()resize()ScrollBardraw()resize()SteamedVideoViewdraw()resize()11Plaindraw()resize()3Ddraw()resize()Fancydraw()resize()Decorator contains a visual componentHorizdraw()resize()Vertdraw()resize()27The Decorator Pattern: ConsequencesMore flexible than static inheritanceAvoids feature laden classes high up in hierarchyLo