CSC 309 Specification Change Orders



No. Date Spec Section Description Approvals Updated?
1 5jan11 Base spec From CSC 308 Fall 2011, Morning Section. XX,YY NO
2 5jan11 2.X.Y P5 This section has two clerical errors: ... .                      XX,YY NO
3 7jan11 2.Y.Z This will section be designed and implemented to Level 1.5; the following specific features will be implemented ... ; the following features will not be implemented ... . XX,YY NO
4                          . . .    



The following are instructions for using this template; delete the instructions, and the example table entries, after installation of the file.

  1. Store a copy of this file in the project administration directory, under the name scos.html.

  2. For each SCO, add a new table row in the table format given above.

  3. For the No. field, put the number of the SCO, starting from 1.

  4. For the Date field, enter the date that the SCO was initially recorded, using the same ddmmmyy date format as described in ./meeting-minutes-template.html.

  5. For the Spec Section field, provide the number of the affected section of the requirements specification, down to the individual paragraph number if necessary. The section/paragraph number should link to the actual section in the requirements specification document.

    IMPORTANT NOTE: The spec section link should refer to the requirements specification document as stored in www.csc.calpoly.edu/~gfisher/classes/309/specs/... . The requirements specifications stored there will remain fixed, so that references to the original documents will remain consistent in case the design team performs the change described for this SCO entry.

  6. For the Description field, provide a description of the change(s) to be made.

  7. When the SCO is approved, enter the initials of the team leader and overall project leader (Fisher) in the Approvals field,

  8. For the Updated? field, enter "YES" or "NO" to indicate if the change described in this table entry has been made in the design team's copy of the requirements specification document. In most, if not all cases, the entry will be "NO".