Welcome Page

Table of Contents

The Project Management link contains:

  • The Team Working Agreement
  • The Individual Responsibility Agreement
  • The Project Schedule
  • The Meeting Notes

The Business Plan link contains:

  • The User Identification and Interviews
  • The Electronic/Print Advertisement
  • The Pitch Video with Demonstration

The Software Documentation link contains (for all 3 games)

  • An Introduction
  • The User Manual
  • A Program Description for Developers
  • The Final Psuedocode
  • The Final Program with Comments
  • A Discussion
  • The Conclusions and Recommendations
  • The References Used

Executive Summary

G – Nathan Savino, Brandon Deuch, Jacob Kenneally, Brian Hartman

Instructor – Krieger, GTA – Warren

Background & Purpose

The goal of the software design project was to demonstrate the cumulative knowledge of MATLAB acquired by students throughout the course. The students were required to design and create a minimum of two points worth of games. Students were also given the opportunity to earn extra credit by designing up to six points of games. There were many different approaches for creating each game, each with their own benefits and drawbacks and the main learning goal of the project was for each team to decide which methods best fit their respective skill sets. The software design problem doesn’t only consist of the actual game, each group was required to also submit an advertisement for one game, a video explaining the project and the process of designing one game, and submitting a notebook. This notebook consisted of multiple forms of lab documentation and pseudo code the games that were submitted. Group G chose to create a total of three games, Blackjack, Over/Under Seven, and War.

Results and Analysis

Through the development process, many skills were refined by applying everything learned in MATLAB throughout the semester at once rather than individually. The man skill refined and combined with other skills, was the ability to create and call functions. Functions were an integral part of stream lining the code for each game and making the code easier to follow and debug as the games were being developed. Without being given explicit directions on how each game should be developed, group members were able to develop each other’s skills in MATLAB by sharing ideas and helping each other through various problems encountered throughout the process. Proficiency in MATLAB wasn’t the only desired outcome from the project. Groups were also able to showcase and develop their ability to work and communicate as a team. Teamwork was essential for the software design project. The code for each game wouldn’t have nearly as efficient or clear without using the collective knowledge of each group.

Conclusion and Recommendation

Overall, through the project, students were able to expand on their knowledge of MATLAB and use effective teamwork and communication to create one or more games from the ground up. Going forward, if the teams were given the opportunity to do the project again, the main focus would be expanding on the graphics in the original games created because that aspect was definitely the weakest part of each game. While there are limitations with MATLAB, the graphics could still be improved upon.