12.07.2015 Views

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 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6. Conclusion 150RQ.8 What are the drawback and advantages <strong>of</strong> the new technique ?Information about advantages and drawbacks is presented in section 5.5.3.The most important advantage is that the guidelines consider architectural patternsapplied in migrated architecture. The most significant drawback is limitation<strong>of</strong> application. The guidelines are applicable only for systems that do notuse functions provided by MVC supporting frameworks.The elaborated guidelines are implementation <strong>of</strong> White–Box technique. Themost important advantage <strong>of</strong> the guidelines is solution for the drawback that thatexist in identified White–Box, Grey–Box and Black–Box techniques, namely “Thetechnique does not consider architectural patterns that are applied in architecture<strong>of</strong> migrated systems”.6.3 Future worksThe example system that was used for illustrating application <strong>of</strong> the guidelineswas small. This was caused by problem <strong>of</strong> availability <strong>of</strong> candidate projects. Theelaborated guidelines should be applied for migration <strong>of</strong> other systems in order<strong>to</strong> validate them and propose improvements.The elaborated guidelines provide a migration technique only for MVC architecturalpattern, but the target architecture can be classified as Process–EnabledSOA (see 5.5.2). This architecture could also be applicable for other migrations.Future researches could modify the guidelines in order <strong>to</strong> adjust them other architecturalpatterns. At the beginning for other patterns belonging <strong>to</strong> the samecategory as MVC (see table 3.3 for categories and patterns).Finally, elaborated technique <strong>of</strong> migration is a list <strong>of</strong> subsequent steps thatintroduce additional elements in<strong>to</strong> architecture. The technique is systematic andit known how the architecture changes after each guideline. This property can beused in future in order <strong>to</strong> implement a framework supporting the migration.6.4 SummaryThe contribution the thesis is the list <strong>of</strong> guidelines that are applicable for migration<strong>of</strong> systems based on MVC architectural pattern <strong>to</strong>ward <strong>Service</strong> <strong>Oriented</strong>Architecture. The target architecture and the migrated architecture are based onarchitectural pattern. <strong>Pattern</strong> encapsulate proven solutions, thus they increasequality <strong>of</strong> architecture. Additionally, the target architecture, the next outcome<strong>of</strong> the thesis is expressed as a pattern language that can be used <strong>to</strong> describe alsoother target systems.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!