Because the I-394 ICMS is a System of Systems, it is conceivable that separate developers might develop different portions of the overall system. Similarly, for some of the systems, existing systems may be enhanced or expanded to address the ICMS requirements. Also, during operations, each agency will operate their systems as part of the overall ICM approach. For these reasons, Table 20 defines a set of requirements for documentation to be prepared for the systems and for training on the systems.
Table 20: Documentation and Training Requirements
| ID |
Requirement Description |
Source |
Allocation |
Criticality |
| DOC-1 |
The ICMS Systems shall be documented. |
All |
All |
H |
| DOC-1-1 |
The ICMS Systems final deliverables shall include a basic level of software documentation.
The ICMS Systems final deliverable shall include software source code documentation that includes a basic level of detail that is agreeable to all developers to be defined following the design period. |
All |
All |
H |
| DOC-1-2 |
Documentation shall be electronic.
The ICMS Systems final deliverables shall include electronic software source code documentation that is searchable and can be cut and pasted into other documents. |
All |
All |
H |
| DOC-1-3 |
Procedures shall be documented
The procedures for using the ICMS Systems shall be documented. |
All |
All |
H |
| TRAIN-1 |
The ICMS Operators shall be trained. |
All |
All |
H |
| TRAIN-1-1 |
ICMS operators shall be trained on the overall ICMS.
The operators within each agency shall receive overall high level training of the entire ICMS in order that they will understand the collective functions and procedures. |
All |
All |
H |
| TRAIN-1-2 |
ICMS operators shall be trained on individual systems.
The operators within each agency shall receive detailed training on the functions and procedures of the ICMS system(s) they will operate and/or administer. |
All |
All |
H |
Previous | Next
