V-Model enables product to achieve quality, it consists of developing the product and testing the product simultaneously. V-Model extends testing to the beginning of the lifecycle. It uses static testing techniques for finding the faults in the functional specification. V-Model is very helpful in execution and planning of the project.
Concept Analysis: V-Model initiates its process by analyzing the Concept of Customer and establishes has to perform for accomplishing the project hence a requirement document would be provided to the QA team at the start of the project. V-Model follows the parallel way to accomplish the project so document would be sent to the customer for reviewing it. There can be different methods for gathering the requirements such as interviews, Questionnaires, Observation, Use Cases and many more.
Designing Phase: Includes studying of requirements where professionals find out the possibilities and techniques which enables concept to be implemented. Customer would be informed if any of the requirements is not feasible and Document would be edited as per the feasibility study. Software Requirements Specification (SRS) Document would work as a Blue print for the Development phase.
Functional Phase: In the functional phase, Functionality would be defined of each module as interdependency of modules, database functionality, Diagrams and etc.
Technical Phase: In the technical phase, technologies that would be used for particulars modules would be defined which enables analyst to assign separate modules to particular coder.
Development Phase: In development phase, Developer starts their development. It includes of listing the issues, to have complete input and output for a module and to design unit test for this module.
Unit Testing: Unit test are the individual tests which determines developed code is fit for use or not. The purpose of unit testing is to verify the internal logic code within function. During the unit test, tester use static tools where variation of data can be tested.
Component Testing: Component testing, we use for testing the separate module together to reveal faults in the interfaces and to make interaction between integrated components.
System Testing: We use system testing for comparing between the actual system and system requirements. System testing is nothing but to predicate the future user of the product. With the help of this test, actual requirements can be met.
Maintenance Testing: We use this part of testing to maintain and support for the whole testing process and nourishment would be done in this part of test.
User Acceptance Testing: This is the test which is tested from the user point of view and it determines whether system satisfies the specified requirements or not.
Concept Analysis: V-Model initiates its process by analyzing the Concept of Customer and establishes has to perform for accomplishing the project hence a requirement document would be provided to the QA team at the start of the project. V-Model follows the parallel way to accomplish the project so document would be sent to the customer for reviewing it. There can be different methods for gathering the requirements such as interviews, Questionnaires, Observation, Use Cases and many more.
Designing Phase: Includes studying of requirements where professionals find out the possibilities and techniques which enables concept to be implemented. Customer would be informed if any of the requirements is not feasible and Document would be edited as per the feasibility study. Software Requirements Specification (SRS) Document would work as a Blue print for the Development phase.
Functional Phase: In the functional phase, Functionality would be defined of each module as interdependency of modules, database functionality, Diagrams and etc.
Technical Phase: In the technical phase, technologies that would be used for particulars modules would be defined which enables analyst to assign separate modules to particular coder.
Development Phase: In development phase, Developer starts their development. It includes of listing the issues, to have complete input and output for a module and to design unit test for this module.
Unit Testing: Unit test are the individual tests which determines developed code is fit for use or not. The purpose of unit testing is to verify the internal logic code within function. During the unit test, tester use static tools where variation of data can be tested.
Component Testing: Component testing, we use for testing the separate module together to reveal faults in the interfaces and to make interaction between integrated components.
System Testing: We use system testing for comparing between the actual system and system requirements. System testing is nothing but to predicate the future user of the product. With the help of this test, actual requirements can be met.
Maintenance Testing: We use this part of testing to maintain and support for the whole testing process and nourishment would be done in this part of test.
User Acceptance Testing: This is the test which is tested from the user point of view and it determines whether system satisfies the specified requirements or not.
Posts
