Abstract: Size of a software application testing project is determined, and person/hours required for the testing project is estimated. The software application is sized by counting the number of different parameter types that occur within testing activities associated with the application. The parameter type numbers are then divided by a scaling weight to arrive at a Testing Unit number, which is then divided by a Testing Unit rate, e.g., person hours associated with each testing unit, to arrive at an estimated testing project effort. Some embodiments include an uncertainty calculation that potentially increases testing time based on clarity of the project requirements, the tester familiarity with the application area and the tester familiarity with the domain. Some embodiments calculate separate testing project times for different phases of the testing project.

Abstract: Size of a software application testing project is determined, and person/hours required for the testing project is estimated. The software application is sized by counting the number of different parameter types that occur within testing activities associated with the application. The parameter type numbers are then divided by a scaling weight to arrive at a Testing Unit number, which is then divided by a Testing Unit rate, e.g., person hours associated with each testing unit, to arrive at an estimated testing project effort. Some embodiments include an uncertainty calculation that potentially increases testing time based on clarity of the project requirements, the tester familiarity with the application area and the tester familiarity with the domain. Some embodiments calculate separate testing project times for different phases of the testing project.