Difference between revisions of "GAM670/DPS905 Project Requirements 20111"
(→Phase 2) |
(→Project Requirements) |
||
| Line 99: | Line 99: | ||
= Project Requirements = | = Project Requirements = | ||
| − | Your game involves a real-time audio-visual experience in | + | Your game involves a real-time audio-visual-haptic experience in a 3-D world using advanced techniques to improve performance and appeal. The user experiences force feedback through some form of controller in response to certain actions in your game. Each member must contribute their own feature to the game in a selected area or areas of their choosing. Each member should also contribute to the integration of a feature developed by another team. |
== Phase 1 == | == Phase 1 == | ||
| − | The first phase is | + | The first phase is an informal, written proposal of the features that your team intends to implement. Your description should identify the basic aspects of the features as well as the refinements needed to produce a comprehensive implementation. Your proposal should be documented on the team project page of the course wiki under '''Proposal'''. Your proposal should identify the parts of the framework that you expect to modify in your implementation. |
| − | + | Each team member should have their own successfully compiled version of the starting sample in their own workspace in the branch sub-directory of their team's repository. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | Each team member should have their own successfully compiled version of the | ||
Branch submission path: svn://zenit.senecac.on.ca/dps901_103rep??/branches/SenecaID/15C | Branch submission path: svn://zenit.senecac.on.ca/dps901_103rep??/branches/SenecaID/15C | ||
| − | + | The source code for the starting sample should include the following updates: | |
| − | |||
| − | |||
| − | The source code for the | ||
* add your own name to the caption for the dialog box | * add your own name to the caption for the dialog box | ||
* change the window title to include the name of the team | * change the window title to include the name of the team | ||
| − | |||
Merge all of the team members' 15C workspaces back to trunk so that the caption of the dialog box shows all of the names of the team members. See [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Merging_your_work_back_to_trunk Merging your work back to trunk] for detail | Merge all of the team members' 15C workspaces back to trunk so that the caption of the dialog box shows all of the names of the team members. See [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Merging_your_work_back_to_trunk Merging your work back to trunk] for detail | ||
| − | |||
The purpose of this first phase of the project is twofold: | The purpose of this first phase of the project is twofold: | ||
| − | * to define your game in both scope and detail | + | * to define your game in both scope and detail |
| − | * to | + | * to enable your instructor to identify some of the details that you will need to handle in implementing the selected features |
| − | |||
Your team should decide its own group to individual ratio for grading purposes and post the agreed ratio on its project page. | Your team should decide its own group to individual ratio for grading purposes and post the agreed ratio on its project page. | ||
| − | Your team must arrange a time and date to meet with your instructor to discuss the proposal and to commit the different responsibilities of the team members | + | Your team must arrange a time and date to meet with your instructor to discuss the proposal and to commit the different responsibilities of the team members. |
== Phase 2 == | == Phase 2 == | ||
Revision as of 23:57, 4 January 2011
GAM670/DPS905 | Weekly Schedule | Student List | Project Requirements | Teams and their Projects | Student Resources
Contents
Appointment Schedule
| Team Name | Date and Time |
| Tuesday January 18 10:00AM | |
| Tuesday January 18 10:15AM | |
| Tuesday January 18 10:30AM | |
| Tuesday January 18 10:45AM | |
| Tuesday January 18 11:00AM | |
| Tuesday January 18 11:15AM |
Due Dates
| Proposed game and team members selected | January 18 |
| Proposal completed and members' roles selected | January 31 |
| Phase 1 completed | February 22 |
| Phase 2 completed - Presentation | March 22 |
| Approval meeting with instructor | March 29 |
| Phase 3 completed - Presentation | April 12-14 |
Project Requirements
Your game involves a real-time audio-visual-haptic experience in a 3-D world using advanced techniques to improve performance and appeal. The user experiences force feedback through some form of controller in response to certain actions in your game. Each member must contribute their own feature to the game in a selected area or areas of their choosing. Each member should also contribute to the integration of a feature developed by another team.
Phase 1
The first phase is an informal, written proposal of the features that your team intends to implement. Your description should identify the basic aspects of the features as well as the refinements needed to produce a comprehensive implementation. Your proposal should be documented on the team project page of the course wiki under Proposal. Your proposal should identify the parts of the framework that you expect to modify in your implementation.
Each team member should have their own successfully compiled version of the starting sample in their own workspace in the branch sub-directory of their team's repository. Branch submission path: svn://zenit.senecac.on.ca/dps901_103rep??/branches/SenecaID/15C
The source code for the starting sample should include the following updates:
- add your own name to the caption for the dialog box
- change the window title to include the name of the team
Merge all of the team members' 15C workspaces back to trunk so that the caption of the dialog box shows all of the names of the team members. See Merging your work back to trunk for detail
The purpose of this first phase of the project is twofold:
- to define your game in both scope and detail
- to enable your instructor to identify some of the details that you will need to handle in implementing the selected features
Your team should decide its own group to individual ratio for grading purposes and post the agreed ratio on its project page.
Your team must arrange a time and date to meet with your instructor to discuss the proposal and to commit the different responsibilities of the team members.
Phase 2
The second phase releases a version of the framework that includes the new features that your team has incorporated. This phase includes a presentation that shows how your new features work within your own game.
Phase 3
The third phase presents your completed game with your team's new features and two new features of other teams incorporated. Your presentation includes a demonstration of how the game plays along with an explanation of the innovative aspects that your team members have implemented. Each team has no more than 20 minutes to showcase its game.
Some Suggested Upgrades to the Framework
The Framework in its final stage consists of 12,000 source lines of code. The Framework is only a starting point and fallback position for the design of your game. There are numerous opportunities to refactor different parts depending upon what your game requires and what your personal interests are. Decisions to focus on certain parts should reflect the areas with which you wish to become more familiar. Listed below are some areas that you should consider in deciding where to devote your energy. If you wish to add items to this list, consult your instructor.
Each team will introduce its own upgrades to the Framework. The nature of these upgrades will vary from team to team. Each team member is responsible for a thorough understanding of at least one particular upgrade.
