Information about Software testing & Planning.

Asked By 90 points N/A Posted on -
qa-featured

I have some inquiries about the Requirement Traceability Matrix. What is it and what are its purpose in a system? Also, I want to know the difference between Pilot and Beta Testing. Another thing is, how can I be able to do a risk analysis while testing a software?

Sorry if I have lots of questions, but I  will be using this on a project. Few more question is, what is the distinction between coupling and cohesion and lastly, when can I select the automated testing over manual testing?

That's it. Please help me in all these queries as I need to pass this project ASAP.

SHARE
Answered By 0 points N/A #188929

Information about Software testing & Planning.

qa-featured

Hello,

How are you?

The requirement traceability matrix is simply a tool that helps one trace each and every requirement of an IT project to various phases of the project. This helps in maintaining a relationship between the various phases of the software life cycle development.

For ex: Say a requirement R1 traces to design element D2, links to a development/coding element C3 and also connected to a test case T4. The requirements traceability matrix will help you identify a relationship between these elements. So in case R1 changes, you need what other elements will change.

It also helps user to trace whether all requirements have been met, various deliverable documents have been created and plan project tasks. A sample traceability matrix screenshot is attached.

Pilot testing is performed by a group of selected users mostly to identify any potential problems related with the performance or requirements and is performed in the development environment of a software, whereas, the Beta testing is what is performed in Production/Real time environment by all users, i.e., not a selected set.

For analyzing risk in software testing you might have to look at the below aspects;

  1. Hardware – whether a new hardware is being used or the old hardware is capable of running the new software.
  2. Technology – whether my personnel or my system is equipped to handle the new software.
  3. Automation Tool – how will the new automation tool behave?
  4. Availability of test resource – whether it resources be available 24*7 or only some part of the day.

Coupling is the strength of interconnections between different program units.

Cohesion describes how various modules fit together.

Automated testing is advisable to use when you have a large set of test cases to be executed and the reliability of test cases is important. The automated software cost can be significant.

Manual testing should be used where limited number of test cases is to be used. They are less reliable than automated results. They are used when cost criteria is important.

Teresa Mat

Related Questions