dft street manager spike 0000 technical overview
This document is intended as a guide to new developers to the technical approach for Alpha.
The technical purpose of Alpha is to explore the technical risks and challenges of getting the service into Beta, making decisions on technical implementations and documenting approaches so they can be validated by external parties and auditors (security, GDS etc.). It does not involve implementing common or known functionality and any code created should be considered throw away, the knowledge gained is what matters.
This will involve creating a UX prototype to assist with user research and iterating over designs, and creating a series of proof of concept applications as part of technical spikes.
See here.
Developers will work with designers to create and update the UX prototype (Node JS Express, forked from govuk_prototype_kit) to assist in user research and iterating over the proposed screens for the user journeys. The UX prototype will also be used to test variations on complex controls and design patterns like mapping displays. This will provide a guide for implementation in beta using the GDS styles and patterns, avoiding additional effort to meet service manual standards.
All technical spikes should be documented and end with a conclusion that can be used to support decisions for Beta which is reviewed by another technical source. Any proof of concept code (PoC) should be kept in the alpha repo for future reference.
The standards and conventions for Alpha code do not need to meet production quality but developers should always note and consider how they would be implemented later, e.g. don't need full unit test coverage but should document how components would be tested.
All technical spikes should be recorded in JIRA as tasks and included in sprint.
- TODO