c. Chapter 3 - Issues. Issues shall be presented in a table
(see Table I-A-2) or an outline containing the same data. Operational issues
shall be grouped under the mission impacted, then under the functional
capability impacted under that mission. When an issue involves more than one
mission, subsequent missions shall be marked with the previous issue number
and those fields that are the same as the original, should be marked as such.
If the issue's impact differs between missions, then the description for each
mission may also differ accordingly. The following minimum column headings:
Issue Number; Supporting System; Issue, Issue Description; Issue Impact; and
Mitigation Strategy or Resolution Path). Number each issue as “C-#” for
critical shortfalls and “S-#” for substantive issue. Issues shall include
resolution paths with projected dates to be corrected. If resolution details
are not known, a discussion on the approach (including anticipated responsible
parties) shall be provided.
Table I-A-2. Issue Summary