For this project you will design and implement a computer game of your own choosing, subject to the constraints that it must:
Regarding networking: a two-player game is fine, and the game can require the players to cooperate or compete (your choice). You may strive for a more-than-two player game if you wish, but that is not required. Be cautious about games that require large amounts of information to be exchanged in real time.
Regarding the three categories of feaures: It is very difficult for you to “scope” the project appropriately for a 3-week team project. By listing your features in three categories, you allow yourself to recover from a badly scoped project (either one that turns out to be too easy or one that turns out to be too hard). See Grading below for how this affects the grading.
This is a team assignment and all that we said about that in VectorGraphics' Administrative Background section applies here as well.
Continue to use the same SVN repository for this assignment as you did for VectorGraphics,
but checkout the
CapstoneProject
project from that repository, and all subsequent work should be placed in this project folder and committed back to your repository.
Continue to use the same Rules and Practices of Extreme Programming listed in the VectorGraphics' Process section.
You will produce the same deliverables described in the VectorGraphics' Deliverables section.
Cycle 0 (for specification and design — not a development cycle) | Cycle 1 | Cycle 2 | Cycle 3 |
---|---|---|---|
May 5 - May 12 | May 12 - May 15 | May 15 - May 19 | May 19 - May 22 |
Milestone date | Time due | Deliverable(s) due |
Thursday, May 7 | By the END of class: | Screen Layout sketch, draft |
CRC cards | ||
Friday, May 8 | By the END of class: | Screen Layout sketch, final
|
UML class diagram, draft
|
||
Tuesday, May 12 | By the BEGINNING of class: | Cycle 0 Swing Experiments (if any) |
Cycle 0 Individual Reports (one for each team member) | ||
By the END of class: | Cycle 1 User Stories | |
UML class diagram UPDATED to contain details (attributes, properties) relevant to Cycle 1
| ||
Cycle 1 Task List
|
||
By midnight: | Your Team Evaluation Survey for Cycle 0 | |
Friday, May 15 | By the BEGINNING of class: | Cycle 1 Swing Experiments (if any) |
Cycle 1 Status Report | ||
Cycle 1 Individual Reports (one for each team member) | ||
By the END of class: | Cycle 2 User Stories | |
UML class diagram UPDATED to contain details (attributes, properties) relevant to Cycle 2
| ||
Cycle 2 Task List
|
||
By midnight: | Your Team Evaluation Survey for Cycle 1 | |
Tuesday, May 19 | By the BEGINNING of class: | Cycle 2 Swing Experiments (if any) |
Cycle 2 Status Report | ||
Cycle 2 Individual Reports (one for each team member) | ||
By the END of class: | Cycle 3 User Stories | |
UML class diagram UPDATED to contain details (attributes, properties) relevant to Cycle 3
| ||
Cycle 3 Task List
|
||
By midnight: | Your Team Evaluation Survey for Cycle 2 | |
Friday, May 22 | By the END of class: | Cycle 3 Swing Experiments (if any) |
Cycle 3 Status Report | ||
Cycle 3 Individual Reports (one for each team member) | ||
Final working code | ||
By midnight (FIRM deadline for graduating seniors!): | Your Team Evaluation Survey for the entire project | |
Extensions | Plan on completing your project per the above schedule — that's best for you. But I'll grant request for short extensions (a day or two or maybe even three) with no penalty except for graduating seniors (for whom I need to turn in grades Saturday morning, May 23). |
---|
You establish the Required, Additional and Bonus features for your project. List these features, in their respective categories, in your Screen Layout document.
You will determine the Required, Additional and Bonus features for your project.
Here is my grading plan: First, compute the process score, which is 30 points based on: