Presentation is loading. Please wait.

Presentation is loading. Please wait.

Syndicate Members: 1. GC Muhammad Uzair 2. GC Umer Naveed Malik.

Similar presentations


Presentation on theme: "Syndicate Members: 1. GC Muhammad Uzair 2. GC Umer Naveed Malik."— Presentation transcript:

1 Syndicate Members: 1. GC Muhammad Uzair 2. GC Umer Naveed Malik

2  Validation checks that the product design satisfies or fits the intended use (high-level checking), i.e., the software meets the user requirements. This is done through dynamic testing and other forms of review. Validation Testing2

3 According to the Capability Maturity Model (CMMI-SW v1.1) : Software Validation: The process of evaluating software during or at the end of the development process to determine whether it satisfies specified requirements. [IEEE-STD- 610] Validation Testing3

4  Validation Testing ensures that the product actually meets the client's needs. It can also be defined as to demonstrate that the product fulfills its intended use when deployed on appropriate environment.  It answers to the question, Are we building the right product? Validation Testing4

5  Validation Testing - Workflow: Validation testing can be best demonstrated using V-Model. The Software/product under test is evaluated during this type of testing. Validation Testing5

6 6

7 Following methods are included in validation testing: 1. Unit Testing 2. Integration Testing 3. System Testing 4. User Acceptance Testing Validation Testing7

8  Unit testing, a testing technique using which individual modules are tested to determine if there are any issues by the developer himself. It is concerned with functional correctness of the standalone modules.  The main aim is to isolate each unit of the system to identify, analyze and fix the defects. Validation Testing8

9  Reduces Defects in the newly developed features or reduces bugs when changing the existing functionality.  Reduces Cost of Testing as defects are captured in very early phase.  Improves design and allows better refactoring of code.  Unit Tests, when integrated with build gives the quality of the build as well. Validation Testing9

10 10

11  Black Box Testing - Using which the user interface, input and output are tested.  White Box Testing - used to test each one of those functions behavior is tested.  Gray Box Testing - Used to execute tests, risks and assessment methods. Validation Testing11

12 Upon completion of unit testing, the units or modules are to be integrated which gives raise to integration testing. The purpose of integration testing is to verify the functional, performance, and reliability between the modules that are integrated. Validation Testing12

13  Big-Bang Integration  Top Down Integration  Bottom Up Integration  Hybrid Integration Validation Testing13

14  System Testing (ST) is a black box testing technique performed to evaluate the complete system the system's compliance against specified requirements. In System testing, the functionalities of the system are tested from an end-to-end perspective.  System Testing is usually carried out by a team that is independent of the development team in order to measure the quality of the system unbiased. It includes both functional and Non- Functional testing. Validation Testing14

15 Validation Testing15

16  User acceptance testing, a testing methodology where the clients/end users involved in testing the product to validate the product against their requirements. It is performed at client location at developer's site.  For industry such as medicine or aviation industry, contract and regulatory compliance testing and operational acceptance testing is also carried out as part of user acceptance testing. Validation Testing16

17  UAT is context dependent and the UAT plans are prepared based on the requirements and NOT mandatory to execute all kinds of user acceptance tests and even coordinated and contributed by testing team. Validation Testing17

18 Validation Testing18

19 Acceptance criteria are defined on the basis of the following attributes:  Functional Correctness and Completeness  Data Integrity  Data Conversion  Usability  Performance Validation Testing19

20  Software validation ensures that the product actually meets the user's needs, and that the specifications were correct in the first place.  Software validation ensures that "you built the right thing". Software validation confirms that the product, as provided, will fulfill its intended use. Validation Testing20


Download ppt "Syndicate Members: 1. GC Muhammad Uzair 2. GC Umer Naveed Malik."

Similar presentations


Ads by Google