|
Group: |
Group Members |
Grader: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Section |
Max Pts |
Your Pts |
Comments (What I'm
looking for) |
|
Product Overview |
7 |
|
This section is judged as a whole, since it's pretty subjective as to
what goes where. Does it tell me: What's being built What the purpose of it is Why you're implementation is needed What you expect from the product Any special problems/situations that might affect you What it's NOT going to do A grand summary A description of who will accept it, what the test environment will be
and what will constitute success. Don't get carried away, but really think about this. This should fit on
one or two pages and you should be able to give it to your boss to tell him
why what you're doing is important. |
|
Applicable Documents |
2 |
|
All our milestones At least one source for game rules, unless the game is made up
completely by your group. |
|
Context Diagram |
5 |
|
Graphically shows the boundaries of your system |
|
Users |
5 |
|
Identifies Favored, Disfavored and Ignored and identifies the effects
of these decisions. Identifies methods of user inclusion. |
|
Constraints |
2 |
|
At least one constraint listed. |
|
Use Cases |
20 |
|
Can I see how the game will be played, from the beginning to a win and
start over, including error conditions? |
|
Functions/Behaviors |
20 |
|
The requirements support all the documented use cases and all the
undocumented ones, e.g. if use cases
are left out, such as error conditions, you will be penalized for missing the
use case and for not having requirements to support it. |
|
Attributes |
2 |
|
Some attributes identified |
|
Unresolved Issues |
2 |
|
At least two unresolved issues identified |
|
Assumptions |
2 |
|
If any are known, they should be stated |
|
Data Elements |
2 |
|
If any are known, they should be stated |
|
Design Decisions |
2 |
|
If any have been made, they should be stated |
|
Risk |
5 |
|
Identifies the major risk, describes what will be demoed approximately
a month before end of quarter. |
|
Document Conventions |
2 |
|
If any unusual conventions were used, state them. |
|
Sample Displays |
5 |
|
Four or 5 hand drawn displays to support key points in your use cases:
initialization, first play, win, help display, etc. |
|
Glossary and Acronyms |
2 |
|
|
|
Presentation |
5 |
|
Correct spelling Clear sentence construction Follows template Consistent format You INSTANTLY 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) |
|
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: |