System for ensuring comprehensiveness of requirements testing of software applications

A system for determining a comprehensiveness of software requirements tests for testing a software application comprised of a plurality of code modules, the system comprising:

• input circuitry configured to receive data that defines artifacts of a software project, the artifacts including application requirements, application code comprised of a plurality of code modules, and test cases;
• and a traceability link generator configured to:
• identify a first sub-link between at least one application requirement and at least one code module of the application code, where the first sub-link indicates a relationship between the at least one application requirement and the at least one code module;
• identify a second sub-link between at least one test case and the at least one code module, where the second sub-link indicates a relationship between the at least one test case and the at least one code module;
• determine an existence of a first traceability link between the at least one test case and the at least one application requirement based on the first sub-link and the second sub-link, whereby the first traceability link indicates that the at least one test case tests the software application for compliance with the at least one application requirement, wherein the existence of the first traceability link is determined based upon a number of algorithms, wherein the traceability link generator is further configured to determine a reliability value that represents an accuracy of the existence of the first traceability link between the at least one test case and the at least one application requirement, and wherein the reliability value is determined as a function of the number of algorithms by which the existence of the first traceability link is determined such that the reliability value increases as the number of algorithms increases;
• determining an existence of a second traceability link between an application and test case based at least in part on the determination of the first traceability link;
• communicating information regarding the first and second traceability links to a user;
• receiving an indication from the user that the first traceability link is invalid;
• and determining the second traceability link to be invalid based at least on the indication from the user.

A non-transitory machine-readable storage medium having stored thereon a computer program comprising at least one code section for determining a comprehensiveness of software requirements tests for testing a software application, the at least one code section being executable by a machine for causing the machine to perform acts of:

• receiving data that defines artifacts of a software application, the artifacts including application requirements, application code comprised of a plurality of code modules, and test cases;
• identifying a first sub-link between at least one application requirement and at least one code module of the application code, where the first sub-link indicates a relationship between the at least one application requirement and the at least one code module;
• identifying a second sub-link between at least one test case and the at least one code module, where the second sub-link indicates a relationship between the at least one test case and the at least one code module;
• determining an existence of a first traceability link between the at least one test case and the at least one application requirement based on the first sub-link and the second sub-link, whereby the first traceability link indicates that the at least one test case tests the software application for compliance with the at least one application requirement, wherein the existence of the first traceability link is determined based upon a number of algorithms, wherein the traceability link generator is further configured to determine a reliability value that represents an accuracy of the existence of the first traceability link between the at least one test case and the at least one application requirement, and wherein the reliability value is determined as a function of the number of algorithms by which the existence of the first traceability link is determined such that the reliability value increases as the number of algorithms increases;
• determining an existence of a second traceability link between an application and test case based at least in part on the determination of the first traceability link;
• communicating information regarding the first and second traceability links to a user;
• receiving an indication from the user that the first traceability link is invalid;
• and determining the second traceability link to be invalid based at least on the indication from the user.