Use case list
Summary
We should write down the use case list. Deriving this list from the list of requirements seems to be a good idea if there must be a high-level of correspondence between requirements and use cases (see coordinators' comment here).
A one-to-one correspondence would generate too many use cases, the requirements should probably first be grouped to define more precise use cases. Minor divergences between e.g. different types of data can be specified inside one use case rather than generate different use cases with almost the same body.
Use case list
Map data to calibration parameters - Done
Description: The QualPipe accesses the CalibPipe database to check that to all data products can be associated calibration parameters (through time and array configuration).
Related requirements: B-DPPS-1330
Sub-issue #31 (closed)
IRF production - In progress
Description: The CalibPipe receives the notification that new MC simulations have been produced in the SimPipe database and calculates IRFs from the MC data.
Related requirements: B-DPPS-1460, B-DPPS-3200, B-DPPS-3210, B-DPPS-3220, B-DPPS-3230, B-DPPS-3255, B-DPPS-37xx
Alternatives: Muon images for alternative PSF.
Sub-issue #24 (closed)
Atmosphere and throughput calibration - Done
Description: The CalibPipe receives new calibration data for atmospheric and throughput calibration and calculates the associated calibration coefficients.
Related requirements: B-DPPS-2205, B-DPPS-2250, B-DPPS-2310, B-DPPS-3540, B-DPPS-3550
Alternatives:
- Cherenkov transparency coefficient (No requirement ref, title: "Cherenkov Transparency Coefficient for Cat-A data")
- Muon images (B-DPPS-2330)
- Muon images for the relative reflectance of each mirror (B-DPPS-37xx)
Sub-issue #25 (closed)
Flat-field monitoring - Done
Description: The CalibPipe receives new flat-field events from the observatory and must derive the corresponding calibration coefficients with an analysis uncertainty of less than 2% rms.
Related requirements: B-DPPS-3560, B-DPPS-37xx
Alternatives: Muon images.
Sub-issue #28 (closed)
Array pointing - Done
Description: From productions of the gamma-ray direction reconstruction algorithm, the CalibPipe must calculate the systematic mispointing of sub-arrays of telescopes.
Related requirements: B-DPPS-3570, B-DPPS-3580
Sub-issue #27 (closed)
Atmospheric extinction maps - Done
Description: The CalibPipe receives new atmospheric data from on-site measurements and is asked to produce an atmospheric extinction map.
Related requirements: B-DPPS-3600
Sub-issue #33 (closed)
Array calibration - To do
Description: The CalibPipe receives input data from array-level calibration light sources and calculates array-level calibration coefficients.
Related requirements: B-DPPS-3610
Sub-issue #34 (closed)
Calibration from gamma-like events - Done
Description: The CalibPipe must produce calibration parameters directly from the analysis of gamma-like Cherenkov images.
Related requirements: B-DPPS-3620
Sub-issue #35 (closed)
Query to the CalibPipe database - Done
Description: An actor (can be human e.g. Simulation Scientist or system e.g. SimPipe) accesses the CalibPipe database to retrieve calibration information. This should be distinguished from the configuration change use case here.
Related requirements: None
Sub-issue #42 (closed)
Ignored requirements
- B-DPPS-0110 and B-DPPS-0120. Related to access rights management.
- B-DPPS-2200: Too general and mostly related to the DataPipe.
- B-DPPS-1895? and others (no ref): General software requirements.
- B-DPPS-2210: Too general (error estimation).
- B-DPPS-2280: Mostly the responsibility of the DataPipe ?
- B-DPPS-2320: Mostly the responsibility of the DataPipe ?
- B-DPPS-3110: Too general and applies to all CalibPipe productions.
- B-DPPS-3240: Too general.
- B-DPPS-3500, B-DPPS-3510, B-DPPS-3520, B-DPPS-3530: Related to error budget (quality rather than functional requirements).
- B-DPPS-3650, B-DPPS-3660, B-DPPS-3710: Related to error budget (quality rather than functional requirements).
- B-DPPS-2280 and its counter-part ("Array timing correction", no ref.): Should be included in a use case but for now I am not sure if they should have their own use case or not.