requirements whose fulfillment they will determine. The document should include a requirements-to-test procedure matrix that shows the test coverage relationship among the tests and the requirements. Every requirement should have at least one test case associated with it and each test case should have at least one requirement associated with it. Test Cases. Each test case include a set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular path within a system or a software application or to verify compliance with a specific requirement or set of requirements. Test Procedures. Test Procedures spell out exactly how one verifies and validates that the component of the system undergoing integration actually functions as intended and as desired. If test data are going to be used as part of the verification and validation process in this step, the test procedures should also spell out how one will determine that the system actually performed the correct transformations on the data entered. Test Data. Test Data should include scripts used to execute software operations, data that must be entered by someone as part of the process of verification and validation of the system and its component integration, or a description of what system-generated data will flow through different components of the system to accomplish a system function. Test Results. Documents that describe the results of each test conducted. Operations and Maintenance Plans. Operations and Maintenance (O&M) plans should describe policies and high-level procedures governing operation and maintenance of the system. Minimally, it should address the activities described in the project’s Concept of Operations and any other activities needed to achieve the project’s objectives. Note: The Recipient may elect to conduct formal walkthroughs (see IEEE Standard 1028-1997) for key systems engineering deliverables to solicit inputs and feedback from stakeholders to help ensure consensus. To support knowledge and technology transfer efforts, all systems engineering documentation developed for the Smart City Demonstration should be developed with the intent to share publically and be formatted for Section 508 compliance.
requirements whose fulfillment they will determine. The document should include a requirements-to-test procedure matrix that shows the test coverage relationship among the tests and the requirements. Every requirement should have at least one test case associated with it and each test case should have at least one requirement associated with it. Test Cases. Each test case include a set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular path within a system or a software application or to verify compliance with a specific requirement or set of requirements. Test Procedures. Test Procedures spell out exactly how one verifies and validates that the component of the system undergoing integration actually functions as intended and as desired. If test data are going to be used as part of the verification and validation process in this step, the test procedures should also spell out how one will determine that the system actually performed the correct transformations on the data entered. Test Data. Test Data should include scripts used to execute software operations, data that must be entered by someone as part of the process of verification and validation of the system and its component integration, or a description of what system-generated data will flow through different components of the system to accomplish a system function. Test Results. Documents that describe the results of each test conducted. Operations and Maintenance Plans. Operations and Maintenance (O&M) plans should describe policies and high-level procedures governing operation and maintenance of the system. Minimally, it should address the activities described in the project’s Concept of Operations and any other activities needed to achieve the project’s objectives. Note: The Recipient may elect to conduct formal walkthroughs (see IEEE Standard 1028-1997) for key systems engineering deliverables to solicit inputs and feedback from stakeholders to help ensure consensus. To support knowledge and technology transfer efforts, all systems engineering documentation developed for the Smart City Demonstration should be developed with the intent to share publically and be formatted for Section 508 compliance.
NOFO%20Smart%20City%20Challenge%20Phase%202.docx