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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 34Selection of literature sourcesSelection of architectural patterns from the literature sourcesRemoval of patterns that exist in only one sourceAssignment of architectural patterns to selected categorySelection of representatives for categoriesRemoval of rarely interacting patternsPrefeasibility StudyFinal SelectionFigure 3.1: Procedure of selection of Pattern for migration4. Identified Architectural Patterns– presents a list of identified ArchitecturalPattern. The identified patterns are selected from literature presented insection Sources of Architectural Patterns. The list is further reduced to thepatterns existing in two out of three sources.3.1.1 Patterns in Software EngineeringPattern is not a brand new idea. The first person who defined a pattern as [56]: “A recurring solution to a common problem in a given context and system offorces.” was Christopher Alexander [24] [56] – an architect born in Vienna. Hepublished (1977) in his book more than two hundreds of architectural solutions,which included both very general and abstract tasks like city planning as well
Chapter 3. Architectural Patterns 35as very detailed tasks like room planning. The Alexander’s idea inspired KentBeck and Ward Cunningham. They presented their observations and adaptationsof patterns to Software Engineering during Object Oriented Programming, Systemand Language (OOPSLA) conference in 1987 [56]. However , the origin ofpatters are patterns used in architecture, the patterns in Software Engineeringdo not refer only to architecture of system. The general classification presentedin “Patterns in the field of software engineering”[56] groups patterns into threemain categories that in turn are divided into seven subcategories (see figure 3.2.The main categories are[56] :1. Implementation patterns – present implementation of the system from differentpoints of view. Those patterns are further broken into four morecategories.(a) Reference Architectural Patterns – this category contains patterns thatare dedicated to a particular domain [56].(b) Design Patterns – in general, design patterns define, explain and solvedesign problems in an object oriented system [56].(c) Analysis Patterns – those patterns are rather a group of concepts thatrepresent a common modeling in business [56].(d) Architectural Patterns – architectural patterns provide predefined subsystemswith relations between them and responsibilities of those subsystems[56].2. Process and improvement patterns – this type of patterns present solutionsfor tasks that are common during development and improvement activities.The category is further broken into two subcategories:(a) Process Patterns – the patterns show and guide how to conduct specifictasks in the development of process [56].(b) Software process Improvement Patterns – define improvements for alreadyintroduced processes [56].3. Configuration management patterns – contains only one subcategory.(a) Software configuration management patterns – the patterns describeprocesses that are associated with whole lifecycle of a product(see [56]for more detailed information about types of patterns ).3.1.2 Definition of Architectural PatternsDespite the fact that the classification [56] of patterns in Software Engineeringclearly separates Architectural Patterns from Design Patterns, it is not always
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 43: Chapter 3. Architectural Patterns 3
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 95 and 96:
Chapter 4. Service Oriented Archite
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 ...

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

Delete template?

Save as template?