Software Test Effort Estimation via Business Priority and Defect Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods lack an efficient technique for generating effective test plans and performing risk assessments to determine schedules and effort levels for User Acceptance Testing in software development projects.
Innovation Solution
A system and method that recommend the number of test cases and effort allocation to business processes in software testing projects by identifying business priorities, estimating defects, determining quality levels, and analyzing past project efforts to calculate the required test cases and effort needed, displayed through an interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional manual test plan generation is used, then flexibility and adaptability are maintained, but efficiency and consistency are reduced
Solution Approach 1:
The system enables self-service through automated test plan generation where the software testing system independently analyzes business processes, estimates defects, determines quality levels, and generates test plans without requiring extensive manual intervention, thereby improving efficiency while maintaining manageable complexity through automation
Solution Approach 2:
The system applies parameter changes by dynamically adjusting test case numbers and effort allocation based on estimated defect counts, business priority levels, and quality level requirements. This allows the system to adapt test plan parameters automatically to different project scenarios, improving productivity across varying conditions
2Reliability
If comprehensive testing is performed to ensure high quality, then reliability is improved, but time and effort requirements increase
Solution Approach 1:
The system implements local quality by differentiating testing effort across different business processes based on their individual risk profiles. High-risk processes receive more extensive testing while low-risk processes receive reduced testing, allowing the system to maintain high overall reliability while reducing total testing time through targeted quality assurance
Solution Approach 2:
The system applies partial action by calculating and executing only the necessary portion of testing required to achieve the desired quality level. Through mathematical models that relate test case numbers to defect detection probabilities, the system determines the minimum adequate testing effort rather than performing comprehensive testing, thereby reducing time loss while maintaining acceptable reliability
3Productivity
If risk assessment is performed to determine effort levels, then resource allocation is improved, but assessment complexity increases
Solution Approach 1:
The system performs preliminary action by pre-establishing mathematical models and algorithms for risk assessment that can be automatically applied to new projects. The system pre-calculates relationships between business process characteristics, defect probabilities, and required testing effort, allowing rapid resource allocation decisions without complex real-time analysis, thus improving productivity while keeping assessment complexity manageable
Data Source
AI summary
A system, method, and computer program product are provided for recommending a number of test cases and effort to allocate to one or more business processes associated with a software testing project. In use, one or more business processes associated with a software testing project are identified. A business priority and customization level is set for each of the one or more business processes associated with the software testing project Additionally, a number of defects are estimated for each of the one or more business processes associated with the software testing project. Further, a quality level is determined for each of the one or more business processes associated with the User Acceptance Testing software testing project. In addition, a number of test cases to be executed to achieve the quality level is determined for each of the one or more business processes associated with the software testing project, the number of test cases to be executed to achieve the desired quality level being based, at least in part, on the estimated number of defects and the business priority. Furthermore, an effort analysis associated with one or more past software testing projects is identified. Moreover, an estimated effort is determined for each of the one or more business processes associated with the software testing project, the estimated effort being based, at least in part, on the number of test cases to be executed to achieve the quality level, the business priority, and the effort analysis of the one or more past software testing projects. Still yet, the estimated effort is displayed for at least one of the one or more business processes associated with the software testing project utilizing at least one interface.