Process and system for quality assurance for software

A system for conducting a quality assurance process comprising:

• (a) means for developing a high level quality assurance resource estimate and a high level quality assurance time estimate;
• (b) means for producing a business analysis outline;
• (c) means for creating an acceptance test plan using an acceptance test plan template with the business analysis outline;
• (d) means for refining the high level quality assurance resource estimate and the high level quality assurance time estimate based on at least the acceptance test plan;
• (e) means for creating a plurality of test cases to be carried out during a test execution phase of the quality assurance process using the acceptance test plan;
• (f) means for executing each of the test cases in an acceptance test to produce a set of test results for each of the test cases;
• (g) means for evaluating each of the sets of test results against the refined high level quality assurance resource estimate and the refined high level quality assurance time estimate;
• (h) means for reporting one or more defects tracked during the execution of each of the test cases;
• (i) means for correcting the one or more reported defects;
• (j) means for re-testing the corrected one or more defects;
• (k) means for negotiating a sign off of the acceptance test with a client;
• and
• (l) means for creating and storing an application audit package.

A process of acceptance test plan processing in a quality assurance process comprising the steps of:

• (a) creating an overview describing a project being implemented;
• (b) developing a plurality of objectives stating a plurality of high level goals and a plurality of strategies required to successfully complete the acceptance test plan process;
• (c) identifying a plurality of risks to a schedule for and a quality level of the acceptance test plan process;
• (d) proposing one or more remedies for each identified risk;
• (e) identifying one or more basic testing-related issues and support issues required to successfully complete the acceptance test plan process;
• (f) drafting a description of software and hardware necessary for the acceptance test plan process;
• (g) identifying one or more limitations imposed upon the acceptance test plan process;
• (h) identifying a list of persons necessary to approve an acceptance test plan of the acceptance test plan process;
• (i) drafting a glossary including a definition of each technical, business and QA term used in the acceptance test plan;
• (j) developing an acceptance test strategy;
• (k) identifying one or more conditions for execution of the acceptance test plan;
• (l) creating a test specification including one or more types of processing cycles and one or more environmental changes that may be required during the acceptance of the acceptance test plan;
• (m) identifying a plurality of test cases to be verified during the execution of the acceptance test plan;
• (n) identifying a testing schedule and a scope of testing described in the acceptance test plan;
• and
• (o) identifying a framework for handling one or more severe system problems that are present at the end of the execution of the acceptance test plan.

A system for acceptance test plan processing in a quality assurance process comprising:

• (a) means for creating an overview describing a project being implemented;
• (b) means for developing a plurality objectives stating a plurality of high level goals and a plurality of strategies required to successfully complete the acceptance test plan process;
• (c) means for identifying a plurality of risks to a schedule and a quality level of the acceptance test plan process;
• (d) means for proposing one or more remedies for each identified risk;
• (e) means for identifying one or more basic testing-related issues and support issues required to successfully complete the acceptance test plan process;
• (f) means for drafting a description of software and hardware necessary for the acceptance test plan process;
• (g) means for identifying one or more limitations imposed upon the acceptance test plan process;
• (h) means for identifying a list of persons necessary to approve an acceptance test plan of the acceptance test plan process;
• (i) means for drafting a glossary including a definition of each technical, business and quality assurance term used in the acceptance test plan;
• (j) means for developing an acceptance test strategy;
• (k) means for identifying one or more conditions required for execution of the acceptance test plan;
• and
• (l) means for creating a test specification including one or more types of processing cycles and one or more environmental changes that may be required during the acceptance test;
• (m) means for identifying the test cases to be verified during the execution of the acceptance test plan;
• (n) means for identifying a testing schedule and a scope of testing described in the acceptance test plan;
• and
• (o) means for identifying a framework for handling one or more severe system problems that are present at the end of the execution of the acceptance test plan.

A process of creating a plurality of test scripts for use in a quality assurance system comprising:

• (a) reviewing an acceptance test plan;
• (b) performing a function log process to produce a function log document including a plurality of individual test cases;
• and
• (c) performing a test script process to produce a test script document including a plurality of specific testing instructions for each of the individual test cases of the function log document.

A system for creating a plurality test scripts in a quality assurance system comprising:

• (a) means for reviewing an acceptance test plan;
• (b) means for performing a function log process to produce a function log document including a plurality of individual test cases;
• and
• (c) means for performing a test script process to produce a test script document including a plurality of specific testing instructions for each of the individual test cases of the function log.

A process for processing one or more defects found in a quality assurance process comprising the steps of:

• (a) identifying a potential defect;
• (b) creating a defect ticket record for the identified defect;
• (c) recording the identified defect on a project defect tracking log;
• (d) transmitting the defect ticket record to a developer;
• (e) receiving the defect ticket record from the developer after the developer processes and corrects the identified defect;
• (f) retesting the corrected defect;
• (g) updating the project defect tracking log and closing the corrected defect if the retesting is successful;
• (h) transmitting the defect ticket record to the developer if the retesting is not successful;
• and
• (i) placing the defect ticket record in a project folder after the closing of the defect ticket record.

A system for processing defects in a quality assurance process comprising:

• (a) means for identifying a potential defect;
• (b) means for creating a defect ticket record for the identified defect;
• (c) means for recording the identified defect on a project defect tracking log;
• (d) means for transmitting the defect ticket record to a developer;
• (e) means for receiving the defect ticket record from the developer after the developer processes and corrects the identified defect;
• (f) means for retesting the corrected defect;
• (g) means for updating the project defect tracking log and closing the corrected defect if the retesting is successful;
• (h) means for transmitting the defect ticket record to the developer if the retesting is not successful;
• and
• (i) means for placing the defect ticket record in a project folder after the closing of the defect ticket record.

A process for processing one or more defects in a quality assurance process comprising the steps of:

• (a) identifying a potential defect;
• (b) creating a defect ticket record for the identified defect;
• (c) recording the identified defect on a project defect tracking log;
• (d) transmitting the defect ticket record to a developer area;
• (e) correcting the identified defect in the developer area if the identified defect needs to be corrected;
• (f) explaining the identified defect in the developer area if the identified defect does not need to be corrected;
• (g) transmitting the defect ticket record to a quality assurance area;
• (h) retesting the identified defect if defect correction was attempted in the developer area;
• (i) updating the project defect tracking log and closing the defect ticket record if the corrected defect passes the retesting;
• (j) transmitting the defect ticket record to the developer area if the corrected defect does not pass the retesting;
• (k) updating the project defect tracking log and closing the defect ticket record if defect correction was not attempted in the developer area;
• and
• (l) placing the defect ticket record in a project folder after the closing of the defect ticket record.

A system for processing defects in a quality assurance process comprising:

• (a) means for identifying a potential defect;
• (b) means for creating a defect ticket record for the identified defect;
• (c) means for recording the identified defect on a project defect tracking log;
• (d) means for transmitting the defect ticket record to a developer area;
• (e) means for correcting the identified defect in the developer area if the identified defect needs to be corrected;
• (f) means for explaining the identified defect in the developer area if the identified defect does not need to be corrected;
• (g) means for transmitting the defect ticket record to a quality assurance area;
• (h) means for retesting the identified defect if defect correction was attempted in the developer area;
• (i) means for updating the project defect tracking log and closing the defect ticket record if the corrected defect passes the retesting;
• (j) means for transmitting the defect ticket record to the developer area if the corrected defect does not pass the retesting;
• and
• (k) means for placing the defect ticket record in a project folder after the closing of the defect ticket record.