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

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