An Approach to Software Quality by SW-Quality.com
I believe Aristotle said it best, “Excellence is not an act, its a habit”. The same applies to Software Quality, “Quality is not an act, its a habit”.
All Software processes need to be stable and repeatable. A stable process that is repeatable allows for consistency in Software Development.
What is Software Quality? The technical definition is defined by IEEE, “Failure free operation of the software in a given environment.”
I believe the bigger challenge is achieving software quality, and how can we consistently achieve software quality?
Below are our principles to achieving building software quality into the software instead of testing for quality.
- An ability to anticipate potential defects in your software design.
- An ability to detect mistakes as soon as they are made.
- An ability to feedback the lessons learned from the mistakes to improve the Software design.
- An ability to feedback the lessons learned from the mistakes to improve the organizations process or SDLC (Software development life cycle).
- A measurement ability to know when your baseline quality is improving or getting worse.
SW-Quality.com recommendations on how to achieve best in class Software Quality
- Given the above principles, the framework designed to meet most of the above is Orthogonal Defect Classification or ODC. Please see our Blog post on Orthogonal Defect Classification for details.
- Measurement ability does exist in ODC, and can be further boosted. We at SWReliability.com provide a complete solution.
- The other factor is the ” proactive Quality culture”, which requires an organization to be proactive and continuously feedback the lessons learned.
- ODC has mechanisms built in for continuous feeback of lessons learned.
- SWReliability.com’s approach to FMEA provides a proactive methodology to anticipate software defects.
- We do believe that the culture of an organization is set by its leaders, and expect the leadership to encourage proactive approaches such as FMEA.
- We do have a case study for FMEA, Failure Modes and Effects Analysis, applied to Software development is at our FMEA Blog. Please see our blog: http://www.sw-quality.com/2016/02/25/can-we-apply-fmea-failure-modes-and-effects-analysis-to-software-development/
- We at SWReliability.com have a complete process for applying FMEA to software development. We provide training and consulting services to help our clients with application of FMEA to Software.
- There are also other Six Sigma tools that we can use in Software Development.
- It is also very important that all the software processes be stable and repeatable, to continuously improve our software quality.
Please share with us what you may have done at your work to improve Software Quality. We would like to know if you agree with our approach to Software Quality or you have suggestions for us.
This post is authored by Vivek Vasudeva