What’s the difference between Inspections and Walkthroughs?

As said in the previous sections the difference between validation and verification is that in validation we actually execute the application, while in verification we do review without actually running the application. Verifications are basically of two main types Walk-through and Inspection. Walkthrough is an informal way of verification. For instance you can call your colleague and do an informal walkthrough to just check if the documentation and coding is proper. Inspection is a formal procedure and official. For instance in your organization you can have an official body which approves design documents for any project. Every project in your organization need to go through an inspection which … Click here to continue…..

Can you explain requirement traceability and its importance?

In most organization testing only starts after executio n / coding phase of the project. But if the organization wants to really benefit from testing, then testers should get involved right from the requirement phase. If the tester is getting involved right from the requirement phase then requirement traceabil ity is one of the important reports which can give what kind of test coverage the test cases have . Below is the figure which shows how we can measure the coverage using the requirement traceability matrix. We have extracted the important functionality from the requirement document and aligned the same on the left hand side of … Click here to continue…..

What are the different strategies of rollout to the end users?

There are major four ways of rolling out any project:- Pilot: – Actual production system is installed at a single or to limited number of users. Pilot basically means that the product is actually rolled out to limited users for real work. Gradual Implementation: – In this implementation we ship the entire product to the limited users or all users at the customer end. Here the developers get instant feedback from the earlier recipients which allow them to make changes before the product is available. But yes the downside is that developers and testers maintain more than one version at one time. Phased implementation: – In … Click here to continue…..

Can you explain what is Usability testing?

Usability testing is a testing methodology where the end customer is asked to use the software to see if the product is easy to use, to see the customer perception and task time. The best way to finalize customer point of view for usability is by using prototype or mock up software during the initial stages. By giving customer prototype before the development startup we confirm that we are not missing anything fro m the user point of view. Prototype and Usability testing