Mumbai University > Information Technology > Sem 8 > Software testing and Quality Assurance

Marks: 5 Marks

Year: May 2016

1.The most common way to measure software testing effectiveness is to determine whether testers can validate the presence or absence's of the development team's defined requirements. In this case, four different metrics enable you to measure software testing effectiveness, as follows :

• Requirements tested and founded correct.

• Requirements does not execute as specified.

• Requirement is missing.

• Requirement found in tested software, but not specified by the development team.

2.Measuring Quality Factors

• The quality factor of “correctness” refers to testers validating whether the requirements specified by the development team work.

• However, the quality factor of correctness does not include all the other quality factors that the test team should be addressing.

• For example, it does not address whether the software is maintainable. Note that the software can be implemented with all the functional requirements in place and working, but cannot be efficiently or effectively maintained because the software was not built with maintenance in mind.

• For example, the logic may be so complex that it is difficult for a maintainer to implement a change in the software.

3.If the tester represents the customer/user, the tester’s responsibility may include testing some or all of the quality factors.

4.This is generally determined in the relationship of the tester to the customer/user.

5.If the tester is to evaluate more than the correctness quality factor, additional effectiveness criteria must be determined and used.

6.The quality factors and the software criteria relate to the specific application system being developed.

7.The desire for quality is heavily affected by the environment created by management to encourage the creation of quality products.

8.An environment favorable to quality must incorporate those principles that encourage quality.

9.Building Software Effectiveness and Efficiency Metrics includes:

10.The measurement criteria should be recorded on Paper and should include the following:

11.Criteria name

• Description

• Efficiency

• Effectiveness

• Rank

12.After the agile implementation team has agreed on the criteria used to measure test efficiency and effectiveness, they need to rank those criteria. The ranking should be a two-part process:

i. Rank the criteria high, medium, or low. (Those ranked high are the best criteria for measurement.)

ii. Starting with the high criteria, select no more than five criteria for efficiency and five for effectiveness. Note: These do not have to be those ranked high, but those ranked high should be considered before those ranked medium.

13.Both the efficiency and effectiveness metrics are developed the same way. It is recommended that three to five criteria be used.

14.Then the criteria must be measurable. Use the following method to do that:

i. A method for calculating a criteria score must be determined. It is recommended that the calculated score for individual criteria be a range of 0 to 100. This is not necessary, but it simplifies the measurement process because most individuals are used to scoring a variable using a range of 0 to 100.

ii. The criteria used for efficiency or effectiveness must then be weighted. The range should total 100 percent. For example, if there are five criteria and they all weighted equally, they each will be given a 20 percent rating or 20 percent of the total effectiveness or efficiency score.

iii. To calculate a specific efficiency or effectiveness score for a project, the criteria score is multiplied by the weighting percentage to produce an efficiency or effectiveness score. The individual scores for efficiency and effectiveness are added to produce a total score.