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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 58Client Implicit Mechnism ServerFigure 3.24: Example usage of Implicit Invocation pattern3.2.2 Methods of patterns categorisationLiterature presents several different methods of pattern categorisations [8][38]which are meant to underline specific aspects of patterns like their structure,properties or applications. The reason why particular aspects are underlinedmay also vary in addition, may include for instance justification for architectureselection e.g. highly adaptive architectures adaptation. Source literature forarchitectural pattern section provides several different ways of pattern categorisation.Buschmann [21] presents following approaches:1. Domain –This categorisation groups all patterns that are often used in aspecific domain. An example domain can be for instance: scientific application.Most of those scientific applications need a lot of disc space toshare common data and a high performance algorithm to do calculations.In many cases, algorithms are distributed over many computers that haveto work together. This set of requirements and constrains can impose a setof most adequate patterns.2. Partition –Groups all the patterns that present a system as a stack of tiers.For instance, there can be a business tier and an integration tier. Integrationtier contains all patterns that enable easy integration and adaptation.Business tier groups patterns that improve maintainability and extendability.3. Intent –This category groups patterns in very narrow and high–specializedgroups. Each group consists of patterns that solve the same problem or helpto reduce it. For instance Intent may enclose a group of patterns that solvea problem of system distribution or a group that collects only patterns thatenables easy exchange of data.Presented categorisations of patterns start from very general idea of a domainand go deeper through grouping of pattern having structure presented as a stackof tiers. Finally, patterns having the same application are put together.The second source [38] provides only one categorisation, namely categorisationby domain of application. This approach is in fact a clarification of the domain
Chapter 3. Architectural Patterns 59category presented by F. Bushamnn. Author distinguishes seven main domainsand allocates patterns to each of them. If allocation fails then pattern is treatedas ’Other’. The domains are following:1. Embedded Systems –Systems dedicated for special machines. The machinesmay have also a dedicated hardware what may set additional limitations.2. Dataflow and Production –This category enclose systems designed for processmonitoring and logistic.3. Information and Enterprise Systems –Enterprise systems that have to manageand present data.4. Web–based Systems –This category includes all the systems that are designedfor web interaction.5. Case and Related Developer Tools –This category contains all the applicationsthat help developers.6. Games –The category contains patterns applied in computer games.7. Scientific Approaches –Include all the patterns that do support calculationsfor scientific purpose.However the descriptions are not to detailed, the names of domains explain littlebit more. An interesting fact is that there is no category that in opposite to“Others” could group solutions that do not match to only one category. Thosepatterns could be assigned to category “MIXED”. The categorisation by domainsassumes that each pattern can belong to only one domain. An example of mixbetween domains can be a mix of Web based and Enterprise system because suchsystems are not unusual.The last literature source presents different perception of pattern categorisation.Author presents categorisation by View, which in fact is a mixture ofconcept of Intent presented by F.Bushman[21] and an approach based on structureof patterns. P. Avgeriou and U. Zdun distinguish following categories [8]:1. Layered View – In this approach architecture is presented as a complexentity that can be decomposed into interacting parts. A special emphasisis laid on description of particular parts and their mutual interaction.The view also requires strong decoupling of parts of pattern and takes intoaccount attributes of the pattern like scalability and modifiability.2. Data Flow View – The next view gathers data flow related patterns. Thepatterns are composed from elements performing transformations, carryingdata streams and connections between them. Essential attributes aremodifiability and integrity.
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 67: Chapter 3. Architectural Patterns 5
Page 85 and 86: 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?