CSE 3902 Professional Software Development - Sprint 4 - Super Mario Bros Level 1-1

Due (subject to change):

• Sprint planning: Wednesday, February 27th, before class.
• Initial implementation: Monday March 4th, before class.
• Refactored code: Friday March 8th, before class.
• Group Team Rubrics: due Friday, March 8th in class.

Objectives:

• Finish implementing all requirements and uses cases for level 1-1, making use of good programming principles and design patterns to separate concerns of UI or events from actions and concerns of collision detection from collision response.
• Implement a Kinect controller.
• Add a scrolling camera.
• Add a HUD.
• Add sounds.
• Add points and the score system.
• Add coins and the coin system.
• Implement the winning game state for when Mario reaches the end of the level.
• Implement the transition between Mario's death and restarting the level.

Sprint 4 Tasks:

• Planning (20 points):
  • Add dates for Sprint 4.
  • Add a task for adding a Kinect controller.
  • Add a task for creating a camera.
  • Add a task for creating the HUD.
  • Add a task for adding sound effects.
  • Add a task for adding background music.
  • Add a task for adding the flagpole and castle and the level complete ending animation.
  • Add any additional tasks you deem necessary for content found in level 1-1.
  • Associate all of these work items and tasks with Sprint 4.
  • Grading will be based on TFS admin (3 points), completeness of tasks and assignments (12 points), and burndown chart (5 points)
• First Implementation (30 points):
  • Assign initial tasks to each team member and have them implement them.
  • When you sit down to work on this sprint, drag the task you are going to work on to in-progress on the board.
  • If you finished the task during that session, drag it to Done and check your work into TFS.
  • If you did not finish, but it compiles, change the remaining work for the tasks and check your work into TFS.
  • If it is not finished and does not compile, change the remaining work for the tasks and make sure your work is saved (or shelved).
  • Grading will be based on whether it works and is complete (25 points) and did everyone contribute (5 points).
• Final Refactored Implementation (50 points):
  • Go through each class and tighten the variable names, check the logic and end cases.
  • After changes are made, send a Code Review request to another team member (or two).
  • Run Code Analysis on your solution and fix any reported warnings or errors. For warnings you do not wish to fix, provide justification in the readme file.
  • Respond to any criticisms from the instructors on your code.
  • Grading will be based on: does it still work (5 points), Code review quality and participation (10 points), adherance to coding standards (10 points), percentage of Code Analysis errors (10 points) and overall code quality (15 points)

Additional notes:

Grading:

See above. In addition, your individual scores will be weighted based on the team rubrics and activity in TFS.

Key Mappings
Please use lower case letters for the keys
Use the arrow keys for left/right/crouch movement
Use the z key for jumping
Use the x key for running and fireballs

GamePad Mappings

Use the left joystick for left/right/crouch movement
Use the a key for jumping
Use the b key for running and fireballs

Kinect Mappings

To be determined...