...the service should focus on throughout the beta phase and must be addressed before coming for a live assessment. Publishing source code must be in place for the live assessment....
...team are working toward a public beta date in January 2015. Department / Agency: HMRC Date of Assessment: 8/1/2015 Assessment stage: Beta Lead Assessor: R. Morgan Service Manager: I. Atkin...
...Department / Agency: HMRC Date of Assessment: 1 July 2015 Assessment stage: Beta Result of Assessment: Not Pass Lead Assessor: L. Reichelt Service Manager: M. Duffield Digital Leader: M. Dearnley...
...early stage of development. The team has been working with the Personal Support Unit (PSU), a charity that provides free, independent advice to litigants in person, witnesses, victims, their family...
...code, code that contains sensitive information (e.g. fraud detection components) or can pose a security risk if open. Publishing the source code will be a mandatory requirement when the service...
...see all code open sourced, regardless of usefulness to a wider audience or not. The only exceptions are configuration management code, code that contain sensitive information (e.g. fraud detection components)...
...convincing explanation as to why this can’t be done for specific subsets of the source code). Code from the service has been published and is currently being reused by another...
...aspects to the code, so effort should be made to code in the open and share as much as possible with the rest of DWP, government community and third parties....
...as described in https://gds.blog.gov.uk/2014/10/08/when-is-it-ok-not-to-open-all-source-code/. The panel would also like to encourage communication between this team and other parts of government that are developing services using Microsoft technologies, such as how...
...and has refactored the code base for legibility. The code now is well structured. Test coverage has improved vastly from having no existing tests to around 80% coverage. The team...