Table of Contents
Project Management
– Team Working Agreement – Agreed upon values by team
– Individual Responsibility Agreement – Initial and Final Team Assignments
– Project Schedule – Schedule followed by the team
– Meeting Notes – Notes from each of the team’s meetings
Business Plan
– User Identification and Interviews – Idenfitied Users and Interviews with select users
– Electronic/Print Advertisement – Game Advertisements
– Video Pitch with Demonstration – Various Elevator Pitch Videos
Software Documentation
– Introduction – Introduction to the game
– User Manual – General Manual on how to play the game
– Program Description for Developers – Technical Description of how the game runs
– Final Algorithm, Flowchart, or Pseudocode – The game’s final flowchart
– Final Program with Comments – Raw code with comments
– Discussion – Progression of code, Testing Description, Obstacles faced
– Conclusions and Recommendations – Final Conclusions
– References
Executive Summary:
| Group K –Christopher McCann, Carter Langston, Jahiem Mason, Junyi Cheng | Software Design Project |
| Instructor – Dr. Bailey Braaten , GTA – Chante’ Vintes | Date – 12/6/22 |
Executive Summary
Background & Purpose:
- The objective of this project was to use MATLAB and the simpleGameEngine to create playable games for users. This project allowed the team to cement their knowledge of MATLAB, as well as put together all of the collected knowledge during the course of Engineering 1181. Furthermore, this project also served to simulate real-world tasks that engineers would have to go through, such as elevator pitches, software documentation, user interviews, and algorithmic flowcharts. The purpose of this project is quite important as it allows future engineers to practice the skills that they will need in the workforce.
Results and Analysis:
- During the course of this project, the team was able to observe the overall MATLAB proficiency increase greatly. This is largely due to the amount of coding that was put into both the BlackJack game and BrutusTale. BrutusTale ended up being slightly different than we had initially planned, mostly in the battle mechanics. However, the essence of the game stayed consistent throughout development and the finishing of the game. Furthermore, the team also agreed that our efficiency as a team increased greatly. The team was able to figure out how to use everyone’s strengths to operate at maximum efficiency. This was an integral part of being able to complete this project on time as each member put their whole into completing their assigned work.
- The team recognizes that the technical and teamworking skills improved greatly throughout this project. However, it is recognized that there is always room for improvement. The coding team recognizes that the overall BrutusTale code could have been slightly more concise through the use of more functions and simpler organization. The BrutusTale development team also planned to scale the game up further and add music to the game. The Blackjack development team recognizes that the graphics of the game could be improved upon and planned to do so given more time.
Conclusion & Recommendations:
- The team believes that the Software Design Project went quite well and is pleased with the output that was produced. The team believes that all aspects of the Software Design Rubric were thoroughly fulfilled and enjoyed the creation of both BrutusTale and BlackJack. Furthermore, the team would also consolidate the code for both games and add the new desired aspects if given more time. The team recommended that the Software Design Project continue to be assigned as the progression in skill is quite valuable.