Migration of a Chosen Architectural Pattern to Service Oriented ...
Migration of a Chosen Architectural Pattern to Service Oriented ... Migration of a Chosen Architectural Pattern to Service Oriented ...
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 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: Chapter 4. Service Oriented Archite
- Page 93 and 94: Chapter 4. Service Oriented Archite
- Page 95 and 96: Chapter 4. Service Oriented Archite
- Page 97 and 98: Chapter 4. Service Oriented Archite
- Page 99 and 100: Chapter 4. Service Oriented Archite
- Page 101 and 102: Chapter 4. Service Oriented Archite
- Page 103 and 104: Chapter 4. Service Oriented Archite
- Page 105 and 106: Chapter 4. Service Oriented Archite
- Page 107 and 108: Chapter 4. Service Oriented Archite
- 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: 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
Chapter 5. Guidelines 127Concluding, the authors <strong>of</strong> 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 <strong>of</strong> projects:2Result number <strong>of</strong> projects:15.3.4 Description <strong>of</strong> the selected projectThe selected student’s project is meant <strong>to</strong> support maintenance <strong>of</strong> IT assets.Name <strong>of</strong> the system is “TRWAM”. The system is a desk<strong>to</strong>p 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 <strong>to</strong> the vision, the system is developed in order <strong>to</strong> replace an existingsystem. The new system has <strong>to</strong> have the same functionality as the old, has <strong>to</strong>preserve standards <strong>of</strong> data persistence and enable printing <strong>of</strong> reports. The systemsupports following main activities:1. Maintenance <strong>of</strong> database <strong>of</strong> assetsThe system must provide functionality <strong>of</strong> creating, reading, updating anddeleting information about assets. The asset related information includesfor instance name <strong>of</strong> the asset and provider <strong>of</strong> the asset. Search functionalityis also required.2. Support in maintenance <strong>of</strong> assetsThe system must provide functionality <strong>of</strong> generation <strong>of</strong> documents basedon content <strong>of</strong> database and applied criteria. The documents are associatedwith for instance process <strong>of</strong> lending (lending form) and removing (pro<strong>to</strong>col<strong>of</strong> removal) <strong>of</strong> assets.3. Au<strong>to</strong>mation <strong>of</strong> activities associated with maintenance <strong>of</strong> assetsThis functionality includes au<strong>to</strong>mation <strong>of</strong> calculations <strong>of</strong> fees, fines andamortizations. The system should also inform about violation <strong>of</strong> rule andother incorrectnesses.4. Creation <strong>of</strong> reports and listingsIt includes creation <strong>of</strong> reports and listing based on actual state <strong>of</strong> database.
Change language