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 6Conclusion6.1 ConclusionThis chapter summarises outcomes of the work. The section is broken into threesection1. Answers to Research Questions – provides answers to research questionsasked in the first chapter2. Future Works – addresses works that could derive from outcome of thisstudy3. Summary – provides summary of contribution brought by the thesis6.2 Answers to Research QuestionsRQ 1 What are the existing techniques of migration toward SOA?According to Z.Zhang and H.Yang there are three types of migration to SOA[84]: White–Box, Grey–Box and Black–Box. Each type is characterised by differentproperties. The list below presents example techniques classified to thosethree types of migration( see chapter number 2).1. White box–This technique needs deep insight view into existing code anddocumentation of the migrated system. Example: SMART[49]2. Gray box–This approach is a mix of white and black box techniques. Applicationof the technique requires analysis of code of the application andthe system with subsystems. Example: Taxonomy Analysis[84].3. Black box–The technique treats the migrated system as a black box. Migrationaccording this technique bases upon analysis of system’s input andoutput. Example: Wrapping[23]146
Chapter 6. Conclusion 147There are also some attempts of migration toward SOA based on architecturalpattern applied in the migrated systems. Some patterns like Pipe–and–Filtersare already part of SOA[70]. Other patterns like Client–Server have prototypesof frameworks automating migration to SOA [36]. There are also some attemptsof migration of MVC[73][67][28][78], PCBMER[52] or Peer–to–Peer[69].In addition to those works, a standard (Architectural–Driven Modernisation)of modernisation of systems was identified. The standard considers migration ofsystems as a form of modernisation. The standard consists of seven substandards.At the time being, only two substandards are defined. The third substandard(issued in 2009) is especially important in context of this work. The standard isnamed “Pattern Recognition” and is meant to identify patterns and anti–patternsin order to identify requirements and opportunities for transformation(see section2.2.1).RQ.2 What are drawbacks and advantages of identified techniques ofmigration toward SOA?The presented techniques of migration have different approach to migration.Their advantages and drawbacks are consequences of the way how they treat themigrated system. Some of advantages and drawbacks were identified while establishingcontext of the work (see section 1.1) while others were identified duringstudying related works (see sections 2.1.2, 2.1.3 and 2.1.5 ). Here only the mainadvantages and drawbacks are mentioned. See respective sections for full list ofadvantages and drawbacks. The sections for particular techniques are mentionedbelow.SMART was classified as a White–Box technique. It generates a lot of documentationbut it also gives a deep insight view into the system (see 2.1.2 for moreinformation ).Taxonomy Analysis was classified as a Gray–Box technique. The main advantageof the technique is the fact that relationships between services are identifiedduring identification of services. Application of the technique also gives a deepunderstanding of the system and relationship between its element. The drawbackis that the technique is executed both on code and documentation of thesystem. The problem here is with documentation that may not be maintainedand the result of the analysis many be misleading(see 2.1.3 for more information).Wrapping is the last colour technique. This Black–Box technique is very specificbecause it does not require analysis of the code of the system. It treats thesystem as a black box. Unfortunately, application of the technique requires well
- Page 105 and 106: Chapter 4. Service Oriented Archite
- Page 107 and 108: Chapter 4. Service Oriented Archite
- Page 109 and 110: Chapter 4. Service Oriented Archite
- Page 111 and 112: Chapter 4. Service Oriented Archite
- 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: Chapter 5. Guidelines 145FrontendSc
- 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
Chapter 6Conclusion6.1 ConclusionThis chapter summarises outcomes <strong>of</strong> the work. The section is broken in<strong>to</strong> threesection1. Answers <strong>to</strong> Research Questions – provides answers <strong>to</strong> research questionsasked in the first chapter2. Future Works – addresses works that could derive from outcome <strong>of</strong> thisstudy3. Summary – provides summary <strong>of</strong> contribution brought by the thesis6.2 Answers <strong>to</strong> Research QuestionsRQ 1 What are the existing techniques <strong>of</strong> migration <strong>to</strong>ward SOA?According <strong>to</strong> Z.Zhang and H.Yang there are three types <strong>of</strong> migration <strong>to</strong> SOA[84]: White–Box, Grey–Box and Black–Box. Each type is characterised by differentproperties. The list below presents example techniques classified <strong>to</strong> thosethree types <strong>of</strong> migration( see chapter number 2).1. White box–This technique needs deep insight view in<strong>to</strong> existing code anddocumentation <strong>of</strong> the migrated system. Example: SMART[49]2. Gray box–This approach is a mix <strong>of</strong> white and black box techniques. Application<strong>of</strong> the technique requires analysis <strong>of</strong> code <strong>of</strong> the application andthe system with subsystems. Example: Taxonomy Analysis[84].3. Black box–The technique treats the migrated system as a black box. <strong>Migration</strong>according this technique bases upon analysis <strong>of</strong> system’s input andoutput. Example: Wrapping[23]146
Change language