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

More documents

Recommendations

Info

Chapter 5. Guidelines 110Problem The same business rules are applied in many different services.This may lead to redundancy and problem with maintenance of the changes.ContextA System uses many rules across services.Forces(a) Rules may change over time(b) New rules may be added(c) Outdated rules may be removed(d) One rule may be used by many servicesSolution Business rules are stored and accessible through dedicated entitieslike business rules services.Result Context The application has unified access and storage of businessrules. The rules are easy to update and access.9. Name Inventory EndpointProblem An inventory may contain several services providing functionalitythat might be used outside the inventory. Services accessing the inventoryfrom outside should not know structure of the inventory and itsfunctionality. The access also needs to be secured.ContextAn application exposes some of its services to external services.Forces(a) The services that can potentially access the inventory are not known.(b) Structure of the inventory needs to be hidden.(c) The functionality of the inventory needs to be limited.(d) Access to the inventory needs to be secured.Solution Inventory Endpoint establishes an entry point for external serviceconsumers. Each customer accessing service repository, access the endpointand receives information from the endpoint. Capabilities of endpointscan be extended by for instance direct / brokered authentication. A singleInventory can have more than one endpoint.
Chapter 5. Guidelines 111Result Context Application of Inventory Endpoints introduces an additionallayer of abstraction that guards access to inventories. Endpoint serveas facades to inventories and may provide security related functionality.10. Name Process AbstractionProblem Grouping of business process services together with non-businessprocess services makes harder maintenance of both types of the services. Itis harder to change processes and maintain functionality provided by otherservices.ContextAn application contains business process.Forces(a) Business process cannot be changed.(b) Development of business services needs to be separated from developmentof non-business services.Solution This pattern introduces enterprise wide process services as anadditional layer. The services are mainly stateful and manipulate servicesfrom all the underlying layers.Result Context The system has clearly separated layer of process services.Those services maintain only the process. Other functionality isimplemented in other services.11. Name State RepositoryProblemLong living processes occupy system resources for a long time.ContextAn application contains long living processes.Forces(a) A long living process may need store and restore state few times(b) State cannot be lost–restored state must be the same as stored
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:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70: Chapter 3. Architectural Patterns 5
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: Chapter 5. Guidelines 109ContextAn
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?