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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 64exist neither in MVC nor in PAC. The connectors specify more precisely way ofcommunication between elements. Summarizing, MVC pattern is the most generalpattern within the category and becomes representative of User InteractionView.Representative: Model–View–ControllerComponent Interaction ViewCandidates: Explicit Invocation, Implicit Invocation, Client–Server, Peer–to –Peer,Half–Sync / Half–AsyncSelection: Pattern descriptions presented in section 3.2.1 underlines similaritiesbetween Explicit invocation, Implicit Invocation and Client–Server. Client–Serverdefines division of a system into two parts. Explicit and Implicit Invocations alsomake this division but they also introduce new elements determining communicationdetails between Client–Server parts. They are just variants of Client–Serverpattern, therefore Client-Server is more general in terms of previously stated criteria.Peer–to–Peer pattern describes interaction between elements that are clientsand servers in the same time. In fact, this pattern crates a network of modifiedClient-Server entities. The problem appears when a comparison between Client-Server and Half–sync/half–async has to be made. The problem is that those twopatterns describe different model of connection between components. Responsibilitiesof elements those two patterns are incomparable. Parts of Half–Sync/ Half–async pattern in opposite to Client–Server take care about two differentaspects of communication, therefore those two patterns cannot compared to eachother. The Component Interaction view has two representatives.Representative: Half–Sync / Half–Async, Client–ServerDistribution ViewCandidates: Broker,Remote Procedure Call, Message QueueingSelection: Distribution View contains three architectural patterns. The firstin row is Broker. The description of Broker pattern underlines similarities betweenthis pattern and previous category. The structure and functionality of thispattern matches description of Client –Server pattern. In fact, Broker is just amore complex version of Client–Server; therefore, this pattern will not be comparedwith patterns from Distribution View and shall be moved to ComponentInteraction View. Since this pattern is a more complex version of Client–Server,Broker is not a representative of Component Interaction View. Remote ProcedureCall does not have fixed structure. It is rather an idea how to keep connectionsbetween different parts of distributed systems masked. The patterns are incomparable;consequently, this view has also two representatives–both are differentin terms of their structure and functionality.Representative: Remote Procedure Call, Message Queueing
Chapter 3. Architectural Patterns 65View Name Pattern Name RepresentativeLayered View Layers LayersData Flow View Pipe and Filters Pipe and FiltersData –Centered View Shared Repository Shared RepositoryActive RepositoryBlackboardAdaptation View Microkernel MicrokernelInterceptorReflectionReflectionUser Interaction View Model –View –Controller Model –View –ControllerPresentation –Abstraction–ControllerC2Component Interaction Half –Sync / Half –Async Half –Sync / Half –AsyncViewExplicit Invocation Client ServerImplicit InvocationClient ServerPear –to –PearDistribution ViewBrokerRemote Procedure Call Remote Procedure callMessage QueuingMessage QueuingTable 3.3: Architectural Patterns – categories with their representatives3.3 Mutual InteractionThe Problem of pattern interaction is an implication of pattern organisation andcomplexity of systems. This problem cannot be neglected during pattern selection.The problem derives from the fact that combination of patterns affectssystem and have an impact on non-functional properties. A way in which patternsinteract has to be carefully considered. It may strongly increase quality ofa system, but it also may lead to a disaster. This section presents patterns thatare applied together in real systems. The section is organized as follows:1. Definition of Pattern Language – the subsection provides basic definitionof pattern language, including criteria required to be fulfilled by a patternlanguage2. Pattern Language in real systems – presents shortly results of studies aboutnumber of architectural patterns in systems
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 73: 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?