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

More documents

Recommendations

Info

Chapter 6. Conclusion 150RQ.8 What are the drawback and advantages of the new technique ?Information about advantages and drawbacks is presented in section 5.5.3.The most important advantage is that the guidelines consider architectural patternsapplied in migrated architecture. The most significant drawback is limitationof application. The guidelines are applicable only for systems that do notuse functions provided by MVC supporting frameworks.The elaborated guidelines are implementation of White–Box technique. Themost important advantage of the guidelines is solution for the drawback that thatexist in identified White–Box, Grey–Box and Black–Box techniques, namely “Thetechnique does not consider architectural patterns that are applied in architectureof migrated systems”.6.3 Future worksThe example system that was used for illustrating application of the guidelineswas small. This was caused by problem of availability of candidate projects. Theelaborated guidelines should be applied for migration of other systems in orderto validate them and propose improvements.The elaborated guidelines provide a migration technique only for MVC architecturalpattern, but the target architecture can be classified as Process–EnabledSOA (see 5.5.2). This architecture could also be applicable for other migrations.Future researches could modify the guidelines in order to adjust them other architecturalpatterns. At the beginning for other patterns belonging to the samecategory as MVC (see table 3.3 for categories and patterns).Finally, elaborated technique of migration is a list of subsequent steps thatintroduce additional elements into architecture. The technique is systematic andit known how the architecture changes after each guideline. This property can beused in future in order to implement a framework supporting the migration.6.4 SummaryThe contribution the thesis is the list of guidelines that are applicable for migrationof systems based on MVC architectural pattern toward Service OrientedArchitecture. The target architecture and the migrated architecture are based onarchitectural pattern. Pattern encapsulate proven solutions, thus they increasequality of architecture. Additionally, the target architecture, the next outcomeof the thesis is expressed as a pattern language that can be used to describe alsoother target systems.
References[1] http://www.soa-manifesto.org/.[2] Stefan Link Fabian Jakobs Ludwig Neer Sebastian Abeck. Architecture ofand migration to soas presentation layer. Technical report, Cooperation andManagement, Universitt Karlsruhe (TH), 76128 Karlsruhe 2 CAS GmbH,76131 Karlsruhe, 2006.[3] Mohammed A. Aboulsamh. Towards a model-driven approach for planninga standard-based migration of enterprise applications to soa. In SERVICES’09: Proceedings of the 2009 Congress on Services - I, pages 471–474, Washington,DC, USA, 2009. IEEE Computer Society.[4] Mark S. Aldenderfer and Roger K. Blashfield. Cluster Analysis. Sage UniversityPaper Series on Quantitative Applications in the Social Sciences. SagePublications Inc., Beverly Hills, 1984.[5] Firstservis Pty Ltd. Alexander Roussekov, Senior SOA Architect. Evaluationof soa vendors a technical white paper from firstservis. Technical WhitePaper.[6] Lianjun An and Jun-Jang Jeng. Business-driven soa solution development. Ine-Business Engineering, 2007. ICEBE 2007. IEEE International Conferenceon, pages 439 –444, 24-26 2007.[7] Francesca Arcelli, Christian Tosi, and Marco Zanoni. Can design patterndetection be useful for legacy systemmigration towards soa? In SDSOA ’08:Proceedings of the 2nd international workshop on Systems development inSOA environments, pages 63–68, New York, NY, USA, 2008. ACM.[8] P. Avgeriou and U. Zdun. Architectural patterns revisited - a pattern language.In Proceedings of the 10th European Conference on Pattern Languagesof Programs (EuroPLoP 2005), Irsee, Germany, July 2005.[9] Paris Avgeriou, Patricia Lago, and Philippe Kruchten. Towards using architecturalknowledge. SIGSOFT Softw. Eng. Notes, 34(2):27–30, 2009.151
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:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Chapter 4. Service Oriented Archite
Page 87 and 88:
Page 89 and 90:
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: Chapter 4. Service Oriented Archite
Page 111 and 112: Chapter 4. Service Oriented Archite
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: Chapter 6. Conclusion 149RQ.6 How t
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?