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

More documents

Recommendations

Info

Chapter 4. Service Oriented Architecture 100Summarizing, introduction of SOA requires positive attitude of IT staff becauseit is not an easy task and requires some overhead. It challenges theirexperience and ability of creative thinking, but in long range it brings a lot ofnon-trivial benefits which enhance quality of a pro duct and associated processes.Summarising, introduction of SOA requires positive attitude of IT staff becauseit is not an easy task and requires some overhead. It challenges theirexperience and ability of creative thinking, but in long range it brings a lot ofnon–trivial benefits which enhance quality of a product and associated processes.4.8 SOA ManifestoService Oriented Architecture is not standardised and different vendors may haveslightly different understanding of this specific type of architecture, but the mainidea remain the same. Diversity of implementation provided by different SOAvendors is an advantage of SOA.Nevertheless lack of clear explanation what exactly SOA is, leads to manydifferent misconceptions and misunderstanding like presented in [47] [14]. Thisproblem was notified by leading SOA experts and resulted in SOA Manifestoannounced in October the 4th 2009 during SOA Symposium in Rotterdam. Themanifesto is following [1]:Service orientation is a paradigm that frames what you do. Service–orientedarchitecture SOA is a type of architecture that results from applying serviceorientation.We have been applying service orientation to help organizations consistentlydeliver sustainable business value, with increased agility and cost effectiveness,in line with changing business needs.Through our work we have come to prioritize:Business value over technical strategyStrategic goals over project–specific benefitsIntrinsic interoperability over custom integrationShared services over specific–purpose implementationsFlexibility over optimizationEvolutionary refinement over pursuit of initial perfectionThat is, while we value the items on the right, we value the items on the leftmore.However, the manifesto tries to clarify the concept of SOA, it has been criticised.The main objection is that the manifesto is ambiguous, consequently someauthors like Joe McKendrick [55] try to explain and motivate Manifesto statements.Nevertheless the manifesto is a good omen that brings some clarification
Chapter 4. Service Oriented Architecture 101into the domain which according to Martin Fowler [33] is “semantics–free conceptthat can join ’components’ and ’architecture’.”4.9 SummaryService Oriented Architecture is not standardised. There are many vendorsproposing their understanding of SOA along with tools support this understanding.Service Oriented Architecture has several benefits that may be presentedfrom personal and business perspective. There are also some challenges that haveto be faced.Definition of Service Architecture revolves around services, frontends, servicerepositories and service bus.This section identifies 14 architectural patterns that were extracted from 73found patterns. Based on identified architectural patterns, the target architecturewas elaborated.
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: Chapter 3. Architectural Patterns 4
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 109: 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?