Usually the V model is chosen over other QA methodologies because it’s the most logical way to carry out development and testing of a project. In any software development model, the development plan and test plan needs to be developed together. This is because the testing team acts parallel to the development team, i.e., the output of the testing team goes as input to the next development activity. Once the final design of the project is drawn and development begins, the first step, i.e. unit testing is conducted. It is done by the developer himself using a local test case sheet. Once a complete module is completed and unit-tested by the developer, it is sent for integration testing. Here, smaller modules of the project are tested together based on test functions supplied by the customer.
Once all modules work in unison, they are passed on for system testing that is done by the onsite team. After the onsite team confirms the successful run of the module, it is sent for user acceptance testing. This is done by the client himself on real world data. This entire testing process needs to be done on a common testing tool to track overall metrics pertaining to defects and quality.
Use Patent Claims
Include Install Instructions
These details are provided for information only. No information here is legal advice and should not be used as such.