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

Chapter 6. Conclusion 148elaborated and consequently maintained documentation in order to identify allinput–output pairs and use cases to cover(see 2.1.5 for more information).In addition to those drawback. The presented techniques do not use architecturalpattern built into migrated system.RQ.3 What process employ in order to select the pattern for migration?There are many architectural pattern. Selection of the pattern for migrationneeds to be structured and conducted in a way that allows to remove successivelypatterns that do not fulfil current criteria. The selection of the final pattern isconducted according to following steps:1. Selection of literature sources2. Selection of architectural patterns from the literature sources3. Removal of patterns that exist in only one source4. Assignment of architectural patterns to selected category5. Selection of representatives for categories6. Removal of rarely interacting patterns7. Prefeasibility study8. Final SelectionMore detailed information about all the steps is presented in chapter 3RQ.4 Which pattern should be chosen for migration?Model–View –Controller is the pattern for migration. The pattern was selectedbecause it passed process of selection. MVC was mentioned in revised publicationand occurred to be the most generic from within its category. The pattern is alsoapplied with other patterns (see table 3.6). Finally, the pattern was found to bein scope of researches related to migration to SOA (see section 3.4.1)RQ.5 What elements should be the building blocks of the target architecture?The target architecture consists of identified SOA architectural pattern. Thefull list of pattern is presented in table 4.3. Detailed description of the patternsis presented in section 4.6.1