<br />
= Research Project = Your research project involves the investigation and implementation of a specific feature in the update base code. Identifying the features and the required refinements will demand some initial research on your part. The project is in two phases. == Phase 1 == The first phase is an informal, written proposal of the features that your team has decided to implement in its final game. Your description should identify the basic aspects of these features as well as the refinements to those features that are needed to implement in your own game by the end of the semester. Your proposal should be presented 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 extensively in your implementation. Your proposal should be on the wiki before your first meeting with your instructor. You should update your proposal after this meeting. Your instructor will use your updated proposal as the reference for marking this assignment. The base code for this course is an updated version of the base code for the previous course. You should use the updated base code to develop the feature that you have selected and present the results of your work using the updated base code. The updated base code with the new features installed will serve as the source for other teams' access. Each team member should have their own successfully compiled version of the updated base code in their own workspace in the branch sub-directory of their team's repository. The source code for each team member's copy of the base code 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' 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 details. The purpose of this first phase of the project is twofold:* to identify the features that your final game will include* to identify the features that each member of your team will incorporate* to identify the features that your team is expecting to incorporate from the research projects of other teams. == Phase 2 == The second phase releases the updated base code with your new features to the class. This phase concludes with a presentation that shows* how your new features work within the updated base code* how to incorporate the new features in external code You will have one hour to make your presentation and to describe the feature that you have implemented. == Appointment Schedules ==Research Project {| border="1"|-|Team Name|Date and Time|-||Wednesday February 15 11:40AM|-||Wednesday February 15 12:00AM|-||Friday February 17 11:40AM|-||Friday February 17 12:00AM|-|} == Project Presentation Schedule ==
{| border="1"
|-
* enable Streaming SIMD Extension 2 in Configuration Properties with optimized math calculations
= Appointment Schedules =
Research Proposal
{| border="1"
|-
|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
|-
|
|Tuesday January 18 1:30PM
|-
|}
Proposal Acceptance
{| border="1"
|-
|Team Name
|Date and Time
|-
|
|Tuesday February 1 10:00AM
|-
|
|Tuesday February 1 10:15AM
|-
|Andrei Kopytov
|Tuesday February 1 10:30AM
|-
|
|Tuesday February 1 10:45AM
|-
|
|Tuesday February 1 11:00AM
|-
|
|Tuesday February 1 11:15AM
|-
|
|Tuesday February 1 1:30PM
|-
|}
Project Review
{| border="1"
|-
|Team Name
|Date and Time
|-
|
|Tuesday February 22 10:00AM
|-
|
|Tuesday February 22 10:15AM
|-
|
|Tuesday February 22 10:30AM
|-
|
|Tuesday February 22 10:45AM
|-
|
|Tuesday February 22 11:00AM
|-
|
|Tuesday February 22 11:15AM
|-
|
|Tuesday February 22 1:30PM
|-
|}
<br />
Each member must contribute their own feature to the game development in a selected area of specialization. Each member should also contribute to the integration of a separate, unrelated feature developed by another team.
== Phase 1 == The first phase is an informal, written proposal of the features that your team wishes to implement in its final game. Your description should identify the basic aspects of these features as well as the refinements to those features that are needed to implement your game design. Identifying the features and the required refinements will demand some research on your part. 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 extensively in your implementation. A draft of your proposal should be on the wiki before your meeting with the instructor and you should update your proposal after consultation with your instructor. In developing your game, you may start with the code that you used in the previous course or you may start with the updated base code for this course. The base code for this course is an updated version of the base code for the previous course. In any event, each member should use the updated base code to develop the feature that they have selected and present the results of their work using the updated base code. In other words, the update base code with the new features installed will serve as the source for other teams' access. Each team member should have their own successfully compiled version of the updated base code in their own workspace in the branch sub-directory of their team's repository. The source code for each team member's copy of the base code 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' 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 details The purpose of this first phase of the project is twofold:* to identify the features that your final game will include* to identify the features that each member of your team will incorporate* to identify the features that your team is expecting to incorporate from the work of other teams. Your team should decide its own group to individual ratio for grading purposes and post the agreed ratio on its project page. == Phase 2 == The second phase releases a version of the updated base code that includes the new features that your team members have incorporated. This phase includes a presentation that shows* how your new features work within** the updated base code** your own game* how to incorporate the new features in external code Your team will have one hour to make its presentation and each team member will have fifteen minutes to describe the feature that they implemented themselves == Phase 3 == The third phase presents your completed game with your team's new features and two new features that members of other teams developed.
You present your completed game with your team's new features and two new features that members of other teams developed. Your presentation includes
* a demonstration of how the game plays
* an explanation of the innovative aspects that your team members have implemented
