Abstract: Identifying missing test scenarios based on a repository of organization-specific in-use scenarios, including: accessing a set of organization-specific in-use scenarios, each organization-specific in-use scenario executes least two transactions; comparing the organization-specific in-use scenarios with available test scenarios repairable by a non-programmer user, each available test scenario repairable by a non-programmer user tests at least two transactions; identifying organization-specific in-use scenarios that do not have corresponding test scenarios repairable by a non-programmer user; and providing at least one of the missing test scenarios to a non-programmer user for generating a test scenario repairable by a non-programmer user that covers the at least one missing test scenario.

Abstract: Methods for accessing impact analysis repositories and transaction-refinement index for each of the impact analysis repositories. According to the obtained transaction-refinement index, associating the combined repository with information from the most transaction refined impact analysis repository. Associating the combined repository with information from the less transaction refined impact analysis repository in the case of a request to insert or delete a table record for tables that do not contain any impacted transaction in the more transaction refined impact analysis repository. And associating the combined repository with information from the less transaction refined impact analysis repository in the case of a request to update a table record for table columns that do not contain any impacted transaction in the more transaction refined impact analysis repository.

Abstract: Executing semiautomatically a functioning test scenario to enable a non-programmer user to generate a new test scenario based on the functioning test scenario, including: recording the non-programmer user while interacting with the semiautomatic execution of the functioning test scenario; and generating the new test scenario based on the recording; wherein the semiautomatic execution enables the following features: automatically entering data inferred from the functioning test scenario into a form of a data-oriented large-scale software system; and enabling the non-programmer user to: change the automatically entered data, add a new form to the semiautomatically executed functioning test scenario, and enter data into fields inside the new form.

Abstract: Methods for accessing impact analysis repositories and transaction-refinement index for each of the impact analysis repositories. According to the obtained transaction-refinement index, associating the combined repository with information from the most transaction refined impact analysis repository. Associating the combined repository with information from the less transaction refined impact analysis repository in the case of a request to insert or delete a table record for tables that do not contain any impacted transaction in the more transaction refined impact analysis repository. And associating the combined repository with information from the less transaction refined impact analysis repository in the case of a request to update a table record for table columns that do not contain any impacted transaction in the more transaction refined impact analysis repository.

Abstract: One non-limiting embodiment of the invention comprises the steps of accessing at least two impact analysis repositories, calculating a combined impact analysis repository from the at least two impact analysis repositories, and utilizing the combined impact analysis repository for supplying better quality impact analysis results.

Abstract: A system and method for analyzing a computer program comprising a first multiplicity of elements having a second multiplicity of functional relationships defined therebetween, the first multiplicity of elements including interface elements and non-interface elements, the method comprising reading source code, finding at least selected interface elements in the source code, and identifying, and displaying to a user, only those functional relationships which are defined between the selected interface elements.