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

More documents

Recommendations

Info

Chapter 2. Related Work 28Figure 2.3: Relation between PCBMER and PCBMER–U, adopted (figure 3) from[52], potentially inconsistent dependencies are marked in red2.2.3 Peer–to–PeerAvailable literature provides also an example of mixture of both Service Orientedand non–SOA patterns. The approach proposes a union of services andPeer–to–Peer infrastructure. The infrastructure is build upon Gradient Topologyand Distributed Hash Table. Gradient Topology supports efficient Peer discoverability[29],Distributed Hash Table (DHD) provides efficient routing algorithmthat enables consumption of services [69] and can be successfully employed as amean of service discoverability and registration [50]. The infrastructure has alsoone more important element of the Peer–to–Peer pattern, namely a set of serversused as start up points for other peers (see 14 for more P2P related information).Gradient Topology supports also service registration through decentralized ServiceRegistry [69].In order to register, a service (peer) has to discover an instanceof service registry via gradient topology. Then the service registers itself and uploadsown proxy via DHT. After this sequence of steps a service can be discoveredby other services.
Chapter 2. Related Work 292.3 SummaryThis chapter presents briefly main Service Oriented Migration approaches. Thefirst three techniques are the most mature and have the more detailed documentation.SMART (White–Box) technique analyses the code in details. Wrapping(Black–Box) wraps the legacy system into services and does not integrate intocode of the migrated legacy system. Taxonomy Analysis (Grey–Box) analysis thecode of the migrated system. As the result of analysis a dendogram is created.The diagram is further converted into sub–threes that are implemented as services.Remaining three approaches differ in scope of migration. ADM migrateswhole systems by migrating their infrastructure, architecture and business layer.In turn PCBMER is migrated to SOA using additional layers. The last techniqueapplies architectural pattern on more abstract level. The whole communicationwithin system is organised as a Peer–to–Peer network. Study of architecturalpatterns becomes a part of standard. Migration of the system will base uponwhite or black or grey technique.
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: Chapter 2. Related Work 274. Mediat
Page 41 and 42: Chapter 3. Architectural Patterns 3
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:
Page 93 and 94:
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?