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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 46Knowledge source 1ModeratorKnowledge source 2BlackboardKnowledge source 3Figure 3.8: Example usage of Blackboard pattern4. BrokerOverview – Broker is an architectural pattern that organises communicationwithin distributed system.ElementsClient – is a user application that sends requests to the broker.Broker – has to maintain all requests, provides security and loadbalancing.Node – is a part of the system that encapsulates logic of the system.Relationships – client as a requesting element connects to a broker. Theclient does not know location of nodes. Locations of nodes are known onlyto the broker. The nodes do not know location of the clients, but they knowlocation of the broker. This knowledge is required because each node hasto register itself in the broker. Connections between broker and nodes aredynamic, it means that any node can connect and disconnect in runtime(see figure 3.9).5. Model View Controller (MVC)Overview – the pattern is dedicated for systems that emphasise role of informationdisplayed to users. Due to clear separation of presentation part,the pattern supports development and simplifies maintenance of this sortof systems.ElementsModel – represents represents data of the system and functionalities to manipulatethemView – displays informationController – handles requests from view and translates them to request tomodel.Relationships – Model cooperates with Controller because it can update
Chapter 3. Architectural Patterns 47Client 1Node 1Client 2BrokerNode 2Client 3Figure 3.9: Example usage of Broker patternregistered Controllers. It also cooperates with View because Model cannotify View about changes of state of Model. View interacts with Controllerbecause View invokes Controller. It can also retrieve data fromModel.Controller interacts with both Controller and Model (see figure 3.10)6. Presentation Abstraction ControllerOverview– the purpose of the pattern is similar to the purpose of MVCpattern. This pattern represents different approach to the problem of interactionof a user with an application.ElementsAgent– each agent consist of three elements: Presentation which is meantto provide information to a user, Abstraction manipulating data of thesystem and Controller handling communication between Presentation andAbstraction. Agents are further divided into agents representing particularfunctionalities and agents coordinating the system.Layer of Abstraction– an application consists of several Layers of Abstraction.Each layer contains Agent on the same level of abstraction. The toplayer contains only one agent which coordinates the whole application whilethe “leaves agents” in the lowest layer represent particular functionalities.A layer invokes other layer on behalf of an agent.Relationships– Each Agent can communicate directly with other agentsin the same layer of abstraction. Layers of Abstraction communicate onlywith layers bellow (see figure 3.11).
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 55: Chapter 3. Architectural Patterns 4
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 107 and 108:
Chapter 4. Service Oriented Archite
Page 109 and 110:
Page 111 and 112:
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?