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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 68Pattern nameOccurrencesLayers 18Shared Repository 13Pipes and Filters 10Client–Server 10Broker 9Model– View– Controller 7Presentation–Abstraction–Control 7Explicit Invocation 4Plug–in 4Blackboard 4Microkernel 3Peer to Peer 3C2 3Publish–Subscriber 3State Transition 3Interpreter 2Half Sync, Half Async 2Active Repository 2Interceptor 2Remote Procedure Call 1Implicit Invocation 1Table 3.5: Popularity of particular patterns. Adopted from [38]There is a strong correlation between table 3.5 and table 3.1, namely, mostpopular patterns from table 3.5, like Layer or Pipe And Filters exist in all sourcedocuments. Less popular patterns like Plug–in or State Transmission did not passthe first selection or do not exist there at all. Paris Avgeriou and Uwe Zdun [8]] present one more very interesting outcome, a table 3.5presenting which exactlypatterns interact with others.Pattern nameOccurrencesLayers – Broker 6Layers – Shared Repository 3Pipes Filters – Blackboard 3Client Server – Presentation Abstraction3ControlLayers – Presentation Abstraction 3ControlContinued on Next Page. . .
Chapter 3. Architectural Patterns 69Pattern nameOccurrencesLayers – Model View Controller 3Broker – Client-Server 2Shared Repository – Presentation Abstraction2ControlLayers – Microkernel 2Shared Repository – Model View Controller2Client Server – Peer to Peer 2Shared Repository – Peer to Peer 2Shared Repository – C2 2Peer to Peer – C2 2Layers – Interpreter 2Layers – Client Server 2Pipes and Filters – Client Server 2Pipes and Filters – Shared Repository 2Client Server – Blackboard 2Broker – Shared Repository 2Broker – Half Sync/Half Async 2Shared Repository – Half Sync/Half 2AsyncClient Server – Half Sync/Half Async 2Table 3.6: Popularity of pairs of architectural patterns. Adopted from [38]However, there are many pairs of patterns, not all are included. Reviewers excludedsixty seven pairs that appeared only once.3.3.4 Representatives of categories in real systemsFilter 6: Removal of rarely interacting patternsTable presenting categories 3.3 with their representatives provides ten representativepatterns as follows: Layers, Pipes and Filters, Shared Repository,Microkernel, Reflection, Model View Controller, Half Sync/Half Async, ClientServer, Remote Procedure Call and Message Queueing. Additionally. Table 3.6,which is presenting popularity of particular patterns presents thirteen differentpatterns combined into pairs. The patters are as follows: Layers, Broker, SharedRepository, Pipes and Filters, Blackboard, Client Server, Presentation AbstractionController, Model View Controller, Microkernel, Peer to Peer, C2, Interpreter,Half Sync/Half Async. In order to minimize the list of potential patterns
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 77: 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?