Software Quality Assurance:

Software QA 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'.

Quality Assurance measures the quality of processes used to create a quality product.
1. It is a system of management activities.
2. It is a preventive process.
3. It applies for entire life cycle.
4. Deals with Process.

It is very important for a tester to know difference between Quality Assurance and Quality Assurance.

Quality control:
Quality control measures the quality of a product
1.It is a specific part of the Quality Assurance procedure.
2. It is a corrective process.
3. It applies for particular product.
4. Deals with the product.

Severity and priority will be assigned for a particular bug to know the importance of the bug.
Severity: How severely the bug is effecting the application.
Priority: Informing to the developer which bug to be fix first.

Defect: While executing the Test Case if u found any mismatch, the u will report
it to the development team that is called defect.
Bug: Once the developer accepts your defect, then it is called as a bug.

Test case

Test case is a Document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly.

Test condition The condition required to test a feature.(pre condition)

Test script
A. Test script is the script which is generated by an automation tool while recording a application features.

Test data
A. Test data means the input data (valid, invalid data) giving to check the feature
of an application is working correctly.

Test bed

Test bed means under what test environment (Hardware, software set up) the
application will run smoothly.

Baseline document
The review and approved document is called as baseline document (i.e) Test plan,SRS(Software requirement Specification).

Configuration management:

Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes.

Verification:
Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings

Validation: Validation typically involves actual testing and takes place after verifications are completed.

The term 'IV & V' refers to Independent Verification and Validation.

Walkthrough:

A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required.

Inspection:
An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a moderator, reader, and a recorder to take notes. The subject of the inspection is typically a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything. Attendees should prepare for this type of meeting by reading through the document; most problems will be found during this preparation. The result of the inspection meeting should be a written report. Thorough preparation for inspections is difficult, painstaking work, but is one of the most cost effective methods of ensuring quality.