Migration of a Chosen Architectural Pattern to Service Oriented ...
Migration of a Chosen Architectural Pattern to Service Oriented ... Migration of a Chosen Architectural Pattern to Service Oriented ...
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 43 and 44: Chapter 3. Architectural Patterns 3
- Page 45 and 46: Chapter 3. Architectural Patterns 3
- Page 47 and 48: Chapter 3. Architectural Patterns 3
- Page 49 and 50: Chapter 3. Architectural Patterns 3
- Page 51 and 52: Chapter 3. Architectural Patterns 4
AbstractContext: Several examples <strong>of</strong> successful migrations <strong>of</strong> systems <strong>to</strong> <strong>Service</strong><strong>Oriented</strong> Architecture (SOA) are presented in the literature. Some <strong>of</strong> theapproaches also try <strong>to</strong> structure the process <strong>of</strong> migration <strong>to</strong> SOA. The reportedmigration attempts underline the role <strong>of</strong> architecture <strong>of</strong> migratedsystem, but they do not explore the architectural patterns applied in architecture<strong>of</strong> migrated systems while proper usage <strong>of</strong> patterns may simplifyand improve quality <strong>of</strong> migration.Objectives: This work is aimed at elaborating guidelines that supportmigration from a system that is based on a chosen architectural pattern<strong>to</strong>wards a system based on <strong>Service</strong> <strong>Oriented</strong> Architecture.Methods: Literature review is used as a basic method in the initial steps<strong>of</strong> the research, that is during investigation <strong>of</strong> existing techniques <strong>of</strong> migration<strong>to</strong> SOA, establishing procedure for selection <strong>of</strong> the migrated patternand identifying building blocks <strong>of</strong> the target architecture. Results <strong>of</strong> theliterature reviews are further analyzed in order <strong>to</strong> select the migrated architecturalpattern and <strong>to</strong> elaborate the target architecture. The guidelinesfor migration are the result <strong>of</strong> the synthesis <strong>of</strong> 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 <strong>of</strong> migration guidelines. The approach is alsoillustrated with migrating an example student project.Conclusion: The study shows that the usage <strong>of</strong> an architectural patternduring migration allows <strong>to</strong> define the migration in a simple, structured andprecise way using guidelines that represent a set <strong>of</strong> subsequent well definedsteps that should be applied in order <strong>to</strong> migrate a specific type <strong>of</strong> legacysystem.Keywords:<strong>Architectural</strong> pattern, MVC,migration, SOA, guidelines
Change language