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

More documents

Recommendations

Info

Chapter 4. Service Oriented Architecture 90pattern), design of a single component (typical design pattern) or maybe designof a process (process pattern)(see section 3.1.1). The distinction grows in importancewhen architectural knowledge is taken into consideration. ArchitecturalKnowledge is meant to describe an architecture and rationale behind decisionmade during architecture designing [9]. The decisions do not refer only to rationaleof fine-grained components but also to a “big picture” – system architecture.Architecture requires more detailed studies, due to a large-scale impact on system.This subsection describes SOA architectural patterns in following manner..1. SOA patterns– presents a problem with SOA architectural patterns andpresents results of pattern investigation.2. The target architecture – presents the target architecture that is a result ofcombination of patterns found in section 4.6.14.6.1 SOA patternsThe book “SOA –Design Patterns” [32] is the largest and the most completesource of pattern in SOA domain[54]. Patterns presented in the book belong todesign patterns, but their descriptions question this adherence. The problem risesfrom definition of pattern and design pattern used by T.Erl in this book.According to T.Erl pattern [32]“provides a proven solution to a common problemindividually documented in a consistent format and usually as part of a largercollection” what corresponds to the definition of pattern presented in section 3.1.1.Design pattern is defined as follows [32]: “Patterns in the IT world that revolvearound the design of automated systems are referred to as design patterns.”.Thisdefinition can be also applied to other types of patterns. All the pattern describedin section 3.1.1 “revolve” around design of automated system, not only designpatterns.SOA patterns are described also in“Patterns: Service–Oriented Architectureand Web Services”[30] but they refer to Enterprise Application Integration. Integrationis out scope of this thesis.Selection of architectural patternsThe target architecture will be build on architectural patterns. Usage of the book“SOA –Design Patterns” [32] as a source of architectural patterns requires furtherstudies.Analysis of patterns presented by T. Erl (see [32]) results in division of presentedpattern into four categories. The categories are following
Chapter 4. Service Oriented Architecture 911. Architectural Patterns – describe general solution for a whole architecture ora part of architecture. Those patterns refer to structure and communicationwithin the system.2. Design Patterns – provide solution for a fine-grained problems that has alocal impact on the architecture3. Process patterns – describe patterns for processes that should be applied inorder to gain particular outcome.4. SOA Concepts – describe issues that already are part of Service OrientedArchitecture5. Technical Issues – describe both Design and Architectural patterns whichare build-in exiting frameworks and supported by external technologies.Table 4.1 presents summary of pattern assigned to particular categories.Pattern TypeAmountArchitectural 14Design 28Process 12Technology issue 9SOA concept 10Total 73Table 4.1: Summary of pattern typesExamples of pattern that were not classified as architectural (see table 4.2 forsummary):1. Canonical Expression –assumes up-front analysis in order to standardisenaming conventions, which is later applied to service contracts. A goodexample of Canonical Expression is CRUD.Motivation: Canonical Expression was classified as a Process pattern, becauseit defines a process – analysis.2. Service Encapsulation –defines a service as a containing logic entity. Thelogic can be encapsulated in a new service as well as become a part of anexisting service.Motivation: Encapsulation of logic in a service is a basic concept ofSOA,therefore there is nothing what could be considered as a pattern. SeeService Definition 4.2.1
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: Chapter 3. Architectural Patterns 3
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 99: 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?