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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 42source. Those patterns are not taken into consideration during next steps. Thetable contains also Publisher-Subscriber. Publisher–Subscriber is also rejectedbecause it is a known design pattern [22][34] while the table should contain onlyarchitectural patterns. This exception is important because it confirms previouslyaddressed problem that says that it can be very hard to distinguish both architecturaland design patterns from each other. Moreover, authors of the secondsource claim that all architectural patterns were checked before in terms of theiradherence to domain of architectural patterns. This finding means that othersources may also present a design pattern as an architectural pattern.3.2 CategorisationIn the previous section, nineteen architectural patterns out of thirty two werechosen. Analysis of feasibility of migration of this number of architectural patternswould require a lot of effort, consequently, the number of pattern will bereduced during the next selection. The selection is based on categorisation ofpatterns. The patterns are grouped and the most general pattern is chosen as arepresentative. This approach reduces considerably amount of patterns to analyse.The most general means that a pattern can be compared to other patternsbecause they have similar structure and purpose. Additionally, its structure isthe simplest. The representatives of each category reconsidered in next sections.This section presents process of selection of representatives of categories. Thesection is organized in following manner:1. Description of selected Architectural Patterns – the subsection provides descriptionsof patterns selected in the previous section. Each description hasfour elements: overview, elements and relationships between elements. Additionallya picture presenting an example usage of a pattern is provided.Since P. Avgerious in opposite to authors of other sources does not providedescriptions of patterns in his work, the descriptions and pictures base onremaining two sources of patterns.2. Methods of patterns categorisation – this subsection presents shortly identifiedways of pattern categorisation. Since creation of own categorisationmethod is not in scope of the work, one of presented approach is chosen.3. Allocation of pattern to categories – the purpose of this subsection is to allocatepatterns described in the first subsection to categories of categorisationmethod selected in the second subsection.4. Selection of representatives – this section provides comparison of patternswithin categories. As the result of comparison, representatives of categoriesare selected. The pattern for migration will be selected from those representatives.
Chapter 3. Architectural Patterns 433.2.1 Description of selected Architectural PatternsThis section presents descriptions of previously selected architectural patterns.The description includes short overview of the pattern, elements of the pattern,relationship between the elements and a picture presenting an example usage ofthe pattern. Figure 3.5 presents notation used in figures presented example usageof architectural patterns.Layer’s name1) 2) 3) 4)Element’s nameFigure 3.5: Notation used in example application of patternsDescription of the notation1. Unidirectional relationship– the relationship is represented by a dashed linewith an arrow on one end. An arrow on the top of the line points directionof the relationship. An element having end of line without an arrow canstart interaction with the element pointed by the arrow.2. Bidirectional relationship– the relationship is represented by a dashed linewith arrows on both ends. In this case, elements on both sides of line canstart an interaction.3. Layer– it is represented by a dash-lined rectangle. This is a grouping elementhaving abstract meaning depending on description of the pattern. Itcan be linked using both types of relationships. It can contain other layersand elements. A layer is identified by a name.4. Element– it is represented by a solid lined rectangle. An element has aspecific meaning dependent on particular pattern. An element is identifiedby a name.Architectural Patterns The architectural patterns are listed in the order theyappear in the table 3.1. Their description is following: tab:PatternSummary1. LayersOverview – This pattern imposes encapsulation of the similar functionalitiesin containing layers what helps to separate low-level functionalitiesfrom high level.Elements
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 51: Chapter 3. Architectural Patterns 4
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 103 and 104:
Chapter 4. Service Oriented Archite
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
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?