Software Quality: Framework & Measurements
Mukta Sharma
LinkedIn Top Voice |3C - Communication, Collaboration, Community || Community TOP VOICE*5 || TOP 100 Women In Tech || TOP 10 LinkedIn Influencers- London || AWS Certified || Scrum Master || Technical Blogger
If I ask you one question, What is Quality mean to you? What will be your answer? How to ensure the quality of a software? How do you describe product quality? Can we measure Quality? How do we do that? These are some of the questions which are explained effectively by renowned Srinivas Kantipudi in one of his webinar on The Test Chat Community platform which I attended day before yesterday.
While measuring the quality of a software, we must look at internal and external factors which together makes a quality software. There are many quality models which we need to look upon to establish the quality of our software. Some key takeaways are:
1. McCall’s Quality Model – established in 1977 and based upon 11 factors divided among 3 sections: Product Revision, Product Transition and Product Operation.
Now the question is, how we define Quality under Product Revision. So, we need to look for the below factors:
Testability
Flexibility
Maintainability
Similarly, to define quality under Product Transition, we have the below factors:
Portability
Reusability
Interoperability
To define quality Under Product Operation:
Correctness
Reliability
Efficiency
Integrity
Usability
2. ISO/IEC 25010:2011 – SQUARE – (System & Software Quality Requirements & Evaluations) – based upon 8 parameters which are internal as well as external to the system.
3. FURPS +:- HP Model for defining the quality of requirements. Factors which concludes the quality of requirements are:
Reliability
Functionality
Usability
Performance
+ in FURPS indicates constraints which are applied while defining the quality of requirements.
There are many more described in his webinar like the below:
SQALE - Software quality assessment MODEL
Quality Metrics
GQM- Goal Question Metric
About Metrics KPIS etc.
3 P of Quality – which we can use while defining the quality.
3P stands for People, Processes and Product.
Thank you Srinivas Kantipudi for the interesting webinar. Please visit "The Test Chat" on Youtube for detailed webinar and many more like that.
Thank you reading! Lets enjoy sharing & gaining knowledge and support our testing community.
Quality obsessed and Agile enthusiast professional / Freelance hands-on software testing specialist and test coach / Blogger / Interpreter / Catalan Proofreader / Radio host / Humane Technologist
3 年Thanks for posting, Mukta. I take the opportunity to recommend this article by James Bach.
Software Test Engineering (#freelancer #B2B) | QA Leadership|Test Engineering|Test Automation|Quality Assurance|Quality Engineering|#hybrid|#remote|#Devops|#europe|#worldwide|
3 年Rather than being tech or specific we need to be be cognizant of the fact that Quality meaning is different for different people.
ISTQB Certified Test Engineer at Kongsberg Maritime???
3 年Thanks for sharing
Software Tester | Exploratory Tester | Quality Advocate | Risk Finder | Critical Thinker | Problem Solver | Collaborator | Mentor | Teacher | Leader | Helping People To Build High Quality Software Through Collaboration
3 年Mukta Sharma you pose the questions "What is Quality mean to you? What will be your answer? How to ensure the quality of a software? How do you describe product quality? Can we measure Quality?" and then list a bunch of approaches/ideas. I'm unclear how they really help us answer, in meaningful ways, the questions you posed. At what point are we going to our customers and asking them for feedback? "Is our software helping you complete perform your job effectively/efficiently?" While models and frameworks look great and sound impressive we should consider fitness for context and whether they return useful information. Isn't it about keeping our customers satisfied? Perhaps they can provide us with much of the feedback we need.