wiki:DMS/IntegrationTestPlanV0.0
Last modified 8 years ago Last modified on 08/25/2011 09:51:58 PM

DRAFT Last revised 25 Aug 2011

Revision Date Editor
1 9-24-2010 R Allsman
2 9-28-2010 R Allsman
3 7-13-2011 R Allsman
4 8-25-2011 R Allsman

DMS System Integration Test (IT) Plan

1. Test Plan Identification

  • Baseline Identifier: DMS V0.0
  • Testing Level: Integration

2. References

3. Use Case and Activity Implementations being Validated

The Data Management System UML reference model is maintained by and within the LSST Enterprise Architect model at LSST_SysArch:LSST System Architecture: Physical: Data Management Subsystem: DMS Use Case and Activity Model.

The specific Use Cases and Activities being validated in each DM Release during Construction are specified within Document-12064

4. Features to be tested

The full set of LSST Project requirements which resolve to Data Management responsibility will be tested and verified by the close of the Project Integration and Test period in FY 2020.

5. Approach

5.1 Testing Strategy

Refer to SDP: Verification and Validation, 6.1-4.3 DM Integration Test for the sequenced process by which the testing and validation will occur.

5.2 Test Types

Test types are described in SDP: Verification and Validation, 4.3 Integration Test.

5.3 Overall Test Sequencing

Subsidiary Software Release Project Plans will be constructed for each major software release. The LSST Project schedule specifies a major release once a year and a mid-year minor release.

The testing sequence, broken down by WBS task, is specified in Document-12064. The subsidiary Software Release Project Plans will provide the WBS tasks at finer resolution than this overarching plan.

5.4 Test Coverage Metric

A minimum test coverage metric will be defined prior to Integration and Test commencement.

6. Test Criteria

Each component being integrated into the validated baseline, must successfully complete the integration tests specified to exercise the component. For additional information on test specification, test failure and test resumption, refer to V&V 6.1-4.3 DM Integration Test.

7. Test Deliverables

Refer to:

8. Testing Tasks

8.1 Test Precursor Tasks

The set of tasks necessary to prepare for testing will be described separately for each DMS subsystem.

8.1.1 Alert Production

  • develop Camera/DAQ Test Bed (WBS 02.07.01.08.02)
  • develop Telescope/OCS Interfaces Test Bed (WBS 02.07.01.08.03)
  • develop Test Data (WBS 02.07.01.08.04)
  • develop Test Harnesses and Scripts (WBS 02.07.01.08.07)
  • develop Integration Cluster (WBS 02.07.02.05.02)
  • develop Simulated Data Server (WBS 02.07.01.08.04)

8.1.2 Data Release Production

  • develop Test Data (WBS 02.07.01.08.04)
  • develop Test Harnesses and Scripts (WBS 02.07.01.08.07)
  • develop Integration Cluster (WBS 02.07.02.05.02)
  • develop Simulated Data Server (WBS 02.07.01.08.04)

8.1.3 Calibration Pipeline

  • develop Test Data (WBS 02.07.01.08.04)
  • develop Test Harnesses and Scripts (WBS 02.07.01.08.07)
  • develop Integration Cluster (WBS 02.07.02.05.02)
  • develop Simulated Data Server (WBS 02.07.01.08.04)

8.1.4 Science Data Archive

  • develop Test Data (WBS 02.07.01.08.04)
  • develop Test Harnesses and Scripts (WBS 02.07.01.08.07)
  • develop Integration Cluster (WBS 02.07.02.05.02)
  • develop Simulated Data Server (WBS 02.07.01.08.04)

8.1.5 Operational Control and Monitoring System

  • develop Camera/DAQ Test Bed (WBS 02.07.01.08.02)
  • develop Telescope/OCS Interfaces Test Bed (WWBS 02.07.01.08.03)
  • develop Test Data (WBS 02.07.01.08.04)
  • develop Test Harnesses and Scripts (WBS 02.07.01.08.07)
  • develop Integration Cluster (WBS 02.07.02.05.02)
  • develop Simulated Data Server (WBS 02.07.01.08.04)

8.2 Inter-task Dependencies

TBD

9. Environmental Needs

TBD

See [wiki:XXXXXX? ] for the hardware and operating system specifications of the system to be used for DMS Subsystem integration testing.

Third party software requirements are maintained within the LSST build manifest for each DM Subsystem. The manifest will be reviewed and updated prior to commencement of each subsidiary Software Release Project Plan.

10. Schedule

Refer to Releases v7.pdf for the schedule covering the Construction period for the LSST Project.

11. Planning Risks and Contingencies

TBD Acquire Relevant Risks from the Project Risk Register

11.1 Contingency: Camera/DAQ Test Bed not available

Enhance the test harness to provide, at appropriate times, the requisite events and the data. In other words, simulate the external simulation providing the Camera/DAQ interfaces.

11.2 Contingency: Telescope/OCS Interfaces Test Bed not available

Enhance the test harness to provide, at appropriate times, the requisite events and the data. In other words, simulate the external simulation providing the Telescope/OCS interfaces.

11.3 Contingency: Integration Cluster not available

Co-opt the development cluster.

11.4 Contingency: Simulated Data Server not available

The simple test harness, such as the one providing the existing simulated data, could be employed.

11.5 Contingency: A DM Subsystem has not passed its unit tests

If the failure is not resolvable within a short timeframe, the Release may be delayed until the unit tests succeed or, at the discretion of the DM Project Manager, update of the affected product might be put off for another Release cycle.

12. Test Case Specification

Test specifications will be generated using the EA LsstTool capability.

Appendix

Simulated Input Data

Refer to the Data Challenge Data Handbook for the most recent specifications of the Image Simulation (ImSim) dataset.