Task:
Overview
Rapid prototyping is a critical skill in the game industry. Whether developing a proof of concept or in the early stages of game development, programmers must be able to quickly analyze task documents, learn any new technology, and then accurately implement their tasks for a given prototype within a given time frame. For Part I of the project, you are assigned a rapid prototype project by a hypothetical company that has a hard deadline. The company has given you project documents that provide the specifications required for the rapid prototype. When working on your prototype, you will need to be conscious of scope creep and may have to rebalance your workload or refactor what you are doing to meet your deadline. When you are finished, in Part II of the project, you will write a postmortem report for the company that discusses what went right and what went wrong during prototyping.
This project addresses the following course outcomes:
1. Apply source code control system best practices in effectively managing game development projects
2. Use appropriate techniques for developing rapid game prototypes that ensure basic functionality and are informed by deadlines
3. Develop postmortem documentation that addresses the development process according to industry standards for informing future game projects
4. Implement appropriate target programming techniques in rapid prototypes based on applicable game project specifications
Your rapid prototype must conform to the expectations of the company as detailed in the provided project specifications, include any targeted skills (such as use of a touchscreen interface, one-button game, etc.), and use generally accepted coding techniques. You will also be required to thoroughly test your prototype in order to demonstrate a thorough quality assurance process to the company.
Specifically, the rapid prototype must demonstrate the following critical elements:
I. Source Code Control
a) Test the source code control system for prototype and submit a log of your check-ins in order to indicate active project management. Ensure that you check in your source code after each instance of modifications made.
b) Define prototype as a project.
II. Traceability: The prototype delivered must contain all of the required functionality specified in the provided project documents.
III. Test Plan: Your rapid prototype will eventually require testing to ensure errors are not present within the code. You will need to develop a test plan to accomplish this. You plan must:
a) Describe the process and techniques you would utilize for testing for runtime errors.
b) Indicate which appropriate target programming techniques you would use to confirm the prototype operates according to program logic set in the project specifications stated in the design document.
c) Explain, in detail, your process for testing your rapid prototype for bugs prior to the final release.
IV. Alpha Prototype: Your rapid prototype must:
a) Display visual aspects that demonstrate proof of concepts based on the provided project specifications.
b) Employ controls that are intuitive based on project specifications and easy to use.
The post GAM 303 Abbreviated Game Design Documentation appeared first on My Assignment Online.
