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

More documents

Recommendations

Info

Chapter 1. Introduction 42. Requires documentation - this causes problems because documentation ofan old system may be missing or not maintainedWrappingAdvantages1. The technique is systematic2. Execution of the technique is semi automaticDrawbacks1. The technique does not consider architectural patterns that are applied inarchitecture of migrated systems2. A full list of use cases is needed. The use cases are described in documentationthat may be missing or not maintained3. The technique bases on inputs and outputs of the system. It is hard todefine all possible combinations of input-output pairs.SMARTAdvantages1. The technique is systematic2. The technique produces many artifacts that help in understanding the migratedsystem3. SMART has a few variants that are tailored to different needsDrawbacks1. The technique does not consider architectural patterns that are applied inarchitecture of migrated systems2. Application of the technique requires a lot of time1.2 Problem StatementIdentified techniques of migration to SOA do not consider architectural patternsapplied in the migrated system (see first drawback of each technique ).Usage of architectural patterns during migration is important because theyexpress some common structure of the system. A migration technique that baseson an architectural pattern could provide a structured and systematic way ofmigration for systems characterised by this particular pattern. Additionally, it
Chapter 1. Introduction 5was noticed that identification of design pattern helps in identification of services[7].AimThis thesis is meant to elaborate guidelines that support migration from a systemthat is based on a chosen architectural pattern toward a system based on ServiceOriented Architecture.ObjectivesThe objectives of the thesis are as follows:1. To investigate existing migration toward SOA approaches.2. To investigate existing architectural patterns in order to select the patternfor migration.3. To investigate SOA in order to provide understanding of SOA in the contextof this work.4. To elaborate the target architecture.5. To elaborate translation between selected architectural pattern and the targetarchitecture6. Illustrate an application of the translation.Research question:To fulfill the aim and the objectives, the thesis addresses and answers followingresearch questions:ˆ RQ.1 What are the existing techniques of migration toward SOA?ˆ RQ.2 What are drawbacks and advantages of identified techniques of migrationtoward SOA?ˆ RQ.3 What process employ in order to select the pattern for migration?ˆ RQ.4 Which pattern should be chosen for migration?ˆ RQ.5 What elements should be the building blocks of the target architecture?ˆ RQ.6 How the target architecture should look like?ˆ RQ.7 How to translate the selected architectural pattern into the targetarchitecture?
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: Chapter 1. Introduction 3technique
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 65 and 66:
Chapter 3. Architectural Patterns 5
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?