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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 38Figure 3.3: Lazy Acquisition design patternRole of particular elements:1. Resource proxy – simulates requested resource by providing an interfacethat is identical with interface of the requested resource. provider.2. Resource provider –provides resource to resource proxy.3. Resource –contains resources that are obtained through the resource proxy.It is possible to make a whole system implemented using this pattern. Theelements of design pattern have to be converted into subsystems. Additionally,an access interface is needed. Resource provider becomes a subsystem responsiblefor providing resources. It is invoked by access interface. This subsysteminvokes Resource Proxy subsystem. Resource Proxy is responsible for convertingobtained resources into proxies. The system also lazy initiates the proxies if it isneeded. Resource subsystem is responsible for providing required resources. Thesubsystem maintains also connections to database and executes other databaserelated operations. The overview of architecture of this system is determined bya design pattern what in this case makes it an architectural pattern because thepattern does not affect only particular subsystem as definition of Design Patternsays. It defines the subsystems and interactions between them (see figure3.4). Application of the design pattern matches to previously stated definition ofArchitectural Pattern.Applying design patters as architectural pattern is not the only problem inpattern distinguishing. How close are those two types of patterns can be seenin literature [34], where Model View Controller (MVC) pattern is described as
Chapter 3. Architectural Patterns 39Figure 3.4: Lazy Acquisition as architectural patterna composed design pattern, while Bushman for instance presents MVC as anarchitectural pattern [22]3.1.3 Sources of Architectural PatternsFilter 1: Selection of Literature SourcesThe idea of Architectural Patterns in Software Engineering is relatively old andpopular thus there are a number of publications about this particular type ofpattern. Unfortunately, there is no standardized set of architectural patterns.Different authors present their own definitions of architectural patterns and proposetheir own categorisation of those patterns. The process of selection of anarchitectural pattern for migration to SOA requires a number of patterns to revisein order to select the most appropriate pattern. Due to a significant numberof publications, it is impossible to identify all Architectural Patterns in SoftwareEngineering. The initial list of patterns has to be created based on a sized downlist of publication. The initial list of patterns bases on three sources:
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 47: Chapter 3. Architectural Patterns 3
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 99 and 100:
Chapter 4. Service Oriented Archite
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?