Everyone:
For the second project, you are to work in groups of 2 - 4 students to create a game or related artifact for a modern computing platform. What this means is that the software you develop should involve modern computer graphics, networking, mobile computing, or artificial intelligence.
Rate the projects using the Project 02 - Peer Evaluation Form.
Your group's project artifact must meet the following requirements:
The artifact must utilize a modern graphics library (ie. OpenGL, DirectX, etc.], game engine (ie. Unity, Cocos 2D, etc.), or animation software (ie. Maya, Blender, etc.).
The artifact should be interactive and capable of being manipulated by a user via some sort of input device (unless it is an animated movie or an artificial intelligence application).
The artifact must run in on a modern computing platform (ie. Windows, macOS, Linux, Android, iOS, XBox, etc.).
The artifact's source code is stored on an online repository such as GitHub, GitLab, or Bitbucket.
The project includes sufficient documentation to build, deploy, and use the artifact.
The project has a website that presents the artifact in an aesthetic manner, explains how the project it takes advantage of the chosen modern computing platform, and includes a video of the artifact in action.
The purpose of the project is to provide you an opportunity to experience new and modern computing technologies. Because of this, you should avoid things you have previously seen such as Python and PyGame. Moreover, you should avoid doing everything yourself, and try to take advantage of as many libraries and frameworks as possible to create a polished product.
That said, the artifact, platform, and tools are mostly up to you; use this opportunity to explore something interesting to you.
If in doubt, ask the instructor if you can utilize a particular tool or library.
Here are some possible project ideas:
Convert a classic 2D game into a 3D game.
Port a classic game to a mobile or web platform.
Create a short animated film (around 30 seconds to a minute).
Construct a game engine or framework for making a particular type of game.
Implement a significant mod for a current game.
Program a sophisticated bot for a current game.
Write a program that simulates or visualizes interesting scientific data.
Create a competitive multi-player networked game.
Develop a social game for the Chromecast.
Utilize the Kinect to make a demo or game.
Make a virtual reality demo or game.
Significant improve an existing open source game such as 0 AD or The Battle for Wesnoth.
Here is the project timeline:
Date | Milestone | Description |
---|---|---|
March 31 | Proposal | Description of proposed project. |
April 24 | Progress | Status report of current progress. |
May 1 | Sprint | In-class sprints. |
May 9 | Presentations | In-class presentations and demonstrations. |
More details about each of these milestones is described below.
Your group must submit a proposal document by noon on Saturday, March 31, which provides the following information:
Lists the group members and each of their proposed roles.
Describe the proposed project and how it meets the project requirements.
Enumerates any resources required.
If you need any hardware resources please let the instructor know and he will see if he can procure your requests. Please do this sooner rather than later.
Your group must submit a proposal slide deck (5-8 slides) by noon on Saturday, April 21, which provides the following information:
Addresses the questions and expections in feedback email provided regarding the project proposal.
Summarizes the work done this far, in particular the design and implementation details of your artifact.
Enumerates the remaining tasks, with specifics on what you plan on accomplishing during the upcoming sprint week and what you realistically plan on accomplishing before the deadline.
Itemize contributions to the project thus far and what how each member will aid in completing the tasks above.
If possible, provide video or image evidence of your project and your progress.
Your group must submit a link to their project website by midnight on Tuesday, May 8, which provides the following information:
Overview of your project and how you fits into the required theme (and requirements).
Description of the design and implementation of the artifact (and how each person contributed), focusing on the key concepts and ideas.
Summary of what was accomplished and what was learned.
A demonstration of the artifact.
Each group should plan for about 5 minutes for the presentation and 2 minutes for questions. Towards the end of the presentation day, there will be about 15 minutes for students to go around the room and test out the projects presented that day.
The project will be graded with the following rubric:
Metric | Points | Description |
---|---|---|
Proposal | 10 | Does the proposed project meet the requirements? |
Progress | 10 | How much work did the group do before the sprint? |
Presentation | 10 | How well did the group present and demonstrate their artifact? |
Deliverable - Requirements | 10 | How well did the project meet the requirements? |
Deliverable - Technical Challenge | 10 | How difficult was the project? |
Deliverable - Execution | 10 | How complete was the project?. |
Deliverable - User Experience | 10 | How enjoyable was project for end users? |
The first two metrics will be graded by the instructor, but the final five metrics will be evaluated based on feedback from your fellow classmates.
Once you have organized your group, please fill out the following form
You can update your submission whenever you have your proposal, code repository, and presentation slides.