Uncategorized

3. Software Documentation

by at

This section contains the software documentation for the design project.  This includes an introduction to the project, manuals for the project, detailed discussion of the code, and the results.

  • Introduction
  • User Manual
  • Program Description for Developers
  • Final Algorithm, Flowchart, or Pseudocode
  • Final Program with Comments
  • Discussion
  • Conclusions and Recommendations
  • References

B. Individual Responsibility Agreement

by at

Each team member must take the lead on the development of at least 0.5 point of a game. So if you have a 1 point game you should have 2 people working on it sharing equal responsibility.  Additionally, all members must have equal roles in the documentation and the video.

Complete the tables below describing the initial plan, and the end results. After this page is complete, each team member must comment on this post certifying their participation with the following sentence.  “I have participated in this project and completed the work described above.”

Programming Responsibilities/Roles

Team Member Initial Plan End Result
Anna Adventure Game (Gameplay, inputs, design)
Scott Complete Pre-Design of Othello (Rules, Player Names, Initial Gameplay etc…)
 Seth Adventure Game (Gameplay, input, design)
Trey Finish Design for gameplay in Othello

 

Documentation Responsibilities/Roles

Team Member Initial Plan End Result
Anna  Adventure (Intro, User Manual, References, Conclusion and Recommendations with Seth, Final Program, Discussion)
Scott  Othello (Flowchart, Final Program, References, Recommendations, Discussion)
 Seth  Adventure (Flowchart, References, Conclusion and Recommendations with Anna, Program Description)
 Trey  Othello (Final Program, References, Program Description, Conclusions)

 

Video Responsibilities/Roles

Team Member Initial Plan End Result
 Anna  Script/Speaker
 Scott  Speaker/Editor
Seth  Speaker/Editor
 Trey  Main Camera/Speaker