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

More documents

Recommendations

Info

Chapter 1. Introduction 2Migration to Product Line is not as popular as migration toward Object BasedEnvironment. Product Line is meant to increase large-scale software reuse andreduce time to market. Application of Product Line supports well market drivendevelopment [18].Migration trend aims also at migration toward Service Oriented Architecture(SOA). SOA is an approach to software development[13] that integrated businessprocesses and IT infrastructure. Architecture of a system designed in SOA-wayis a package of loosely coupled interoperable services that exchange data and exposetheir functionalities via interfaces. A service is “an asset that correspondsto real-world business activities or recognizable business functions”[59].The conceptof SOA changed during the years and evolved from concepts like distributedcomputing and modular programming [68]. Successful migrations toward SOAhave been achieved in many domains including banking, electronic payment applicationsand development tools [48]. In spite of all those successful migrations,a person that decided to migrate toward SOA has to be aware that migrationtoward SOA is not an ultimate solution to all problems with old systems. Migrationto SOA needs an additional time that is needed to understand this concept.Misunderstanding raises misconceptions [47]that may be costly. Choice of SOArelates to both technical and design challenges, because not every system can bepresented as a set of reusable services or the cost of such adaptation disqualifiesSOA as a solution[47].Literature presents several examples of techniques of migration toward SOA,but three of them are especially important. They present different types of migrationto SOA and they are well described. The first is Taxonomy Analysis thatanalyzes the existing code [84].The next technique suggests to treat legacy systemas a ”black box” and to wrap its code into services [77]. The last approachis rather a family of five approaches. It is called Service Migration and ReuseTechnique (SMART) [10].Taxonomy Analysis is a method that uses an existing code and documentationas an input. Analysis of the documentation set boundaries of the systemand identifies services [84]. The services are described on business level. Analysisof the available code provides a dendogram [84]. This diagram in form of a treepresents the most often-used terms and relations between them. This approachis semi automatic because a decision person (like an architect) has to set cuttingpoints that divide the tree into subtrees. Those subtrees are further implementedas services.Wrapping as a technique of migration to SOA is similar to migration towardObject Based Environment. The migrated system is wrapped into a set of servicesthat cover all the use cases covered by the actual system. The wrapping
Chapter 1. Introduction 3technique conducts a three steps migration [23] The first step is meant to identifyuse cases and candidate services that cover those use cases. The description ofthis step does not provide own way of identification of services, instead it refers toworks of Sneed [76] or SMART [49][10].The identified services are wrapped intoservices during the second step. The last step is deployment and validation. Thisstep establishes infrastructure and deploys already created services. The servicesare further tested in order to assure that the migrated system fulfills requirements.SMART is a family of five approaches of migration toward SOA [10]. The basicSMART approach is SMART-Migration Pilot (SMART-MP). SMART-MP identifiesservices and their components. This technique estimates potential risks andtries to provide a migration pilot with strategies for migration of the whole systems.Four remaining approaches are tailored version of the basic case. SMARTService Migration Feasibility (SMART-SMF) focuses mainly on feasibility of migrationand its risks. SMART Enterprise Service Portfolio (SMART-ESP) dedicatedfor companies that decided to migrate their system but they did not identifyall the services. SMART Environment (SMART-ENV) is meant for companiesthat did not select the target platform for migrated system. This approach aimsat selection of this platform with analysis of its implications like risks and cost.The last family member is SMART System. This technique supports migrationfrom initial estimations and analysis, through implementation and selection ofenvironment till the end of migration. The SMART family provides guidelinesfor migration, but the guidelines are not complete [3]. They neglect impact ofarchitecture of migrated systems on the process of migration and the target architecture.Descriptions of those three approaches allows identifying following advantagesand drawbacks:Taxonomy analysisAdvantages1. Identifies relations between services2. The technique is systematic3. Execution of the technique can be performed semi automatic4. Provides a lot of information about the migrated systemDrawbacks1. The technique does not consider architectural patterns that are applied inarchitecture of migrated systems
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: Chapter 1Introduction1.1 Background
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 63 and 64:
Chapter 3. Architectural Patterns 5
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 ...

Create successful ePaper yourself

Delete template?

Save as template?