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

Chapter 5. Guidelines 104Problem GUI of modern systems is very complex and prone to changes. Thechanges include modification of existing views, elements of the views and creationof new views. Many applications offer also dynamic change of ’look and feel’.Nowadays system offer interaction via many different devices. Interaction viakeyboard and mouse becomes not sufficient. Users want to access their applicationusing mobile phones or tablets. All those types of devices need a separate anddedicated user interfaceContextApplications providing a rich and flexible user interface.Forces1. The same information is presented on different types of devices2. The view should be easy to modify and maintain3. Changes to user interface should be available in runtime, for instance changeof look and feel4. Changes to user interface should not affect core functionality of the systemSolution Introduce MVC architectural pattern. For more information aboutthe pattern see refsec:PatternDescription.Result Context Introduction of the pattern simplifies maintenance and of interface.Clear separation of view from logic of the system supports also developmentof new interface for different types of devices.5.1.2 SOA Pattern LanguageAbstractThis pattern language presents architecture that is created using SOA architecturalpatterns. This pattern language is a high level solution for implementationof SOA. Description of patterns presented in pattern section is a more detailedversion of description presented in section 4.6.1MapFigure 4.4 presents the map of the target pattern language.