Technology architecture

Review the applications you use and compare configuration, integration or replacement options.

Review the setup before commissioning a build

We assess the current systems before recommending a technology change. The review examines the task each application must support, where records are held and who will maintain the setup. Access restrictions and dependencies on other teams are included.

The options may include keeping or reconfiguring a system, connecting another application, or replacing part of the setup. We compare them against the same requirements, with assumptions and unanswered vendor questions recorded in the options note.

When an options review helps

  • A proposed change crosses several applications and team responsibilities.
  • A vendor proposal and an internal build are difficult to compare.
  • The same information is maintained in several places.
  • The team has not agreed who will maintain the system after launch.

Comparing feasible options

  1. Translate the proposed change into requirements, constraints and decisions.
  2. Map the applications, records and interfaces involved.
  3. Compare feasible options, including implementation work and ongoing support.
  4. Set out a first stage and the dependencies that must be resolved before it starts.

System map and options note

  • A view of the current systems and information flows.
  • An options note with tradeoffs, assumptions and unresolved questions.
  • Proposed ownership, access and support responsibilities.
  • A brief for the first stage of implementation or a vendor discussion.

Limits of the review

A review is limited by the information and system access available. Vendor certification, guaranteed compatibility and specialist security assessments are outside this service.

Contact ResolveOps