...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...
...any code. Real-time internal searches dashboard 4. Monitoring search performance on GOV.UK Our developers managed to track the position of internal search results that people are clicking, by using a...
...security, and user research covered attitudes to disclosure or anonymity of potential job-sharers’ personal details. The source code needs to be published in a public repository before the service proceeds...
...They have opened up the source code (they have reused code from other services and anticipate some features of this one will be useful too) and have adopted an approach...
...Use of open standards and open source code; the team have made use of open source code and contributed their own. Collaborative working across the team and different locations (using...
...of transaction questionnaire. partnered well with other parts of HMRC to remove blockers to service development made progress in making source code open since the beta assessment. It was particularly...
...example the team should continue to investigate the usability of the check code and related parts of the process for giving and activating permission to view a driving record, to...
...can refer to a range of circumstances from a simple code issue, like the misplacement of a bracket, to a fundamental misunderstanding of the problem you are trying to tackle....
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.