What is a good requirement and bad Requirement
Answers were Sorted based on User's Feedback
Answer / senthilkumar mps
There is nothing called Good or Bad requirement.i see the
answers posted here are from the developer's angle not from
testers. Any requirement we receive from the client is meant
to satisfy the need of them. if at all, some requirement is
going to be called as bad requirement is that, when it
contradicts other requirements or misleads the functionality
of the same system. even then it'll be called as improper
system requirement.
i hope everyone agree with my answer.
Senthilkumar @ MPS
| Is This Answer Correct ? | 15 Yes | 1 No |
Answer / divya pasupuleti
Which is Freezable,Consistent and clear is a good
requirement and which is changing frequently is a bad
requirement.
| Is This Answer Correct ? | 9 Yes | 1 No |
Answer / 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 |
Answer / sridhar
Requirements which are freeze, understandable,easy and
clear are good one.
Requirements which are keep on modifing are bad one
| Is This Answer Correct ? | 0 Yes | 1 No |
Which is Freezable,Consistent and clear without any
ambiguity, its good requirement and which is changing
frequently is a bad
requirement.
| Is This Answer Correct ? | 0 Yes | 1 No |
How to test a web service manually?
After fix the bug if requirement change the tester what will do?
What is the difference between defect tracking tool and QC?
How can a white box testing performed ? MAnual or automated ?
How to do the performance testing Manualy? Do u have a test case for that?
Can you explain equivalence partitioning?
why we go for winrunner ? and when we go for winrunner
What is the difference between a Test Plan and a Test Strategy?
What are all the documents you are going to submit at the time of release as a testlead?
Assume you are handling multiple projects and the scheduled were clashing how would you mange about this
1.What is Traceability matrix and how it is done ? 2.What are the different levels of testing used during testing the application? 3.What is Traceability matrix and how it is done ? 4. How can you differentiate Severity and Priority based on technical and business point of view. plz do reply..............
why RUPis important or what are all the advances in RUP?