1. Life-cycle of the document
The objectif of this document is to provide a scope of work and to be used as work document. It means that it documents the whole work by design, with an initial version created now and evolving over time.
Software developers can challenge this document, but this needs to be justified, analysed and documented, as well as agreed with the operators.
1.1. Change log
| Ver. | Date | Author | Description | Justification |
|---|---|---|---|---|
| 0.1 | 30/12/2024 | Sergio Sousa | Initial version | |
| 0.2 | 07/02/2025 | Sergio Sousa | Modifications of the architecture to include Equipments | |
| 0.3 | 06/03/2025 | Sergio Sousa | Modifications based on LNDS input | |
| 0.4 | 08/04/2025 | Sergio Sousa | Analyst can now also un-approve / un-reject records. Added the possibility to link a phyiscal link to destination unit or destination equipment. Added a section consistency checks where all manual consistency checks performed by the Analyst will be defined Updated API documentation to allow the viewer to retrieve more data. |
Operators need to have access to the entire physical links to be able to compute the eligibility of the customers. |
| 1.0 | 07/04/2025 | Sergio Sousa | Version number changed to 1.0. | |
| 1.1 | 14/10/2025 | Sergio Sousa | Update according to backend implementation and migration to doc.rncv.lu | During the implementation some missing information was detected, the justification for each is documented in the data model chapter. |