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

More documents

Recommendations

Info

Chapter 2Related WorkMotivation behind migration is a result of two factors. The first factor is the factthat old but very often mission critical systems cannot be developed or maintainedanymore because it becomes too expensive. This factor is called [74]“Legacy Systemdilema”. The second factor describes why a company does not want todevelop a new application from the scratch. This may include for instance lackof documentation of the system. Additionally, the system can be a mature applicationthat is a result of many years of development and maintenance. When acompany decides to migrate an application, it always has to face two very generalproblems [74]. The first problem is caused by own, old application which wasdeveloped for years and may be lacking in documentation. The second problemis a target system, namely the architecture and migration decision that are associatedwith selection of the target system.One of possible migration directions is migration toward Service Oriented Architecturewhich brings some very promising benefits like code reuse and easyfurther integration (see 4.7).But even if the choice is made, still an open questionremains: How to conduct the migration? According to Z.Zhang and H.Yangthere are three types of migration toward SOA [84].The first approach calledWhite–Box requires high understanding of the system and allows to make significantchanges in code if there is such need. The second approach is focusedrather on input and output of the system and is called Black–Box. The thirdapproach lies between white and Black–Box techniques and it is called Grey–Boxtechnique. The ”Gray–Box” technique includes code analysis, modification of thecode and analysis of behaviour of the system as a whole entity.How does migration is important is also evidenced by the fact that it becamea subject of standardisation. The standard, named Architectural–DrivenModernisation (ADM) is meant to facilitate migration efforts[58]. This standardconsiders system on three levels of abstraction. The standard investigates alsorole of patterns in the system. Migration towards Service Oriented Architecturebecame also a subject of interest of architects dealing with non–SOA architecturalpatterns like patterns identified in the second chapter.10
Chapter 2. Related Work 11This chapter is meant to investigate techniques of migration toward SOA inorder to set context of the work and identify advantage and drawback of the existingmethods. The study aims at mature and well described migration techniquesbut techniques that base on architectural patterns are also briefly presented. Thechapter is organised as follows:1. Migration toward SOA – “colour” techniquesThis section presents three example techniques that correspond to White–Box,Black–Box and Grey–Box approaches. Descriptions provided by availableliterature give an overview of studies conducted in the field of migrationstoward SOA. Additonally, the section presented advantages and drawbackof the presented techniques.2. Other approachesThe section presents three other approaches. The first approach is notdedicated for migration toward SOA, but the steps taken during migrationreflect steps taken during creation of SOA. The remaining two techniquespresent different approaches of migration of an architectural patternto SOA.3. SummaryThe summary presents result of investigation in the field of migration towardSOA.2.1 Migration toward SOA – “colour techniques”This section presents briefly examples of migration techniques described byZ.Zhangand H.Yang[84].2.1.1 White–box: Service–Oriented Migration and ReuseTechniqueService–Oriented Migration and Reuse Technique (SMART) is rather a family ofprocesses then a single process. It is meant to support organisations in makinginitial decision about feasibility of migration system towards SOA [10]. SMARTevolved from the Options Analysis for Reengineering (OAR) method developedat the SEI. [49][10]Family membersHowever SMART family consists of five members, the members are just tailoredvariants of the first technique–SMART–Migration Pilot (SMART–MP), thereforethis ”root” approach in opposite to remaining family members is described moredetailed.
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: Chapter 1. Introduction 9Chapter 4
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 71 and 72:
Chapter 3. Architectural Patterns 6
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?