Wolfgang Pree Software Research Lab Univ. of Constance Germany

Transcription

1 Marcus Fontoura CS Department Princeton Univ. U.S.A. Wolfgang Pree Software Research Lab Univ. of Constance Germany Bernhard Rumpe Software Engineering Munich Tech. University Germany 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June UML-F Foundations Terminology: frameworks & components Essential framework patterns Goals of UML-F The UML-F Profile Presentation tags How to present a model? Basic modeling tags Basic modeling concepts Essential pattern tags Annotating 5 essential patterns Catalog & domain-specific pattern tags UML-F & adaptation cookbooks 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

2 Case Study: The JUnit testing framework Tool support for UML-F 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Terminology: frameworks & components 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

3 Construction of complex software systems out of reusable software components: 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Framework := A piece of software that is extensible through the callback style of programming application program library routines 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

4 Component := A piece of software with a programming interface Consequences:» frameworks that offer a programming interface are components» module-oriented languages (Modula, Oberon, Ada) and component standards (CORBA, COM, JavaBeans) just offer different ways of defining such programming interfaces 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Essential framework patterns 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

5 Templates and hooks provide insights in the few construction principles of frameworks, i.e., how to keep socalled hot spots/ variation points flexible. Terminology, Part I: Basic framework building blocks provided by OO language concepts:» template method frozen spot» hook method hot spot/variation point Template methods define a complex default behavior which is adjustable by hook methods. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June UML class diagram inheritance CurrencyConverter convert(...) MyCurrConv public class CurrencyConverter {... public void convert(...) { // template method double result, value;... switch (...) { case... :... result= round(value); break; case... :... result= round(value);... }... } public double round(double val) { // hook method... }... } template hook 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

6 Terminology, Part II: template class T := contains the template method hook class H := contains the hook method(s) only a few combinations are possible these combinations form the essential patterns In the CurrencyConverter example, template and hook method are in the same class, i.e., T and H are unified. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Unification: T and H class are unified CurrencyConverter t() h() TH convert(...) MyCurrConv adaptations can only be done by overriding the hook method adaptations require an application restart 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

7 Separation: T and H classes are separated directed association T H t() h() the behavior of a T object can be modified by composition, i.e., by plugging in specific H objects adaptations at run time become feasible 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June CurrencyConverter rpol RoundingPolicy convert(...) hook template DefaultRPol RPol10 RPol100 public void defineroundingpolicy (RoundingPolicy rp) { rpol= rp; } public void convert(...) { double result, value;... result= rpol.round(value);... } 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

8 Catalog entry hook class hook m ethod A bstract Facto ry AbstractFactory CreateProduct() B uilder Builder BuildPart() Command Command Execute() Inte rpre te r AbstractExpression Interpret() Observer Observer Update() Prototype Prototype Clone() S tate State Handle() S trate gy Strategy AlgorithmInterface() 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June H 1 TH T These patterns allow» building of directed graphs of interconnected objects» message forwarding in the object graphs due to a certain structure of the template method The playground of adaptations through composition is enlarged 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

9 Composite, Decorator, and Chain of Responsibility: * H 1 H 1 TH T T (and Unification, Separation are the 5 essential patterns) 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June What is a template method in one context may become a hook method in another context hooks scale up the essential framework construction patterns scale up T T H T H H 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

10 Framework-centered GoF pattern catalog entries apply essential construction principles» entries mainly differ in the semantics of their hooks.» denoting this semantics in the model helps to understand the design & code how to adapt a framework Modeling standard UML 1.3 does not sufficiently support framework/pattern documentation. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Any framework part that applies a Unification or Separation pattern attaches a specific semantics (purpose) to the hook. Often the pattern is named after the hook s purpose. The structure of a framework-centered pattern relies on one of the essential patterns. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

11 Goals of UML-F 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June UML-F provides the notational elements to precisely annotate and document design patterns. UML-F can be used to concisely communicate design. UML-F is itself structured in the spirit of frameworks, i.e., an extensible profile. UML-F comprises a lean, memonic set of notational elements. UML-F relies on the UML standard, that is, UML-F extends UML using existing UML extension mechanisms. The UML-F notational elements should be adequate for being integrated in UML tool environments. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

12 Catalog & domain specific patterns Factory Method Template Observer Command Essential patterns Unification Separation Basic modeling tags Presentation tags «fixed» «adapt-static» «adapt-dyn» δ Λ 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June UML 1.3 provides «stereotypes» and {tag=value} pairs» stereotypes are restricted: no value attached, only one per model element» Tagged value pairs are more flexible and combinable UML-F unifies both in the tag-mechanism, by writing» «tag:5» and {tag=5} interchangeably» «tag» is short for «tag:true»» «tag1,tag2» is OK» Special forms of tags, e.g. instead of «complete:true»» Tags values have types (e.g. Boolean,String,Integer) 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

13 Presentation tags 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Model diagrammatic representation on the paper Are all elements of the model presented in the diagram?» indicates: yes, all are shown» indicates: no, there may be more present in the model att1 att2 A att1 A attribute list may be incomplete A foo1() foo2() foo1() foo2() the class is shown completely operation list is complete nothing is known about A s structure 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

14 Flat and hierarchical representation of the design m1() m2() m3() m1() m2()» Λ (hierarchy-symbol): all elements are shown (expanded or flat version)» δ (delta): only the delta is shown inherited operation list is completely shown don t care S A m4new() overridden or new overridden with super()-call m1() m2() m3() m1() m2() 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June S A m4new() δ m1() m2() m3() A m4new() Λ inherited new/re-defined ops completely shown, but no inherited operations white rectangle: the method is inherited and not redefined gray rectangle: the method is either newly defined, or it is inherited, but completely redefined half gray / half white rectangle: the method is redefined, but uses the inherited method through a super() call don t care rectangle: the diagram does not reveal any information (can actually be either of the above three) 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

15 Basic modeling tags 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Tag name Applies to Value Description «fixed» «adapt-static» «adapt-dyn» «application» «framework» Class, Method, Generalization Interface, Class, Method, Generalization Interface, Class, Method, Generalization Class, Package, Interface Class, Package, Interface Bool Bool Bool Bool Bool The element is fixed. The element can be adapted during design-time through subclassing. The interface, class, method can be changed through dynamic loading of new subclasses during runtime. The element belongs to the application. The element belongs to the framework. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

16 Modeling the Rounding example with the basic UML-F modeling tags «framework» CurrencyConverter +convert() «fixed» «framework» RoundingPolicy +round() «adapt-static» «adapt-static» «application» DefaultRPol +round() «application» +round() RPol10 «application» +round() RPol , M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Combining basic modeling and presentation tags «framework»... CurrencyConverter +convert() «fixed» «framework» RoundingPolicy +round() «adapt-static» «adapt-static» «application» δ «application» δ «application» δ DefaultRPol RPol10 RPol100 +round() +round() +round() 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

17 Essential patterns tags 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June The basic modeling tags are rather flexible but are also quite low level» Use them as building blocks for introducing new tags» Patterns usually combine several tags Each new layer of tags is more specific and less flexible» the tags contain more semantic that describes purpose and usage 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

18 The «fixed» method becomes The «adapt-dyn» and «adapt-static» methods The class with the template method The class with the hook method «template» «hook» «template» «hook» A class can be both «template» and «hook»» e.g in the Unification pattern,» or through participation in several pattern identification through pattern names 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Two equivalent representations of the same design - using basic tags and using «template» and «hook» tags «template: s1» A foo() «template: s1» «hook: s1» «template: s2» B bar() «hook: s1» son() «hook: s2» C «hook: s2» ton() «template: s2» «fixed» A «adapt-static» B «adapt-static» C foo() «fixed» bar() «adapt-static» son() «adapt-static» ton() «fixed» 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

19 The Rounding example with «template» and «hook» tags «framework» CurrencyConverter +convert() «template» «framework» RoundingPolicy +round() «hook» «adapt-static» «application» DefaultRPol +round() «application» +round() RPol10 «application» +round() RPol , M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Define a tags to:» Make the use of the basic framework patterns explicit» Higher level of system documentation gives more compact, yet concise documentation easier to understand The «template» and «hook» tags are the building blocks for the basic framework patterns tags 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

20 Design based on the «template» and «hook» tags Design based on the Unification pattern tags convert(...) «template, hook: Rounding» CurrencyConverter «template: Rounding» «hook: Rounding» «Unif TH: Rounding» CurrencyConverter convert(...) «Unif-t: Rounding» «Unif-h: Rounding» MyCurrConv pattern specific tag as a combination of basic tags 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Design based on the Separation pattern tags «Sep T: RPol» CurrencyConverter «Sep H: RPol» RoundingPolicy convert(...) «Sep t: RPol» «Sep h: RPol» DefaultRPol RPol10 RPol , M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

21 The «template» and «hook» tags are also the building blocks for the recursive patterns tag set Composite, Decorator, and Chain of Responsibility: * H 1 H 1 TH T T 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June H h() * Item getsizeinbytes(): long... T Folder TextDoc DrawDoc t() getsizeinbytes(): long additem(i: Item) removeitem(name: String)... getsizeinbytes(): long... getsizeinbytes(): long... long size=0; for each i in items size+= i.getsizeinbytes(); return size; add i to collection of items 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

22 object diagram :DrawDoc :Folder :Folder :TextDoc :TextDoc link object 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Class tags «Composite Component» «Composite Composite» «Composite Leaf» Method tags «Composite op()» «Composite add()» «Composite remove» operation() «template» Composite «template» * «hook» Component operation() «hook» , M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

23 Modeling the Item-Folder framework with the Composite pattern tags: * «C Comp: ItemM» Item getsizeinbytes(): long... «C op(): ItemM» «C Composite: ItemM» Folder getsizeinbytes(): long «C op(): ItemM» additem(i: Item) «C add: ItemM» removeitem(name: String) «C remove: ItemM»... «C Leaf» TextDoc getsizeinbytes(): long «C op(): ItemM»... «C Leaf» DrawDoc getsizeinbytes(): long «C op(): ItemM» , M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June vobj vobj 1 1 draw()... «D Comp» VObject «D op()-h» «D Decorator: ScrollerD» Scroller draw() «D op()-t: ScrollerD»... «D Decorator: BorderD» BorderItem draw() «D op()-t: BorderD» vobj.draw(); calculate scroll position scroll to position vobj.draw(); draw border draw()... «D ccomp» TextView 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

24 nextconv 1 «COR Handler» Converter if (nextconv) nextconv.convert(...);... convert(file) «COR hreq-fwd» «COR chandler» HTMLConverter... convert(file) «COR hreq»... convert(file) «COR chandler» RTFConverter «COR hreq»... if (can convert )... // do it if (can convert )... // do it 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Catalog & domainspecific pattern tags 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

25 The UML-F tags for the essential patterns already allow the annotation of frameworks on a pattern level In order to express more semantics, additional tags that resemble directly the framework-related patterns in the GoF catalog are helpful Recipe: take the GoF pattern structure => define UML-F tags Domain-specific pattern tags rely on the tags for the essential framework patterns 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June The Strategy pattern tags are defined in terms of the Separation pattern: «Sep-t» = «Strategy-Ctxt» «Sep-h» = «Strategy-S»... «Strategy Ctxt» «Strategy S» CurrencyConverter RoundingPolicy convert(...) «Strategy cint()» «Strategy algoint()» DefaultRPol RPol10 RPol , M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

26 «Sep T» Calculator «Sep H» CalcAlgorithm calcop() «Sep tl)» calcalgo() «Sep h()» ConcreteAlgorithm calcalgo() «Calc C» CurrencyConverter «Calc Algo» RoundingPolicy convert(...) «Calc cop()» «Calc calgo()» DefaultRPol RPol10 RPol , M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June UML-F & adaptation cookbooks 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

27 A cookbook is framework specific It is a textual description of the» framework architecture and design, and» how to apply the framework through its adaptation (collection of Howto -recipes) UML-F diagrams complement cookbooks describing both, the architecture, and giving suggestions, where and which code has to be written by the application developer 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June How to adapt currency converter?» If all the required rounding policies have been defined the adaptation is by composition only» If a rounding policy still has to be defined: Subclass RoundingPolicy Override round() 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

28 The «fixed» generalization indicates the adaptation by composition principle no new classes are added «framework» CurrencyConverter +convert() «fixed» «framework» RoundingPolicy +round() «adapt-static» «fixed» «application» DefaultRPol +round() «application» +round() RPol10 «application» +round() RPol , M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June The «application» and «adapt-static» tags indicate where the code should be added The symbol indicates that the only method that has to be defined in the application classes is round() «framework»... CurrencyConverter +convert() «fixed» «framework» RoundingPolicy +round() «adapt-static» «adapt-static» «application» δ NewClass +round() 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

29 Use the cookbook recipes for the basic framework patterns to define new ones The UML-F tags provide the mapping How to adapt currency converter (Separation)?» If all the required (concrete Sep-h classes) rounding policies have been defined the adaptation is black-box» If a rounding policy (concrete Sep-h class) still has to be defined: Subclass RoundingPolicy (Sep-h) Override round() (Sep-h()) 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June The JUnit testing framework 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

30 Adding new test cases: JUnit provides a standard interface for defining test cases and allows the reuse of common code among related test cases. Tests suites: Framework users can group test cases in test suites. Reporting test results: the framework keeps flexible how test results are reported. The possibilities include storing the results of the tests in a database for project control purposes, creating HTML files that report the test activities. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Overview of the JUnit design - Class ComplexTest defines test cases for complex numbers «framework» Test composition (form of association) «framework» TestSuite «framework» TestCase «framework» TestResult «application» ComplexTest 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

31 The initialization part is responsible for creating the text fixture. The test itself uses the objects created by the initialization part and performs the actions required for the test. Finally, the third part cleans up a test. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June The TestCase design is based on the Template Method design pattern - method run() controls the test execution «TemplateM-AbstractClass» TestCase +run() «TemplateM-templateM()» #setup() «TemplateM-primitiveOp()» #runtest() «TemplateM-primitiveOp()» #teardown() «TemplateM-primitiveOp()» public void run() { setup(); runtest(); teardown(); } 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

32 TestCases are grouped into TestSuites a variation of the Composite design pattern «interface» «C-Comp» Test +run() «C-op()-h» «fixed» * Black-box adaptation «TemplateM-AbstractClass» «C-Leaf» TestCase «C-Composite» TestSuite +run() «C-op()-t» ftests +run() «TemplateM-templateM()» +addtest(test) «C-add» <<C-op()» #setup() «TemplateM-primitiveOp()» #runtest() «TemplateM-primitiveOp()» #teardown() «TemplateM-primitiveOp()» 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Failures are situations where the assert() method does not yield the expected result. Errors are unexpected bugs in the code being tested or in the test cases themselves. The TestResult class is responsible for reporting the failures and errors in different ways. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

33 TestResult must provide four methods: starttest() - initialization code addfailure() - reports a failure adderror() - reports an error endtest() - clean-up code «Strategy-Ctxt» TestCase +run() «Strategy-cInt()» «Strategy-S» TestResult +starttest() «Strategy-algoInt()» +addfailure() «Strategy-algoInt()» +adderror() «Strategy-algoInt()» +endtest() «Strategy-algoInt()» 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June (extended) sequence diagram :TestCase :TestResult :error :TestCase :TestResult run() starttest() adderror() setup() call runtest() + (error failure) :failure :TestCase :TestResult choice box teardown() addfailure() timeline endtest() activation 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

34 Cookbook recipes and UML-F diagrams for each of the JUnit variation points» Create a test case (ComplexTest)» Create a test suite (for the ComplexTest methods)» Create an HTML reporting mechanism 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June TestCase adaptation recipe:» Subclass TestCase» Override setup() (optional). The default implementation is empty» Override runtest()» Override teardown() (optional). The default implementation is empty 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

35 TestCaseExample exemplifies the code that has to be added by the application developer White-box adaptation «framework» «TemplateM-AbstractClass» TestCase +run() «TemplateM-templateM()» #setup() «TemplateM-primitiveOp()» #runtest() «TemplateM-primitiveOp()» #teardown() «TemplateM-primitiveOp()» «adapt-static» «application» «TemplateM ConcreteClass» TestCaseExample #setup() «TemplateM-primitiveOp()» #runtest() «TemplateM-primitiveOp()» #teardown() «TemplateM-primitiveOp()» 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June «application» Λ «application» Λ TestCaseExample1 TestCaseExample2 For possible adaptation examples, considering the optional hook methods run() «fixed» setup() «fixed» runtest() «fixed» teardown() «fixed» «application» Λ TestCaseExample3 run() «fixed» setup() «fixed» runtest() «fixed» teardown() «fixed» run() «fixed» setup() «fixed» runtest() «fixed» teardown() «fixed» «application» Λ TestCaseExample4 run() «fixed» setup() «fixed» runtest() «fixed» teardown() «fixed» 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

36 One aspect in the TestCase class cannot be captured in UML-F design diagrams» Method runtest() takes no parameters as input» Different test cases require different input parameters.» The interface for theses test methods has to be adapted to match runtest(). 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June «framework» «TemplateM-AbstractClass» TestCase «adapt-static» For adapting testexample1(). One inner subclass has to be defined for each test method. The inner subclass overrides runtest() so that the corresponding test method can be invoked with the appropriate parameters. «application» TestCaseExample #setup() #testexample1() «fixed» #testexample2() «fixed» #teardown() «adapt-static» For adapting testexample2() «application» «application» #runtest() «fixed» #runtest() «fixed» 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

37 «application» ComplexTest #setup() «fixed» #testadd() «fixed» #testmultiply() «fixed» «fixed» «application» «application» #runtest() «fixed» #runtest() «fixed» public class ComplexTest extends TestCase { private ComplexNumber fonezero; private ComplexNumber fzeroone; private ComplexNumber fminusonezero; private ComplexNumber foneone; protected void setup() { fonezero = new ComplexNumber(1, 0); fzeroone = new ComplexNumber(0, 1); fminusonezero = new ComplexNumber(-1, 0); foneone = new ComplexNumber(1, 1); } public void testadd() { //This test will fail!!! ComplexNumber result = foneone.add(fzeroone); assert(foneone.equals(result)); } public void testmultiply() { ComplexNumber result = fzeroone.multiply(fzeroone) assert(fminusonezero.equals(result)); } 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June «interface» «C-Comp» Test +run() «C-op()-h» «fixed» * Adaptation by overriding the suite() method :TestCase suite() s:testsuite «C-Leaf» TestCase +run() «C-op()» «C-Composite» TestSuite +run() «C-op()-t» +addtest(test) «C-add» ftests s * addtest() +suite() 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

38 TestCase and TestSuite are related variation points public static Test suite() { TestSuite suite = new TestSuite(); suite.addtest(new ComplexTest("testing add") { protected void runtest() { this.testadd(); } } ); suite.addtest(new ComplexTest("testing multiply") { protected void runtest() { this.testmultiply(); } } ); return suite; } 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June «framework» «Strategy-S» TestResult +starttest() «Strategy-algoInt()» +addfailure() «Strategy-algoInt()» +adderror() «Strategy-algoInt()» +endttest() «Strategy-algoInt()» «adapt-static» «application» TestResultExample +starttest() +addfailure() +adderror() +endttest() «application» HTMLTestResult +starttest() «fixed» +addfailure() «fixed» +adderror() «fixed» +endtest() «fixed» print the number of tests executed so far and closes the file create the HTML file report the failure by appending a line to the HTML file report the error by appending a line to the HTML file 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

39 Display of a sample HTML file that reports a failure. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Pattern-annotated diagram for the main JUnit classes Composite: Component Test +run() #setup() Template Method #runtest() #teardown() * Composite: Leaf +run() TestCase +run() TestSuite +addtest() ftests Composite 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

40 Tool support for UML-F 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June «Strategy-Ctxt» TestCase +run() «Strategy-cInt()» «Strategy-S» TestResult +starttest() «Strategy-algoInt()» +addfailure() «Strategy-algoInt()» +adderror() «Strategy-algoInt()» +endtest() «Strategy-algoInt()» «Sep-T» TestCase «Sep-H» TestResult +run() «Sep-t» +starttest() «Sep-h» +addfailure() «Sep-h» +adderror() «Sep-h» +endtest() «Sep-h» 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

41 A single class participates in several design patterns This is a common situation that may lead to a polluted design «TemplateM-AbstractClass» «C-Leaf» «Strategy-Ctxt» TestCase +run() «TemplateM-templateM()» <<C-op()» «Strategy-cInt()» #setup() «TemplateM-primitiveOp()» #runtest() «TemplateM-primitiveOp()» #teardown() «TemplateM-primitiveOp()» 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Use of design incompleteness presentation tags for slicing the design «TemplateM-AbstractClass» «C-Leaf» «Strategy-Ctxt» TestCase +run() «TemplateM-templateM()» <<C-op()» «Strategy-cInt()» #setup() «TemplateM-primitiveOp()» #runtest() «TemplateM-primitiveOp()» #teardown() «TemplateM-primitiveOp()» To the Template Method To the Composite To the Strategy 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

42 «framework» «Strategy-S» TestResult +starttest() «Strategy-algoInt()» +addfailure() «Strategy-algoInt()» +adderror() «Strategy-algoInt()» +endttest() «Strategy-algoInt()» «adapt-static» «application» TestResultExample +starttest() +addfailure() +adderror() +endtest() «application» HTMLTestResult +starttest() «fixed» +addfailure() «fixed» +adderror() «fixed» +endtest() «fixed» 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Bibliography 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June

43 UML-F Web-site: Fontoura M., Pree W., Rumpe B. (2000) The UML Profile for Framework Architectures, Addison- Wesley. Beck K. (1999). extreme Programming explained, Addison-Wesley Beck K. and Gamma E. (1998a). JUnit: A Cook s Tour (ftp:// Beck K. and Gamma E. (1998b). Test Infected: Programmers Love Writing Tests, Java Report, 3(7) Boehm B. (1994). Megaprogramming. Video tape by University Video Communications ( Stanford, California Booch G. (1994). Object-Oriented Analysis and Design with Applications. Redwood City, CA: Benjamin/Cummings Booch G., Rumbaugh J., Jacobson I. (1998) The Unified Modeling Language User Guide. Reading, Massachusetts: Addison-Wesley Coad P. (1992). Object-oriented patterns. Communications of the ACM, 33(9) D Souza D., Wills A. (1998) Objects, Components, and Frameworks with UML. Reading, Massachusetts: Addison- Wesley D Souza D., Sane A., Birchenough A. (1999) First-Class Extensibility for UML Packaging of Profiles, Stereotypes, Patterns. In: «UML» 99 The Unified Modeling Language. Conference Proceedings. Eds: R. France, B. Rumpe. Springer Verlag. LNCS , M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June Fayad M., Schmidt D., Johnson R. (1999) Building Application Frameworks: Object-Oriented Foundations of Framework Design, Wiley Fayad M., Schmidt D., Johnson R. (1999) Implementing Application Frameworks: Object-Oriented Frameworks at Work, Wiley Fayad M., Schmidt D., Johnson R. (1999) Domain-Specific Application Frameworks: Manufacturing, Networking, Distributed Systems, and Software Development, Wiley Gamma E., Helm R., Johnson R. and Vlissides J. (1995) Design Patterns Elements of Reusable OO Software. Reading, MA: Addison-Wesley (also available as CD) Jacobson I., Booch G., Rumbaugh J., (1999) The Unified Software Development Process. Reading, Massachusetts: Addison-Wesley Johnson R. (1992). Documenting Frameworks Using Patterns, ACM Conference on Object-Oriented Programming, Systems, Languages and Applications 1992 Krasner G. and Pope S. (1998). A Cookbook for Using the Model-View-Controller User Interface Paradigm in Smalltalk-80, Journal of Object-Oriented Programming, 1(3) Pree W. (1995) Design Patterns for Object-Oriented Software Development. Reading, Massachusetts: Addison- Wesley/ACM Press Rumbaugh J., Jacobson I., Booch G., (1998) The Unified Modeling Language Reference Manual. Reading, Massachusetts: Addison-Wesley Szyperski C. (1998) Component Software Beyond Object-Oriented Programming, Addison-Wesley. 2000, M. Fontoura, W. Pree, B. Rumpe TE, Mont Saint-Michel, June