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

More documents

Recommendations

Info

Chapter 5. Guidelines 130layers. View becomes View Layer, Controller becomes Controller Layer andModel becomes Model Layer. Connections between particular componentsalso have to be reorganized in order to minimize dependencies (coupling)between layers. Dependency reduction can be achieved by removing registrationmechanism from Model. This change removes notification functionalitywhat not always is intended.Lack of the mechanism eliminates Model ⇾ View and Model ⇾ Controllerdependencies. This change also eliminates transitive dependencies. Additionallythe View ⇾ Model dependency needs to be removed In case of themigrated project.Output projects: Frontend, ProncessAbstractionService and Basic Ser- vices.The Frontend project is meant to contain all GUI related code. Pro- cess-AbstractionService is meant to contain BPEL. Basic Services project is atemporary project that is meant to contain code that cannot be copied toany of the existing services. This project will be deleted at the end. Thecode from this project will be further transformed into services.2. Chose main communication protocolApplied SOA pattern: Canonical ProtocolApplication Project meant for adaptation is not a mission critical system.The system is also used only within university by very limited group ofpeople and any external user (non-university IP) does not have any accessto the application. Therefore a standard HTTP plus SOAP messagingis applied for project migration. Besides, technologies like RosettaNet orWebShare tie architects to vendors, while SOAP and HTTP are vendorindependent.Output: Communication protocol: SOAP over http3. Unify used schemasApplied SOA pattern: Canonical SchemaApplication: In order to simplify schema maintenance following name notationis used:(a) name of a namespace have to refer to the name of lower layer whennamespace contains definitions of information used in communicationbetween two layers. For instance information used in communicationbetween Process Abstraction and Canonical Resource will be placedin a namespace referring to Canonical Resource.(b) schema is divided into a set of sub–schemas. Each of sub–schemas definesone “main” complex type and a set of related types. In case of AssetDAO,the main complex type is Asset and related types are: Com-
Chapter 5. Guidelines 131puter (extends Asset), Part (composes Asset), AssetNumber (identifiesAsset). The name of such schema is defined as.xsd. For instanceresourceAsset.xsd.Output: XML schema. The schema is located in ProcessAbstractionService.The document will contain definition of arguments of service’s methods andtheir return types.4. Unify PoliciesApplied SOA pattern: Policy CentralisationApplication: Available documentation does not require special security protocols.Application of policies is a complex task. See [44] for more information.Output: No new elements are introduced in case of this project.5. Identify and wrap into services all coarse grained utilitiesApplied SOA pattern: Utility AbstractionApplication: Presentation Layer has only GUI related code, while Controllerexcept process flow code has some code responsible for maintenanceof temporary assets. Code of Model also do not provide any “utility” code.The project does not have utility related code, therefore application of thisguideline in case of TRWAM will not introduce changes to the target architecture.Output: No new services are implemented in case of this project. If aUtility Abstraction related code would exist; it would be wrapped into abasic service.6. Identify and encapsulate access to any external resourceApplied SOA pattern: Canonical ResourcesApplication: In case of MVC, the only place where an access to Resourceis allowed is Model. Therefore any resource-related parts of Model shouldbe identified. Analysis of TRWAM project shows only two resource relatedclasses. The first, AbstractDAO defines general CRUD operations. Thesecond is AssetDAO (SrodkiTrwaleDAO) which executes asset related operationson database. AssetDAO becomes a service providing asset-relateddatabase operations.Output: Two projects are created. The first is crAssetService providingasset related operations like addAsset (adds a new asset) and getCurrent-MaxNumber (returns max id of an asset). There is also removeAsset operationbut it is only a stub that takes crComputer as an argument. This
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:
Chapter 4. Service Oriented Archite
Page 89 and 90: 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: Chapter 5. Guidelines 129UsecasesTh
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?