Merging of TOSCA Cloud Topology Templates - IAAS

More documents

Recommendations

Info

2 Fundamentals Framework class using the Template Method pattern 1 public abstract class FrameworkClass{ 2 public abstract void hookMethod(); 3 public final void templateMethod(){ 4 // generic algorithm steps 5 hookMethod(); 6 // generic algorithm steps 7 } 8 } Listing 2.3: Code example of a framework class using the Template Method pattern 3 This is clarified further by the code example in Listing 2.4. The non-abstract SpecificClass extends the FrameworkClass by inheritance and overrides the hookMethod to provide specific steps for the overall solution of a particular application area specific problem. Specific class using the Template Method pattern 1 2 3 4 5 public class SpecificClass extends FrameworkClass{ } public void hookMethod(){ } // specific algorithm steps Listing 2.4: Code example of a specific class using the Template Method pattern 4 2.4.3 Factory Method The second design pattern used in the context of frameworks is the Factory Method. 5 The goal of the Factory Method design pattern is to decouple the generic programming logic from the concrete implementation classes. This is especially useful if not all the concrete classes are known during build time. Therefore, the generic (framework) code is implemented against interfaces or abstract classes and is independent of concrete subclasses. The classical Factory Method design pattern is depicted in Fig. 2.3. The Factory class provides an abstract factoryMethod that declares an interface for creating objects of type Product, i.e. extending the abstract Product or also possible implementing an Interface of that name. For every ConcreteProduct that implements or overrides the Product, a corresponding ConcreteFactory that knows how to specifically create a ConcreteProduct has to be provided. 3 Adopted from [15] 4 Adopted from ibid 5 and also its variation the Abstract Factory 18
2 Fundamentals class Factory Method «abstract» Product + operation() : void «abstract» Factory + factoryMethod() : Product ConcreteProduct + operation() : void ConcreteFactory + factoryMethod() : Product return new ConcreteProduct() Fig. 2.3: Factory Method design pattern 6 In the following Listing 2.5, Listing 2.6, Listing 2.7 and Listing 2.8 provide a simple continuous example of the usage of the Factory Method. Abstract Factory using the Factory Method 1 2 3 public abstract class Factory { } public abstract Product createProduct(); Listing 2.5: Code example of abstract factory class of the Factory Method design pattern The abstract class Factory in Listing 2.5 shows the aforementioned abstract factory that defines an abstract factoryMethod to create a new instance of a class implementing a particular interface, in this case the abstract class Product not depicted here but being the same as in Fig. 2.3. A concrete implementation of the abstract factory class is shown in Listing 2.6. The class overrides the createProduct factory method and returns an instance of the ConcreteProduct class from Fig. 2.3. The choice of the specific factory must take place only once, e.g. in an initialization method of the framework as depicted in Listing 2.7. In the rest of the code the factory creates instances by utilizing polymorphism without knowing the exact type of Product. 6 Adopted from [15] 19
Page 1: Institute of Architecture of Applic
Page 5 and 6: Contents Contents 1 Introduction...
Page 7 and 8: List of Figures List of Figures Fig
Page 9 and 10: List of Listings List of Listings L
Page 11 and 12: List of Tables List of Tables Table
Page 13: List of Abbreviations SaaS SAX SESE
Page 16 and 17: 1 Introduction Not in the scope of
Page 18 and 19: 1 Introduction Chapter 6 - Concept
Page 20 and 21: 2 Fundamentals arcs = (, ) and =
Page 22 and 23: 2 Fundamentals bination with a publ
Page 24 and 25: 2 Fundamentals Syntax of the XML co
Page 26 and 27: 2 Fundamentals Additional Relations
Page 28 and 29: 2 Fundamentals However, the TOSCA P
Page 30 and 31: 2 Fundamentals 2.4 Frameworks The f
Page 34 and 35: 2 Fundamentals Code example for a c
Page 36 and 37: 3 Related Work 3 Related Work The f
Page 38 and 39: 3 Related Work tive algorithm with
Page 40 and 41: 4 Assumptions and Requirements for
Page 46 and 47: 5 Concept for Matching of Topology
Page 82 and 83:
5 Concept for Matching of Topology
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
6 Concept for Merging of Topology T
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
7 Architecture & Design of an Exten
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
8 Implementation of the Framework (
Page 148 and 149:
8 Implementation of the Framework F
Page 150 and 151:
8 Implementation of the Framework a
Page 152 and 153:
8 Implementation of the Framework 8
Page 154 and 155:
9 Evaluation of the Algorithms and
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
10 Conclusion and Future Work 10 Co
Page 164 and 165:
Bibliography Bibliography [1] Amazo
Page 166 and 167:
Bibliography [28] S. Melnik, H. Gar
Page 168:
Erklärung Hiermit erkläre ich, da
show all

Merging of TOSCA Cloud Topology Templates - IAAS

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?