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

More documents

Recommendations

Info

Chapter 5. Guidelines 124was implemented intentionally or it is just an artificial product of Reverse Engineering.The second criterion is quite obvious having selected pattern for migration inmind.The third criterion rejects projects implemented with frameworks implementedMVC like Zend, JSF, Spring MVC or ASP.NET MVC. This is a serious constraintaking into consideration a number and popularity of those frameworks but therequirement is dictated by the nature of the framework. A framework ”frames” aproject by providing architecture, Application Programming Interface (API) andpreimplemented functionalities. A framework is meant to simplify work by executionof own (preimplemented) code “behind the scene”. The code of applicationusing framework is more transparent than code that does not use frameworks.Complexity of the code using frameworks is also lower because framework providessome core implementation. Unfortunately, it is hard to migrate a projectthat uses a framework because functionality provided by frameworks would haveto be reimplemented. Additionally, even frameworks supporting the same architecturalpattern provide different scope of the support. The guidelines that donot exclude framework would need to be tailored to a particular framework.If more than one projects fulfils the criteria, an additional analysis of availabledocumentation of the projects is carried out. The project with the most detailedand descriptive documentation will be selectedCompletedocumentationBuild uponMVC patternNo frameworksDetailedanalysisFigure 5.14: Overview of the criteria5.3.2 Source of projectsSelection of the system to migrate is not an easy task taking previously statedcriteria into consideration. At the very beginning, open source systems wereconsidered as potential candidates. Unfortunately, found project did not haveany formal documentation- only comments in code (if any) and/or ApplicationProgramming Interface (API). They also did not clearly support any architecturalpattern - lack of documentation. Theoretically, architectural metrics (see [65] formore information) could be used to identify architectural patterns but themetricsdo not prove that the pattern was used intentionally. Additionally, usage oftechnologies like Java Server Faces (supports MVC) also reduce scope of thesearch because those frameworks violate previously stated criteria. Due to all the
Chapter 5. Guidelines 125complications related to open source projects; a new source of candidate systemshas to be chosen.Student’s projects occurred to have more documentation; consequently theyare better choice than open source systems. Analysis of works of students doesnot require assumptions - at least theoretically. Process of design of the systemis documented with motivation behind decisions taken during design time.There are many student projects available but majority of them do not fulfilthe first criteria. The projects do not have documentation except comments incode. This is caused by the aim of the projects. They are dedicated to showhow to apply particular languages or frameworks. Projects developed by studentsfrom last years of studies are more elaborated. They have documentationand good quality of code. Unfortunately (for selection process) most of themare implemented with cooperation of companies. Code of those project cannotbe published or given to people not participating in it due to Non DisclosureAgreements (NDA).There were only twelve projects that were available and could be given forresearch studies.5.3.3 Application of the criteria1. The system must have documentation with models including at least overviewof architecture and flows of business processes. All twelve projects have documentationhaving at least following documents:(a) Vision– describes overview of the system including description of problem,stakeholders, product features and constrains.(b) Software Architecture Document– describes goals and limitations, usecasesview, logical view, view of processes, view of deployment, viewof implementations, view of data.(c) Rules and Limitations– specify business rules and domain constrains.(d) Glossary – glossary used in system.(e) Usecases– detailed description of usecases.Beginning number of projects:12Result number of projects:122. The system must implement MVC architectural patternArchitectural pattern applied in system is present in seven projects.Architectural pattern applied in system is present in seven projects. Five ofthem do not mention any architectural pattern. Only systems based uponMVC are further take into consideration. The patterns mentioned in thedescriptions are:
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: Chapter 3. Architectural Patterns 7
Page 85 and 86: 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: Chapter 5. Guidelines 123FrontendFr
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?