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

More documents

Recommendations

Info

Chapter 3. Architectural Patterns 44Layer – A layer encapsulates common logic on the same level of abstraction.Each layer provides an interface allowing another layer to cal its functionality.Relationships – A layer can use other layer only if they are connected.There are uni and bi directional relations between layers. This pattern ischaracterized by lack of direct calls of layers to non-neighbor layers. If thelayer number one wants to call the method from the layer number threeand there is no direct connection between them, the layer number one hasto call the layer number two in order to call the layer number three. Alayer can invoke only a layer that is bellow or above this layer. Connectionlimited to only upper and lower layer increases maintainability but reducesperformance (see figure 3.6).Layer 1Layer 2Layer 3Figure 3.6: Example usage of Layer pattern2. Pipe and filtersOverview – The pattern is characterized by a good and efficient way ofdata processing but the structure of the pattern reduces its reliability becauseif one of the filters fails, the whole process fails as well.ElementsFilter – processes data. A filter can push data to a pipe or pull it out froma pipe.
Chapter 3. Architectural Patterns 45Pipe – forwards processed data to next filter.Relationships – Each pipe connects two filters and each filter has to beconnected to at least one pipe. There is no possibility to connect a pipe toa pipe or a filter to a filter directly. Additionally, pipes offer only unidirectionalconnections (see figure 3.7)Filter 1PipeFilter 4PipeFilter 3PipeFilter 2PipeFigure 3.7: Example usage of Pipes and Filters pattern3. BlackboardOverview – the pattern is very useful when no deterministic solution isknown. The pattern improves solution-finding process that bases on smalldeterministic solutions.ElementsBlackboard – contains all currently gained knowledge or solutions. Theblackboard serves also as a place for future solutions / knowledgeKnowledge source – provides more advanced or more complete solutionbased on own data and blackboard’s information.Moderator – moderates knowledge improvement. The element determinesthe order in which every source of knowledge has to access the blackboard.Relationships – Moderator is in relationship with Knowledge Source andBlackboard. Knowledge Source can operate only on Blackboard. Blackboarddoes not invoke other elements of the pattern (see figure 3.8).
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 53: Chapter 3. Architectural Patterns 4
Page 85 and 86: Chapter 4. Service Oriented Archite
Page 105 and 106:
Chapter 4. Service Oriented Archite
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?