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

Chapter 3. Architectural Patterns 613.2.3 Allocation of patterns to categoriesFilter 4: Assignment of architectural patterns to selected categoryThis subsection presents allocation of patterns identified in subsection 3.1.4 toviews described in the previous subsection. Since eighteen out of nineteen identifiedpatterns exist in the document that provides selected approach to categorization(see second source [8] in the Source of Patterns subsection), the categorisationis almost automatic. The table 3.2 presents results of allocation.View NameLayered ViewData Flow ViewData–Centred ViewAdaptation ViewLanguage Extension ViewUser Interaction ViewComponent Interaction ViewDistribution ViewPattern NameLayersIndirection LayerBatch SequentialPipes and FiltersShared RepositoryActive RepositoryBlackboardMicrokernelReflectionInterceptorInterpreterVirtual MachineRule –Based SystemModel –View –ControllerPresentation –Abstraction–ControllerC2Explicit InvocationImplicit InvocationClient –ServerPeer –to –PeesrPublisher –SubscriberBrokerRemote Procedure CallMessage QueuingTable 3.2: Architectural Patterns – View organisation. Adopted from [8]The table 3.2 contains also names of pattern marked grey. Those patterns areassigned to particular categories (“views”) but they were rejected during PatternIdentification subsection. This table clearly shows that Language Extension Viewis discarded due to lack of assigned patterns. The pattern that is not presentin the table 3.2 but exists in the Pattern Summary table 3.1 is Half sync / half