...for this project to be coded in the open, with all code published on github.com in open repositories. Where this is not possible there should be a convincing explanation as...
...and a live chat feature present in early prototypes (and welcomed by respondents) were missing from the beta design. It is recommended that the status of these user needs/requirements is...
...reflect the high data protection requirement. The source code was peer reviewed by GDS before being finalised by the supplier. At present security requirements are too entangled with the general...
...user research and analytics. Make source code open and reusable - point 15 For beta assessment the panel expect to see steps taken for this project to be coded in...
...sensible manner. It is good that the team has pulled out ‘form-monkey’, a library for creating forms, from the core code base with plans to open source it. The panel...
...opening up the code they have developed. The use of widely adopted open source tools limit locking, and allow for future reuse/repurposing. The plans, agreed by the relevant BIS staff...
...target to meet, and will explore promotion of the digital service through key identified community groups in order to meet this target. Recommendations Research and user needs While the team...
...was far superior and welcomed HMRC’s move to digital. Listening to the user has been at the core of service development designing such features as 'Save and Retrieve', summaries, ability...
...conform to the service design manual and design patterns. The team will need to include a front-end developer that can quickly iterate the code and make changes to the template....
...able to ensure that internal and external stakeholders are being kept up to date with progress. The technology choices are embracing open source and all code is being made available...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.