What is V & V? Difference between V & V...

Verification ensures the product –
is designed to deliver all functionality to the customer; it involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; and it can be done with checklists, issues lists, walkthroughs and inspection meetings.

Validation ensures –
that functionality, as defined in requirements, is the intended behavior of the product; and
validation typically involves actual testing and takes place after verifications are completed.

Verification
It takes place before validation, and not vice versa.
evaluates documents, plans, code, requirements, and specifications.
The inputs of verification are checklists, issues lists, walkthroughs and inspection meetings, reviews and meetings.
The output of verification is a nearly perfect set of documents, plans, specifications, and requirements document.

Validation
It evaluates the product itself.
The input of validation, is the actual testing of an actual product.
The output of validation, is a nearly perfect, actual product.

In short, Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements, and specifications. Validation, on the other hand, evaluates the product itself. The inputs of verification are checklists, issues lists, walkthroughs and inspection meetings, reviews and meetings. The input of validation, on the other hand, is the actual testing of an actual product. The output of verification is a nearly perfect set of documents, plans, specifications, and requirements document. The output of validation, on the other hand, is a nearly perfect, actual product.

SQC Vs. SQA

Software Quality Control Software Quality Assurance


Is perceived as a professional role Is perceived as management’s eyes and
ears.

Has well-defined technical goals Has no history of saving anyone yet

Has leverage to stop the show Has fuzzy alignment with the project’s
goals.

Has authority with the developers Has no leverage to stop anything

Is aligned with the project goals Has few opportunities to show proficiency
before the problem

What is the difference among Testing, QA and QC

Quality Assurance: A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives. E.g are requirements being defined at the proper level of detail.

Quality Control: A set of activities designed to evaluate a developed work product. E.g. are the defined requirements the right requirements.

Testing: The process of executing a system with the intent of finding defects. (Note that the "process of executing a system" includes test planning prior to the execution of the test cases.)

Most Frequently asked Questions in Unix...

1. Which command is used to run an interface?
Sh

2. How will you see the hidden file ?
Ls -a

3. What is the command used to set the date and timings …
Date

4. Some basic commands like copy, move,delete ?
Cp, mv, rm

5. Which command used to the go back to the home directory ….
cd..

6. Which command used to view the the current directory
PWD

7. How to unzip the files in Unix?
tar -cvf

8. How to find help for a specific Command?
Mount (Command)

9. How t ochange Password ?
Passwd

10. How to search a string from file?
grep

11. How to cahnge Permissions on a file?
chmod

12. What is the command for a calculator?
bc

What should be done after writing test case?

After writing testcase we should review it. Reviewing can be done by another Test engineer/Peer or test lead...Once got the result fix the review comments. After completion of writing test cases you need to review the cases for completeness and correctness to check whether every functionality is covered, then we have to wait for build and we have to exe the reviewed testcases....