Quality Measures

  Home  Business and Economy  Quality Measures

“Product Quality Measures Interview Questions and Answers will guide you that Product Quality Measures is based on conformance to requirements or program specification; related to Reliability, Scalability, Correctness, Completeness, Absence of bugs, Fault-tolerance, Extensibility, Maintainability etc. So learn more about the Product Quality Measures with the help of this Product Quality Measures Interview Questions and Answers”

33 Quality Measures Questions And Answers

1⟩ How to measures customer satisfaction for the Product?

(Quality ultimately is measured in terms of customer satisfaction.)

Surveyed before product delivery and after product delivery (and on-going on a periodic basis, using standard questionnaires)

Number of system enhancement requests per year

Number of maintenance fix requests per year

User friendliness: call volume to customer service hotline

User friendliness: training time per new user

Number of product recalls or fix releases (software vendors)

Number of production re-runs (in-house information systems groups)


2⟩ Define Quality Control (QC)?

Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.


3⟩ How to measures Reliability for the Product?

Availability (percentage of time a system is available, versus the time the system is needed to be available)

Mean time between failure (MTBF)

Mean time to repair (MTTR)

Reliability ratio (MTBF / MTTR)

Number of product recalls or fix releases

Number of production re-runs as a ratio of production runs


4⟩ Define Quality Assurance (QA)?

QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.


5⟩ How to measures Costs of quality activities for the Product?

Costs of reviews, inspections and preventive measures

Costs of test planning and preparation

Costs of test execution, defect tracking, version and change control

Costs of diagnostics, debugging and fixing

Costs of tools and tool support

Costs of test case library maintenance

Costs of testing & QA education associated with the product

Costs of monitoring and oversight by the QA organization (if separate from the development and test organizations)


6⟩ How to measures Test coverage for the Product?

Breadth of functional coverage

Percentage of paths, branches or conditions that were actually tested

Percentage by criticality level: perceived level of risk of paths

The ratio of the number of detected faults to the number of predicted faults.


7⟩ How to measures Defect removal efficiency for the Product?

Number of post-release defects (found by clients in field operation), categorized by level of severity

Ratio of defects found internally prior to release (via inspections and testing), as a percentage of all defects

All defects include defects found internally plus externally (by customers) in the first year after product delivery


8⟩ How to measures Product volatility?

Ratio of maintenance fixes (to repair the system and bring it into compliance with specifications), vs. enhancement requests (requests by users to enhance or change functionality)


9⟩ How to measures delivered defect quantities for the Product?

Normalized per function point (or per LOC)

At product delivery (first 3 months or first year of operation)

Ongoing (per year of operation)

By level of severity

By category or cause, e.g.: requirements defect, design defect, code defect, documentation/on-line help defect, defect introduced by fixes, etc.


10⟩ How to measures Re-work for the Product?

Re-work effort (hours, as a percentage of the original coding hours)

Re-worked LOC (source lines of code, as a percentage of the total delivered LOC)

Re-worked software components (as a percentage of the total delivered components)


12⟩ How to measures Cost of defects for the Product?

Business losses per defect that occurs during operation

Business interruption costs; costs of work-arounds

Lost sales and lost goodwill

Litigation costs resulting from defects

Annual maintenance cost (per function point)

Annual operating cost (per function point)

Measurable damage to your boss's career


13⟩ How to measures Defect ratios for the Product?

Defects found after product delivery per function point

Defects found after product delivery per LOC

Pre-delivery defects: annual post-delivery defects

Defects per function point of the system modifications


15⟩ Why test-ware is special?

Testware is special because it has:

1) Different purpose

2) Different metrics for quality and

3) Different users


16⟩ Tell me what you know about Testware?

✰ The subset of software which helps in performing the testing of application.

✰ Testware is term given to combination of all utilities and application software that required for testing a software package.

✰ Testware are required to plan, design, and execute tests. It contains documents, scripts, inputs, expected results, set-up and additional software or utilities used in testing.


18⟩ List the benefits of destructive testing?

Benefits of Destructive Testing (DT):

✰ Verifies properties of a material

✰ Determines quality of welds

✰ Helps you to reduce failures, accidents and costs

✰ Ensures compliance with regulations


19⟩ What is regression testing, Why it is important?

Regression Testing: When changes in the code of the software are made to fix the previous bug. Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any functionality that it offered previously.

Regression Testing is important because of following reason:

✰ That the application works even after the alteration in the code were made.

✰ The original functionality continues to work as specified even after doing changes in the software application.

✰ The alteration to the software application has not introduced any new bugs.


20⟩ List key challenges of software testing?

✰ Application should be stable enough to be tested.

✰ Testing always under time constraint.

✰ Understanding requirements, Domain knowledge and business user perspective understanding.

✰ Which tests to execute first?

✰ Testing the Complete Application.

✰ Regression testing.

✰ Lack of skilled testers.

✰ Changing requirements.

✰ Lack of resources, tools and training.