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

More documents

Recommendations

Info

Chapter 4. Service Oriented Architecture 964.6.2 SOA– The target architectureThe target architecture (see figure 4.4) is expressed using identified SOA architecturalpatterns and relations between them. Motivation behind location ofparticular patterns the target architecture is following:1. Schema – is an XML document which describes vocabulary to express businessdata [82]. The schema is divided into domains. The reason why eachlayer depends on the schema is that each information in the system has tobe described according to the schema, consequently each service includes apart of the schema layer.2. Policy – provides a model and a syntax to describe and communicate policies[13]. The policies are defined in one place and as the schemas are applied toparticular services, therefore each layer has to have an access to the policies.3. Frontend – contains service clients therefore it is a top layer. Frontends maycommunicate with UI–Mediator if continuous feedback to user is required.This layer does not exist in patterns presented by T.Erl[32] but legacysystems have some user interface that also have to be migrated.4. Endpoints Layer – contains entry point for each inventory of basic services.If a service from other inventory or a client application wants to consumea service then the consumption has to be conducted via an endpoint. Endpointsdefine also possible operations therefore they serve also as Facade.5. Process Abstraction – consists of process services. Process services dependson basic services.6. Basic Services consist of services that provided by Entity Abstraction(Entity),Utility Abstraction(Utility), Rules Centralisation(Rules), Canonical Resource(Resources)and State Repository(State). Names in round brackets correspond to namesin figure.4.7 Benefits of SOASOA requires many experienced specialists including architects, programmers,requirement engineers and project managers. SOA requires also a lot of timewhat does not support well projects with a short time-to-market. NeverthelessService Oriented Architecture is introduced to companies that operate on a varietyof business domains including banking [46](Halifax Bank Of Scotland), post
Chapter 4. Service Oriented Architecture 97FrontendUI-MediatorProcess AbstractionSchemaInventory EndpointsPolicyBasic ServicesUtilityResourcesEntityRulesStateFigure 4.4: SOA target architecture[46](Deutsche Post AG ) or insurance companies [46] (Winterthur). The choiceof SOA is justified by a number of benefits. Literature provides a variety ofSOA benefits and advantages that include business and personal perspective. Onaccount of a huge list of potential profits, only the most significant and characteristicare presented in this section. For more information about SOA benefitssee [46][31][62].Business perspectiveThe main benefit of SOA is agility [46][31]. This word and its variants becamevery popular in last few years. There is a number of publications having “agilityin name”. We can find Agile Software Development, Agile Architecture, Agile
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: Chapter 3. Architectural Patterns 4
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 105: 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 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?