Abstract: A computer implemented method for monitoring an overall health of a software project. The method includes: providing a plurality of business process checkers; storing a plurality of criteria, wherein each of the plurality of criteria measures an aspect of the software project process; storing an upper bound parameter and a lower bound parameter for each business process checker; assimilating data from one or more data sources related to aspects of the software project process; calculating, by each business process checker, a score for each criterion responsive to said upper bound and lower bound parameters and said data from said one or more data sources; calculating an overall health score for the software project from each calculated score for each criterion; and displaying an indication of the overall health of the software project responsive to the calculated overall health score.

Abstract: A method for enforcing business rules in a computer program, using static analysis. The method includes: storing a plurality of business rules corresponding to a plurality of business processes representing a behavior of an enterprise; parsing a representation of business processes in the computer program to create a parse tree; extracting execution paths from the parse tree; creating control flow graphs and data flow graphs from the extracted execution paths, wherein the created control flow graphs and data flow graphs adhere to one or more of the stored business rules; following the created control flow graphs and data flow graphs; applying said one or more of the stored business rules to the created control flow graphs and data flow graphs; and reporting whether any of the applied rules is violated.

Abstract: A method and system for assessing effect of a change in a computer software including a plurality of requirements and a plurality of test cases. The method and system include: changing a requirement from the plurality of requirements; correlating the computer software with the changed requirement to identify a portion of the computer software that is affected by the changed requirement; and correlating one or more of the test cases with the portion of the computer software that is affected to identify one or more of the test cases that is affected by the changed requirement. Additionally, the computer software may be changed and the effect of that change on the requirements and the test cases may then be determined.

Abstract: A system and method for generating test cases for a computer program. The method and system include invoking execution of the computer program via a remote client and monitoring the execution of the computer program. Information about execution path of the computer program is collected and then the execution of the computer program is stopped via the remote client. One or more test cases are then generated utilizing the collected information. In one embodiment, the remote client is a computer test tool and the computer program is a web application.

Abstract: A method and system for enforcing functionality in computer software through policy including converting a natural language policy to sample code, wherein the natural language policy is represented by logical patterns; creating one or more static analysis rules from the sample code to enforce the natural language policy at a centralized location of the computer software; and enforcing the created one or more static analysis rules for the computer software.