CSC 402 Milestone 6
CSC 402 Milestone 6
Revised 28 October
Due:
In-Class Presentations: 2pm Friday 28 October
Other Deliverables: 11:59pm Friday 28 October
Overview
The team-specific tasks for Milestone 6 are a continuation of those begin in
Milestone 5, with necessary appropriate adjustments to be determined. The
tasks are the following:
-
Requirements Team:
-
Evaluation of client feedback posted on the forum. This will be limited
in quanity for Milestone 6, due to late release of Phase 1. Therefore this
task needs to be finished for Milestone 7.
-
First draft of slides with new features and updated features, based on the the
feature prioritization work of milestone 5, and the forum feedback evaluation
of the previous task, including these features alternatives:
-
tabular and dialog-based editing; as of 26oct11, there is a pending question as
to whether dialog-based editing will be supported in Phase 2
-
four to five different forms of schedule viewing
-
one-click feedback link to topic-specific thread of the forum
-
Presentation of new slides to class on Friday 28 October.
-
Prototyping Team:
-
Client-deployable prototype, demonstrated and deployed to class on Friday 28
October.
-
If possible with GWT, implementation of these table edit features:
-
one-click column sorting
-
click-and-drag column positioning
-
click-and-drag column resizing
-
checkbox dialog for column show/hide
-
Infrastructure Team:
-
Marketing Group: Decision made on product identity and logo. Present
draft of ideas on decisions to class on Friday 28 October.
-
Usability Group: Draft of plan for usability testing of these
features:
-
The four to five different forms of schedule viewing described in the Milestone
5 writeup.
-
Two different forms of database editing: in-place tabular, separate dialog.
Again, existence dialog editing feature in Phase 2 is TBD.
Task 1a: Evaluation of Forum Feedback
As of 26oct11, the Phase 1 release will have happened. The client feed back
will be posted on forum of the PolyLearn class named "Scheduler". This
feedback needs to be processed using the same methodology that was used for
the original intervies. Specifically, the feedback is analyed to determine
client-requested features, and to integrate these features into the existing
feature prioritization matrix.