G. Conclusions and Recommendations

The software design project tested many of the skills learned in this fundamentals of engineering course. Table Q used teamwork and problem solving strategies from early in the semester along with our knowledge of MATLAB to create a simple game that could be played on MATLAB. Coding the games went fairly smoothly because whenever we ran into an error or some sort of road block we put our heads together and were able to break through and find the solutions. We spent the majority of class time working on the code of the games. In future projects when the whole group is together we should talk about what is done and what needs to be done and spend more time working on the project on our own.

This software design project also tested our technical communication skills that were learned at the beginning of the semester. This website was used to document the progress of the project. Table Q procrastinated much of the documentation and in the future it really should be done as the game is being made.  Weekly meetings outside of class can help with this so everybody on the team is up to date on where the project is and where the team wants to take it next.  The documentation of the project makes it similar to real life work scenarios. In almost all cases when given a task you are expected to document the project.