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

More documents

Recommendations

Info

Chapter 2. Related Work 14two main goals. The first is to identify gaps in knowledge about the legacysystem. The second is to create Component Option Table which is used asan input to the final process.(a) Component Option Table –maps possibilities between Service Tableand Component Table. The table contains also mapping used in systemCommercial Off The Shelf (COTS) components. There are twopossible ways in which the process can be conducted [49]. The firstis “manual” allocation of components prepared by SMART team.Thesecond approach is enriched by supporting tools. The supporting toolsare used mainly for analysis of the code that does not have completedocumentation or quality of the code is not determined.6. Process 6 –Develop StrategyStrategy development is the last and the final SMART–MP process. Theprocess makes use of all the previously gathered information including migrationissues and information related to cost and risk estimations. Bothcost and risk estimations have to be determined precisely, because they setadditional constrains for the project. They also decide about feasibility ofthe project. In turn, migration issues include [10]identification of a pilotproject by identification of initial set of services and the order of their implementation.The issues address guidelines created during describing ofthe target environment and specify possible migration paths like wrappingor re–writing [49]. In result, two artifacts are created:(a) Migration alternatives table – alternative table takes as an input ComponentsService Options Table and produces feasible migration strategies.The strategies differ mainly in a list of components selected formigration, order of processes and code modification.(b) Service Migration Strategy – migration strategy is a final documentthat is a result of all the processes and artifacts. The strategy describesservices that can be implemented and what components wouldcreate them. The document contains also description of the processesrequired to accomplish the migration and full cost and risk analysis.
Chapter 2. Related Work 15Figure 2.1: SMART work flow. Adopted from [10]However the numeration assigned to each process may suggest that the processesare strictly sequential, it is not true. Moreover the processes should beconducted in an iterative manner and the order of activities can be changedto align to changes better and better support project specification [50]. Consequently,iterative approach forces to reconsider previous steps if informationgathered in current steps influences it. Reconsideration refers also to artifactsobtained as results of the processes. SMART–MP contains one more elementwhich has significant impact on the Process of migration but was not mentionedbefore. This element is a decision point that is localized after Establishing Context.The decision point provides initial answer for the question: “Is the projectfeasible to create?”.The answer for this question is based on artifacts acquiredfrom the first step and relays on availability of stakeholders and a level of both
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: Chapter 2. Related Work 13(b) Chara
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 75 and 76:
Chapter 3. Architectural Patterns 6
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?