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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 50Meta Object ProtocolMeta Object 1Meta Object 2Meta layerElement 1 Element 2Base layerFigure 3.13: Example usage of Reflection patternistered interceptorsInvoked Component– contains business logicPreaction Interceptor– this interceptor is invoked before “Invoked Component”is invokedPostaction Interceptor– this interceptor is invoked just after action invokedby Client is accomplished but before Client gets answerRelationships– Client invokes Interceptor Manager, which invokes preactioninterceptors. Then, the manager executes an action on the componentand invokes postaction interceptors when the action is finished (see figure3.14).PreActionInterceptorPostActionInterceptorClientInterceptor ManagerInvoked ComponentFigure 3.14: Example usage of Interceptor pattern10. Half–sync/half–asyncOverview– supports control over synchronous and asynchronous operationsin concurrent systems without reducing performance of the system.ElementsSynchronous Service Layer– contains high–level elements executing syn-
Chapter 3. Architectural Patterns 51chronous logic of the systemSynchronous Service– represents logic of the system executed in a synchronousmannerAsynchronous Service Layer– contain low–level elements executing asynchronouslogic of the systemAsynchronous Service– represents logic of the system executed in an asynchronousmannerQueueing Layer– contains element mediating between Synchronous andAsynchronous layersQueue– a mediating element from Queueing LayerExternal Event Source– generates event processed by services from AsynchronousLayerRelationships– - Services from each layer can cooperate with other servicesfrom the same layer. They can also invoke Queue that serves as a messagestore. External Data Source can invoke only services from AsynchronousLayer (see figure 3.15 ).Sync Service 1 Sync Service 2 Sync Service 3 Synchronous Service LayerQueueQueueing LayerAsync Service 1Asynchronous Service LayerExternal Event SourceFigure 3.15: Example usage of Half–Sync Half–Async pattern11. Shared RepositoryOverview– provides solution for problem of passing large amount of databetween elements of a system. The pattern reduces additional overhead andperformance drop.ElementsRepository – is a core element of the pattern. It is meant to store, maintain
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 59: Chapter 3. Architectural Patterns 4
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 111 and 112:
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?