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

More documents

Recommendations

Info

Chapter 2. Related Work 16current and target system understanding.SMART – SMF Application of SMART Service Migration Feasibility determinateswherever the project is feasibly for migration toward SOA. This versionof SMART is meant for companies that are new in the field of Service Orientationor migration of projects that are characterized by a high risk of migration.SMART – ESP In opposite to SMF, Enterprise Service Portfolio (ESP) isdesigned for enterprises that decided to migrate their systems to SOA. ESP supportscreation of service portfolio. The portfolio is based on services selected fromall the systems across the organization.SMART ENV The Environment variant is something between ESP and SMFversions. This variant is the best for organization that chosen SOA as theirtarget environment but they are still not completely aware of implications, costsand risks of migration.SMART System SMART System is designed from a perspective of migrationof a current system to a complete Service Oriented environment. SMART Systemsupports identification and creation of services. This variant establishes acomplete Service Oriented infrastructure[10].2.1.2 Advantages and drawbacks of SMARTThe SMART migration technique is a technique that examines the migrated systemin details. This high level of granularity of the examination brings bothadvantages and drawbacks.Advantages1. The technique is systematic2. SMART examines the migrated application from different points of view,including risks, costs and migration feasibility3. The technique produces many artifacts that help in understanding the migratedsystem4. SMART has a few variants that are tailored to different needs
Chapter 2. Related Work 17Drawbacks1. Application of the technique requires a lot of time2. The technique is heavy. It produces a lot of documents3. The technique does not consider properties of architecture of migrated system2.1.3 Black–Box: WrappingIn opposite to White–Box technique, Black–Box technique does not affect thecode of the migrated system. The system is considered as a whole entity andanalysis of a legacy system is limited only to analysis of inputs and outputs. Thissection presents briefly an overview of an example of a Black–Box technique,namely Wrapping [23].The description presents two parts of the approach. Thefirst part describes basic elements. The second presents main processesElementsWrapping technique consists of several element that work on Finite State Automationand legacy screens. See picture 2.2 for wrapper schema. The elementsare following:Terminal emulator – replaces server terminal that normally has an access tothe legacy system and transfers requests from a GUI based application or requestscalled via legacy system’s API. In other words, terminal emulator provides aninterface to access legacy functionality. The implementation depends of terminaltype. There are two main types of terminals [23]:1. Stream Oriented Terminal –communicates with the system via two–directionalchannel. The terminal sends data just after they are typed. Received dataare computed by the legacy system and send back as a screen representedby a matrix of characters.2. Block Oriented Terminal –in opposite to stream terminal, Block OrientedTerminal uses screens represented by a set of fields with their localisation.The legacy system computes the result and sends back a screen containinga new set of fields with corresponding localisations.States identifier – Given an input and a start state, the system can reach afinite amount of states. Each state has own screen that is returned by the systemas an output. The responsibility of State Identifier is to match Screen Template tothe screen returned by the system. To increase matching probability, the legacyscreen should be described by the biggest possible amount of data that can beobtained using reverse engineering on the legacy screen.
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: Chapter 2. Related Work 15Figure 2.
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 77 and 78:
Chapter 3. Architectural Patterns 6
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?