TDA Submission Template - Architectural Alignment
Introduction
This guidance has been designed to help project teams submitting proposals to the Technical Design Authority (TDA) using the TDA Submission Template.
Teams are asked to supply details of how their proposal meets specified criteria in three areas - architecture, security and data.
This section contains information on each item listed in the “Architectural Alignment” section of the presentation, and provides guidance by attempting to answer three questions.
- What does the item mean in this context?
- Why does the item need to be addressed?
- How would a team go about meeting the item requirements?
Re-use before buy, buy before build
What? – Sharing and re-using existing resources (technology, data, services) is encouraged before purchasing any technology, and buying a technology solution is recommended before building from scratch. Benefits include avoiding duplication, speeding up the initial project phases and lowering costs.
Why - Your proposal needs to show you’ve considered whether you can share and re-use technology to comply with point 8 of the Technology Code of Practice (TCoP).
To comply with TCoP point 11 your proposal must demonstrate
- the user need/problem you need to solve
- your decision process for building or buying any technology
- how your proposal meets user needs and solves or mitigates your problem
- how you’re following government contractual limitations
Your proposal should also include details on increasing sustainability to comply with TCoP point 12.
The spend control process requires you to demonstrate you are meeting the requirements for TCoP point 8 and TCoP point 11.
How? – Explore the potential for re-use and sharing technology in the guidance for TCoP point 8 and developing a purchasing strategy in TCoP point 11. Section 11 of the GOV.UK service standard also includes guidance on choosing the right tools and technology.
Configure, not customise to improve business agility
What? – Configuration is handled via a solution’s settings, meaning changes can be contained within the solution’s properties. Customisation can require extra development work, so changes are subject to a full development life cycle, and an extra cost.
Why? – To meet the requirements for TCoP point 9, your proposal needs to demonstrate your solution is adaptable and integrates into the organisation. To meet the requirements for TCoP point 11 you should also outline the reasons for any proposed customisation work and its effect on your purchasing strategy.
The spend control process requires you to demonstrate you are meeting the requirements for TCoP point 9.
How? – Review the guidance in section 11 of the GOV.UK service standard, as well as TCoP point 9. Include information in your proposal on why customisation is required to deliver your service.
User-led to meet user needs
What? – User research will help you to understand user needs and behaviour. It helps to define how your technology project or programme improves the user experience. It can identify risks associated with technological changes, skills needed for project delivery and management, requirements for any end user support and any commercial or operational requirements (like replacing obsolete technology).
Why? – Your proposal needs to show you understand user needs and behaviour to comply with TCoP point 1.
The spend control process also requires you to demonstrate you are meeting the requirements for TCoP point 1.
How? – The GOV.UK service standard contains details on how to develop a user-led solution. Your presentation should include information on any user research you’ve conducted, and the impact of the research on the proposal.
Cloud First
What? – Cloud computing should be the first data storage/retrieval solution considered for any proposal to the TDA.
Why? – To comply with government cloud first policy and TCoP point 5, your presentation should demonstrate that cloud computing has been considered before any other options.
The spend control process also requires you to demonstrate you are meeting the requirements for TCoP point 5.
How? – Review the guidance on cloud migration in TCoP point 5 and include the reasons for choosing your proposed solution in your presentation, assessed on these criteria:
- continual re-validation of the cloud hosting strategy
- any distinct issues regarding legacy technology
- assessment of a hosting business case
Control technical diversity, simplifies the estate
What? – Minimising the number of different technologies used to develop your solution helps to encourage sharing and re-use of technology across different projects and streamline the range of technologies the organisation is required to support.
Why? – To meet the requirements for TCoP point 8, your proposal needs to demonstrate how your solution successfully integrates with existing technologies in the organisation.
The spend control process also requires you to demonstrate you are meeting the requirements for TCoP point 8.
How? – Review the guidance in section 11 of the GOV.UK service standard, as well as TCoP point 8. Include information on keeping the range of technologies used to a minimum and explain why your solution may require the use of any innovative technologies not currently used within the organisation.
Manage obsolescence to reduce technical debt
What? – Any proposed solutions should outline the process and cost of replacing technology which has become obsolete, as well as the future cost of maintenance or re-work to minimise the build-up of technical debt.
Why? – To meet the requirements for TCoP point 9, your proposal needs to demonstrate how your solution will successfully replace any obsolete technology. To meet the requirements for TCoP point 11 you should also the effect of any replacement on your purchasing strategy.
The spend control process also requires you to demonstrate you are meeting the requirements for TCoP point 9.
How? – Review the guidance in section 11 of the GOV.UK service standard, as well as TCoP point 9. Include information on replacing legacy technology in your proposal, demonstrating how it could reduce technical debt.
Use open standards
What? - Open standards are common rules which allow for the creation of compatible and consistent products, processes and services. They are designed collaboratively and publicly available at little or no costs and incorporating them into a project offers several benefits.
- using technology which is already available saves time and money
- using standards applied in other projects increases compatibility with a range of stakeholders
- using public standards helps to avoid vendor lock-in and recurring costs
Why? - To meet the conditions for TCoP point 4, your proposal should include evidence that you’ve considered using open standards and data.
The spend control process also requires you to demonstrate you are meeting the requirements for TCoP point 4.
How? - Consult the GOV.UK open standards reference pages to make sure you comply with any compulsory standards for government projects and assess if any standards would be suitable for your proposal. In your presentation, demonstrate where open standards are applied in your proposed solution.