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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 62async. This missing pattern will be further considered as a Component InteractionPattern because the pattern describes ways of communication between elementsof the system. It separates synchronous operations from asynchronous. Existenceof only one non–assigned pattern shows that selected categorisation method fitswell to list of identified patterns.3.2.4 Selection of representativesFilter 5:Selection of representatives for categoriesThis subsection provides list of representatives of patterns assigned to categoriesin previous subsection as well as motivation behind selection of those representatives.Thiscriterion of selection is structure (elements and relations among them)of the pattern including purpose and behavior of elements of the pattern. Themore generic structure a pattern has, the more likely it is to become a representativeof the category. The structure is generic when it is similar to structure ofother patterns in the same category and has the lowest complexity. A categorymay have more than one representative when structure of considered patternsis very different. All the patterns rejected during previous steps are not takenand will not be taken into consideration during pattern selection. The selectionof representatives shown below provides a list of candidates (patterns from category),motivation behind each selection and selected representative(s). Summaryof representatives allocated to particular categories is provided in table 3.3Layered ViewCandidates: LayersSelection: This category is composed of only one pattern so this pattern automaticallybecomes the representative.Representative: LayersData Flow ViewCandidates: Pipes–and–FiltersSelection: This category is composed of only one pattern so this pattern automaticallybecomes the representative.Representative: Pipes–and–FiltersData Centred ViewCandidates:Shared Repository, Active Repository, BlackboardSelection: Consideration of all of the candidates in terms of criterion for selectionof representatives results in conclusion that Blackboard pattern is not a goodrepresentative because this pattern introduce a moderator, which does not existsin remaining two patterns. However, amount of elements does not decideabout pattern rejection, but a behavior of this particular element does. Moderatorintroduces additional data access mechanism that does not exist in remain
Chapter 3. Architectural Patterns 63two patterns. Shared and Active Repositories are different in only one, but veryimportant detail. Active Repository provides notification service what makes itmore specialized then Shared Repository, consequently Shared Repository is moregeneral, therefore it automatically becomes the representative of this view.Representative: Shared RepositoryAdaptation ViewCandidates: Microkernel, Reflection, InterceptorSelection: Microkernel is a pattern that strongly influences architecture of system.Everything has to be organized around the kernel of the system. Communicationthrough this element is the only way to get to other elements of the pattern.Interceptor has also a main part –Interceptor Manager, which serves as a mainconnection to remaining parts of the system. Additionally, Interceptor providesfunctionality allowing invocation of other elements before the target element isreached. This makes the pattern less abstract than Microkernel. The last candidate-Reflection is a very specific pattern. This pattern has the structure of thesystem build inside. The pattern is aware of the elements and relations betweenthem. There is no way to compare structure of Reflection to Microkernel. Thiscategory has two representatives –Microkernel and Reflection.Representative: Microkernel, ReflectionLanguage Extension ViewCandidates: noneSelection: The category does not have any pattern assigned so consequently thereis no candidates and no representatives.Representative: noneUser Interaction ViewCandidates: Model–View–Controller, Presentation–Abstraction–Controller, C2Selection: User Interaction View consists of three patterns. The first in rowis Model-View-Controller. The pattern was mentioned before as an example ofcategorisation of an architectural pattern as a design pattern. The second is PresentationAbstraction Controller (PAC). Names of both patterns underline similarapproach to the problem of user interaction. Elements of PAC pattern can bemapped to some degree to elements of MVC but in case PAC those elements arenot the main elements. The main elements of PAC pattern are agents containingpresentation, abstraction and controller parts. Those parts could be theoreticallyreplaced by MVC parts, this makes the pattern sort of a MVC agent network,therefore, MVC pattern is more general than PAC. The last pattern in this viewis C2 pattern. C2 is not as similar as PAC and MVC. C2 defines componentsthat serve as elements in MVC or PAC, but in opposite to MVC or PAC they donot have specialized function. Even if an artificial division of C2 elements intoModel / View / Controller components is made, there remain connectors that do
Page 1 and 2:
Master ThesisSoftware EngineeringTh
Page 3 and 4:
AbstractContext: Several examples o
Page 5 and 6:
List of Figures1.1 Research methodo
Page 7 and 8:
List of Tables3.1 Summary of archit
Page 9 and 10:
3.3.1 Definition of Pattern Languag
Page 11 and 12:
Chapter 1Introduction1.1 Background
Page 13 and 14:
Chapter 1. Introduction 3technique
Page 15 and 16:
Chapter 1. Introduction 5was notice
Page 17 and 18:
Chapter 1. Introduction 7do not pro
Page 19 and 20:
Chapter 1. Introduction 9Chapter 4
Page 21 and 22: Chapter 2. Related Work 11This chap
Page 23 and 24: Chapter 2. Related Work 13(b) Chara
Page 25 and 26: Chapter 2. Related Work 15Figure 2.
Page 27 and 28: Chapter 2. Related Work 17Drawbacks
Page 29 and 30: Chapter 2. Related Work 19Figure 2.
Page 31 and 32: Chapter 2. Related Work 21Advantage
Page 33 and 34: Chapter 2. Related Work 23between a
Page 35 and 36: Chapter 2. Related Work 252. Applic
Page 37 and 38: Chapter 2. Related Work 274. Mediat
Page 39 and 40: Chapter 2. Related Work 292.3 Summa
Page 41 and 42: Chapter 3. Architectural Patterns 3
Page 71: Chapter 3. Architectural Patterns 6
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 113 and 114: Chapter 5. Guidelines 1035.1 Patter
Page 115 and 116: Chapter 5. Guidelines 105Descriptio
Page 117 and 118: Chapter 5. Guidelines 107Result Con
Page 119 and 120: Chapter 5. Guidelines 109ContextAn
Page 121 and 122: Chapter 5. Guidelines 111Result Con
Page 123 and 124:
Chapter 5. Guidelines 113System’s
Page 125 and 126:
Chapter 5. Guidelines 115ViewSchema
Page 127 and 128:
Chapter 5. Guidelines 117ViewViewCo
Page 129 and 130:
Chapter 5. Guidelines 119ViewViewCo
Page 131 and 132:
Chapter 5. Guidelines 121ViewViewPr
Page 133 and 134:
Chapter 5. Guidelines 123FrontendFr
Page 135 and 136:
Chapter 5. Guidelines 125complicati
Page 137 and 138:
Chapter 5. Guidelines 127Concluding
Page 139 and 140:
Chapter 5. Guidelines 129UsecasesTh
Page 141 and 142:
Chapter 5. Guidelines 131puter (ext
Page 143 and 144:
Chapter 5. Guidelines 133Group 3 ma
Page 145 and 146:
Chapter 5. Guidelines 135Output: Du
Page 147 and 148:
Chapter 5. Guidelines 137generation
Page 149 and 150:
Chapter 5. Guidelines 139(a) Fronte
Page 151 and 152:
Chapter 5. Guidelines 141Figure 5.1
Page 153 and 154:
Chapter 5. Guidelines 143Figure 5.1
Page 155 and 156:
Chapter 5. Guidelines 145FrontendSc
Page 157 and 158:
Chapter 6. Conclusion 147There are
Page 159 and 160:
Chapter 6. Conclusion 149RQ.6 How t
Page 161 and 162:
References[1] http://www.soa-manife
Page 163 and 164:
References 153[22] Frank Buschmann,
Page 165 and 166:
References 155[46] Dirk Krafzig, Ka
Page 167 and 168:
References 157[67] Xiaohong Qiu. Bu
show all

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

Create successful ePaper yourself

Delete template?

Save as template?