Specification Change Orders

Specification Change Orders


No. Date Spec Section Description Approvals Updated?
1 15jan97 Sample bogus requirement or spec. This specification is bogus. Fix it. XX,YY NO

Instructions for using this template (delete these instructions after installation of this file):

  1. Store a copy of this file in the administration project 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 a brief description of the affected section of the requirements or specification. Insert an HTML link to the appropriate section of the requirements specification document. IMPORTANT NOTE: this link should refer to the requirements specification document as stored in www.csc.calpoly.edu/~gfisher/projects/alpha/polysuite/subprojects/... . The requirements specifications stored there will remain fixed, so that references to the original documents will remain consistent in case the design group performs the change described for this SCO entry.
  6. For the Description field, provide a reasonably brief description of the change to be made.
  7. When the SCO is approved, enter the initials of the group 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 group's copy of the requirements specification document.