Milestone 6
Team Members and Their Roles
![]()
Brad Coverdale: Team Leader, Liaison, Testing
Christopher Dries: Web Designer, JSP programming
Christina Felts: PowerPoint presentation, Testing
Josh Henry: JSP programming
Summarized Results of Milestone
![]()
We made the application more intuitive for the user. We added help menus at the most complicated areas of the application, and added little notes to clarify things, such as teh meaning of the range of scale type questions. We obtained approval from Joel Worrall on behalf of WSEFC. However, this did not come in the form of a formal approval document, since he did not have the time. Joel emailed the professor and the group to explain this, and a transcript of his email is available in the deliverables section under the name Sponsor Organization Approval. We also compiled two CDs that contain the project website and the application, per the syllabus. The application can be viewed at Survey interface. The administration interface can be viewed at Admin interface. The username and password are the same as the one emailed to the professor for Milestone 5.
Strengths of Milestone
![]()
We created user manuals for both the administrator and the normal user. We obtained full approval of the project from the sponsor organization. As for training the sponsor organization, we have provided user manuals that can be referenced, and we will be available for the duration of the summer to answer any questions that Joel Worrall may have, as he will be in charge of training the individual users at WSEFC.
Weaknesses of Milestone
![]()
We struggled over how much protection to provide for editing surveys.
We only allowed a survey to be editable if the survey was un-posted and if the
results had been deleted, even if the only error was a typo in the question.
We emailed Joel to see what he wanted, and he replied, "I think that since
the states change from just edit to posted, the office staff should be smart
enough to pick up the problem." Therefore, we left the editing security
as it was in Milestone 5. A transcript of Joel's reply can be found in the Meeting
Notes in the deliverables section. For our Milestone
6 intentions, we said that we would be adding indexes to the database and generally
improving speed and efficiency. We did not actually add any indexes, because
we did not feel that adding indexes would actually improve the speed.
Effort
![]()
| Christina | Brad | Chris | Josh | Total |
| 15 hrs | 15 hrs | 7 hrs | 5 hrs | 42 hrs |
![]()
Meeting Notes
Screenshots of Application
Administrator
Manual
User Manual
Test Plan
Test Plan
Results
Sponsor Organization
Approval
Completed
Functionality
![]()
Last Updated: 03 May 2004