Skip to main content
Advanced Search
Search Terms
Content Type

Exact Matches
Tag Searches
Date Options
Updated after
Updated before
Created after
Created before

Search Results

97 total results found

4.55. Organisation Approver - Approve delete equipment request for organisation

Architecture documentation 4. User stories

Id 4.55. Description As an Organisation Approver,   I need to be able to approve equipment deletion requests from Editors linked to my Organisation,   So that I can guarantee that no equipment is deleted by mistake and to preserve the qualit...

4.56. Organisation Approver - Approve or reject update vertical cabling request for organisation

Architecture documentation 4. User stories

Id 4.56. Description As an Organisation Approver,   I need to be able to approve an update vertical cabling request from Editors linked to my Organisation,   So that I can guarantee that the data updates performed on the registry are accurat...

4.57. Analyst - Access to all data

Architecture documentation 4. User stories

Id 4.57. Description As an Analyst,   I need access to all the data in the System,   So that I can apply visualisations and perform advanced analytics on the available data and extract valuable insight. Priority High Actors Ana...

status
to_be_reviewed

4.58. Analyst - Querying data

Architecture documentation 4. User stories

Id 4.58. Description As an Analyst,   I need perform advanced queries on the available data,   So that I can extract specific datasets for further analysis. Priority High Actors Analyst API Calls GET /sites GET /blocks...

4.59. Analyst - Query historical data

Architecture documentation 4. User stories

Id 4.59. Description As an Analyst,   I need to be able to analyse trends in the vertical cabling infrastructure and historical evolutions,   So that I determine the progress and trends of vertical cabling adoption over the years. Pri...

4.60. Analyst - Query audit logs

Architecture documentation 4. User stories

Id 4.60. Description As an Analyst,   I need to be able to analyse the audit logs,   So that I perform advanced analytics on changes performed on the system. Priority Medium Actors Analyst API Calls GET /admin/audit-logs ...

4.61. Analyst - Export data [to be reviewed]

Architecture documentation 4. User stories

Id 4.61. Description As an Analyst,   I must be able to export all or part of the data,   So that I can analyse the data in external analytics tools or import it into other systems. Priority High Actors Analyst API Calls ...

status
to_be_reviewed

4.62. Analyst - Integrate external applications [to be reviewed]

Architecture documentation 4. User stories

Id 4.62. Description As an Analyst,   I must be able to integrate external application with the register,   So that I can access the data from within these applications in order to perform advance analytics (e.g. Tableau). Priority H...

status
to_be_reviewed

4.63. Analyst - Un-reject/approve an approved/rejected record

Architecture documentation 4. User stories

Id 4.63. Description As an Analyst   I need to be able to un-approve/reject that do not comply with the quality standards defined.   So that I can rollback invalid changes and allow the approvers to correct their mistakes. Priority ...

status
to_be_reviewed

4.64. Viewer - Search sites/blocks/units/equipments by address

Architecture documentation 4. User stories

Id 4.64. Description As a Viewer,   I must be able to search for sites, blocks, units or NTPs by address,   So that I can determine the vertical cabling status of a given site, block, unit or NTP. Priority High Actors Viewer ...

4.65. Viewer - Read single entries by ID

Architecture documentation 4. User stories

Id 4.65. Description As a Viewer,   I must be able to access any site / block / unit / connection / ntp by ID,   So that I can retrieve detailed information on a given database entry. Priority High Actors Viewer API Calls ...

4.66. Viewer - Read different versions of connections

Architecture documentation 4. User stories

Id 4.66. Description As a Viewer,   I must be able to access a specific physical link version,    So that I can compare previous and new versions of a physical link and understand the works that have been performed on site. Priority ...

4.67. ETL - Retrieve addresses

Architecture documentation 4. User stories

Id 4.67. Description As an ETL user,   I must be able to read all address information present in the NRVC address database,    So that I can determine the changes that need to be performed on the address database to synchronise it with the e...

4.68. ETL - Create and update addresses

Architecture documentation 4. User stories

Id 4.68. Description As an ETL user,   I must be able to create and update address on the NRVC address database,   So that I can populate new addresses or correct / approve existing ones. Priority High Actors ETL API Calls...

5. Functional requirements

Architecture documentation

The background colors of the above image are to be interpreted as: purple: the core application a.k.a. backend that will be built in the context of this project green: supporting systems that will be used in the context of this project blue: tru...

6.1. User management

Architecture documentation 6. Organisational Cases

All user management use cases are covered by the processes below. Processes 7.1. User management process

6.2. Address ingestion

Architecture documentation 6. Organisational Cases

The background colors of the above image are to be interpreted as: purple: the core application a.k.a. backend that will be built in the context of this project green: supporting systems that will be used in the context of this project blue: tru...

6.3. Versioning, approvals and audit logs

Architecture documentation 6. Organisational Cases

In order to fulfil the needs of the different parties, guarantee the data quality and accountability of each actor, three different mechanism are put in place: Mechanism Purpose Concerned data Audit logs The purpose of audit logs is to kee...

6.4. Data privacy

Architecture documentation 6. Organisational Cases

Data privacy has been one of the key considerations will design the data architecture of the NRVC. you will find below the key principle we followed during the development of the data architecture. Principle 1: Data minimisation Description Only data that i...

6.5. Data quality

Architecture documentation 6. Organisational Cases

A lot of mechanisms are used to guarantee data quality. You will find below a brief explanation of all the mechanisms used and a link to the documentation where you can see them in action. Data dictionary Definition The data dictionary contains all the term...