Migration of a Chosen Architectural Pattern to Service Oriented ...
Migration of a Chosen Architectural Pattern to Service Oriented ... Migration of a Chosen Architectural Pattern to Service Oriented ...
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 43 and 44: Chapter 3. Architectural Patterns 3
- Page 45 and 46: Chapter 3. Architectural Patterns 3
- Page 47: Chapter 3. Architectural Patterns 3
- Page 51 and 52: Chapter 3. Architectural Patterns 4
- Page 53 and 54: Chapter 3. Architectural Patterns 4
- Page 55 and 56: Chapter 3. Architectural Patterns 4
- Page 57 and 58: Chapter 3. Architectural Patterns 4
- Page 59 and 60: Chapter 3. Architectural Patterns 4
- Page 61 and 62: Chapter 3. Architectural Patterns 5
- Page 63 and 64: Chapter 3. Architectural Patterns 5
- Page 65 and 66: Chapter 3. Architectural Patterns 5
- Page 67 and 68: Chapter 3. Architectural Patterns 5
- Page 69 and 70: Chapter 3. Architectural Patterns 5
- Page 71 and 72: Chapter 3. Architectural Patterns 6
- Page 73 and 74: Chapter 3. Architectural Patterns 6
- Page 75 and 76: Chapter 3. Architectural Patterns 6
- Page 77 and 78: Chapter 3. Architectural Patterns 6
- Page 79 and 80: Chapter 3. Architectural Patterns 6
- Page 81 and 82: Chapter 3. Architectural Patterns 7
- Page 83 and 84: Chapter 3. Architectural Patterns 7
- Page 85 and 86: Chapter 4. Service Oriented Archite
- Page 87 and 88: Chapter 4. Service Oriented Archite
- Page 89 and 90: Chapter 4. Service Oriented Archite
- Page 91 and 92: Chapter 4. Service Oriented Archite
- Page 93 and 94: Chapter 4. Service Oriented Archite
- Page 95 and 96: Chapter 4. Service Oriented Archite
- Page 97 and 98: Chapter 4. Service Oriented Archite
Chapter 3. <strong>Architectural</strong> <strong>Pattern</strong>s 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 <strong>of</strong> <strong>Architectural</strong> <strong>Pattern</strong>sFilter 1: Selection <strong>of</strong> Literature SourcesThe idea <strong>of</strong> <strong>Architectural</strong> <strong>Pattern</strong>s in S<strong>of</strong>tware Engineering is relatively old andpopular thus there are a number <strong>of</strong> publications about this particular type <strong>of</strong>pattern. Unfortunately, there is no standardized set <strong>of</strong> architectural patterns.Different authors present their own definitions <strong>of</strong> architectural patterns and proposetheir own categorisation <strong>of</strong> those patterns. The process <strong>of</strong> selection <strong>of</strong> anarchitectural pattern for migration <strong>to</strong> SOA requires a number <strong>of</strong> patterns <strong>to</strong> revisein order <strong>to</strong> select the most appropriate pattern. Due <strong>to</strong> a significant number<strong>of</strong> publications, it is impossible <strong>to</strong> identify all <strong>Architectural</strong> <strong>Pattern</strong>s in S<strong>of</strong>twareEngineering. The initial list <strong>of</strong> patterns has <strong>to</strong> be created based on a sized downlist <strong>of</strong> publication. The initial list <strong>of</strong> patterns bases on three sources:
Change language