chore: complete runtime and builing block views for access request submission

Author: brunopacheco1

docs/access-request-submission/assets/access_request_submission_sipoc.drawio.png

@@ -0,0 +1,3 @@
+SPDX-FileCopyrightText: 2026 PNED G.I.E.
+
+SPDX-License-Identifier: CC-BY-4.0

docs/access-request-submission/assets/access_request_submission_system_context.drawio.png

@@ -9,4 +9,47 @@ description: Static decomposition of the system, abstractions of source-code, sh
 
 # Building Block View
 
-To be added soon.
+This section describes the static decomposition of the system components involved in the Access Request Submission process. It maps the operational steps identified in the SIPOC diagram (dataset selection, collaborator contributions, application completion, signing confirmation, and cost estimation) to the underlying technical building blocks.
+
+## Whitebox Overall System
+
+This level describes the main components required to support the access request submission workflows, enabling users to create and submit data access applications with dataset selection, collaborator contributions, and signing official confirmation.
+
+To support the processes outlined in the runtime view—such as dataset selection, application form completion, collaborator contributions, submission initiation, signing official confirmation, and cost estimation—the system must be decomposed into functional components that handle distinct responsibilities, ensuring data integrity, governance compliance, and auditability.
+
+![System Context](./assets/access_request_submission_system_context.drawio.png)
+
+### Contained Building Blocks
+
+1. **User Portal**
+   - **Responsibility:** Serves as the primary web interface for users to interact with the access request submission system. Provides user-facing workflows for main applicants to create, edit, and submit access applications. Enables collaborators to view and contribute to shared draft applications. Provides interfaces for signing officials to review and confirm access request submissions. Routes user actions to backend systems and presents application status and updates.
+
+2. **Dataset Catalogue**
+   - **Responsibility:** Maintains the inventory of available datasets accessible through the 1+MG network. Enables users to browse, search, and view dataset metadata, availability information, and associated terms of use. Responds to dataset queries from the User Portal and provides dataset information for application completion.
+
+3. **Access Request Governance**
+   - **Responsibility:** Manages the governance and validation aspects of access request applications. Confirms dataset accessibility for datasets selected in access applications, ensuring data protection compliance. Receives submitted access requests from the User Portal and validates them before forwarding to downstream processes. Maintains the authoritative record of submitted applications and their governance status.
+
+4. **Access Request Operator**
+   - **Responsibility:** External actor responsible for receiving submitted data access applications and initial cost summaries from the submission system. Informs Central Coordination about initial cost estimates. Acts as the liaison between the submission system and Central Coordination for downstream review processes (conformity checks, ethics review, access decisions).
+
+### Important Interfaces
+
+- **Main Applicant - User Portal:** Web interface for main applicants to create, edit, correct, and submit access applications.
+- **Collaborator - User Portal:** Web interface enabling collaborators to view and contribute to shared draft applications.
+- **Signing Official - User Portal:** Web interface for signing officials to review and confirm access request submissions.
+- **User Portal - Dataset Catalogue:** API integration for users to query and retrieve available datasets, metadata, and terms of use.
+- **User Portal - Access Request Governance:** API integration for submitting access applications and receiving confirmation of dataset accessibility.
+- **Access Request Governance - Dataset Catalogue:** API integration to confirm dataset accessibility for selected datasets.
+- **Access Request Governance - Access Request Operator:** Interface for transferring submitted applications and communicating initial cost estimates.
+- **Access Request Operator - 1+MG Central Coordination:** External interface for delivering submitted data access applications and initial cost estimate information to Central Coordination.
+
+### Data Types
+
+| Name                            | Risk Classification | Comments                                                                                                                                                |
+| :------------------------------ | :------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Select Datasets**             | Low                 | List of datasets chosen by users from the Dataset Catalogue for their access request.                                                                   |
+| **Details from Collaborator**   | Medium              | Information and documentation provided by collaborators contributing to the application.                                                                |
+| **Details from Main Applicant** | Medium              | Information and documentation provided by collaborators contributing to the application.                                                                |
+| **Data Access Application**     | Medium              | Structured data entries completing the access application form including research purpose, intended use, investigator details, and data handling plans. |
+| **Initial Cost Summary**        | Medium              | Preliminary cost assessment report based on datasets requested and project scope. Communicated to Central Coordination via Access Request Operator.     |

docs/access-request-submission/assets/access_request_submission_system_context.drawio.png.license

@@ -19,30 +19,30 @@ This section details the dynamic behavior and scenarios involved in the Access R
 
 ![SIPOC Analysis](./assets/access_request_submission_sipoc.drawio.png)
 
-## Create Data Access Application
+## Create data access application
 
-A user initiates the access request by selecting the desired datasets and creating a draft data access application. This draft serves as the foundational document where all requirements, research goals, and required data variables will be detailed.
+Once the desired datasets are identified, the main applicant initiates a new data access application. The system creates a draft application and associates the selected datasets with it. This step establishes the foundation of the application that will be progressively completed through subsequent collaboration and data entry steps.
 
-## Invite collaborator from the same organisation (optional)
+## Invite collaborators from the same organisation (optional)
 
-If the research project involves multiple individuals from the same organisation, the primary user can invite them as collaborators. These collaborators can then contribute to filling out and reviewing the data access application.
+The main applicant may invite other individuals from their own organisation to contribute to the access application. These collaborators can view and edit the draft application, providing additional research details, methodological information, or compliance documentation required for the application to be complete.
 
-## Invite collaborator from the different organisation (optional)
+## Invite collaborators from different organisations (optional)
 
-For cross-organisational research projects, the primary user has the option to invite external collaborators. This facilitates joint research efforts by allowing members from different vetted organisations to collaborate on a single data access application.
+In cases of multi-institutional research projects, the main applicant can invite collaborators from different organisations to participate in the access application. These collaborators can access the shared draft application and contribute their organisational details, roles, and relevant information to support the application submission.
 
 ## Fill application
 
-The user, along with any invited collaborators, provides the necessary details within the application form. This includes specifying the research purpose, methodology, requested datasets, and ensuring all ethical and legal requirements are addressed.
+The main applicant and any invited collaborators complete the structured application form with all necessary information. This includes research purpose, intended data use, investigator qualifications, data security measures, compliance certifications, and other details required by the network. The application evolves through multiple updates as collaborators contribute their sections.
 
 ## Start application submission
 
-Once the application is fully completed, the user initiates the submission process. This action typically forwards the finalized draft to the user organisation's signing official for formal approval before it reaches the data access committee.
+Once the application is fully completed and all required information is provided, the main applicant initiates the formal submission process. This action transitions the application from draft status to pending submission, triggering the workflow for signing official confirmation and downstream processing.
 
 ## Confirm submission by the signing official
 
-The designated signing official from the user organisation reviews the application. By confirming the submission, the official provides organizational endorsement, verifying that the request aligns with the organisation's policies and the terms of service.
+A designated signing official from the user organisation reviews the completed application to verify its accuracy and confirm that the applicant is authorized to submit the request on behalf of their organisation. The signing official provides formal confirmation through a secure authentication mechanism before the application can be officially submitted to Central Coordination.
 
 ## Inform about initial cost estimates
 
-Upon receiving the submitted application, the 1+MG DAC reviews the request and provides the user with an initial estimate of the costs associated with data provisioning, processing, or egress, allowing the user to secure necessary funding or approvals.
+After the signing official confirms the submission, the system calculates and communicates initial cost estimates for the access request to Central Coordination. These preliminary estimates are based on the selected datasets, project scope, and complexity, informing the coordination point about anticipated resource requirements for processing the access request through subsequent review stages.