Table of Contents:
Business Plan
A.) User Identification and Interviews
B.) Electronic/Print Advertisement
C.) Pitch Video with Demonstration
Project Management
A.) Team Working Agreement
B.) Individual Responsibility Statement
C.) Project Schedule
D.) Meeting Notes
Software Documentation
A.) Introduction
B.) User Manual
C.) Program Description for the Developers
D.) Final Algorithm, Flowchart, or Pseudo-code
E.) Final Program with Comments
F.) Discussion
G.) Conclusions and Recommendations
H.) References
_________________________________________________
Executive Summary:
As we built the game of war we became more versed in the software of MatLab. What we can share is our experience with the software what it is like to come completely in contact with new software and its syntax and the way in which we have traverse learned and experienced it. We found that though the game of war was common the code was anything but. In our experience war was an interesting game to try and write into code based on the randomness and the way that it is scored is often different from person to person. We think that our version of war is unique for the fact that it is incredibly easy to play and it offers an input system so simple to the user that almost anyone could use it.
We found Matlab to be a new experience for all of us. While we were given the nuts and bolts for this project we found that along the way we had to as a team figure out what our goal was exactly on the step by step basis rather than the larger part of just knowing we wanted to create the game war. The first problem we really ran into was the fact that we did not know exactly how the loops would fit inside each other we also didn’t know how the game would be scored and just at first glance we didn’t think we had a good grasp on all the syntax needed to write even a simple game like war. We decided to score the game on a control of the majority of the two decks and after some further research with the help of the Matlab help bar we figured out figuring out most things in the software was a couple of keywords a click and some reading away from a better understanding of how to program worked and exactly why it worked and how to use it well. We found that with time and effort Matlab was very traversable in the way it would teach you the syntax if any questions arose and show examples of the problem you face. The code was an experience to write itself and once we got the game to function in the way we planned it was a relief. We actually lost a team member during the midst of this project and we found that it made everybody else take the next step up and get more involved in the production of our Matlab game.