1. Welcome Page

Table of Contents

Project Management Documentation

A. Team working agreement

B. Individual Responsibility agreement

C. Project schedule

D. Meeting notes

Business Plan

A. User Identification and Interviews

B. Electronic/Print Advertisement

C. Pitch Video with Demonstration

Software Documentation

A. Introduction

B. User Manual

C. Program Description for Developers

D. Flowchart of game

E. Final Program with Comments

F. Discussion

G. Conclusions and Recommendations

H. References

 

Executive Summary

The goal of this software design project was to make two games – a text-based adventure game and a graphical Connect-4 game – written and playable in MATLAB. Since MATLAB is not commonly used to develop games, we determined that we would have competitors and a greater chance of success. By pioneering the MATLAB format for gaming, we have the potential to expand the perception of the utility of MATLAB to beyond engineering applications.

This site is divided into three sections which contain different parts of our project documentation.

First, the Project Management Documentation section contains our agreements, outlining the amount of work each group member committed to do. The team working agreement was formulated prior the project’s inception, focusing on general responsibilities and expectations of each team member. The Individual Responsibility Agreement outlined the planned responsibilities specific to the project once the games had been determined and detailed what each group member had done once the project was completed. Additionally, notes and a progress report were kept each meeting to ensure the group was on pace to complete the project before the deadline.

The Business Plan section follows, containing our interviews, poster advertisement, pitch videos intended for varying audiences, and game demonstration videos. This section is centered around all of the media that we have created to promote our game and research of our demographic.

The Software Documentation section is last, containing the bulk of data concerning the project code. This includes content intended for other software developers: A technical description of the programs, a flowchart that visualizes the program’s processes for other developers, and the final, raw code with ample commenting. There is content directed toward general audiences as well, including an introduction, user manual, discussion of testing, problem solving, and progression that took place during the project, and conclusions and recommendations for the future of the program.