2.2 Mapping To Task Order Request Requirements
As shown in Table 2-1, the CSC/PBFI Team has produced detailed system design documentation that responds to the minimum deliverable requirements specified the MDSHA task order request from Mr. Michael Zezeski, dated December 16, 1997.
Table 2-1. Map of Task Order Request Requirements
CSC/PBFI Advantage: The CSC/PBFI Team design documentation meets all of the requirements of the MDSHA task order request.
|
Required Documentation |
Section Addressed In This Deliverable |
|
A functional description of the software that fully defines all processing, displays, interfaces, and databases. |
4.1 User's View of the System 4.3 System Architecture 4.4 Software Design 4.5 Archived Data User Service Appen. B Use Cases/ Sequence Diagrams |
|
A discussion of the selected system architecture and the capabilities of this architecture in comparison with other architectures that have been considered. |
4.3 System Architecture |
|
The design must be consistent with the National Architecture and emerging standards. |
3.3.2 An Open Systems Approach Appen. A CHART II Architecture |
|
A user's view of the system that provides all information related to displays, inputs and outputs. |
4.1 User's View of the System |
|
Life cycle requirements including anticipated hardware and software upgrades to reflect changing requirements and new technology, software and hardware maintenance requirements. |
5.1 Life Cycle Requirements |
|
Estimated operations and maintenance requirements for the system including recommendations regarding both the levels, types and costs of contracting support that might be needed. |
3. Alternative O&M Approaches 4. Staffing Requirements |
|
Database definition documentation that defines the data structure and all data elements to be stored in the system's memory resident and on disk. |
4.4.6 Data Stores Appen. B Use Cases/ Sequence Diagrams |
|
Catalog descriptions of all commercial off-the-shelf (COTS) software to be used during the system development and required for system operation. |
Appen. C COTS Catalog Descriptions |
|
Detailed description of the recommended hardware configuration including all equipment and networks. |
4.3.7 Communications Architecture and Supporting Hardware Solutions |
|
Definition of all size capacities and limitations including the maximum number of field devices, workstations, communications interfaces, detectors, GUI windows, graphic symbols, and database elements. |
4.4.1.1 Windows NT and UNIX 4.4.5.1 Windows NT vs. UNIX |
|
Description of the actions required for system expansion including database, graphical, hardware modifications. |
4.4.5.3.1 Expansion of Existing Capabilities |
|
Description of the procedures that will be required to add new functionality to the system including procedures to incorporate changes in the operator interface(s), database, and techniques required to interface new algorithms with the existing software system. |
4.4.5.3.2 Addition of New Capabilities |
|
Description of system security features and capabilities. |
4.3.8 Security |
|
Description of all failure modes and backup capabilities. |
5.2.3.2 Backup and Recovery |
|
Description of remote field device and central system maintenance monitoring capabilities. |
5.2.3.2.2 Failures and Alarms |
|
Description of the approach required to interface the replacement CHART system with existing traffic management systems operated by other agencies. |
An Open Systems Approach 4.3.6 Legacy Applications and External Communications |
|
Descriptions of the approach required to interface the replacement CHART system with legacy systems operated by the MDSHA. |
Software Architecture 4.3.6 Legacy Applications and External Communications |
|
A detailed staffing plan, schedule and budget for the work. The budget shall identify shared resources or other public-private partnership arrangements that might offer cost reduction potential. |
6.5 Organizing for Success 7 Cost and Schedule |
|
An acceptance plan shall be included with the system requirements document that will fully define all tests to be performed in connection with factory acceptance tests, final system acceptance, and any intermediate evaluations that might be identified in the system schedule. |
4.6.1 Test Planning 4.6.3 Test Execution |