CMPS115, Milestone 2

Preliminary Design Document Instructions

Assignment due in lab: Develop a preliminary design document (PDD) for your game. PLEASE NOTE: Students usually include coding activities during this time. The reason for coding at this time is to determine if something that is needed is possible.

• Functional design document OR object-oriented design document. Examples of the diagrams to use in the PDD are given in the primary textbook. If you use functional design, include both a data flow diagram and a structure chart. If you use object-oriented design, include an object design. Also, list at least two scenarios and make sure that you have added necessary operations and attributes from these scenarios into your object design. In either case, you will need to include the names of the data structures and all of the modules. Include in the module specification the purpose of the module, its interface,the modules it invokes, and the estimated size of the module in LOC (lines of code). If using OO design, distinguish between public and private parts of the module specifications. You will be graded on the completeness of your design. We need to verify that you have a good design. Please include any work documents that you created to produce your preliminary design. For example, if you have created your design using OOD, then you could include the scenarios and sequence diagrams that you created to assist you in producing your PDD. In addition, it is generally expected that a design undergoes numerous revisions before one is agreed upon. I expect to see earlier designs that have been rejected in your project notebook. Put the rejected designs with this milestone. Please label them as rejected. This part is worth 75% of the PDD points.
• Any assumptions made. This refers to assumptions that you made about available software resources (include files and other vendors' source files). Additionally, if there were critical issues and trade-offs that were considered in generating the design, include the information about these issues here. This can include issues such as external file formats or assumptions about how system may be used by the user.
• Requirements tracing. List each major requirement and then list the modules that you have included to implement that requirement. Check your game rules and see if you have included each of these rules in at least one module. This is worth 15% of the PDD points.
• Group time recording log. This is worth 5% of the PDD points.
• Group meeting notes. This is worth 5% of the PDD points.

Acknowledgements: I would like to gratefully acknowledge Linda Werner, the author of this assignment.