...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...
...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...
...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,...
...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...
...how IP addresses can be excluded from collection using when WebTrends. Ensure there are clear plans for publishing open source code in the next stage of development. The service team...
...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...
...code open and reusable. Although work is underway to make code from other components of the PAYE service available via a public GitHub it would be good to see code...
...any issues lie. The technical architect also described what measures are in place (sanitisation, workflows, role access) to ensure that data is handled appropriately. Call centre code has been looked...
...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...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.