...the on-screen service independently. In respect of point 8, the team should keep the new process for reviewing and releasing code under review, and continue to develop the process throughout...
...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...
...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...
This is a new digital service that will enable intermediaries (or Agents acting on their behalf) to comply with legislation by uploading a report to HMRC providing details of the...
...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...
...regularly explored original ways of using the interface functionality and the API. This experimentation has opened up new understanding of user behaviour which wasn’t available to us before. We’ve regularly...
...finalise development and will also maintain the service. User needs The team drew on customer feedback on the previous system and also tested the new transaction with around 20 students...
...of the public beta release the team must: make their source code open and reusable. The team explained that the code was written to be shared and reusable but it...
...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...
...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...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.