Wii Toothbrush Project

Final Presentation

Project Introduction:Abstract

• Client: Kenneth G. Rawson, DMD, SIUE School of Dentistry

• Purpose: to create a game whose goal is to teach children ages four to six proper technique for brushing their teeth, specifically by using the Nintendo Wii Remote to emulate using a toothbrush on a virtual model of human teeth.

• The game will be used by the client to conduct a test over whether or not children can be taught proper brushing technique via video games.

System Requirements

• PC – Windows XP, Vista, or 7– DirectX 9.0c or above.– Bluetooth stack

• Wii Remote

• Bluetooth Device

Project PlanSpiral Lifecycle model with 4 phases:

•First Build - Core Gameplay - 3D teeth model is included and the Wii Remote was used to simulate brushing.•Second Build - Menus, Sound, and varied levels: included brushing of the tongue (beginning of second semester).•Third Build - Content Editors: allowed creation of game "skins."•Final Build – Content: fulfill the remaining requirements, which all relate to game content.

Project Schedule

Meeting the RequirementsI. The WiiBrush game engine. The game executable, which uses the Wii remote to

simulate using a toothbrush.II. Source code and resources. Includes the source code and 3D models needed to

modify the game engine.

• Implemented in C# with XNA game studio.

• Gameplay includes simple scripted “scenes” and brushing “levels.”

• Both the installer and the C# project will be delivered to the client.

III. Content editors. Editors to modify game content such as graphics, level progression, sound effects, and trivia. Content editors will include instructions for use.

• Content editors are implemented in Visual Basic.

• User manual with walkthrough for building a skin is included.

Meeting the RequirementsIV. Specific game content.

A. Three game modes or “skins.”

1. One appealing to boys.

2. One appealing to girls.

3. One targeted to a general audience.

• King Arthur, Princess, and Halloween skins were built.

B. Dental hygiene trivia

• Random trivia is displayed before and after each level. Additional trivia is displayed as scripted in the skin. Trivia can be displayed as a fact or a question to the player.

C. Voice-overs for text.

• Scenes, trivia, and menus are voiced.

Meeting the RequirementsD. Sound effects.

• Sound effects can be attached to menu events, germ death, brushing movement, and level clear. Sounds can be played in the scripted scenes.

E. Specific level progression difficulty.

• Germ groups have adjustable speed and toughness. Levels can include specific brushing surfaces.

V. Installation on the client's demonstration laptop.

VI. Instructions for future installations, including instructions for a suggested Bluetooth device.

•Installation instructions are included with the user manual.

UML Diagram – Main Program

UML Diagram - Skins

UML Diagram – Visual Effects

UML Diagram - Menus

Interface Design

• Must be simple and appeal to children.• Target age group can’t read well, so

voiceovers are required for everything – dialogue, menus, and trivia.

• Multiple menu systems and control schemes created and tested for ease of use.

Implementation

• Using C# with XNA 3.1.

• WiiMoteLib to handle Wii Remote interactions.

• Standardized coding and comment styles.

Testing - Stability

• Each team member was responsible for unit testing his own modules.

• The most complex and potentially problematic parts of the system were formally reviewed by other team members.

• Defects were communicated via email and in team meetings.

Testing - Usability

• Tested in the MUC with normal college students

• Structure: Play one level of the game, then fill out questionnaire regarding playability and ease of control.

• Menu and control schemes finalized based on results.

Testing - Appeal

• Tested in with children ages 4-6.• Structure: play through one entire game

mode, asked about whether it was fun or not.• Notes taken regarding potential changes to

the program.

Retrospective

•Content Editor•Amount of effort necessary was underestimated.•Oversight and miscommunication between members regarding skinnable elements.

•Artwork/content bottleneck

Individual Contributions:Matthew Wilmsmeyer

• First Semester:– Recorded all meetings.– Implementation of Sound module.– Created first draft of all presentations.

• Second Semester:– Implementation of Skin parser.– Wrote scripts for boys and girls skins.– Recorded and edited all dialogue.– Designed interfaces of Content Editor.

Individual Contributions:Michael Calvin

• First Semester:– Design and implementation of Graphics subsystem.– Worked extensively on Level and Motion.

• Second Semester:– Design and implementation of Menu subsystem.– Addition of visual effects.– Implementation of trivia.– Voiced all of the system menus and trivia.– Implemented the Girl’s storyline.– Created 3D models.

Individual Contributions:Charles Montgomery

• First Semester:– Implementation and upkeep of Input Module.– Dynamic compiling of user-created content.

• Second Semester:– Integration of third party image importing library.– Implementation and bug-testing of Content

Editor.– Code inspections.– Implementation of the King Arthur skin.

Individual Contributions:Gary Basarich

• First Semester:– Creation and maintenance of web site (both

semesters).– Worked on Motion.

• Second Semester:– Code inspections.– Completion of Motion.– Acquisition of artwork.– Content Editor Manual Walkthrough Script

Individual Contributions:Robert Lynn

• First Semester:– Generated requirements from client interview.– Worked extensively on Level, Germ, and Motion.

• Second Semester:– Design and implementation of Skin subsystem,

and integration of Skin parser.– Control schemes.– Heads up displays.– Scripted and implemented the Halloween game

mode.

Individual Contributions:Dr. Rawson

• Supplied test hardware (Wii Remotes).• Purchase of 3D teeth model.• Gave us an awesome Senior Project!