Coverage of the product's features, and justification for its development.

Good introduction and coverage of the motivation. Demo was very effective in showing off the game.

Team presented their game "Notebook Ninja", a 3D street brawler. Team wanted a game they could make with only "programmer art", that is art not done by an art major but instead drawn by a software developer with no art talent.

Team presented a live demo of their application and asked students to download and and play it themselves. The demo was very convincing.

Summarization of the development/technical strategy used by the group. Should include some information about the important decisions that the group made about technology, any benefits, drawbacks or problems they had.

The description of the movement and the ink engine was really interesting. You did a good job of showing us what you did.

Game was written in C++ with OpenGL graphics. SDL was used to support the application setup (such as creating windows).

Bugzilla was used by the team to track bugs.

valgrind was used to help troubleshoot memory problems early on; this saved the team a lot of effort later.

Game objects were a simple interface which permitted update and display on each frame.

Group had good presentation practices. Slides were readable for the audience, group was audible to everyone in the audience, material was well organized.

Slides were clever and interesting. I appreciated the cartoon drawn during Programming Languages. The whole presentation was presented in a very engaging manner that kept everyone interesested and involved.

All team members participated in a presentation which was cohesive and well planned. Team members were coordinated with one another and "put on a good show". Group members handled questions from the audience.

They were well coordinated and were clear on what and when they were delivering.