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

More documents

Recommendations

Info

Chapter 2. Related Work 265. ADM: Visualization –illustrates meta–data collected in KDM. The visualisationincludes charts, graph, views, metrics and UML models.Status ow work: No target date set6. ADM: Refactoring –includes modernisation of an application by structuring,rationalising and modularising.Status ow work: No target date set7. ADM: Transformation –brides existing application with the target systemby defining possible mapping and transformations. It is worth to underlinethat the standard will target at usage of Model–Driven Architecture (MDA)paradigm.Status ow work: No target date setThose specifications cover many different aspects of modernisation but in contextof this research mainly Pattern Recognition is very interesting. The fact thatPattern Recognition is becoming a part of standard emphasises contribution ofpattern during migration. The status of work is taken from [64]. The documentis dated February 2009 but it still available on the web page.2.2.2 PCBMERPresentation–Controller–Bean–Mediator–Entity–Resources (PCBMER) is an architecturalpattern elaborated by Lech Maciaszek. The pattern is dedicated forhighly adaptive systems [53]. The pattern is based upon Holistic theory. Thetheory says that a holon in a recursive entity that can contain other holons inside.The theory is also enriched by Holarchy (Hierarchy of holons) [53]. Thearchitecture consists of six following layers:1. Presentation –is a top level layer and represents User Interface (UI). Theinterface provides information contained in beans from underlying Beanlayer.Depends on: Bean Layer, Controller Layer2. Controller –corresponds to Controller from MVC or PAC architectural pattern.A controller encapsulates an enterprise business logic which is invokedby Presentation LayerDepends on: Bean Layer, Entity Layer, Mediator Layer3. Bean –represents information meant to be displayed on UI. A single beanis an object that consists of entities from Entity layer as well as additionalproperties.Depends on: Independent
Chapter 2. Related Work 274. Mediator –mediates between Resource Layer and Entity Layer. The purposeof the layer is to manage business transactions, enforce business rules,instantiate business objects in Entity Layer and manage the memory cacheof the application.Depends on: Resource Layer, Entity Layer5. Entity –represents all the business objects within the application.Depends on: Independent6. Resources –mediates between application and data sources. The source canbe a database, service or other external entity containing required information.Depends on: External ResourcesThe pattern fits well to for business solution and as the business solutions becomea subject of integration. The integration presented by L. Maciaszek aims atintegration with Service Oriented Architecture. The pattern is modernised inorder make the integration possible. The modernisation of the pattern is namedPCBMER–U (Utility) and introduces three new elements into the pattern(seefigure 2.3).1. Broker –is a message broker2. Orchestration –encapsulates and executes a new business logic (see 4.3.2 formore information)3. Service Registry –is responsible for service discovering and depends only onmediator.The modification seems to have some contradiction. The first is that accordingto description, Registry depends on “utility’s business logic in Mediator” [52]what in fact is quite interesting because Mediator Layer does not depend onController Layer, consequently Mediator layer is not ”aware” of Controller layer.Registry may not discover higher level services located in Controller. The nextpotential contradiction is where Orchestration is introduced. According to figure3 in [52] Controller depends on Orchestration what seems to be against roleof Orchestration, because in fact Orchestration / Process Services depend onunderlying services what in this case may mean that Orchestration depends onservices allocated in Controller layer. The last contradiction refers to the figure 3and the description. Description says that Broker and Orchestration depend onlogic in Controller Layer while the dependency in the picture is opposite. Thesame situation refers to Mediator Layer and Registry.
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: Chapter 2. Related Work 252. Applic
Page 39 and 40: Chapter 2. Related Work 292.3 Summa
Page 41 and 42: Chapter 3. Architectural Patterns 3
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 87 and 88:
Chapter 4. Service Oriented Archite
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
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?