Introduction
Purpose
A guide to managing software development projects for Digital Health and Care Wales.
Scope
In-scope
-
Good practice for requirements gathering, building, testing, and deploying software.
Out-of-scope
-
Broader lifecycle topics, including project inception, software architecture, user acceptance testing and operations.
-
Guidance on publishing software as open source.
-
In-depth instructions; this guide links to other standards instead.
Roles and responsibilities
Application and Product teams in the Operations and Primary Care and Mental Health directorates have a responsibility to follow this guide.
References
- Digital Service Standard for Wales
- Welsh Technical Standards Board Statement of Principles
- How to request and manage software subscriptions
- Using Source Control
- T-SQL Coding Standard
- RESTful API Design and Build Standards
- How to Organise Your Software Solution
- General Coding Standards
- Azure DevOps handbook
- Informatics Systems in Wales, National Assembly for Wales, Public Accounts Committee
- SOP-OSD-004 - Web Applications
- SOP-OSD-005 - Encryption in Transit
- SOP-OSD-006 - Application Programming Interfaces
Conventions
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in RFC 2119.
Practical tips
Practical tips
Examples of good practice
Examples of good practice...
Practices to avoid
...and practices to avoid
Further reading and information
Links to further guides, information and work instructions. If a link is missing, search for the document in the Document Management System.
The need for guidance
Developing software for healthcare needs consistent, robust practices. Following clear processes and good practice helps you deliver robust and secure solutions.