Posts filed under 'v model'
V-model & Testing Tools
There are many QA methodologies that are used by software organizations; but one of the most commonly and widely used methodology is the waterfall methodology. The methodology has a logical approach to software development and implements the development and testing activity simultaneously.
Waterfall or V-model is one methodology that works well with new testing tools. It is easy to integrate a test automation tool into an existing setup that works with the v-model. In the v-model, test case generation and test metrics generation is very simple. Coupled with an intelligent testing tool, the test management team can realize high throughput for all its projects.
Add comment August 17, 2009
V Model Working of Project Development
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.
Add comment April 3, 2009
V Model, Truly the Best but….
Of the different software development lifecycles, V model comes very useful in managing complex projects. Known as the verification and validation model, the peculiarity of this model is that development and testing happen side by side. That means whatever the developing team has developed is checked by the testing services team so as to reduce the possibility of errors. This model helps the QA test management team in ensuring the quality of the product better than other models.
But for every process there are some drawbacks. The two important drawbacks of V model are that it’s time consuming as well as expensive. So if the requirements are perfect and clear it is always better to go for the less expensive models.
Add comment February 13, 2009
V Model
The kind of software methodology used in the development of software determines the quality of the software product. There are several QA methodologies, each having their own merits as well as demerits. The most common methodologies used in software development are Hybrid, Waterfall, Agile model, V Model and so on. Of the different models let’s look at V Model in particular. In V Model the most important aspects are verification and validation and hence the name ‘V’.
V Model is suitable for projects which are complex. Its most important aspects are that it is a structured, well documented and disciplined process. Not only that, it is also a rigorous, measurable and predictive process. In order to make sure that the developed software conforms to the defined requirements, the test tools used should be equally good. It should perfectly fit with the software methodology selected. Let’s see how the test development tools perform if the methodology selected is V Model.
Feature-rich advanced test development tools like Zephyr produce live metrics on all key stages of the V Model testing cycle. It constantly measures the productivity, efficiency and quality of the software by reporting on test case creation, coverage, test execution progress and defects. It helps to maintain rigor in the testing process and handles multiple testing cycles for System, Integration, and final Acceptance.
Add comment September 18, 2008