Welcome Page

Table of Contents

1. Project Management
   1. Team Working Agreement
   2. Individual Responsibility Agreement
   3. Project Schedule
   4. Meeting Notes
2. Business Plan
   1. User Identification and Interviews
      1. Blackjack
      2. Over Under 7
   2. Electronic/Print Advertisement
      1. Blackjack
      2. Over Under 7
   3. Pitch Videos With Demonstration
      1. Blackjack
      2. Over Under 7
3. Software Documentation
   1. Introduction
      1. Blackjack
      2. Over Under 7
   2. User Manual
      1. Blackjack
      2. Over Under 7
   3. Program Description for Developers
      1. Blackjack
      2. Over Under 7
   4. Final Flowchart
      1. Blackjack
      2. Over Under 7
   5. Final Program with Comments
      1. Blackjack
      2. Over Under 7
   6. Discussion
      1. Blackjack
      2. Over Under 7
   7. Conclusions and Recommendations
      1. Blackjack
      2. Over Under 7
   8. References
4. Function Files
   1. Blackjack
   2. Over Under 7

Group P- Michael Manning, Mitchell Lewis, Grace Espey, Kyle Cmich              SDP

Dr. Deborah Grzybowski, Naitik Choksi (GTA)                                             12/03/2020

Executive Summary

The Ohio State engineering group was tasked with the development of a software design project, or the creating of code for a simple game or games. This project was assigned to allow students to show what they have learned in ENGR 1181 throughout the semester. The code was to be accompanied by documentation, which included flow charts, meeting notes, a user manual, consumer interviews, as well as advertisements and pitch videos to various stakeholders.

Group P of ENGR 1181 at The Ohio State University started the software design by interviewing an avid online gaming customer to establish what is desirable in game code. This result was used to determine the games to be coded: BlackJack and Over Under 7. Next, loose ideas of how the games would run were put together in the form of flow charts. These flow charts were used as guides for the code, ensuring all aspects of the game were included. After many meetings of hard work and a slew of issues, codes were created for each game. Once coding was finished, a second interview was conducted to collect consumer feedback on what had been created. This feedback was used to determine any revisions needed to be made to the code. Once revisions were complete, final documentation was created.

While both simple, single player games, BlackJack and Over Under 7 proved more difficult to code than previously expected. Many drafts were made for the card distribution function in BlackJack before the development of our final project. Nearly as difficult was the addition of visuals to Over Under 7. Though both games had their own struggles, the project ended with the development of a smooth single player card game including a strategic AI, BlackJack, as well as a fast paced dice game showing the dice rolled and involving participant betting, Over Under 7.

After finalizing the coding and reflecting on the team’s work, the team would make a few general recommendations that the team thinks would make the process easier. One recommendation is using a different software that would allow people to be more collaborative. Unfortunately, MATLAB only allows one person to work on the code at once. As a result, it was difficult for the team to be efficient at editing and contributing. Additionally, another recommendation we’d make is the approach to creating the game. The team began with the goal of turning an in-person Blackjack game into an online MATLAB program. This caused the team to run into problems since the team couldn’t directly translate each element of Blackjack into coherent code. There is a language barrier between the real world and coding just like there is between two world languages. Two things may seem like the same thing but cannot be represented in the same way. If the team would have recognized this before, the team could’ve been more prepared for the issues to come.