Monday, 27 October 2014

Verification & validation

                                    More....

 VERIFICATION AND VALIDATION


Verification and validation, in engineering or quality management systems, it is the act of reviewing, inspecting or testing, in order to establish and document that a product, service or system meets regulatory or technical standards.

1.The objective of verification and validation is  found to be similar.
2.Both these designs have been designed to remove errors in software.
3.In spite the apparent similarity between their objectives,the underlying principles of these two bug detection techniques and their applicability are very different.
4.The main difference between verification and validation are the following.

VERIFICATION:

1.Verification is the process of determining whether the output of one phase of software development conforms to that of its previous phase whereas in validation is the process of determining whether fully developed project conforms to its required specification.
2.verification step can be used to check if the design documents produced after the design step conform to the requirement specification.on the other hand,validation is applied to the fully developed and integrated software to check if it satisfies the customer’s requirements.
3.The technique used in verification include review,simulation,and formal verification.on the other hand,validation techniques are primarily based on product testing.
4.verification process is carried out during the development process to check if the development activities are being carried out correctly,whereas validation is carried out towards the end of the development process to check if the right product as required by the customer has been developed.

5.verification technique can be viewed as an attempt to acheieve phase containment of  errors. phase containment of  errors has been acknowledged to be a cost-effective way to eliminate program bugs.


Protected by Copyscape Online Plagiarism Scanner

SQA two marks


1) Test plan Identifier: - Some companies generated a unique number to represent the test plan and to find the software level to which it is related. Test plan level will be the same as the software level. The number is used to identify whether the test plan is a master plan or level plan or an integration plan or whichever plan level.

2)  What is stress testing?
       Stress testing  is  used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, it includes:
·          determining breaking points or safe usage limit and to  confirm intended specifications are being met

3) What are the levels of testing?
        A software product has three different levels
They are,
Unit testing
Integration testing
System testing

4) What is test plan?
        Test plan consists of determining relevant test strategies and planning for any test bed that may be required. Since there must be a careful implementation of test plan is necessary.

5) What is performance testing?
§  Testing that is being done under stability and workload. It can serve different purposes like it can demonstrate that the system meets performance criteria.

6) What is security testing?
§                          Security testing is basically a type of  testing that’s done to check whether the application or the product is secured or not.

§      It is a process to determine that an information system protects data and maintains functionality as intended

7) Quality : - 

  • cannot  be defined, but can be assessed from the user's perspective and important factor in business.
  • Quality must be monitored when it occurs.
  • Quality must be measurable and predictable when it occurs
8) Views of software Quality: - 
  • Dr.Boehem define software quality as achieving higher levels of user satisfaction, portability, maintainability, robustness and fitness for use.
  • Phil Crosby define software quality as conformance to user requirements.
  • Edward Deming considers quality to be striving for excellence in reliability and functions by continuous improvement in the software development lifecycle itself.






Have a look at


Protected by Copyscape Online Plagiarism Scanner

Friday, 17 October 2014

Software quality assurance questions


Two marks: -

  1. Differentiate validation and verification.
  2. What is test plan.
  3. Give any two examples of equivalence partitioning.
  4. What is combinatorial generation.
  5. What is a finite state machine.
  6. Give any two examples of transition coverage
  7. Differentiate control flow and data flow graph.
  8. Give any two examples of test automation technique.
  9. What are test oracles?
  10. What are the techniques available for usability testing.
16 marks: - 

  1. Discuss boundary value analysis
  2. Explain the decision table with diagram in detail
  3.  Explain the different controls in flow graph.
  4. Describe the multiple condition testing with suitable example.
  5. Explain the different types of functional testing.
  6. Explain acceptance testing with an example
  7. Explain system testing with an example.
other questions
  1. Explain the types of testing(4)
  2. Explain the test generation in detail(12)
  3. Explain test cases with an example(8)
  4. Explain validation with an example(8)
  5. Explain MC/DC path test with an example.
  6. Discuss the Def-clear and Def-use in detail.

Thursday, 16 October 2014

Equivalence Partitioning: -
   

  • It involves the process of identifying a small set of representative input values that would produce as many different output conditions as possible.
  • Input domain is too large for testing so we move on to equivalence partitioning.
  • Input domain must be partitioned into finite number of sub-domains for the test input.
  • The sub-domains are known as equivalence class.
  • Equivalence class is the source of test input.
  • The objective is to divide the input domain of the system under test into classes or groups of input.
  • Every input in the same class have the same effect on the system under testing.
  • The equivalence class is a set of input and the system treats them identically when the system is tested.
  •