What is a good requirement and bad Requirement

Answer Posted / abhijeeth

When a requirement is submitted and if the requirements are
stable till the deployment of project, then we can say it's
a good requirement.
When we have written test cases for a particular
requirement and also some modules have been developed and
during these stages if the requirement is changed it's
called bad requirement.

Is This Answer Correct ?    1 Yes 1 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

Zenq interview questions for manual testing

1415


HI GUYS,, I HAVE 3 YEARS OF EXP IN MANUAL TESTING...NEXT MONTH ONWARDS I WORK FOR MOBILE TESTING....PLS SUGGEST ME WHAT I LEARN FOR TRAING,, MOBILE TESTING OR ANDROID....FOR MOBILE TESTERS NEED ANDROID(IFONE) DEVOLOPMENT KNOWLEDGE OR NOT? EXPLAIN CLEARLY

1709


what types of testing have u done in ur project?and expalin it detail?

1548


What are the different types of software testing?

715


how will you estimate of your website?

1674






do we require any scripting languae to write test cases in test director? what for it is used?it is like back end?only database we can there?

1659


date format and we should 8 digits - not accepted only /accepted write how many in test cases in the date format valid , and in valid

1058


When should you opt for manual testing over automation testing?

789


what are the Cs in testing

1633


How to do integration testing on duster......

1252


HI, This question is Investment Banking domain related Question. I was asked in an Interview to tell the 5 test cases for Equity,Bond,Futures and options. Please help.. Pragya

3889


What is your Approach when you find 10 Sev-1 bugs in 50 test cases?

2080


Can any1 tell me suppose u r doing manual testing on unix platform with Shell Script, then how it is done? How u r implementing it & what is the use of Shell scripting on Manual Testing? plzzzzzzz i need ur help.

1802


Information about Automated Software Installer

1465


can anybody send the project you have tested with the clear descriptions,and recent bugs u found in that

1699