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

More documents

Recommendations

Info

Chapter 2. Related Work 12SMART–MP – SMART Migration Pilot focuses mainly on early project analysis.The analysis determinates potential challenges, trade–offs, risks and costby identifying potential services and their components [10]. Migration Planningtries also to recognise pilot project and appropriate migration strategies [10]. Accordingto SMART–MP description[10], the technique consists of four followingelements :1. Element 1 –SMART–MP ProcessThe first element is a process that is meant to analyze the gap betweenboth the actual and a target system by gathering information about legacycomponents and potential services build on them. Gap analysis leads todevelopment of an initial migration strategy.2. Element 2 –Service Migration Interview Guide (SMIG)Interview Guide aims at identification of potential risk and costs associatedwith the migration process. The identification is based on answeringquestions, which are categorized in more than 60 categories [10].3. Element 3 –SMART ToolThe tool supports data collection and organization. The support of assignationof answers to the question to related risks [10].The tool uses SMIGas a framework to create a draft migration strategy.4. Element 4 –Artifact TemplatesThe element consists of templates for following artifacts [10]: MigrationIssues List, Business Process–Service Mapping, Service Table, ComponentTable, Service – Component Alternatives Table and Migration Strategy.Elements presented above are further used during migration process by SMARTactivities (see figure 2.1). SMART–MP technique distinguishes six iterative processes:1. Process 1 –Establish ContextEstablishing of the context is the first SMART–MP process. The processis meant to gather basic information about the system by describing itsbusiness and technical context. Business context includes identification ofstakeholders and identification of their goals. The technical context includesidentification of candidate services and analysis of legacy system. Servicesidentified during this step are generic because generalisation helps to determinateproject feasibility and provides required experience if the decisionabout migration is made [10]. However, this is the first SMART process, itgenerates three out of eight documents [10].(a) Stakeholder List –contains list of stakeholders with contact data andinformation to elicit from each of them.
Chapter 2. Related Work 13(b) Characteristic List –contains a set of predefined characteristics meantto support decision about migration feasibility. The information refersto legacy system’s components.(c) Migration Issues List –the list contains information about potentialmigration issues of both the system and single components2. Process 2 –Define Candidate ServicesService Candidate Definition is restricted to a small number (typically 3–4)of well defined in the previous step services. A good candidate keeps highcohesion, high reuse (see 4.3.1) and clearly defined input and output. Finally,selected services are specified more precisely in terms of Quality ofService (QoS) and definition of input–output.3. Process 3 –Describe Existing CapabilityCapability description is meant to localize and gather information aboutcomponents of legacy system that contain functionality required by previouslyselected services [10]. The description of component includes botharchitectural view like design paradigms, system quality and technical viewlike implementation platform, language, code documentation, code size [10],age of the components, code complexity and interfaces for users and systems[49].Asides from gathering technical and business description, componentsshould be described from quality point of view, by taking into considerationtheir change history, outstanding problems, likehood of meeting long termneeds and historical cost of development and maintenance [49]. All thisinformation is presented in two formal artifacts:(a) Component Table – contains only components meant for migration toservices. The table captures also characteristics described in characteristiclist.(b) Service Table –contains a list of possible services derived from componenttable with characteristics of those services.4. Process 4 – describes Target SOA EnvironmentDescription of a target environment includes major components of targetenvironment with influencing technologies and standards, guidelines for serviceimplementation, their interaction with environment and quality of services(QoS) [10].5. Process 5 –Analyse the GapThe gap analysis is meant to provide preliminary approximation of costsand risks of particular services allocated from the legacy system. The approximationis based on necessary changes of each required component. Inturn, the allocation is based on characteristic of SOA environment and requirementscoming from previously identified services. Gap analysis has
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: Chapter 2. Related Work 11This chap
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 73 and 74:
Chapter 3. Architectural Patterns 6
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?