# US 9,201,768 B1 · System, method, and computer program for recommending a number of test cases and effort to allocate to one or more business processes associated with a software testing project > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,201,768 B1 - Document ID: US9201768B1 - Status: Granted - Kind: B1 - Application number: 14/174,797 - Filed: 2014-02-06 - Granted: 2015-12-01 - Earliest claimed: 2014-02-06 - Assignees: Amdoes Software Systems Limited - Applicants: Amdocs Software Systems Limited - Inventors: Adi Fledel Alon; Gilli Shama; Sagar Subhash Surana - Web page: https://patentgrep.com/patent/US9201768B1 ## CPC - G06F 11/3672: {Test management} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract 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. ## Claims ### Claim 1 A computer program product embodied on a non-transitory computer readable medium, comprising: computer code for identifying one or more business processes associated with a software testing project; computer code for setting a business priority and customization level for each of the one or more business processes associated with the software testing project, the business priority including a priority level assigned to each of the one or more business processes, and the customization level including a magnitude of customization for each of the one or more business processes; computer code for estimating a number of defects for each of the one or more business processes associated with the software testing project; computer code for calculating a quality level for each of the one or more business processes associated with the software testing project as a function of the business priority for each of the one or more business processes, where for each of the one or more business processes the quality level includes a percentage of targeted defects to be removed from the business process; computer code for determining a number of test cases to be executed to achieve the quality level 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; computer code for identifying an effort analysis associated with one or more past software testing projects; computer code for determining an estimated effort 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; and computer code for displaying the estimated effort for at least one of the one or more business processes associated with the software testing project utilizing at least one interface. ### Claim 2 (depends on 1) The computer program product of claim 1, further comprising computer code for generating a test management recommendation associated with the software testing project based on the estimated number of defects for each of the one or more business processes and the quality level for each of the one or more business processes. ### Claim 3 (depends on 2) The computer program product of claim 2, wherein the computer program product is operable such that the test management recommendation associated with the software testing project includes a recommendation associated with testing personnel. ### Claim 4 (depends on 2) The computer program product of claim 2, further comprising computer code for displaying the test management recommendation utilizing the at least one interface. ### Claim 5 (depends on 1) The computer program product of claim 1, further comprising computer code for displaying one or more of the determined number of test cases to be executed as a recommended number of test cases to be executed. ### Claim 6 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that displaying the estimated effort for the at least one of the one or more business processes associated with the software testing project utilizing the at least one interface includes displaying the estimated effort as a recommended amount of effort to allocate to each of the one or more business processes associated with the software testing project. ### Claim 7 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that identifying the one or more business processes associated with the software testing project includes selecting the one or more business processes and setting the business priority for each of the one or more business processes. ### Claim 8 (depends on 7) The computer program product of claim 7, wherein the computer program product is operable such that the business priority for each of the one or more business processes is set based on a service level agreement associated with the software testing project. ### Claim 9 (depends on 8) The computer program product of claim 8, wherein the computer program product is operable such that the quality level for each of the one or more business processes associated with the software testing project is calculated based on the estimated number of defects and the business priority for each of the one or more business processes. ### Claim 10 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the number of defects for each of the one or more business processes associated with the software testing project is estimated utilizing a fault prediction algorithm. ### Claim 11 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the number of defects for each of the one or more business processes associated with the software testing project is estimated utilizing defect information associated with the one or more past software testing projects. ### Claim 12 (depends on 11) The computer program product of claim 11, wherein the computer program product is operable such that the defect information associated with the one or more past software testing projects includes a severity associated with each defect associated with the one or more past software testing projects. ### Claim 13 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the number of defects for each of the one or more business processes associated with the software testing project is estimated utilizing metadata associated with the one or more past software testing projects. ### Claim 14 (depends on 13) The computer program product of claim 13, wherein the computer program product is operable such that the metadata associated with the one or more past software testing projects includes at least one of a project type, a product, a service level agreement for defect removal efficiency, a line of business, a geographic region, or a testing and development effort. ### Claim 15 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the number of defects for each of the one or more business processes associated with the software testing project is estimated based, at least in part, on the customization level associated with the software testing project. ### Claim 16 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that determining the number of test cases to be executed to achieve the quality level for each of the one or more business processes associated with the software testing project includes calculating the number of test cases to be executed from an S-curve function that links a number of discovered defects associated with the one or more past software testing projects to a number of test cases associated with the one or more past software testing projects. ### Claim 17 (depends on 16) The computer program product of claim 16, wherein the computer program product is operable such that determining the number of test cases to be executed to achieve the quality level for each of the one or more business processes associated with the software testing project further includes tracing back the S-curve function utilizing the number of test cases associated with the one or more past software testing projects to determine the number of test cases to be executed to achieve the quality level. ### Claim 18 (depends on 1) The computer program product of claim 1, further comprising computer code for generating at least one test calendar for each of the one or more business processes, the at least one test calendar indicating at least the number of test cases to be executed to achieve the quality level for each of the one or more business processes associated with the software testing project. ### Claim 19 A method, comprising: identifying one or more business processes associated with a software testing project; setting a business priority and customization level for each of the one or more business processes associated with the software testing project, utilizing a hardware processor, the business priority including a priority level assigned to each of the one or more business processes, and the customization level including a magnitude of customization for each of the one or more business processes; estimating a number of defects for each of the one or more business processes associated with the software testing project; calculating a quality level for each of the one or more business processes associated with the software testing project as a function of the business priority for each of the one or more business processes, where for each of the one or more business processes the quality level includes a percentage of targeted defects to be removed from the business process; determining a number of test cases to be executed to achieve the quality level 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; identifying an effort analysis associated with one or more past software testing projects; determining an estimated effort 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; and displaying the estimated effort for at least one of the one or more business processes associated with the software testing project utilizing at least one interface. ### Claim 20 A system comprising: a memory system; and one or more processing cores coupled to the memory system and that are each configured to: identify one or more business processes associated with a software testing project; set a business priority and customization level for each of the one or more business processes associated with the software testing project, the business priority including a priority level assigned to each of the one or more business processes, and the customization level including a magnitude of customization for each of the one or more business processes; estimate a number of defects for each of the one or more business processes associated with the software testing project; calculate a quality level for each of the one or more business processes associated with the software testing project as a function of the business priority for each of the one or more business processes, where for each of the one or more business processes the quality level includes a percentage of targeted defects to be removed from the business process; determine a number of test cases to be executed to achieve the quality level 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; identify an effort analysis associated with one or more past software testing projects; determine an estimated effort 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; and display the estimated effort for at least one of the one or more business processes associated with the software testing project utilizing at least one interface.