My queries

Question to ask to tutor
Sr. Particulars
1. What is definition of software testing?
2. What is validation?
3. What is verification?
4. What is static analysis?
5. What is seizes?
6. What is maneuvering?
7. Please explain” Testing can be done by tests where the software code is executed to demonstrate the results of running tests (often called dynamic testing)
8. Explain “Demonstrate that (software products) are fit for purpose” ?
9. What is root cause analysis?
10. What is component testing?
11. What is Integration testing?
12. What is system testing?
13. What does this statement means “This can take the form of attribute measures such as mean time between failures to assess reliability, or an assessment of the defect density in the software to assess

Component testing:
>Component testing is also known as module and program testing. It finds the defects in the module and verifies the functioning of software.
>Component testing is done by the tester.
>Component testing may be done in isolation from rest of the system depending on the development life cycle model chosen for that particular application. In such case the missing software is replaced by Stubs and Drivers and simulate the interface between the software components in a simple manner. Let’s take an example to understand it in a better way. Suppose there is an application consisting of three modules say, module A, module B and module C. The developer has developed the module B and now wanted to test it. But in order to test the module B completely few of it’s functionalities are dependent on module A and few on module C. But the module A and module C has not been developed yet. In that case to test the module B completely we can replace the module A and module C by stub and drivers as required.
Stub: A stub is called from the software component to be tested.
Driver: A driver calls the component to be tested.

System testing:
In system testing the behavior of whole system/product is *tested as defined by the scope of the development project or product.
*It may include tests based on risks and/or requirement specifications, business process, use cases, or other high level descriptions of system behavior, interactions with the operating systems, and system resources.
*System testing is most often the final test to verify that the system to be delivered meets the specification and its purpose.
*System testing is carried out by specialists testers or independent testers.
*System testing should investigate both functional and non-functional requirements of the testing.

Validation:
Determining if the system complies with the requirements and performs functions for which it is intended and meets the organization’s goals and user needs.
Validation is done at the end of the development process and takes place after verifications are completed.

Verification:
It makes sure that the product is designed to deliver all functionality to the customer.
Verification is done at the starting of the development process. It includes reviews and meetings, walkthroughs, inspection, etc. to evaluate documents, plans, code,requirements and specifications