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 3. <strong>Architectural</strong> <strong>Pattern</strong>s 603. Data–Centered View – presents system as a data s<strong>to</strong>re. The s<strong>to</strong>re containsone or more independent components <strong>to</strong> s<strong>to</strong>re data and one or morecomponents that request data. Description <strong>of</strong> patterns has <strong>to</strong> provide informationabout a method <strong>of</strong> data s<strong>to</strong>rage, access, update and distribution aswell as a method <strong>of</strong> communication with and among data s<strong>to</strong>ring elements.The patterns have also <strong>to</strong> point out whether they are active or passive.The description <strong>of</strong> a pattern belonging <strong>to</strong> Data-Centered View includes itsscalability, modifiability, reusability and integrability.4. Adaptation View – presents a system from adaptivity point <strong>of</strong> view. Systemmust have two main parts: static and dynamic. The static part is a core<strong>of</strong> the system. Dynamic parts can be added or removed from the system inruntime. <strong>Pattern</strong>s introduced in this category have <strong>to</strong> enable architecture <strong>to</strong>evolve and keep communication between particular elements when a systemevolves.5. Language Extension View – divides system in<strong>to</strong> two parts. The first partis native for environment in opposite <strong>to</strong> the second, which is not. <strong>Pattern</strong>sunderline how non–native parts <strong>of</strong> the system are integrated and translatedin<strong>to</strong> environment.6. User Interaction View – underlines perspective <strong>of</strong> users. <strong>Pattern</strong>s that belong<strong>to</strong> this category have presentation that is strongly separated from therest <strong>of</strong> the system. Those patterns take special care about data, applicationlogic and their associations with presentation, therefore an impact onusability, modifiability and reusability is also considered.7. Component Interaction View – underlines communication between particularcomponents <strong>of</strong> a system and presents the system itself as a set <strong>of</strong> independentcomponents. The communication technique can be synchronous aswell as asynchronous. The important fact is that whichever communicationtype is chosen it has <strong>to</strong> be indirect. Important aspects are modifiability andintegrability.8. Distribution View – lays a special emphasis on physical localisation andrelations <strong>of</strong> components over network. A special emphasis is laid on decoupling<strong>of</strong> distributed components. Important aspects are performance,modifiability, location and transparency.Categorisation by View presented by P. Avgeriou and U. Zdun provides methodcovering not only elements <strong>of</strong> architecture and connection between those elementsbut also other properties like usability <strong>of</strong> application are considered This way <strong>of</strong>categorisation <strong>of</strong> patterns will be further used as a selected <strong>to</strong> categorisation.

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

Saved successfully!

Ooh no, something went wrong!