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

More documents

Recommendations

Info

Chapter 5. Guidelines 126(a) Pipe-and-FiltersFound amount: 1This pattern is used in system processing images.(b) LayersFound amount: 2Used in desktop applications.(c) MVCFound amount: 5Used in desktop and web applications.Beginning number of projects:12Result number of projects:53. The system cannot be build using frameworks supporting MVCThree out of five systems were web applications. Those applications werebuild using web frameworks for JAVA. Found frameworks are following:(a) Spring 1.0 MVC –this framework was applied in two systems.(b) JSF 1.0 –applied in one system.Beginning number of projects:5Result number of projects:2Application of the criteria results in two potential systems for migration. A moredetailed analysis is needed in order to choose the system for migration. Both ofthem are written in Java and have documentation. They are also using MVCarchitectural pattern.Analysis of documentation of one of the project questions usage of MVCpattern in the project because:1. Document describing “Project of the architecture” in point three says that:“Doimplementacji aplikacji klienta przyj ↩eta zostanie architektura MVC (ModelView Controller).” MVC architecture is used to implement client application.2. The “Project of the architecture” document shows that system is composedof database server and client3. Document describing “Design of classes” presents following figure describedas “Architecture of the system”:
Chapter 5. Guidelines 127Concluding, the authors of the system claims that the system is build using MVCpattern but the diagram presenting architecture is Layers, not MVC. Even the figurecontains names like Layer. The diagram contains Top Layer and MiddlewareLayer. The architecture contains no Model, View or Controller names.Consequently, this project cannot be taken as an example project for migration..Beginning number of projects:2Result number of projects:15.3.4 Description of the selected projectThe selected student’s project is meant to support maintenance of IT assets.Name of the system is “TRWAM”. The system is a desktop application written inJava with SWING user interface. The system performs create, read, update anddelete operations (CRUD). The description below presents roughly the system.The information derives from available documentation.VisionAccording to the vision, the system is developed in order to replace an existingsystem. The new system has to have the same functionality as the old, has topreserve standards of data persistence and enable printing of reports. The systemsupports following main activities:1. Maintenance of database of assetsThe system must provide functionality of creating, reading, updating anddeleting information about assets. The asset related information includesfor instance name of the asset and provider of the asset. Search functionalityis also required.2. Support in maintenance of assetsThe system must provide functionality of generation of documents basedon content of database and applied criteria. The documents are associatedwith for instance process of lending (lending form) and removing (protocolof removal) of assets.3. Automation of activities associated with maintenance of assetsThis functionality includes automation of calculations of fees, fines andamortizations. The system should also inform about violation of rule andother incorrectnesses.4. Creation of reports and listingsIt includes creation of reports and listing based on actual state of database.
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 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: Chapter 5. Guidelines 125complicati
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?