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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 32(c) A pattern cannot be recommended as not suitable for migration toSOA(d) A pattern cannot be already a part of SOAInput: Representatives of categories without the less mutually interactingarchitectural patterns.Output:Architectural patterns that are feasible for migration to SOA.8. Final SelectionThis is the last filter. The filter selects a pattern that will be further migratedto SOA. The selection bases on literature gathered during prefeasibilitystudy.Input: Architectural patterns feasible for migration to SOAOutput: Architectural pattern that will be migrated to SOABeside the main flow of the filters, the chapter presents some backgroundinformation. The information helps to understand steps of the procedure andmotivation behind them.This chapter is organized in following manner:1. Patterns – presents basic information about patterns including descriptionof types of patterns in Software Engineering. This section addresses also theproblem of distinguishment of architectural patterns from design patterns.The section provides an initial list of patterns that bases on three sources:a series of books and two articles. Finally, the list of patterns is reduced byremoving the patterns that appear in only one source. This list is furthercategorised in the next section.Covers filters: Selection of literature sources, Extraction of architecturalpatterns from the literature sources, Removal of patterns that exist in onlyone source.2. Categorisation – the first section provides nineteen patterns. This amountis too large to choose from, thus it still has to be downsized. This sectiondescribes patterns from the last section by providing their overview, descriptionof elements, description of relationships between elements and apicture presenting example application of the pattern. Afterwards, severalexisting ways of pattern categorisation are presented. One of the methodsis selected and previously selected patterns are assigned to categories accordingto the selected method. Finally, the patterns inside each categoryare compared to each other and representatives of the categories are chosen.The representatives are further reconsidered.Covers filters: Assignment of architectural patterns to selected category,Selection of representatives for categories.
Chapter 3. Architectural Patterns 333. Mutual Interaction – this section describes pattern language and its roleduring system design. Next, result of study of forty-seven real documentationsof systems is presented. The results of the study present frequencyof usage of particular patterns and common pairs of patterns. Finally, thelist of representatives of the categories is confronted with results presentingoccurrences of pairs of patterns.Covers filters: Removal of rarely interacting patterns.4. Pattern selection – this section presents selection of the pattern for migration.The selection requires a research helping to determinate which patternis the most feasible to migrate. The assumption is that a pattern is feasibleto migrate if there are any works describing attempts of migration ofthe pattern in context of SOA. The more works and the more elaboratedthey are, the higher feasibility is. Additionally, if the pattern occurs to bemigrated to SOA or the pattern is already a part of SOA then this patternwill be discarded because the solution already exists. Finally, a detaileddescription of the selected architectural pattern is presented.Covers filters: Prefeasibility study, Final selection.5. Summary – a summary of the chapter3.1 PatternsSoftware Engineering is a domain that covers practical as well as theoretical aspectsof software development. Software Engineering is also a term that appearedfor the first time during NATO conference in 1969 year [57]. Since then, the domainevolved and adapted new engineering solutions. One of such adapted solutionis the concept of patterns. This section is meant to provide basic informationabout patterns in Software Engineering emphasising Architectural Patterns. Thesection provides also a list of Architectural Patterns. This section is broken intofollowing subsections:1. Patterns in Software Engineering– presents the origin of Patterns in SoftwareEngineering and describes groups of those patterns.2. Definition of Architectural Patterns– presents definition of architecturalpatterns.3. Sources of Architectural Patterns– presents sources of Architectural Patternsused during selection of pattern for migration.
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: Chapter 3. Architectural Patterns 3
Page 45 and 46: Chapter 3. Architectural Patterns 3
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 93 and 94:
Chapter 4. Service Oriented Archite
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?