Table of Contents and Executive Summary

Table of Contents:

1.) Project Management

A. Team Working Agreement: A signed agreement describing how to deal with interpersonal conflicts.

B. Individual Responsibility Agreement: A signed agreement detailing the individual responsibilities of each team member.

C. Project Schedule: A list of goals, their progress, and how long it took to complete to help keep the team on task.

D. Meeting Notes: A summary of the proceedings of each meeting and who attended.

2.) Business Plan

A. User Identification and Interviews: The target audience of each game and an interview was conducted before and after development.

B. Electronic/Print Advertisement: A possible advertisement for each of the games.

C. Pitch Video with Demonstration: A pitch video with a demonstration for the text-based adventure game.

3.) Software Documentation

A. Introduction: An introduction to the software documentation.

B. User Manual: A set of instructions for each of the games.

C. Program Description for Developers: A list of all variables used in the game along with technical details.

D. Final Algorithm: A final algorithm that matches the finalized code.

E. Final Program with Comments: The final program with step comments explaining each step.

F. Discussion: A discussion of the game and how its design changed throughout the course of the project.

G. Conclusions and Recommendations: A summary of the discussion and recommendations on how to improve the game.

H. References: A list of sources used.


Executive Summary:

This project was the culmination of everything we have learned over the semester. We were tasked with creating a short game in MATLAB. It took a combination of teamwork, technical skill, and a knowledge of MATLAB to create this game. As a team, we created a teamworking agreement to deal with interpersonal conflicts, an individual agreement to ensure that the work is divided evenly and completed on time, a project schedule to keep the team on task, and meeting notes to summarize the events of each meeting. In order to ensure coherence throughout the versions of the game, the entire design process, from brainstorming to final testing of the code, was documented.

Our business plan consisted of interviewing beta testers/ interviewees that were selected from our class on what they enjoyed and what they wanted from video games. Each of the games we produced received a poster/ title card that was tailored to the style of each one’s content. Our pitch video featured each of our team members explaining their role and what content they were able to contribute to our project, along with demonstrating gameplay from our finished product

The software documentation starts with an introduction stating what was documented for each game. Each game includes a user manual, a program description, an algorithm, the final program, and conclusions and recommendations. The user manual for The Quest for Chegg explains to users the types of choices they encounter, and a list of all the health statistics. Connect Four’s user manual simply describes the goal of the game and how to win. The program description for each game listed all of the variables we used and what they were for. We also listed all of the separate functions we created and used for Connect Four in the description. The final algorithms for each game is a map of the code that makes each game easier to understand. The final program with the comments section simply contains each game’s code with comments for readability. The discussion section for each game contains developer comments on the making of each game. The conclusions and recommendations summarize the software documentation section. The references section is just a list of references we used.