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

More documents

Recommendations

Info

Chapter 1. Introduction 6ˆ RQ.8 What are the drawback and advantages of the new technique ?Expected outcomes: The following outcomes are expected to be elaborateby the thesis.ˆ EQ.1 List of techniques of migration toward SOA with descriptionsˆ EQ.2 List of drawback and advantages of found techniques of migrationtoward SOAˆ EQ.3 Process for selection of the migrated architectural pattern, motivationbehind the activitiesˆ EQ.4 Architectural pattern for the migrationˆ EQ.5 List of elements building the target architectureˆ EQ.6 Target architectureˆ EQ.7 Guidelines for migrationˆ EQ.8 Example illustration of implementation of the migration according tothe guidelinesˆ EQ.9 Advantages and drawback of the guidelines for migration to SOA1.3 Research MethodologyThis study is conducted in two domains: Architectural Patterns and Service OrientedArchitecture. Both of the domains are covered by a number of publications.Entry points for the research are books containing body of knowledge. The bookswere identified during elaborating the topic for this thesis. For Architectural Patterns,the series of books by Frank Buschmann [22][71][45][20][21] is consideredas a body of knowledge. In turn, body of knowledge for Service Oriented Architectureor more precisely Architectural Patterns in SOA is described in “SOADesign Patterns”[32] by T.Erl. In case of migration to SOA, the entry pointare techniques for migration to SOA described in introduction (see section 1.1).Those approaches and other further identified are deeper investigated in order toget better understanding what is done and how it is done.The basic research methods applied in this thesis are Literature Review, Analysisand Synthesis. The core of the literature review applied in this thesis arebooks containing bodies of knowledge and publications describing identified techniquesfor migration. Those sources are investigated in the first order. If they
Chapter 1. Introduction 7do not provide satisfying information then other books, conference and journalpapers are studied. Web pages are referenced mainly when some knowledge abouttechnology is needed. Literature review is conducted until a satisfying informationis not found. The review takes into account year of publication of foundsources. The newest publications are revised in the first order. The main sourcesof journals and conference papers are: IEEE, Inspec, Springer and ACM digitallibrary. Literature review in domain of Architectural Patterns and SOA is conductedseparately. Information provided by literature review is further analysedand synthesisedLiterature Review in the domain of Architectural Patterns is applied in order toestablish procedure for selection of architectural pattern( answer for RQ.3).Theprocedure is further applied and results of each activity is analysed. The patternfor migration is chosen based on those results (answer for RQ.4).In case of SOA, literature review is conducted twice. The purpose of the firstreview is to investigate the existing methods of migration to SOA (answer forRQ.1). The second literature review is meant to find elements that will build thetarget architecture (answer for RQ.5). The identified methods of migration arefurther analysed in order to identify their advantages and drawbacks (answer forRQ.2). Design of the target architecture (answer for RQ.6) is result of analysisoutcome of literature review providing building blocks of the target architecture.Information gathered during selection of the architectural pattern for migrationand elaboration of the target architecture is further synthesised in order to elaboratetranslation between the chosen architectural pattern and the target SOA(answer for RQ.7). Finally the information gather during analysis of identifiedmigration to SOA techniques is synthesised with the elaborated guidelines (answerfor RQ.8).Overview of the described process is presented in figure 1.1. The EO.8 is notpresent in the figure because it is not a direct outcome of research questions.
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: Chapter 1. Introduction 5was notice
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 67 and 68:
Chapter 3. Architectural Patterns 5
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 ...

Create successful ePaper yourself

Delete template?

Save as template?