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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 663. Popularity of architectural patterns in real systems – presents occurrencesof particular patterns in real systems.4. Representatives of categories in real systems – this section presents applicationof filter removing patterns that do not exist in pairs with otherarchitectural patterns. The guidelines elaborated in this thesis shall be useful.This also means that the guidelines should be as much applicable aspossible. What in turn means that the migrated pattern should be popular- often used. Not often used patterns reduce usability of the guidelinesbecause they cannot be applied frequently.3.3.1 Definition of Pattern LanguageRobert S. Hanmer and Kristin F. Kocan present [37] broad studies on mutualinteraction of patterns. They provide following definition of pattern language:Pattern languages are collections of patterns that can be used to build somethinglarger than any individual pattern can be used to build. They present two criteriawhich define complete pattern language:1. “Morphologically complete (i.e., complete enough that an entire solution canbe seen from only the patterns present in the language)”2. “Functionally complete (i.e., the language contains patterns that resolve allthe new forces introduced by the use of the languages patterns). ”According to Robert S. Hanmer and Kristin F. Kocan [8]definition of patternlanguage should contain following parts:1. Abstract - provides high-level understanding of the pattern language. Thispart is usually a few sentences long.2. Map - The map is a non-cyclic graph presenting patterns as nodes andrelations between them as arcs. The arcs are directional. Arrowhead pointthe pattern that is influenced by the pattern on the opposite side of the arc.Each pattern presented on the map should contribute to the patterns thatare in relation with this pattern.3. Description - the description presents order of application of all the patternscreating the pattern language.4. Patterns(a) Name - the name of the pattern(b) Problem - the problem that needs to be solved(c) Context - in fact, this is a cause of the problem
Chapter 3. Architectural Patterns 67(d) Forces - presents factors that should be taken into consideration whileapplying the pattern.(e) Solution - the pattern is a solution(f) Result Context - this context presents results of application of thesolution. What is gained or introduced.3.3.2 Pattern language in real systemsAn additional study in the domain of pattern languages was conducted by HarrisonB. Neil and Paris Avgeriou [38].During the study, documentation of realsystems was analysed [16]. One of the outcomes of the studies was amount ofidentified patterns in the documentation. Result of analysis is presented belowin table 3.4.Number ofpatternsfoundNumber ofsystem1 102 223 94 45 06 17 08 1Table 3.4: Identified amount of patterns. Adopted from [38]Analysis of documentations stated that in ten systems only one architecturalpattern was found. This number may be over the top, because it is possible thatthe reviewers of the documentations did not recognise all the patterns or just didnot know the applied patterns. Moreover, if reviewers were not sure whether apattern is an architectural pattern, the pattern was rejected as well. Nevertheless,78% of systems were built using more than one architectural pattern.3.3.3 Popularity of architectural patterns in real systemsThe next outcome of the investigation is popularity of particular patterns expressedas a number of occurrences of an architectural pattern in documentations.The summary of pattern “popularity” presents table 3.5
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 and 40: Chapter 2. Related Work 292.3 Summa
Page 41 and 42: Chapter 3. Architectural Patterns 3
Page 75: Chapter 3. Architectural Patterns 6
Page 85 and 86: Chapter 4. Service Oriented Archite
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?