Common - What is a good requirement ?

GeekInterview.com > Interview Questions > Testing > Common

Go To First | Previous Question | Next Question

Common | Question 194 of 249

What is a good requirement ?

How do you describe a good requirement, In terms of characteristics.
As far as I know, A requirement without hidden dependencies and with general characteristics such as unique and so on.. can you add more

Total Answers and Comments: 5

Last Update: March 17, 2008 Asked by: Gnanesh77

Sponsored Links

Best Rated Answer

—

Submitted by: billyin

-complete. Is anything missing or forgot?
-Accurate. Is the proposed solution is correct?Does it properly define the goal?

-precise, unambiguous, and clear. Is the description exact and not vague? Is it easy to read and understand?
-Consistent.Is the description of the feature written so that it doesn't conflict with itself or other itemsin the spec.
-Relevant. Is it extra information that should be left out? Is the feature traceable to an original customer need?
-Feasible. Can the featurebe implemented with the available personnel, tools,and resourceswithin the specified budget and schedule?
-testable. Can the feature be tested? Is enough infomation provided that a tester could create tests?

Above answer was rated as good by the following members:
KauShreya

November 13, 2007 06:49:59

Gnanesh77

Member Since: June 2007 Contribution: 5

RE: What is a good requirement ?

Characteristics of a good requirement--->
1. Clear
2. Complete
3. Detailed
4. Attainable
5. Cohesive(able to intergrate/unite)
6. Testable

Is this answer useful? Yes | No

November 28, 2007 05:04:20

vandana Shekhar

Member Since: November 2007 Contribution: 4

RE: What is a good requirement ?

I want to add few more characteristics to the list:

1. Consistent: doesn't contradict other requirements.

2. Unambigous: Each requirement must have one and only one interpretation.

3. Verifiable: Stated requirement is not vague or general but is quantified in a manner that can be verified by one of the following 4 alternative methods:
a) Inspection
b) Demonstration
c) Analysis
d) Test

Is this answer useful? Yes | No

January 02, 2008 18:48:00

billyin

Member Since: April 2007 Contribution: 8

RE: What is a good requirement ?

-complete. Is anything missing or forgot?
-Accurate. Is the proposed solution is correct?Does it properly define the goal?

-precise unambiguous and clear. Is the description exact and not vague? Is it easy to read and understand?
-Consistent.Is the description of the feature written so that it doesn't conflict with itself or other itemsin the spec.
-Relevant. Is it extra information that should be left out? Is the feature traceable to an original customer need?
-Feasible. Can the featurebe implemented with the available personnel tools and resourceswithin the specified budget and schedule?
-testable. Can the feature be tested? Is enough infomation provided that a tester could create tests?

Is this answer useful? Yes | No

1 0

Overall Rating: +1

January 31, 2008 06:45:31

melosha

Member Since: October 2006 Contribution: 7

RE: What is a good requirement ?

A Good Requirement should be

1. Unambiguous- Are the definitions and descriptions of the required capabilities precise?
2. Complete - Are there any gaps or omissions?
3. Consisent - Free from Internal and external contradictions?
4. Implementable - Can the requirements be realized in practice?
5. Testable - Can the requirements be tested effectively?

Is this answer useful? Yes | No

March 17, 2008 16:26:54

saransh.kanaujia

Member Since: February 2008 Contribution: 20

RE: What is a good requirement ?

a good requirement is which is clear. contains all necessary details required to design code and test any product.

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank