Summary

Choose tools and technology that let you build a good service in an efficient, cost-effective way.

Build a sustainable service that allows you to change direction in the future.

Detailed guidance of how to meet this standard can be found in the DfE Architecture Guidance and DfE Technical Guidance.

Why it's important

When you make a decision about technology, you're making a significant investment. The choices you make will have a huge impact on your ability to create, iterate, and operate the service in a flexible, sustainable way.

It's important to make sure you're not working on your own and use learnings from other teams or services where possible. Always try to align technology choices with other DfE teams. The more common components that are created and used, the more efficient you can be in building a great service that meets the Service Standard.

When you make a decision about tools, look across DfE to see what's currently being used. Align with tools being used across other DDT communities as much as possible.

How to meet this standard in every phase

You'll be assessed on what you've done to meet this standard at service assessments. However, even if the service you're working on is not being assessed, it's good practice to consider how you'll meet this standard point.

All phases

Things to consider:

  • evidence that the team has considered different options for how the service will be delivered technically and the rationale for the chosen technical direction
  • technology choices are technically feasible and security assured
  • the tools the team will be using and why they are value for money
  • how the tools and technology you choose meet accessibility standards, including Web Content Accessibility Guidelines (WCAG) 2.2
  • any constraints with legislation, contracts, or technology that impact the service
  • align technology choices with the recommended tech stack used across DfE, where possible
  • a working prototype, technical spikes, or proof of concept using the chosen tools and technology has been built and tested to prove that the architecture is fit for purpose
  • architectural artefacts, decisions, and plans have been documented, shared across your community, and reviewed and assured
  • evidence that the team will continue to re-evaluate and challenge previous decisions as new requirements are discovered
  • demonstration that technology choices are sustainable longer term

Things to avoid in all phases

  • choosing technology without considering long-term sustainability or alignment with existing DfE tech stacks
  • overlooking security assurance when selecting tools and technology

Profession specific guidance

Each DDaT profession in DfE has their own community and guidance.