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

More documents

Recommendations

Info

Chapter 4. Service Oriented Architecture 94provided by other services.This pattern introduces enterprise wide processservices as an additional layer. The services are mainly stateful and manipulateservices from all the underlying layers.Rationale: See Utility Abstraction rationale.7. Policy Centralisation–Services may require to process individual polices.Policies may refer to security, transaction requirements and Quality-of-Services. Replication of policies across inventories brings redundancy andproblems with synchronization of changes to the policies. Application ofthe pattern separates policies from services.Rationale: Forces services to use predefined WS–Policy files. WS–Policydescribes service polices like security.8. Rules Centralisation –The same business rules are applied in many differentservices. This may lead to redundancy and problem with maintenanceof the changes. Business rules are stored and accessible through dedicatedentities like business rules services.Rationale: However the pattern simplifies maintainability, the structureof process–centric services become more complex due to a need of additionalservices invocation in order to validate data against business rulesand constrains.9. Canonical Resources –Modern systems require access to external resourceslike databases, central directories or transaction management frameworks.The resources are accessed by many subsystems of the system. The accesslogic becomes a part of the subsystem. Canonical Resources identifiesand standardises resources across the company. A term resource refers todatabases, activity management systems, state deferral mechanism or otherresource like for instance public services. Separation of access to externalresources grows in importance when an application is not small, because insmall application access to external resources is rather centralised.Rationale: The pattern has significant impact on the architecture becauseeach service requiring access to external resources has to invoke those dedicatedservices.10. State Repository –Long living processes occupy system resources for a longtime. The pattern introduces a state repository that is meant to maintainstate of stateful services. Stateful services delegate their state to specialservices in order to free system resources. The state is not transferred automatically.The transfer occurs when special criteria are met. The criteriacan be for instance an extending waiting for a response. This solution occursto be very useful when an asynchronous communication is applied.Rationale: Application of the pattern requires additional effort related to
Chapter 4. Service Oriented Architecture 95state transfer. Each stateful service needs an access to state repository andthe state has to be converted into maintainable data like XML files.11. UI Mediator –Business services bind into process many independent services.The execution time of those services may vary and it can take awhile to provide result requested by the user. Application of the patternintroduces an additional layer that processes information about progress ofinvoked operation. The information is further acquired by frontends andpresented to users.Rationale: See Utility Abstraction rationale.12. Inventory Endpoint–An inventory may contain several services providingfunctionality that might be used outside the inventory. Services accessingthe inventory from outside should not know structure of the inventory andits functionality. The access also needs to be secured. Inventory Endpointestablishes an entry point for external service consumers. Each customeraccessing service repository, access the endpoint and receives informationfrom the endpoint. Capabilities of endpoints can be extended by for instancedirect / brokered authentication. A single Inventory can have more thanone endpoint.Rationale: : Inventory Endpoint enforces communication through gatelikeservices. Requests coming from service consumers and going back haveto go through an endpoint.Pattern NameService LayersCanonical ProtocolCanonical SchemaUtility AbstractionEntity AbstractionProcess AbstractionPolicy CentralisationCanonical ResourcesState RepositoryUI MediatorInventory EndpointRules CentralisationValidation AbstractionSchema CentralisationTable 4.3: Selected SOA architectural patterns. Grey rows contain patterns identifiedas duplicates
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 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54: Chapter 3. Architectural Patterns 4
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 103: 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?