5. Functional requirements

5.1. Core system

The core system comprises all parts of the application that are part of the scope of the NRVC project. This includes

• The register’s address database - this database is mainly used as cache and will be a consolidation of external address databases that are considered as being the source of truth. The register’s database will contain links to these external database in form of external IDs that will be stored to be able to reconcile / override the existing data with fresh data from the Address Data Providers.
• The NRVC data - this is the database that will contain the core data of the system (sites, blocks, units, equipments, …)
• File storage - will be used to store pictures
• Administration API - the endpoints that are meant for the Application Administrator roles
• Administration Panel - the panel that are meant for the Application Administrators. This panel will consume the Administration API
• Private Address Ingestion API - the endpoint used to populate the register’s address database with validated data from the external Address Data Providers
• Authentication & Authorisation - will be the service used to authenticate and authorise access to the users of the core system
• Register’s API - Is the main API used by all different Organisations that will produce and consume data from the NRVC
• Processes & Automations - represents the automations and validation processes that will be implemented by the backend

5.2. Supporting systems

• Backups - External backup systems
• Monitoring and Audit logs - External monitoring and audit log tools

5.3. Trusted parties

• Application Administrator - Represents the application administrator (MyConnectivity)
• ETL - The ETL process that will consolidate addresses from the Address Data Providers and ingest it into the core system
• Address Data Providers - Partners that have reliable address databases

5.4. External users

• Data Producers - the operators or other contributors / consumers of the NRVC data, that will access the system using the pre-defined user roles
• Frontend user interfaces - The data producers can implement their own user interfaces or integrate the APIs directly in their systems. These frontends or other integrations are out of scope of this project.