In reviewing the flowdown for provenance requirements on SuperTask and the Butler-related middleware, I noticed that the high-level requirements OSS-REQ-0122, Provenance:
The LSST Data Management system shall record provenance data on all its processing activities: all information necessary to reproduce computed data products from the associated raw data, and to understand the processing history of any data product.
This shall include at least: software version and build information, settings of all configurable parameters, history of processing steps, identification of all calibration constants used in processing, and hardware and operating system configurations used.
and OSS-REQ-0172, Provenance Archiving:
The LSST project shall archive all processing provenance associated with archived data products.
were never properly flowed down to the DMSR. There are numerous DMSR requirements that mention provenance - regarding maintaining it for specific data products, such as coadds (DMS-REQ-0106), or querying against it, and one that mandates a generic provenance mechanism usable in "Level 3" analyses. But there are no explicit functional requirements at DMSR on the creation of the mechanisms or their features.
This makes it hard to verify their flowdown to the middleware requirements, LDM-556, at which level we currently cover some, but not all, of the features required to meet the OSS requirements.