5G-EMERGE

Information Flow

This page describes how information flows between the upstream SharePoint source documents and the testbed website (DBR).

For the identity and description of each source document, see Information Sources.

Current State — Unidirectional

The current process is unidirectional: the five SharePoint sources are inputs; the DBR is the output and consolidation.

EBU SharePoint
┌─────────────────────────────────────────────────────────┐
│                                                         │
│  SAI ──────────────────────────────────────────────┐    │
│  (service architecture & interface definitions)    │    │
│                                                    │    │
│  TVR ───────────────────────────────────────────── ┼──► │  DBR (Git)
│  (test beds, test specs, scenarios, KPIs)          │    │  ──────────────────
│                                                    │    │  • Test status cards
│  STM ───────────────────────────────────────────── ┼──► │    (per WP/testbed)
│  (E2E scenario → testbed mapping)                  │    │  • Component mapping
│                                                    │    │    spreadsheet
│  GTL ───────────────────────────────────────────── ┼──► │  • Reference docs
│  (all test cases, testbed assignments, KPIs)       │    │  • Dashboard HTML
│                                                    │    │
│  CTM ───────────────────────────────────────────── ┘    │
│  (Strand 2 component → testbed mapping)                 │
│                                                         │
└─────────────────────────────────────────────────────────┘

The DBR is a superset of the upstream sources. For each test area it additionally holds: status tracking (Overall Status, Confidence, Progress %), execution detail (test run counts, latest result, environment), findings and risks, actions and next steps, cross-references between related test statuses, and the rendered navigable dashboard.

Future State — Bidirectional

The intended future state is a bidirectional relationship: status updates and findings recorded in the DBR will flow back to inform (and potentially update) the upstream source documents.

EBU SharePoint ◄────────────────────────────────────────────────────────┐
┌─────────────────────────────────────────────────────┐                 │
│  TVR · SAI · GTL · CTM · STM                        │  ◄── (future)   │
│   (authoritative specs & plans)                     │                 │
└─────────────────────────────────────────────────────┘                 │
              │                                                          │
              ▼  (current)                                               │
         DBR (Git)  ────────────────────────────────────────────────────┘
         (status tracking, findings, KPI results)

Planned bidirectional flows include: KPI results back-populated into GTL and TVR; risk and blocker flags surfaced as action items in GTL or TVR review sections; new test cases proposed from field work into GTL; component deployment confirmations from partners triggering CTM updates. The mechanism for this reverse flow is to be defined in a future phase.

Related Pages