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

More documents

Recommendations

Info

Chapter 4Service Oriented ArchitectureThis chapter presents an overview of Service Oriented Architecture (SOA) alongwith benefits and challenges and the target architecture that bases on SOA architecturalpatterns. Section is organised in following manner:1. Definition of Service Oriented Architecture – presents definition of SOAfrom both business and architectural point of view.2. Elements of SOA – architecture is composed of a set of elements. Thissection briefly presents elements of SOA. This knowledge is required tounderstand architectural point of view.3. SOA – business point of view – the point of view presents SOA as a businessprocess. The perspective underlines activities and services. The activitiesare required to create SOA, while services are abstract entities providingbusiness values.4. SOA – architectural point of view – this point of view presents three differentapproaches to realize Service Oriented Architecture.5. SOA Vendors – one of the basic properties of SOA says that SOA is vendorindependent. Since there is no unified definition describing SOA, each vendorpresents own vision. Those visions are not necessarily similar to visionsof other vendors. This section presents overview of SOA delivered by a fewleading vendors and an overview of tooling provided by the leading vendor.6. Architectural Patterns in SOA – this section presents identified SOA patterns.The patterns support different elements of SOA. Based on the patternsthe target architecture is created.7. Benefits of SOA – the section presents briefly possible motivation for choosingSOA. The benefits present different perspectives on benefits of SOA.The section contains also several SOA related challenges.8. SOA Manifesto – presents SOA Manifesto9. Summary – a section summarizing the chapter.74
Chapter 4. Service Oriented Architecture 754.1 Definition of Service Oriented ArchitectureThere are many definitions of SOA in literature. The definitions differ in termsof scope and details. In general, the definitions underline business or technicalaspects of SA. An example of business-focused definition is provided by ThomasErl [31]:“SOA establishes an architectural model that aims to enhance the efficiency,agility, and productivity of an enterprise by positioning services as the primarymeans through which solution logic is represented in support of the realisation ofstrategic goals associated with service–oriented computing.”Other business focussed definition says that SOA is [13]: “A set of business,process, organizational, governance, and technical methods to reduce or eliminatefrustrations with IT and to quantifiably measure the business value of IT whilecreating an agile business environment for competitive advantage.”While business view on SOA is important and cannot be neglected, the thesisfocuses on architectural aspect of Service Oriented Architecture. “Architecture”or more precisely on “Software Architecture”. Software Architecture [39]:”is nota project plan that describes activities and staffing for designing the architectureor developing the product. Instead it is a structural plan that describes the elementsof the system, how they fit together and how they work together to fulfil thesystem’s requirements. It is used as a blueprint during the development process,and it is also used to negotiate system requirements(...)”The definition of SOA from architectural point of view must align to the definitionof Software architecture presented above. A strict definition of ServiceOriented Architecture, which includes aspects of the Soft- ware Architecture ispresented by Krafzig [46]:A Service–Oriented Architecture (SOA) is a software architecture that is basedon the key concepts of an application frontend, service, service repository, andservice bus. A service consists of a contract, one or more interfaces, and an implementation.The definition of SOA presented by Krafzig is the definition used in this thesis.Each time the term SOA is recalled, it refers to this definition unless it is statedexplicitly that other definition is applied. The definition as presented by Krafzigincludes structural aspects of an architecture using several other terms. Theexplanation those terms is presented in the section below.
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 83: Chapter 3. Architectural Patterns 7
Page 87 and 88: 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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?