Skip to main content
M3 Playbook > Phase 4: Migration > 4.9 Design and Develop Interfaces
Play Icon

4.9 : Design and Develop Interfaces

Technology
  1. Provider

    Update Interface Control Documents to describe flow of data, security, controls, and processes.

  2. Shared

    Leverage standard interfaces and API to create connections between applications

  3. Shared

    Coordinate with interface partner to agree on data exchanges, integration methods & test timeframes

  4. Provider

    Code and unit test Interfaces

  5. Shared

    Establish batch jobs to execute interfaces and conduct integration testing

4.9 Lessons Learned

  • Maintain a detailed network architecture to help troubleshoot interface design and development issues
  • Conduct frequent checkpoints with interfacing application developers between customer and provider
  • Coordinate early with external interface providers to properly plan testing windows

Stakeholders

Recommended stakeholders, inputs, & outputs may vary by implementation; however, agencies that contributed to this Playbook reported these factors as increasing the likelihood of success.

Customer

  • Program Manager
  • Functional Lead
  • Technical Lead/Solution Architect
  • Development Team
  • Network SME

Provider

  • Program Manager
  • Functional Lead
  • Technical Lead/Solution Architect
  • Development Team
  • Network SME

Inputs

Outputs

  • Interface Control Document

USSM.GSA.gov

An official website of the General Services Administration

Looking for U.S. government information and services?
Visit USA.gov