Download A Maintainable Database Driven Website for non-IT

8.0
Prototyping
8.1
Implementation of the Prototype
In order for the prototype to work the sections of database first had to be built. To allow for possible
changes in design as a result of user feedback only the required elements of the database were created,
namely the Info table.
The web pages were then written as to the specifications that can be found in the appendix of this
report. It was very important to develop a good prototype as this would be the first “hands on”
experience users received and I believe first impressions always count in a system’s success.
8.2
Prototype Testing and User Involvement
On completion of the prototype a morning was spent with staff at Vancouver Island Holidays. I sat
with users observing what elements of the page they found hard to understand, and discussing
possible improvements. From the meeting the following improvements were agreed on:
•
To reduce confusion between property long descriptions and short descriptions, on the
creation of a new property only a long description will be required, the short description
should be entered via editing the property page.
•
On creating a new page the following text area fields should contain default examples, as user
aids.
•
As users would not be using this system every week a brief training manual should be
produced by myself working closely with a member of staff, ensuring that it was written in a
language that could be understood.
I am glad to say that the prototype received a very warm welcome and all users looked forward to the
system go-live. The meeting not only enhanced the user-friendly-ness of the system but also
eradicated user resistance to the system at go-live.
8.3
Modifications to Design
The modification to the design of the web pages used in the prototype were made and adopted where
possible by other pages of the site administration tool. Full design specification of each page can be
found in appendix B, modifications to the initial design are also noted.
40