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

More documents

Recommendations

Info

Chapter 5. Guidelines 132stub was needed to make crComputer available. This is a technology relatedissue ( see 5.4.1 for more details ). The second project is crCommons.This is a shared library that is included to canonical resource project. Theproject provides database related operations like executeResultQuery orgetConnection.7. Identify and wrap into services all entity related codeApplied SOA pattern: Entity AbstractionApplication: MVC pattern has two components containing business logic.The first is Model which should be investigated at the begging and controllerwhich potentially can contain core logic but it should not. TRWAMProject is a Create-Read-Update-Delete (CRUD) based application. TR-WAM’s Model contains only DAO classes and corresponding entities. Controllerdoes not contain only work flow controlling code. It also has a coderesponsible for generation of a new id of assets. This generation activityshould not be a part of controller, because controller delegates tasks. Existenceof a non-work flow related code attests to braking structure of thepattern. Asset number generation should be separated into an asset-relatedCore Logic service.Output: A new project is created. The service is named eaAssetService. Theservice provides operation Service providing following operation “generateidentifiers” The operation takes collection of services and starting numberas arguments.8. Identify and wrap into services business rulesApplied SOA pattern: Rule CentralisationApplication: Available TRWAM documentation (SPECYFIKACJA REGU I OGRANI.doc)contains sixteen business rules and five domain constrains.(a) Group 1: OGR/2, OGR/3OGR/2: An asset has to belong to one category: time depreciatingor others(b) Group 2:Rules defining processes are described in form of use cases.(c) Group 3:REG/01, REG/02,REG/03,REG/04,REG/05,REG/06,REG/07,REG/08,REG/09, REG/10, REG/11,REG/12,REG/13, REG/14, REG/15,REG/16,OGR/1, OGR/4REG/02: An asset can be lend if executives allowed.REG/03: Lending person creates a lend note during asset lending.OGR/4: Numbers of assets are unique. Each asset may have morethan one asset number.
Chapter 5. Guidelines 133Group 3 may be encapsulated in services but there is no implementationreferring to those rules in code, consequently no rules validation serviceswill be created during migration .Output: No services are implemented in case of this project. If a RuleCentralisation related code would exist; it would be wrapped into a basicservice as it is done in the previous guideline.9. Provide inventory endpoints to basic servicesApplied SOA pattern: Inventory EndpointApplication: Inventories in TRWAM project consists of only one servicedue to a small size of the project. Introduction of an additional service(inventory endpoint) that will be a facade to the existing services is simplyredundant. Such introduction would unnecessary complex the process andintroduce overhead.Output: No new services are implemented in case of this project. Implementationof an inventory endpoint in case of this system makes no sensebecause inventories have only one service. The endpoint service would haveexactly the same interface.10. Identify all processes within the legacy applicationApplied SOA pattern: Process AbstractionApplication: MVC architectural pattern has one component that takes careabout Business Process Logic within application - Controller. In case ofTRWAM project, Controller is not implemented properly what was noticedin Entity Abstraction part. This is not the only problem of Controllerin TRWAM project. TRWAM’s Controller contains also code responsiblefor maintenance of temporary assets. Temporary asset is an asset thatwas defined by a user but was not persisted yet. Due to wrong Controllerimplementation, the flow of process has been distorted. The process isartificially divided into two separated processes. The fist process createsidentification numbers for temporary assets. The number is based on actualmaximum value of asset primary key and requires additional computing.Computation of a new number for temporary assets does not make sense atall. The assets simple may not be persisted and all the computation effort iswasted. The second process is meant to persist temporary assets. A properwork flow of the process should be following:(a) Create an asset.
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:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Chapter 4. Service Oriented Archite
Page 87 and 88:
Page 89 and 90:
Page 91 and 92: 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: Chapter 5. Guidelines 131puter (ext
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?