Make a list of all of the things that your system must be able to do. These are
not UI designs.
There should be no pictures. A feature is a
particular action that a user might take, not properties of the design. These
are features like:
- Add a student to the class
- Delete a student from the class
- Create a new course
- Remove a course
- Add an assignment to a course
- Edit the description of a course
- Set the grading scale for an assignment
- Accept the upload of a student's assignment
- Let instructor download student's assignment
- Enter a grade for a student for a particular assignment
- Enter a text note to justify the grade
- Student views their grades
- Instructor views a summary of all grades for a particular assignment
- Student can post a question about a particular assignment
- etc.
Your problem should be large enough to have more than 30 such features. Note that
you will be designing and prototyping the UI, not implementing the entire system.
The purpose of this exercise is to form the basis for what specific items must be
included in your designs as you move forward. Be very specific. These
should not be general terms such as "manage a course."
Each of you should discuss your list of features with 2 potential users to
understand the relative value of the varous features.