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

Chapter 5. Guidelines 140(a) Entity Abstraction(b) Rules Centralisation(c) Canonical Resources(d) State Repository(e) Utility AbstractionThe list does not contain Service Layers, Schema Centralisation and Policy Centralisation.Those three patterns set frame of the architecture. Service Layersdefine the layers presented above while the remaining two support in maintenanceof application wide technical elements: schemas and policies.5.5.3 Advantages and DrawbacksAdvantages1. The target architecture represents Process–Enabled SOAProcess–Enabled SOA is the most complex architecture. This architecturecan be used also as a target architecture for systems that are not result ofmigration.2. The guidelines use properties of migrated system – namely applied architecturalpatternElaborated guidelines supports migration of systems based on MVC architecturalpattern3. Documentation is not required but it is very helpful Fact that the documentationof the migrated system is not required is an advantage becausethe systems that are migrated are maintained after they are released. Duringmaintenance, the changes that are introduced to code are not alwaysreflected in documentation.4. The migration is systematicPeople dealing with migration of systems based on MVC have now an elaboratedlist of steps that should be executed.Drawbacks1. Migrated System cannot use frameworks supporting MVC pattern. Modernsystems often use frameworks that provide a lot of out–of–box code. Thecode makes implementation simple but more difficult to migrate.2. The guidelines have limited application – only systems build on MVC patterncan be migratedThe guidelines were elaborated only for MVC architectural pattern. Theyare not applicable as they are for other architectural patterns.