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

More documents

Recommendations

Info

Chapter 4. Service Oriented Architecture 86Figure 4.2: Service Oriented Architecture on three levels of abstraction. Adoptedfrom [46]Despite all the benefits associated with more complex concepts of SOA, itshould be kept in mind that an architect should not introduce additional complexityif the system does not require it. The system should be enough complexto support desired objectives and not more.4.5 SOA VendorsIntroduction of SOA to a company is not an easy task. This difficultly hasbeen noticed by leading software developing companies, what resulted in a numberof supporting frameworks and developer’s suits. The solutions that havebeen proposed differ in scope of support but also in understanding of SOA, what(paradoxically) contributes to companies introducing SOA because SOA is vendorindependent and the diversity allows an architect to create more complex(and cheaper) solutions. List of SOA vendors is relatively long (see [15]) and isstill growing. Some vendors provide sophisticated solutions that allow creatingapplication from concept to detailed plan, while other vendors provide plugginsto IDEs. According to [5][80] IBM is one of the leading vendor in supportingSOA and has the highest market share, therefore, it is worth to outline brieflySOA IBM concept and supporting tools.4.5.1 IBM –Layers of abstractionHowever basic concepts of Service Oriented Architecture like service, ESB or orchestrationare very similar to presented in 4.1, the structure of SOA is slightlydifferent. It is said that: “Any problem in computer science can be solved by
Chapter 4. Service Oriented Architecture 87adding a layer of indirection” and IBM leverages this solution very well. Considerationof a system on different layers of abstraction helps to underline bothbusiness and technical aspects. According to IBM, a system should be consideredon five layers of abstraction during SOA analysis. Starting from the mostabstract enterprise level and ending on very precise object level (see figure 4.3).The layers and their role are following[13]:Enterprise layer – describes an enterprise on business model level. The modelconsists of processes, services (as activities) and enterprise data as well as relationshipbetween those elements.Process layer – Process layer consists of main processes which handle mainbusiness concern by composition and decomposition [83]. Composition createsbusiness services from underlying service layer, whereas decomposition decomposesexiting process into services.Service layer – Service layer contains services that expose technical and businessfunctionality of an application [13]. The services are independent and carryindividual tasks. Those services are also building blocks used by Process Layer.Component layer – On component layer, the system is considered as a set ofphysical components - building blocks of services. This layer is very importantbecause components that exist in more than one place are identified [13]. In resultthose components become potential candidates for becoming services or parts ofa service.Object layer – Object layer is the lowest modelled layer during analysis anddesign activities. However the name refers to objects -instances of classes - thelayer contains description of objects understood as classes characterised by operations,attributes and relationship between them [13].4.5.2 IBM – SOA Foundation SuiteSOA Foundation Suite by IBM is a set of SOA supporting tools. Very importantaspects of IBM solution are modularity which enables usage of only a subsetof all the tools and scalability that simplifies architecture modernization whena company grows [60].The tools support different aspects of SOA like ServiceDesign, Creation, Governance, Integration, Connectivity and Collaboration aswell as Service Security. A short characteristic of the tools supporting differentaspects of SOA is following:
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:
Chapter 3. Architectural Patterns 3
Page 45 and 46: Chapter 3. Architectural Patterns 3
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 95: 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?