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

More documents

Recommendations

Info

Chapter 5GuidelinesThis chapter presents elaborated guidelines in order of their application. Theguidelines apply white-box approach (see section 2.1.1 for example white boxapproach). The presented white-box approach defines process which requirescontext identification, service identification and identification of the target architecture.While the target architecture is already identified (see figure 4.4). Thecontext analysis and service identification is possible because the documentationand source code is available. Each guideline is meant to introduce one SOA architecturalpattern into target architecture. The chapter is organized into followingsections:1. Pattern Languages– the section presents motivation behind chose of patternlanguages as a mean of transformation between two architectural. Additionally,the section describes migrated and the target architectures are patternlanguages.2. Guidelines– Guidelines for migration are meant to simplify migration toSOA. The guidelines are implementation of translation between migratedand target pattern language. Order of application of each guideline reflectthe description section of the target pattern language. Each guidelines introducesone SOA pattern (see section 4.6.1 for full list of identified SOApatterns) into architecture. The target architecture (see figure 4.4 for targetarchitecture) is a result of application of all the guidelines. This sectionpresents how guidelines were created and what determines order of theirapplication. Guidelines are described by “How to” section and figure presentingstate before application of the guideline and after the application.3. Project for migration – the section presents briefly a project selected foran example migration along with selection criteria and their application.Migration of the project illustrates how to apply the guidelines.4. Application of the guidelines– the section presents an example applicationof guidelines and technical issues that were identified during migration.5. Discussion– the section presents a discussion about guidelines and the targetarchitecture that is created as result of their application.102
Chapter 5. Guidelines 1035.1 Pattern LanguagesPrevious chapters provide two architectures. First that is the migrated architectureprovided by MVC architectural pattern. The second is the target architecturethat is a result of application of several SOA architectural patterns. The targetarchitecture is in fact a pattern language because [37]:Pattern languages are collections of patterns that can be used to build somethinglarger than any individual pattern can be used to build.Since the target architecture may be expressed as a pattern language, it isworth to use this fact and convert transformation between two architectures intotranslation between two pattern languages.This section presents the MVC architectural pattern and the target architecturedescribed as pattern languages. The description follows template of descriptionof pattern language presented in section 3.3.15.1.1 MVC Pattern LanguageThis section presents MVC architectural pattern (see 3.2.1 for description ) as apattern language.AbstractThis pattern language is dedicated for application interacting with users. Thepattern language simplifies interaction through clear separation of GUI from logicof the system. Application of the pattern language supports maintenance anddevelopment of multiple user interfaces.MapThis pattern language is one element pattern language only. The map of thispattern language is the map of only one node without arcs. The structure of thepattern is presented in figure 3.10DescriptionThe pattern language is one element only. The order of application is reduced tothe only one step.PatternsName Model View Controller
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:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62: Chapter 3. Architectural Patterns 5
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 111: Chapter 4. Service Oriented Archite
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?