Each team must present the design of their game framework to the class. For your presentation, you should prepare your material ahead of time and make it available from your project website. Each group should have a primary spokes-person, i.e., a master of ceremonies, but each group member should also have a chance to present their area of expertise. Each team will be given approximately fifteen minutes to present.
Each team must present their design to the class. You should be able to present the design at several levels of detail. First, you should be able describe in a sentence or two the primary architecture of your design, or any given package, or how the user will build a game from your package. You should also be able to describe how these objects (or hierarchies of objects) will work together. Additionally, your team will sound better if it can describe trade-offs you have considered during your design meetings.
Finally, when demonstrating your design, you must be able to show how specific objects (using responsibilities already shown in your design) will collaborate to accomplish a task.
Each person in the class not presenting must fill out a "grader sheet" for the presented design. For each part of the sheet, you will score the team based on how well you feel the team's design addresses the concern (as well as a brief comment justifying your score). If you do not have enough information to answer any part of the sheet, you should ask the team for clarification rather than leave the space blank. After each presentation, you will turn in your grader sheet. I will give your comments to the presenting group after I have had a chance to look at them. You will be graded on how perceptive your own comments on the grader sheet are, as well as how good your presentation is.
Additionally, you may be asked to make up a use case for the presenting team to demonstrate.
We have seen many examples of describing designs without necessarily resorting to code: