Migration of a Chosen Architectural Pattern to Service Oriented ...
Migration of a Chosen Architectural Pattern to Service Oriented ... Migration of a Chosen Architectural Pattern to Service Oriented ...
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 43 and 44: Chapter 3. Architectural Patterns 3
- Page 45 and 46: Chapter 3. Architectural Patterns 3
- Page 47 and 48: Chapter 3. Architectural Patterns 3
- Page 49 and 50: Chapter 3. Architectural Patterns 3
- Page 51 and 52: Chapter 3. Architectural Patterns 4
- Page 53 and 54: Chapter 3. Architectural Patterns 4
- Page 55 and 56: Chapter 3. Architectural Patterns 4
- Page 57 and 58: Chapter 3. Architectural Patterns 4
- Page 59 and 60: Chapter 3. Architectural Patterns 4
- Page 61 and 62: Chapter 3. Architectural Patterns 5
- Page 63 and 64: Chapter 3. Architectural Patterns 5
Chapter 1. Introduction 5was noticed that identification <strong>of</strong> design pattern helps in identification <strong>of</strong> services[7].AimThis thesis is meant <strong>to</strong> elaborate guidelines that support migration from a systemthat is based on a chosen architectural pattern <strong>to</strong>ward a system based on <strong>Service</strong><strong>Oriented</strong> Architecture.ObjectivesThe objectives <strong>of</strong> the thesis are as follows:1. To investigate existing migration <strong>to</strong>ward SOA approaches.2. To investigate existing architectural patterns in order <strong>to</strong> select the patternfor migration.3. To investigate SOA in order <strong>to</strong> provide understanding <strong>of</strong> SOA in the context<strong>of</strong> this work.4. To elaborate the target architecture.5. To elaborate translation between selected architectural pattern and the targetarchitecture6. Illustrate an application <strong>of</strong> 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 <strong>of</strong> migration <strong>to</strong>ward SOA?ˆ RQ.2 What are drawbacks and advantages <strong>of</strong> identified techniques <strong>of</strong> migration<strong>to</strong>ward SOA?ˆ RQ.3 What process employ in order <strong>to</strong> select the pattern for migration?ˆ RQ.4 Which pattern should be chosen for migration?ˆ RQ.5 What elements should be the building blocks <strong>of</strong> the target architecture?ˆ RQ.6 How the target architecture should look like?ˆ RQ.7 How <strong>to</strong> translate the selected architectural pattern in<strong>to</strong> the targetarchitecture?