Posts

Table of Contents

by

 

Project Management

Team Working Agreement

Individual Responsibility Agreement

Project Schedule

Meeting Notes

 

Business Plan

User Identification and Interviews

Advertisement

Pitch Video

 

Software Documentation

Introduction

User manual

Program Description for Developers

Flowchart

Final Program with Comments

Discussion

Conclusions and Recommendations

References

Executive Summary

by

The software design project consisted of a team of engineers designing a game on the program MATLAB.  The team of engineers decided to make ‘Hangman’. The objective of creating hangman on MATLAB was to produce a fun game for people that are not familiar with matlab to play.  In order to achieve this, several different types of loops within the code are used, including for loops, while loops, and ‘if’ statements. While employing these strategies, the user sees a basic game of hangman, even though the code behind it was not basic. This is an important aspect of the science community as it is just a base of what has already been achieved. Once these codes get more and more complicated, games are able to be produced on a much larger scale.

 

The initial step was to choose the game that the team was going to code. User interviews were conducted to see which games would be interesting to play using MATLAB. The game our team decided to code was Hangman. After the game was decided team agreements and individual agreements were created. The next step was to begin writing the code in Matlab. Using different loops, it was possible to create the game.

 

The creation of this game allows the user to play a 2 person game alone. User interviews helped decide that this game would be fun and easy to play as you won’t need a paper or pen to play it anymore. Similarly, Matlab can be used to create more complex games in future. This game helped the team to learn something new by using the techniques learned in class and using them to create a game. It helped gain experience with programming and also helped team members to think critically and communicate well with each other.

Project Schedule

by

SDP Project Plan

10/31: (day 1 in class)

  • Create u.osu.edu account
  • Decide on game (hangman)
  • Identify users and conduct interview #1
  • Team working agreement
  • Individual responsibility agreement

11/7: (day 2 in class)

  • Flowchart/algorithm
  • Work on code

11/12 (outside of class)

  • Work on code

11/14: (day 3 in class)

  • Work on code before and during class
  • Draft PowerPoint presentation

11/15

  • Finish code (outside of class)
  • User interview #2

11/26: (outside of class)

  • Filmed video

11/28 (day 4 in class)

  • Final project plan
  • Final testing of code

11/28-12/3 (outside of class)

  • Finalize notebook

Meeting Notes

by

10/31: (day 1 in class)

  • Create u.osu.edu account- Cole created the blog
  • Decide on game (hangman)- group decision, led by Nate
  • Identify users and conduct interview #1
  • Team working agreement- updated old team agreement as a team
  • Individual responsibility agreement
  • Team worked well together to complete many assignments during class

11/7: (day 2 in class)

  • Flowchart/algorithm- Becca
  • Work on code- group effort
  • Lots of problem solving and discussing how to code occurred during this meeting

11/12 (outside of class)

  • Work on code- Becca and Nate, whole team helped
  • Worked very well together in attempt to complete the code before class

11/14: (day 3 in class)

  • Work on code before and during class- team effort
  • Draft PowerPoint presentation- Cole
  • Asked for help from professor and TAs regarding the string characters

11/15: (in class)

  • Finish code (outside of class)- Nate
  • User interview #2- group effort
  • User interview was completed later because the code was not complete the previous day

11/26: (outside of class)

  • Filmed video- group effort
  • More difficult staying on task outside of class, but the video was completed in a timely manner

11/28 (day 4 in class)

  • Final project plan- decided as group
  • Final testing of code
  • Code ran perfectly for the test

11/28-12/3 (outside of class)

  • Finalize notebook- everybody does their part

User Identification and Interviews

by

Users of Game:

The users of our game will consist of anyone who has interest in playing games and is able to read.

User Interview 1: (10/31/18)

Interview with a future player of our game on October 31st, 2018, Mitali.

Q: How long should the game last?

A: Less than a minute.

Q: What games have you played recently?

A: I don’t really play games, but Blackjack and Cards Against Humanity

Q: What games would be fun to play on matlab?

A: Connect four and Blackjack.

Q: What is the most important aspect of a game?

A: The graphics.

 

User Interview 2: (11/15/2018)

Q: Was it fun?

A: Yes!

Q: How were word choices?

A: Yes they were good words

Q: Was it straightforward?

A: Game flowed properly

Q: Improvements?

A: Display word choices after the loss, maybe add a theme?

Q: Graphics?

A: Graphics were good, maybe could make a display screen

Q: How many words should be in the bank?

A: Maybe around 20, that’s how many times I would consider playing.