ABET Program Certification
HCI 551 Project 2

download Project Documentation (.pdf)

From the evaluation in phase two, it became obvious that the more successful prototype is the Java applet prototype. This prototype visualizes the relational data and the information items, such as Performance Indicators, Program Objectives, Courses, and Students, significantly better than the GWT prototype, by allowing a quick overview through all existing information items and there relation to other information items. Also, the Java applet prototype is simpler for modification tasks, as adding, removing, or modifying information items is done in a central location from within a dedicated tab.

On the other hand, the GWT prototype was perceived as visually more appealing and it can therefore be assumed that this prototype will be more interesting and enjoyable to work with rather than the applet. This prototype has the aesthetics of a designed web site, and can be visually customized in its’ entirety – a quality that the applet approach does not have.

As the final design recommendation, there are essentially two conclusions that can be drawn. First, the applet prototype visualizes the data more successfully by presenting different views of similar data and affording the ability to filter the items that are currently presented. This was the major advantage of the Java applet prototype. Second, the GWT prototype allows for the customization of the interfaces texts, color palette and control element layouts in a richer and simpler way. One approach to combine the advantages of both prototypes would be to implement the visualization strategy of the applet prototype in a GWT version, however with the draw back that certain interface-centric interaction features, like tool-tips, will not be available as there are currently not supported in the GWT technology.

Another recommendation for combining the positive aspects of both prototypes is to implement those security features and interface elements that were perceived as helpful in the GWT prototype into the applet. A login screen and user authentication system was the major draw back of the applet approach and was perceived as the most successful component of the GWT prototype. Hence, implementing such a feature along with more expressive and “verbose” interface components (like status bars and context sensitive help in the form of description boxes) in the applet, by taking the status representation paradigm employed in the GWT approach into account, will make the applet an ideal way of representing the complex information item interaction as described in the earlier section.