Welcome to ENGR 1181 Team D’s SDP site! Here, you will find anything and everything you need to know about our games. Algorithms, interviews, presentations, user manuals, and much more is all on this site for you to view. Enjoy!!


Table of Contents:

  1. Project Management
    • A.) Team Working Agreement
    • B.) Individual Responsibility Statement
    • C.) Project Schedule
    • D.) Project Notes
  2. Business Plan
    • A.) User Identification Interviews
    • B.) Electronic/Print Advertisement
    • C.) Pitch Video with Demonstration
  3. Software Documentation
    • A.) Introduction
    • B.) User Manual
    • C.) Program Description for Developers
    • D.) Final Algorithm, Flowchart, or Pseudo code
    • E.) Final Program with Comments
    • F.) Discussion
    • G.) Conclusions and Recommendations
    • H.) References



Executive Summary:

Background and Purpose:

For this project, engineers were to use their creativity, planning, and coding skills in order to develop games that could be played in MATLAB. Unlike previous coding projects, where each member was essentially provided with a guide to complete each module, this task pushed each team of engineers to use their current skill set work through the challenges of software development individually. Accomplishing this task would strengthen each team members ability to effectively code in MATLAB, communicate professionally with potential users, and efficiently work through problems as a team. The finished product is a catalog fun games that both team members and outsiders can enjoy.

Results and Analysis:

After weeks of fine-tuning, the team was left with a fully operational game of MATLAB war. The engineers accomplished this by first coding a vector to represent a deck of cards (all numbers and face cards, no jokers), each card was then assigned a specific point value. Next, the software would pull two random cards from the deck vector: one for the player and the other for the computer AI. These two cards would then by compared using relational operators and then depending on whether the player’s card was higher, lower, or exactly the same as the computers card, a specific message was displayed to the user. If the player won it would display “You Win!”, if the player lost it would display “Sorry, You Lose”, and if the player tied a “War” would ensue where the player has the opportunity to gain up to four cards. After each round is over, the player then is presented with the option to either quit or continue. This feature allows the player to determine when to quit, rather than forcing them to play through the entire game. Although the code was a significant portion of the project, the documentation also proved to be a thorough process. In the documentation is where team members fully fleshed out the game design process, gave potential users the opportunity to understand how the product worked, and pitch why it should be “purchased”. From the entirety of this work, team members gather that while development can be challenging, even a group of inexperienced coding students can produce a polished and professional project with enough hard work and dedication.

Summary and Conclusion:
The Software Design Project forced team members to apply their coding and communication skills in many unique ways. From hard knowledge like how to reference vectors, load data sets, and properly use relational operators to soft skills like how to properly speak on a recording or get information from a potential buyer, each team member’s abilities were put to the test. However, the physical result was both a fully functioning game and an extensive documentation on the process. More importantly though are the lessons each team member took away from the project. These being that working with a team can make even large projects seem manageable, time-budgeting is crucial, communication determines the success of your product: not simply the quality, and that the design process is molded around opinions from outsiders and potential buyers. Looking forward, each team member looks to apply their coding skills and further develop their professional communication skills on future projects.