software-engineering-quality-framework icon indicating copy to clipboard operation
software-engineering-quality-framework copied to clipboard

🏎️ Shared best-practice guidance & tools to support software engineering teams

Results 81 software-engineering-quality-framework issues
Sort by recently updated
recently updated
newest added

Rather than looking just at the KPIs as figures perhaps we could suggest to the terms as well to track a trend of changes of particular metrics in a set...

This quality framework is concerned with "rapid and safe delivery of high-quality software, at scale". All types of engineering are influenced by human factors. I would argue that these human...

Can we have some guidance around where open source should be used, and at a minimum we should be practicing "inner source". https://en.m.wikipedia.org/wiki/Inner_source I often find myself having to ask...

One consideration you might like to document is that when using **_cloud native_** services to deploy your infrastructure you have an additional security benefit in that the role which has...

Add real NHSD examples to some of the principles, including: 1. Cross-region SQL server on Azure (CB) 2. Active/active Postgres read-replicas on AWS (DS) 3. Ephemeral EC2 on AWS (NL)...

In 'Build Quality In' is says 'Three amigos analysis and elaboration to ensure requirements are fully understood at the point the work will be done." This is good, however I...

Some references to example cloud platform services which currently use AWS examples could be replaced or augmented with other examples, primarily from Azure.

Regarding: https://github.com/NHSDigital/software-engineering-quality-framework/blob/master/practices/cloud-services.md Ref: "Prefer serverless platform as a service (PaaS) over infrastructure as a service (IaaS)" I think it is important to recognise that serverless architecture is a good example...

Regarding https://github.com/NHSDigital/software-engineering-quality-framework/blob/master/patterns/outsource-bottom-up.md Ref: "Cloud native vs cloud agnostic" I think you are very slightly implying cloud neutrality in this section but I don't think it would hurt to be more...

Added architecture-patterns to reinforce the pattern of outsource bottom up.