CS 121 Rubric

Beta Executable/Documentation

Evaluation Considerations

Attribute Plus/Check/Minus Comments

Installs according to instructions
In your presentation, describe in detail how this happens. You could even provide screen shots of the process

Realizes Beta Use Cases
In your presentation, you must detail your Use Cases and discuss how your game realizes them.

Highly reliable (no bugs)
Demonstrate this via various paths in your presentation.

Gives a full gameplay experience
Demonstrate this via various paths in your presentation.

Pedagogical merit of game is clear
In presentation, go back to original requirements and discuss your interpretation of them and how that is fulfilled in game.

Graphics are compelling
In presentation, show and discuss this.

UI is intuitive
In presentation, show and discuss this.

Game will be fun for middle school students
In presentation, describe what will draw students into your game. Why will they come back.

Game will be challenging for middle schoolers
In presentation, describe what is challenging for your students, e.g., the content, the game play, ?

Middle schoolers will quickly understand game objectives
In presentation, describe what ensures this understanding, e.g., menues, help, the game itself...

Middle schoolers will be able to develop a winning strategy
In presentation, describe what ensures this will happen, are there sequences that allow students to win

Game is appropriate for novice and avid gamers
In presentation, describe why a nongamer or a gamer will like your game.

Game is appropriate for a culturally diverse audience
In presentation, describe any feature of your game that makes this true.

Game achieves team's initial design goals
In presentation, go back to your original goals and describe whether the resulting game fulfills them or they have changed.

Code is clean
In presentation, display some of your code and discuss your various approaches to naming, testing, etc.

Code is well documented
In presentation, display some of your code and discuss your approach to documentation. This may require displaying the Domain Diagram, UML,

UML includes use cases, class diagrams, and sequence diagrams
In presentation, you may use some of these to detail other features, but make a point to show the who Software Development LifeCycle.

Documentation includes results of user test
In presentation, describe your survey, your experiences with user tests, etc.

Team Presenting:

Team Evaluating:

Grade(10, 7, 3, 0):

Comments:

Mike Erlinger

Last Modified Tuesday, 27-Nov-2012 11:00:47 PST

Beta Executable/Documentation
Evaluation Considerations
Attribute	Plus/Check/Minus	Comments
Installs according to instructions In your presentation, describe in detail how this happens. You could even provide screen shots of the process
Realizes Beta Use Cases In your presentation, you must detail your Use Cases and discuss how your game realizes them.
Highly reliable (no bugs) Demonstrate this via various paths in your presentation.
Gives a full gameplay experience Demonstrate this via various paths in your presentation.
Pedagogical merit of game is clear In presentation, go back to original requirements and discuss your interpretation of them and how that is fulfilled in game.
Graphics are compelling In presentation, show and discuss this.
UI is intuitive In presentation, show and discuss this.
Game will be fun for middle school students In presentation, describe what will draw students into your game. Why will they come back.
Game will be challenging for middle schoolers In presentation, describe what is challenging for your students, e.g., the content, the game play, ?
Middle schoolers will quickly understand game objectives In presentation, describe what ensures this understanding, e.g., menues, help, the game itself...
Middle schoolers will be able to develop a winning strategy In presentation, describe what ensures this will happen, are there sequences that allow students to win
Game is appropriate for novice and avid gamers In presentation, describe why a nongamer or a gamer will like your game.
Game is appropriate for a culturally diverse audience In presentation, describe any feature of your game that makes this true.
Game achieves team's initial design goals In presentation, go back to your original goals and describe whether the resulting game fulfills them or they have changed.
Code is clean In presentation, display some of your code and discuss your various approaches to naming, testing, etc.
Code is well documented In presentation, display some of your code and discuss your approach to documentation. This may require displaying the Domain Diagram, UML,
UML includes use cases, class diagrams, and sequence diagrams In presentation, you may use some of these to detail other features, but make a point to show the who Software Development LifeCycle.
Documentation includes results of user test In presentation, describe your survey, your experiences with user tests, etc.