Software Quality Assurance and not only 

Introduction to Software Testing

•     Software Quality Assurance
• It involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. It is oriented to 'prevention'.
  

•     Software testing
• It is an empirical technical investigation conducted to provide stakeholders with information about the quality of the product or service under test.
  

•     Software defect (BUG)
• Is an error, mistake, failure, or fault in a software that prevents it from behaving as intended
  

•     Defect tracking
• It means logging and maintaining bugs through a dedicated tool
  

•     Test Case
• A specific test to be performed, including the specific steps necessary for completing the test. Test cases typically describe actions or steps and the expected results of the action or step.
  

•     Use Case
• An implementation-neutral description of a reasonable action or task that an end user might want to accomplish. For example, a user might want to browse a site, but not necessarily view a site map. The action is general, and the use case is a tool for evaluating whether the general action can be accomplished in the particular instance of the site.
  

•     Review
• A process or meeting during which a work product or set of work products, is presented to project personnel, managers, users, customers, or other interested parties for comment or approval. Types include code review, design review, formal qualification review, requirements review.
  

•     Risk
• A measure of the probability and severity of undesired effects.
  

•     Test Documentation
• Documentation describing plans for, or results of, the testing of a system or component, Types include test case specification, test incident report, test log, test plan, test procedure, test report.

•     Audit
• To conduct an independent review and examination of system records and activities in order to test the adequacy and effectiveness of data security and data integrity procedures, to ensure compliance with established policy and operational procedures, and to recommend any necessary changes.