The vision statement should include an elevator summary of the project, a business case for the project (including a short analysis of the competition, market space or similar commercial off the shelf software), a description of the project stakeholders, a list of the major features of the completed project, and a list of the major risks of the project.

Good. I found your vision statement to be quite detailed and an interesting read. I'm looking forward to seeing your finished product.

The vision statement is very good. You did a good job describing your game and its business case and competition.

Must supply a list of use cases names. 10% of the supplied use case names should be fully dressed use cases, as discussed in class and the Larman text.

Use cases are good. There is a typo in UC02 weilding shoud be wielding.

Defines the terms used within your project which may not be commonly known.

Glossary is fine.

Must include assignment of use cases and features to specific iterations. The schedule must show the dates each phase and iteration will end.

Your schedule is good. I appreciate that you included the non- functional requirements in your schedule. You don't want to schedule any development during the Transition phase of your project. Transition is for testing and packaging.

Even though we can't pay you to complete your project, you need to develop a project budget which shows how much money you would need to develop your project if someone was paying you to do so. You should include the cost of any materials which you may need to purchase, such as software, hardware, references, etc. You must also show your staffing costs (salary/paychecks). The budget must be presented in terms of US dollars, as that is the local currency.

Budget is fine. Haribo frogs are a real necessity when doing hard-core development.