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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 70to patterns that can cooperate with other architectural patterns, the lists shouldbe intersected. The outcome of intersection removes a few patterns from list ofrepresentatives and provides the final list of patterns that are considered as potentialcandidates for migration. The list will be further reconsidered in terms offeasibility of migration toward SOA. The list of final patterns presents followingentities:1. Layers2. Pipes and Filters3. Shared Repository4. Microkernel5. Model–View–Controller6. Half–Sync / Half–Async7. Client–ServerIn the result of intersection, three patterns were rejected:1. Reflection2. Remote Procedure Call3. Message Queueing3.4 Pattern SelectionThe patterns of the final set are the patterns from intersection of list of patternrepresentatives and patterns from list of mutually interacting patterns. Thissection confronts final list of patterns with available literature in order to removepatterns already migrated and provide information about migration feasibility.1. Prefeasibility Study – presents identified works related to final list of patternsin the context of SOA2. Pattern for migration – provides final pattern for migration with justificationof the choice.
Chapter 3. Architectural Patterns 713.4.1 Prefeasibility StudyFilter 6: Prefeasibility studySelection of a pattern proper for migration is not limited to pointing which patternwill be migrated but it also should consider whether migration has chances to besuccessful. The final group of patterns should be reconsidered from the feasibilitypoint of view. The consideration includes review of available literature. Thereview is meant to search for attempts of migration and their results.LayersThe pattern already exists in context of SOA. This pattern does not have clearlydistinguished subsystems. It is rather focused on separation of different part ofthe system based on their level of abstraction or functionality. Selection of thispattern for migration is not promising because the pattern is rather a concept.The elements of the pattern are very abstract and rather descriptive.Pipes–and–FiltersThe pattern in the context of SOA is considered as a good pattern for EnterpriseApplication Integration (EAI) [70]]. The description provided by authorspresents Filters as separate services that are incorporated into orchestration process(see 4.3.2). The description compares two methods of business integration.In fact is a kind of migration but not from Pipe and Filters architecture. The finalsystem utilizes Pipes and Filters as an element of the final architecture. Summarizing:The pattern is already a part of SOA. It is used in Enterprise ApplicationIntegration.Shared RepositoryNo information about Shared Repository and its integration with / migration toSOA was found.MicrokernelNo information about Microkernel and its integration with / migration to SOAwas found.Model–View–ControllerModel View Controller in relation to SOA exists in literature in several contexts.The pattern does not appear as a part of SOA in opposite to for instancePipes And Filters. Elements of SOA are parts of Model View Controller pattern,namely, services replace controllers in for instance the Art Examination ManagementSystem [73].The system was not a result of migration, but it was created
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 79: 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?