|
Group: |
Group Members |
Grader: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Section |
Max Pts |
Your Pts |
Comments |
|
Table of Contents |
5 |
|
Table of contents Table of figures Table of tables
(if appropriate) |
|
Introduction |
5 |
|
Point of the game Game rules Installation instructions |
|
Using the Game |
|
|
|
|
Terminology |
10 |
|
Special terms are
described (visually and in the narrative) |
|
User Interface |
10 |
|
All
"areas" of the UI are identified and their functions described. |
|
How Tos |
35 |
|
Is there a how-to
to support all the use cases and all the elements in all the use cases from
the SRD? Are the how-tos
complete? Are the how-tos
one step at a time? Do the how-tos
tell the user what to expect at each step? Are the how-tos
presented in a tabular form? Are the how-tos
short enough to not confuse a new user? |
|
Presentation |
5 |
|
Correct spelling Clear sentence
construction Follows template Consistent format You will lose
these points if ALL your group members names and roles aren't on the title
page. (This means you lose 5 points
if you don't have a title page, too) |
|
Supporting Documents: |
|||
|
Traceability Matrix |
20 |
|
Are all the
requirements supported by a how-to? Do all the how-tos
support a requirement or are there extra functions? (requirements creep!) To be
attached. The traceability matrix is not actually an integrated
portion of the user manual.
|
|
Time Log |
5 |
|
Title, so I know
what they are Times for all team
members, even while doing individual work. Total time for
milestone |
|
Meeting
Notes/Agendas |
5 |
|
Title, so I know
what they are Items to be
addressed (agenda) Decisions made Action items
assigned, with due date and responsible person |
|
Total: |
100 |
|
General Comments: |