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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 72from the scratch with usage of Java Struts framework. The framework providesbuild-in support for MVC pattern. Other approach for MVC-SOA integrationproposes changes in MVC pattern. More explicitly, it adapts MMVC pattern toSOA architecture [67] and focuses on data transfer part of the desktop application.The solution proposes introduction of an additional broker component andpublisher-subscriber design pattern for communication. The other approach suggestscollaboration of services with model part of MVC [28]. Model simply bindsand invokes previously found in registry services. The services become externalresources like database. Studies on MVC and SOA include also integration fromGUI point of view [78].Client–ServerClient–Server is an architectural pattern that due to its nature is used in distributedsystems therefore a special interest from SOA related researches mightbe expected. The studies exist and in fact are in advances phase. They do notconsider only possibilities of migration but provide also a prototype frameworkautomating migration from Client-Server legacy application into SOA application[36]. The framework solves problem of migration of VB.Net application bywrapping their code into web services but other languages are also considered asa feature work. Other studies consider performance of SOA applications based onClient–Server pattern and compare it to SOA applications based on Peer–to–Peerpattern [26].Half–Sync / Half–AsyncNo information about Half–Sync / Half–Async and its integration with / migrationto SOA was found.3.4.2 Pattern for migrationFilter 7: Final selectionConsidering information gathered during prefeasibility study, three patterns haveincreased probability of successful migration. The increased feasibility is a resultof already conducted studies related to those patterns and SOA. However, thestudies present the patterns as worthy further consideration, only one can bechosen. Client–Serverpattern is rejected due to advances phase of studies relatedto SOA and migration, while Pipe–and–Filters appears in the context of EnterpriseApplication Integration only. Additionally, Pipes–and–Filters is consideredonly in one study. Model View Controller is the pattern that is analysed frommany perspectives but does not exist in the context of migration. The pattern isalso widely supported by many frameworks which are not restricted to one languagebut rather are a bias of existing languages including Java (Spring, Struts)
Chapter 3. Architectural Patterns 73C#(ASP.Net), PHP (Zend) or Ruby on Rails (MVC Framework), therefore thispattern is a good candidate for migration.3.5 SummaryThe chapter presented several architectural patterns and problem with definitionof an architectural pattern. Next, a list of architectural patterns was elaborated.The patterns from the list were further investigated. Different ways of patterncategorisation were presented. One of the categories was chosen and previouslyfound pattern were assigned to this category. Additionally each category got atleast one representative pattern. The architectural patterns were also consideredin the context of their mutual interaction. Information obtained during selectionof representative of particular categories as well as information about mutualinteraction allowed selecting a final set of patterns that was considered as a setof candidate patterns for migration. A prefeasibility study was conducted andModel View Controller was selected the pattern for migration.
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 81: Chapter 3. Architectural Patterns 7
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?