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

More documents

Recommendations

Info

Chapter 5. Guidelines 118pervise up to ten students in one semester”. This group may partiallyoverlap with the first group.The first group of rules, due to its simplicity and framework support (forinstance JSF allows to add simple validation rules to controls) should beimplemented on a client side. The second group should be included duringcreation of process services. The third group of requirements can be implementedin logic of the system and in database. The code of Model shouldbe check in order to identify all the code validating business rules (see figure5.8).ViewViewControllerControllerSchemaPolicySchemaBasic ServicesPolicyBasic ServicesUtility+ Rules Centralisation =UtilityResourcesResourcesEntityEntityRulesFigure 5.8: Migration step 89. Provide inventory endpoints to basic services Applied SOA pattern: InventoryEndpointHow to: Inventory Endpoint establishes an additional layer of abstractioncomposed of a set of services that serve as facades. The layer contains bothservices that limit access to the system (check permissions etc) and servicesthat serve as facades to particular inventories like Canonical Resource. Ingeneral, each inventory should have at least one endpoint (facade). Operationsprovided by endpoints should be defined by architects. The operationscan be composed of only operations from underlying services (see figure 5.9).10. Identify all business processes within the legacy applicationApplied SOA pattern: Process AbstractionHow to: Business Process logic describes flow of processes within company;therefore all controlling components from Controller should be investigatedin order to identify processes. The next source of process-related knowledgeis an available documentation. At the moment, all non-controlling
Chapter 5. Guidelines 119ViewViewControllerControllerInventory EndpointsSchemaBasic ServicesPolicySchemaPolicyUtility+ Inventory Endpoints =Basic ServicesUtilityResourcesResourcesEntityEntityRulesRulesFigure 5.9: Migration step 9code should be removed from controlling components. If the controllingcomponents still contain additional code, the code should be moved eitherto elements defined previously like Canonical Resource or elements thatwill be described like Frontend, State Repository, UI mediator or InventoryEndpoints. The location of the removed code shall base on function of thecode and purpose of the listed elements of the architecture (see figure 5.10).ViewViewControllerProcess AbstractionInventory EndpointsInventory EndpointsSchemaPolicySchemaPolicyBasic ServicesUtility+ Process Abstraction =Basic ServicesUtilityResourcesResourcesEntityEntityRulesRulesFigure 5.10: Migration step 1011. Identify all statefull services and decide if their state can be deferredApplied SOA pattern: State Repository
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:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78: Chapter 3. Architectural Patterns 6
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 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: Chapter 5. Guidelines 117ViewViewCo
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?