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

104 total results found

Architecture documentation

The Architecture Documentation of the National Registry of Vertical Cabling offers an overview of the current systems and expectations from the perspective of key stakeholders, including MyConnectivity. It outlines their expectations for the future, detailing ...

1. Life-cycle of the document

Architecture documentation

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 ...

2. Introduction

Architecture documentation

3. User management & user roles

Architecture documentation

4. User stories

Architecture documentation

6. Organisational Cases

Architecture documentation

7. Processes

Architecture documentation

1.1. Change log

Architecture documentation 1. Life-cycle of the document

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...

2.1. Context

Architecture documentation 2. Introduction

As stated in “Luxembourg’s ultra-high-speed broadband strategy 2021-2025”, connectivity is no longer just a matter of technological advancement, it is a cornerstone of social and economic inclusion in a digitally driven society. While Luxembourg already enjoys...

2.2. Document purpose and scope

Architecture documentation 2. Introduction

The present document describes the data architecture of the NRVC that has been designed to respond to the requirements expressed by the different stakeholders. The document contains: the requirements that were gathered as well as the methodology used to ga...

2.3. Targeted audience

Architecture documentation 2. Introduction

2.3.1. Confidentiality This document is an internal and confidential document and restricted access to selected audience is provisioned. 2.3.2. MyConnectivity and their shareholders MyConnectivity and their shareholders are responsible and accountable for t...

3.1. User management

Architecture documentation 3. User management & user roles

This section explains the general principles how user will be managed in the system. It explains the core concepts that need to be implemented. IMPORTANT: Please note that when we talk about users, we mean API users. The system is designed around APIs which c...

3.2. Roles

Architecture documentation 3. User management & user roles

3.2.1. User Generic User (applies to all roles) A Generic User is a base-level role assigned to every system user, regardless of their specific functional roles (e.g., Viewer, Analyst, Editor, Approver). This role encompasses fundamental use cases and permis...

4.1. User - Profile management [canceled]

Architecture documentation 4. User stories

Id 4.1. Description As a Generic User I need to be able to update my personal information So that my information stays accurate and up to date Priority High Actors User API Calls N/A Linked Processes Status Canceled ...

4.2. User - Change password

Architecture documentation 4. User stories

Id 4.2. Description As a Generic User I want to be able to change my password   So that I can keep my account secure Priority High Actors User API Calls N/A Linked Processes Status Implemented - Only user with ...

4.3. User - Manage user secrets [canceled]

Architecture documentation 4. User stories

Id 4.3. Description As a Generic User I want to be able to manage my secrets linked to the chosen authentication mechanism and to revoke consents given to external applications, So that I can grant and revoke access given to external applications ...

4.4. Application Administrator - Create users

Architecture documentation 4. User stories

Id 4.4. Description As a Application Administrator, I must be able to create user accounts and assigning them the appropriate roles, So that I can control access to the system and ensure that each user has the correct permissions based on their re...

4.5. Application Administrator - Update users

Architecture documentation 4. User stories

Id 4.5. Description As a Application Administrator, I must be able to update user accounts and re-assign them appropriate roles, So that I can control access to the system and ensure that each user has the correct permissions based on their respon...

4.7. Application Administrator - Recover users marked for deletion

Architecture documentation 4. User stories

Id 4.7. Description As a Application Administrator, I must be able to recover a user marked for deletion, So that I can recover the access of a user that was deleted by mistake. Priority High Actors Application Administrator API C...

4.6. Application Administrator - Delete users

Architecture documentation 4. User stories

Id 4.6. Description As a Application Administrator, I must be able to mark a user for deletion, So that I can remove the access for users that no longer require it, and to ensure that personal data linked to old users are properly removed from the...

4.8. Application Administrator - Create access tokens [new]

Architecture documentation 4. User stories

Id 4.8. Description As an Application Administrator I need to be able to create access tokens linked to existing usersSo that I can grant access to the APIs to the different users Priority High Actors Application Administrator API...

4.9. Application Administrator - Delete access tokens [new]

Architecture documentation 4. User stories

Id 4.9. Description As an Application AdministratorI need to be able to delete access tokensSo that I can revoke access to the APIs for the different users Priority High Actors Application Administrator API Calls DELETE /admin/to...

4.10. Application Administrator - View audit logs

Architecture documentation 4. User stories

Id 4.10. Description As an Application Administrator I want to have access to audit logs So that I can find out what actions have been performed in the system and by whom Priority High Actors User API Calls GET /audit-logs GET /a...

4.11. Application Administrator - View all data on the platform

Architecture documentation 4. User stories

Id 4.11. Description As an Application Administrator I need to see everything that happens in the system including the data itself So that I can analyse any potential issues in the system Priority Low Actors Application Administrator ...

4.12. Application Administrator - Restore deleted records

Architecture documentation 4. User stories

Id 4.12. Description As an Application Administrator I need to be able to recover records marked as deleted So that I can rollback invalid changes Priority High Actors Application Administrator API Calls POST /sites/<site_id>/r...

4.13. Application Administrator - Un-reject/approve an approved/rejected record

Architecture documentation 4. User stories

Id 4.13. Description As an Application Administrator I need to be able to un-approve/reject a record that was unintentionally rejected/approved   So that I can rollback invalid changes and allow the approvers to correct their mistakes. ...

4.14. Application Administrator - Export all

Architecture documentation 4. User stories

Id 4.14. Description As an Application Administrator I want to be able to export the entire database in a format that is supported by external analytics platforms (JSON, CSV) such as Tableau So that I can perform analytics no top of my data P...

status
not started