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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 48ViewControllerModelFigure 3.10: Example usage of MVC pattern7. MicrokernelOverview – This architectural pattern provides a solution for problemsthat need systems characterised by high adaptivity.ElementsMicrokernel – It is called also Message Bus or just Kernel. Kernel receivesmessages through external API from clients, forwards them to specific serviceand returns the result to calling client.Service – It encapsulates business logic. Can invoke other services (acts asa client)Client – Sends request to Kernel.Relationships – a service does not know location of other services andcannot invoke other service directly. A service can invoke only Kernel. Kernelknows location of all the services and can invoke them(see figure 3.12 ).8. ReflectionOverview – This very unusual pattern enables rapid evolution of system.This evolution is ensured by a “self – aware” meta–layerElementsMeta Layer – consists of Meta ObjectsMeta Object – contains information about structure of the system and itsbehavior including knowledge about operations that should be invoked ifan element from Base Layer invokes an action.Base Layer – contains elements of the system.Element – each element calls Meta Layer in order to execute an action.
Chapter 3. Architectural Patterns 49Top AgentTop LayerIntermediate Agent 1 Intermediate Agent 2Intermediate LayerBottom Agent 1 Bottom Agent 2 Bottom Agent 3Bottom LayerFigure 3.11: Example usage of PAC patternService 1ClientMicrokernelService 2Service 3Figure 3.12: Example usage of Microkernel patternMeta Object Protocol – enables modification of Meta LayerRelationships – Meta Object Protocol is a part of Meta Layer and canperform actions only on Meta Objects. Meta Objects can invoke other MetaObjects and Elements from Base Layer but they cannot invoke Meta ObjectProtocol. Elements of the System can invoke other elements of the systemor Meta Objects from Meta Layer (see figure 3.13).9. InterceptorOverview– the pattern is meant for systems that evolve rapidly. TheBuild–in mechanism allows leaving core functionality unchanged and implementingonly extensions.ElementsClient– invokes business functionalityInterceptor Manager– intercepts invocation from the client and starts reg-
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 57: Chapter 3. Architectural Patterns 4
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 109 and 110:
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?