17.10.2014 Views

Disclaimer - Alliance Digital Repository

Disclaimer - Alliance Digital Repository

Disclaimer - Alliance Digital Repository

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

68<br />

What went right and what went wrong in the project:<br />

Throughout the life of the<br />

project the number of things that went right outnumbered the number of things that went<br />

wrong, however, when things went wrong the solution was not straightforward.<br />

The overall design of the database was fairly simple, with the exception of the job<br />

roles and the business logic by which users can create other users, therefore, it can be said<br />

that things went right in that respect. The database contained numerous tables and<br />

constraints, but having normalized it and having thoroughly thought through its design<br />

before actually scripting it helped to simplify this process.<br />

The coding of the application was in line with expectations also. Throughout the<br />

project it was expected that the majority of the application would use HTML tags,<br />

JavaScript and CSS along with underlying ColdFusion logic embedded in the application<br />

pages. However, trying to put too much of the business logic into the ColdFusion code<br />

rather than into database objects proved to be problematic resulting in an application that,<br />

at times, would run slowly. This issue was addressed by moving some of that logic from<br />

the ColdFusion pages to the backend database, but some of the code had to stay in the<br />

front-end pages. As a result, certain areas of the application still are not performing as<br />

efficiently as possible and could be improved.<br />

Another suboptimal event was that the code was insufficiently modularized to<br />

allow for efficient code reuse. If the code was modularized the application would allow<br />

for easier future additions and modifications. By not modularizing the code nothing is<br />

being taken from the application, however, it is proper development practice to use<br />

reusable code whenever possible.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!