...code open and reusable- point 15 The service team should continue the work to open their source code. Testing the end to end service - Point 17 Ensure the service...
...financially? We’ve had 5,881 visits to the service design manual search over 6 months, and reckon it took about £3,000 worth of internal developer time to build. The code should...
...the online service independently. The service team must give early consideration to how they will open the source code for the Service to ensure that any small parts of code...
...make it quicker to roll out updates and improvements. Point 15 - Make all new source code open and reusable, and publish it under appropriate licences (or give a convincing...
...this will reduce the rate of errors and increase the rate of change. Source code The service team should ensure that the approach to source code is open by default,...
...take-up of the service properly extrapolated. 16. Make all new source code open and reuseable, and publish it under appropriate licences (or provide a convincing explanation as to why this...
...the design and design changes (as a result of feedback/data analysis) can be delivered quickly. 2. Implement plan to separate secret code separate from platform and publish non-sensitive code as...
...etc. Open Source Code The panel were encouraged to hear HMRC are making progress in this area, but we are still yet to see any service code published. Publishing source...
...to continuous integration and testing, as well as infrastructure as code. The team should ensure they continue to reduce the risk of lock-in to their current infrastructure provider. The team...
...source code to be made publicly available. Rather than making a judgement on what source code will be useful and reusable, the default approach should be to publish (sensitive information...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.