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

More documents

Recommendations

Info

Chapter 2. Related Work 18Repository – stores Finite State Automaton (FSA) files with correspondingScreen Templates, Automation Variables and actions executed by wrapper afterreaching this particular state. These actions include [23]:1. Init –sets Automation Variables based on Service Request Message2. Set Input Field –sets a value of an input field3. Get Output Field –gets a value of an output field from the legacy screen4. Submit Command –triggers transition from one state to another5. Set –Update Automation Variable –modifies values of Automation Variablesbased on output of variables of legacy screen and other AutomationVariables6. Build Response –creates a service response based on actual values of AutomationVariablesAutomation Engine – Automation Engine is a core of the approach. Theengine is a component that receives web service request and returns an output.Execution of Engine functionality starts once components receive URI of invokedfunctionality and corresponding input data. Component execution can be dividedinto three parts [23]:1. Start Activity –starts when the engine receives request message. Just afterthe start a corresponding XML description file is acquired from the Repositoryand the legacy system is invoked. The first screen returned by thelegacy system is obtained from Terminal and a current state is obtainedfrom State Identifier.2. Interpretation Activity –Interpretation Activities are a set of activities repeatedin a loop until the final state is not reached. The set includes executionof current state activities, update of variable buffer called AutomatonVariables, transfer of a new data to Terminal Emulator and identificationof a new state.3. Final Activity –when the last state has been reached, engine create anoutput message based on Automation Variables values.ProcessesIn order to achieve fully migrated system, three steps should be executed in asequence. The steps are following:
Chapter 2. Related Work 19Figure 2.2: Wrapper Schema. Adopted from [23]Selecting candidate services – This is the first process of the wrapping technique.The process is meant to identify and allocate potential services in legacysystem. However the approach notices meaning of introduction of a structuralprocess in order to support service allocation, it does not provide own solution,but rather refers to work of Sneed [76] or SMART [49][10]Wrapping the selected use case – The second process is a core part of thetechnique. This process aims at wrapping identified use cases into service. It isalso the most complex process which is composed of three sub–processes [23]:1. Service Identification –aims at selection of use cases that can be transformedto services with respect to previously described characteristic (see 4.3.1)andbraking down complex use cases into more elementary [23]. Complex servicesare not removed from the list services. They became process servicesthat utilise lower level services to perform tasks.2. Reverse Engineering –during the second sub–activity, the system is analysedin terms of interaction with user in order to gain broad and in depth coverageof main and alternative scenarios. As the result, information about request
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 and 24: Chapter 2. Related Work 13(b) Chara
Page 25 and 26: Chapter 2. Related Work 15Figure 2.
Page 27: Chapter 2. Related Work 17Drawbacks
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 79 and 80:
Chapter 3. Architectural Patterns 6
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?