Senior Design Group 16

Wiimote and Kinect Labs

Team

Brenton Hankins - Team Leader Jeff Kramer - Communications Liaison Rick Hanton - Team Webmaster Harsh Goel - Team Architect Advisor & Client: Dr. Tom Daniels 309 Nuclear Engineering Building Ames IA 50010

Background

CprE 185: Introductory problem solving course for CprE/SE students at Iowa State Students use Wiimotes as a data source for their labs Creates interest in engineering and problem solving

Problem Statement

The Wii Wrap software used by freshmen Computer Engineering students is simple but needs improvement for installation and use by novice users such as a high school science teachers. In addition, similar software should be developed that uses the Microsoft Kinect sensor as input to student written programs.

Concept Diagram

Use Cases

Functional Requirements

1. Develop an installer for the Wiimote project.

2. Remove known errors from the Wiimote lab software.

3. Test edge cases of WiiWrap.

4. Correct buffering problems and synchronize user program with the incoming data stream.

Functional Requirements

5. Make Kinect sensor data streams available to the user in an efficient and real-time manner (less than 100 ms) 6. Provide an interactive application that students can program using the Kinect data.

7. Have an interface to write programs on the received Kinect data and run them.

Nonfunctional Requirements

RELIABILITY We will refine and package the software that is designed. This pertains to optimization of real-time processes such as data processing. A testing plan shall be developed for this purpose.

PORTABILITY The project shall be portable between computers. We will cater mainly to windows, but will ensure that our libraries are extendable in case there is a need to adapt it to another system. Additionally, the software shall be easy to install and remove.

USABILITY The project shall be easy to use, both for instructors and students. It shall simplify tasks to set up and run projects by means of intuitive GUIs so that students can focus on problem solving aspects as much as possible.

Responsibilities

Jeff: Communications Liaison Maintain communications with advisor, client, and instructor Head of wii project Brenton: Project Manager Developing primarily for Wii project Rick: Webmaster Head of Kinect project Harsh: System architect for both projects Developing primarily for Kinect project

Schedule

Feb. 3 – 10: Get requirements and specifications from customer Feb. 7 – 28: Work on Project Plan Feb. 7 – 28: Research available software for building Kinect package Feb. 28 – Mar. 14: Remove bugs from Wii wrap Feb 28 – Mar. 14: Develop Installer for Wii project Mar. 14 – 21: Write documentation on Wii project Mar. 24 – Apr. 25: Work on the Design Document Apr. 26: Design Review

Schedule (continued)

Summer – Sept. 1: Development on Kinect Package Sept. 1 – 7: Document Kinect package Sept. 7- 21: Testing of Kinect Software

Budget

Item

Microsoft Kinect (1) for development Wiimotes and Bluetooth adapters

Cost

$150 $0 (owned by dept.)

Total: $150

Potential Risks and Mitigations

• Developer becomes ill for a long period of time • Try our best to continue work without developer • Unexpected coursework/responsibilities interfering with development • Set up smaller deadlines to make progress on larger tasks • Equipment we are using stops working • Jeff has several Wiimotes available to him and there are one or two more Kinects Dr. Daniels could let us use.

• Microsoft’s Development of a Kinect SDK that could be a better alternative to OpenKinect • Rearrange software design to compensate.