CMPS115 Milestone 6
Linda Werner
Code Instructions
Assignment due at the end of the sixth week. Location is to be specified
by your group's designated TA/instructor.
- A coding standard. Develop a group coding standard. Consider the
issues discussed in the textbook in chapter 7 about style and standards
when developing your standard. At the minimum, the following items
should be covered: naming conventions for variables, functions, and classes;
use of white space including indention and blank lines; braces; header
contents and format; in-line and block termination comments; and the use
of constants in place of magic numbers.
- Hard copy of code. Using this standard, implement (code) your game. The
program is not required to work correctly YET, however, it is required
to be a complete body of code. The code should be internally consistent.
If there is a call to
function A, the code for function A should be provided. The code should
be an extension of the file that you started in the detailed design
milestone.
- Trace. You ARE required to include the tracing of the modules to
the requirement specification. Take each of the rules of the game and
list what code classes/member functions exist to implement that rule.
Do the trace in the reverse order - take each class/member function and
list what rule it implements (or partially implements). You did this
trace for the detailed design milestone. Any inconsistencies with that
trace should be documented with reasons for the differences (ie. member
function as initially planned was not well-designed because it
implemented two separate functions. It was split into
the following two member functions.)
Update the class diagram to reflect any changes (any additional
classes need to be refected in the class diagram). Include a copy of
the updated class diagram and use a special notation to indicate changes
(ie. highlight changes).
- Group time recording log.
- Group meeting notes.