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

More documents

Recommendations

Info

This thesis is submitted to the School of Computing at Blekinge Institute of Technologyin partial fulfillment of the requirements for the degree of Master of Science in SoftwareEngineering. The thesis is equivalent to 20 weeks of full time studies.Contact Information:Author(s):Piotr KaliniakE-mail: piotr.kaliniak@gmail.comUniversity advisor(s):Dr. Ludwik KuźniarzSchool of Computing,Blekinge Institute of Technology, SwedenExternal University advisor(s)Dr. Bogumi̷la HnatkowskaWroc̷law University of Technology, PolandSchool of ComputingBlekinge Institute of Technology Internet : www.bth.se/comSE-371 79 Karlskrona Phone : +46 455 38 50 00Sweden Fax : +46 455 38 50 57
AbstractContext: Several examples of successful migrations of systems to ServiceOriented Architecture (SOA) are presented in the literature. Some of theapproaches also try to structure the process of migration to SOA. The reportedmigration attempts underline the role of architecture of migratedsystem, but they do not explore the architectural patterns applied in architectureof migrated systems while proper usage of patterns may simplifyand improve quality of migration.Objectives: This work is aimed at elaborating guidelines that supportmigration from a system that is based on a chosen architectural patterntowards a system based on Service Oriented Architecture.Methods: Literature review is used as a basic method in the initial stepsof the research, that is during investigation of existing techniques of migrationto SOA, establishing procedure for selection of the migrated patternand identifying building blocks of the target architecture. Results of theliterature reviews are further analyzed in order to select the migrated architecturalpattern and to elaborate the target architecture. The guidelinesfor migration are the result of the synthesis of the analyzed information.Results: The migration is realized as a translation between two patternlanguages: the first pattern language describes the chosen architectural pattern–Model–View–Controller and the second pattern language describesSOA target architecture, expressed using SOA architectural patterns. Thetranslation is defined by a set of migration guidelines. The approach is alsoillustrated with migrating an example student project.Conclusion: The study shows that the usage of an architectural patternduring migration allows to define the migration in a simple, structured andprecise way using guidelines that represent a set of subsequent well definedsteps that should be applied in order to migrate a specific type of legacysystem.Keywords:Architectural pattern, MVC,migration, SOA, guidelines
Page 1: Master ThesisSoftware EngineeringTh
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 53 and 54:
Chapter 3. Architectural Patterns 4
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Chapter 4. Service Oriented Archite
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
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 ...

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

Delete template?

Save as template?