Skip to main content

Public sector

Information system interoperability programme

Secure the requirements, the functional governance and the quality of deliverables on an interoperability programme.

  • Interoperability
  • Governance
  • Requirements
  • Quality assurance
Network of walkways and connected structures, evoking data exchange between organisations

Context

An interoperability programme intended to allow the secure exchange of data between information systems belonging to separate organisations, over an infrastructure built on X-Road. The programme brings together several parties — business owners, technical teams, integrators — whose rhythms and frames of reference differ.

The challenge

To hold the functional need and the technical implementation together. On a cross-organisation exchange programme, most of the risk sits in how interface requirements are written, in their traceability, and in demonstrating that what is delivered is indeed what was asked for.

What AXENEO did

The work we carried out

  1. 01

    Functional scoping and requirements

    • Gathering and analysis of the needs expressed by the business owners
    • Formalisation of the functional requirements and of the exchange requirements
    • Traceability from need to requirement to test case
    • Assessment and arbitration of the gaps between need and implementation
  2. 02

    Functional governance

    • Structuring of the bodies and of the functional decision circuits
    • Responsibility matrix and ownership of requirements
    • Conditions for moving between phases, and acceptance criteria
    • Coordination between the functional and technical parties
  3. 03

    Quality assurance and validation

    • Test strategy and test plan by level
    • Design of test cases tied back to requirements
    • Functional validation and end-to-end exchange testing
    • Control of deliverables and defect tracking through to closure

Results

What the set-up changed

Results are described qualitatively. We do not publish figures we would not be able to document.

  • A traced requirements repository, shared between the functional and technical parties.

  • Functional governance with explicit bodies and phase-gate conditions.

  • Deliverables checked against acceptance criteria defined up front.

  • A documented alignment between the need expressed and the technical implementation.

Contact

A comparable situation?

We can walk you through the approach taken, the difficulties met along the way, and what we would do differently.