Migration of a Chosen Architectural Pattern to Service Oriented ...

More documents

Recommendations

Info

Chapter 3Architectural PatternsThe goal of this chapter is to select an architectural pattern that will be migratedto Service Oriented Architecture (SOA). Selection of a proper pattern is very important.The selection must eliminate patterns that are not feasible for migration,the patterns that are already migrated to SOA and the patterns that are alreadypart of SOA. Additionally the selected pattern should be popular. It means thatthe pattern should be often implemented in real systems. Guidelines for a rarelyused pattern have reduced application. Since there is a number of architecturalpatterns that differ from each other and the thesis is not meant to migrate all ofthem, a systematic approach for selection of the pattern for migration is needed.The selection bases on a number of steps. Each step is a filter that is meant toreduce number of candidate patterns or prepare the patterns for the next filter.Filters are lined so the output of one filter is the input for another. The filters(in order of their application) are following:1. Selection of literature sourcesThe idea of architectural pattern along with example patterns is described ina great number of publications. This filter selects several literature sourcesthat will be the base for identification of architectural patterns.Input:Literature about architectural patternsOutput: Selected literature sources2. Selection of architectural patterns from the literature sourcesLiterature sources selected by the first filter contain different types of patters(see 3.1.1 for types of patterns), but only architectural patterns are inscope of the work. This filter removes all the non-architectural patterns.Input: Selected literature sourcesOutput: List of architectural patterns3. Removal of patterns that exist in only one sourceThis is the first filter that removes the less popular architectural patterns.All the patterns that exist in only one literature source are removed. Thisassures that the most unusual and rare patterns are not taken in the furtherconsideration.30
Chapter 3. Architectural Patterns 31Input: List of architectural patternsOutput: Architectural patterns that exit in more than one literature source4. Assignment of architectural patterns to selected categoryIn opposite to the previous filters, this filter does not reduce amount ofarchitectural patterns. It organizes previously identified patterns. The outputof this filter is a list of architectural patterns assigned to categories.Both identified and chosen categories are described.Input: Architectural pattern that exits in more than one literature sourceOutput:Categories of architectural patterns and architectural patterns assignedto those categories5. Selection of representatives for categoriesAt this point, architectural patterns are grouped into several categories.Each category contains several patterns. This filter reduces number of candidatearchitectural pattern by selection of patterns that represent particularcategories. Representatives of categories are patterns that have thesimplest structure. In addition, application of the patterns is similar toapplication of other patterns in its category.Input: Categories of architectural patterns and architectural patterns assignedto categoriesOutput: A list of patterns that represent their categories6. Removal of rarely interacting patternsThis filter bases on mutual interaction of patters (see 3.3). Mutual interactionof patterns is important because systems often base on severalarchitectural patterns - pattern language. The choice of applied patternsneeds to be carefully considered. Proper choice of patterns strengthens thesystem. Wrong choice of patterns that are applied together can bring someside effects like performance drop or limited testability. Patterns that bringside effects when they are applied with other patterns are less often implemented.Input: A list of patterns representing categoriesOutput: A list of representatives that does not contain the less mutuallyinteracting architectural patterns.7. Prefeasibility studyThe filter finds literature about architectural patterns in context of SOA.The filter will removes patterns not fulfilling at least one of the followingcriteria:(a) A pattern has to exist in literature in context of SOA(b) A pattern cannot be already migrated to SOA using guidelines
Page 1 and 2: Master ThesisSoftware EngineeringTh
Page 3 and 4: AbstractContext: Several examples o
Page 5 and 6: List of Figures1.1 Research methodo
Page 7 and 8: List of Tables3.1 Summary of archit
Page 9 and 10: 3.3.1 Definition of Pattern Languag
Page 11 and 12: Chapter 1Introduction1.1 Background
Page 13 and 14: Chapter 1. Introduction 3technique
Page 15 and 16: Chapter 1. Introduction 5was notice
Page 17 and 18: Chapter 1. Introduction 7do not pro
Page 19 and 20: Chapter 1. Introduction 9Chapter 4
Page 21 and 22: Chapter 2. Related Work 11This chap
Page 23 and 24: Chapter 2. Related Work 13(b) Chara
Page 25 and 26: Chapter 2. Related Work 15Figure 2.
Page 27 and 28: Chapter 2. Related Work 17Drawbacks
Page 29 and 30: Chapter 2. Related Work 19Figure 2.
Page 31 and 32: Chapter 2. Related Work 21Advantage
Page 33 and 34: Chapter 2. Related Work 23between a
Page 35 and 36: Chapter 2. Related Work 252. Applic
Page 37 and 38: Chapter 2. Related Work 274. Mediat
Page 39: Chapter 2. Related Work 292.3 Summa
Page 43 and 44: Chapter 3. Architectural Patterns 3
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 91 and 92:
Chapter 4. Service Oriented Archite
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Chapter 5. Guidelines 1035.1 Patter
Page 115 and 116:
Chapter 5. Guidelines 105Descriptio
Page 117 and 118:
Chapter 5. Guidelines 107Result Con
Page 119 and 120:
Chapter 5. Guidelines 109ContextAn
Page 121 and 122:
Chapter 5. Guidelines 111Result Con
Page 123 and 124:
Chapter 5. Guidelines 113System’s
Page 125 and 126:
Chapter 5. Guidelines 115ViewSchema
Page 127 and 128:
Chapter 5. Guidelines 117ViewViewCo
Page 129 and 130:
Chapter 5. Guidelines 119ViewViewCo
Page 131 and 132:
Chapter 5. Guidelines 121ViewViewPr
Page 133 and 134:
Chapter 5. Guidelines 123FrontendFr
Page 135 and 136:
Chapter 5. Guidelines 125complicati
Page 137 and 138:
Chapter 5. Guidelines 127Concluding
Page 139 and 140:
Chapter 5. Guidelines 129UsecasesTh
Page 141 and 142:
Chapter 5. Guidelines 131puter (ext
Page 143 and 144:
Chapter 5. Guidelines 133Group 3 ma
Page 145 and 146:
Chapter 5. Guidelines 135Output: Du
Page 147 and 148:
Chapter 5. Guidelines 137generation
Page 149 and 150:
Chapter 5. Guidelines 139(a) Fronte
Page 151 and 152:
Chapter 5. Guidelines 141Figure 5.1
Page 153 and 154:
Chapter 5. Guidelines 143Figure 5.1
Page 155 and 156:
Chapter 5. Guidelines 145FrontendSc
Page 157 and 158:
Chapter 6. Conclusion 147There are
Page 159 and 160:
Chapter 6. Conclusion 149RQ.6 How t
Page 161 and 162:
References[1] http://www.soa-manife
Page 163 and 164:
References 153[22] Frank Buschmann,
Page 165 and 166:
References 155[46] Dirk Krafzig, Ka
Page 167 and 168:
References 157[67] Xiaohong Qiu. Bu
show all

Migration of a Chosen Architectural Pattern to Service Oriented ...

Create successful ePaper yourself

Delete template?

Save as template?