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

More documents

Recommendations

Info

Chapter 4. Service Oriented Architecture 824.3.2 ActivitiesActivities are building blocks of methodologies [13].Each activity derives from amethod principle, constrains or good practices applied in this particular approach.This section discusses a set of common activities required to create Service OrientedArchitecture [13]. The activities are presented in sequence so the firstdescription matches the first activity that should be executed and so on.Service Identification – The goal is to identify services by using supportingtechniques like Input Analysis, Top–down Analysis, Bottom -up Synthesis orTaxonomy Building. However all those techniques can be used separately andguarantee useful output, the best result is achieved by mixing the approaches.This step creates a baseline for further analysis and modelling. The supportingtechniques can be defined as follows:1. Input Analysis [13] requires documentation or business models of the systems,therefore it is applicable to legacy system analysis. According to [13],Input Analysis may be driven answers to following questions:(a) Are the business drivers and goals for the SOA project articulated andquantifiable in terms of key business performance indicators?(b) Have the business processes to be realized been named and described ata level of detail that is sufficient for architectural decision–making atthe IT level?(c) Have the existing and future non–functional requirements been documentedwith any unresolved pain points?2. Top–identifies high-level business concerns in order to capture and modelrequirements [13]. There is no “best solution” for this type of analysis,however it can be implemented using even very basic elicitation techniqueslike interview. The main benefit of this technique is that it does not gointo details on object level. Object level analysis may lead to impossible tomanage “net” of classes and their relationship.3. Taxonomy Building uses semantic of word used within the company takinginto consideration both technical and business aspects[13].As the result, adictionary is elaborated. The dictionary describes all the processes and dependenciesbetween them and this is a good starting point for service identification.Creation of services depends on terms in the elaborated dictionaryand relations between those terms. The most frequent used words identifyentities, rules, processes or others elements of the system that shouldbe encapsulated in a service. Successful realization of taxonomy buildingestablishes also unified vocabulary that improves communication betweenteams.
Chapter 4. Service Oriented Architecture 834. Bottom –Up Synthesis During this type of service identification, the systemis decomposed into single processes and components. Decomposition has tobe performed with potential reuse of components in mind. The next step issynthesis that is executed after the system is broken down. As the result ofsynthesis, new services are created by analysis of processes and previouslyseparated components. This technique is applicable for existing systems.The best result is gained when both Top –Down and Bottom –Up approaches arecombined together [13].Service Categorisation – assigns previously identified services to predefinedcategories. According to [13] services can be assigned to following categories:1. role in business model: process, business function, business rule validation,application utility, infrastructure2. type of consumer: customer, partner internal service3. implementation strategy: external, composed, adaptedCategorisation helps to better understand and describe identified services. Understandingof properties of those services is essential during next steps.Service Specification – defines technical interface of a service by specificationof its contract. The contract shall contain information about a set of operationsand their parameters, preconditions, postconditions and invocation syntax of theoperation [13] This syntax describes types and structure of exchanged information.The contract has to keep high cohesion (see 4.3.1 for more informationabout cohesion).Service Orchestration – Service Orchestration is an activity connecting technologyand business. Service Orchestration creates meaningful processes fromservices. This is a key activity that decides whether the system will success[82].The value of Services Orchestration does not derive only from the value ofits concept but also from the way of process performance. Orchestrationbringsa significant value for the organisation and it is does not require deep technicalknowledge because it is all about modelling [82] without any single line of code.However Orchestration is widely known, it is often confused with choreography.Choreography is very similar but it operates on different level of abstraction. Orchestrationin opposite to choreography is meant to create executable and internalprocesses which communicate with both internal and external services [66], whilechoreography defines how multiple parties of a system exchange messages [59]. Inother words, choreography specifies orchestration in a global model [12].
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 85 and 86: Chapter 4. Service Oriented Archite
Page 91: 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?