Author Topic: Qualities of Good requirement  (Read 1115 times)

kalyan ram.N

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Qualities of Good requirement
« on: August 24, 2018, 02:52:26 am »
What are the Qualities of Good Requirement?

admin

  • Administrator
  • Newbie
  • *****
  • Posts: 3
    • coepd.com
Re: Qualities of Good requirement
« Reply #1 on: August 24, 2018, 11:23:03 am »
IF requirement satisifies SMART and  FURPS techniques then it can be considered as a good requirement.

1180986106

  • Global Moderator
  • Newbie
  • *****
  • Posts: 12
Re: Qualities of Good requirement
« Reply #2 on: August 29, 2018, 06:39:26 pm »
Requirement can be considered good when it is testable, clear, correct, easily understandable, feasible, independent, atomic, necessary.

1180793807

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: Qualities of Good requirement
« Reply #3 on: October 16, 2018, 11:13:36 pm »
a good requirement can be said when it can be easily available to public, can be understood by the developers, can be tested, manipulated, altered when there is need and can be readily available to the users. in short a good requirement should be able to be user friendly for both the makers and also to the users.

1181278605

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Qualities of Good requirement
« Reply #4 on: October 24, 2018, 01:18:30 pm »
A good requirement should follow 3C IE correct,consistent,and complete.
to gather requirement we should follow 5W1H RULE.
TO COMMUNICATE REQUIREMENT one can follow 3 w technique. ie what ,who, when.
we can use different technique to gather requirement. this technique are
FURPUS,CUCV,CAE,APVU,SMART.

it depend on the organiasation which rule they followed. most common use technique are FURPUS AND SMART.

1181278405

  • Global Moderator
  • Newbie
  • *****
  • Posts: 8
Re: Qualities of Good requirement
« Reply #5 on: December 04, 2018, 05:28:13 pm »
Good requirement basically refers to the needs described in a crystal clear manner and do not contradict other requirements.

1182198007

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Qualities of Good requirement
« Reply #6 on: December 04, 2018, 11:35:53 pm »
Even with a set of requirements which communicate well and can be controlled there is still the issue of how they affect the developers. The two key characteristics of good requirement are:

Credible - What is asked for is technically possible.
Clean - They do not have any implementation decisions.

Adithya Mahendra

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Qualities of Good requirement
« Reply #7 on: February 25, 2019, 10:58:46 am »
A good requirement is the one which defines and addresses the needs of a client. It should be a necessary one to resolve the client's issue and also answer the needs of the small stakeholders or end users who use this application. Apart from this, it should be easily developed by the developers and tested by the testers. In case of any change request, it should be easily modified.

1191940101

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Qualities of Good requirement
« Reply #8 on: March 23, 2019, 09:01:23 am »
Good requirements clearly and accurately reflect the business need. They can be used with confidence to develop and test the solution.

1171835509

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Qualities of Good requirement
« Reply #9 on: April 03, 2019, 04:41:06 pm »
Requirements are the most essential aspect for the client and the BA. A good requirement is where the client is concise and clear about his vision and the BA 's capability to understand the client and understand their requirement near precisely. These requirements must be altered in a simple and clear manner for better understanding by the internal teams developing the product and also to explain to the client after its completion.

1190244102

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Qualities of Good requirement
« Reply #10 on: August 03, 2019, 07:58:43 pm »
IF requirement satisfies SMART and  FURPS techniques then it can be considered as a good requirement.

1190687607

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Qualities of Good requirement
« Reply #11 on: August 25, 2019, 03:57:32 pm »
Following are the Qualities of Good Requirement -
1. Correct
2. Unambiguous
3. Complete
4. Consistent
5. Importance
6. Stability
7. Verification
8. Modifiable
9. Traceable

1190538101

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Qualities of Good requirement
« Reply #12 on: October 04, 2019, 07:40:00 pm »
Complete - Requirements must be complete, because if they are not then functionality expected by the users will be missing.
This means as stated in User Requirements they must have all of the:
Functional requirements,Non-functional requirements,Design objectives,Reference material including a definition of terms used and units of measurement.

Clear - Even if the requirements are complete they must be understood with only one meaning. This means they must be unambiguous and specific.

Consistent - The key point about consistency is that no requirement contradicts what another

Control Characteristics - A set of requirements need to do more than just communicate, there are also issues of how they will be controlled through the project. The key control characteristics are that the requirements must be:

Certifiable - They can be verified and validated.

Chosen - They have been ranked as to importance.

Chaseable - They can be traced forward and backwards.

Certifiable - A requirement is not a requirement unless it can be verified and validated.

Chosen - Not all requirements are created equal, some “Must” be included, or the system will be a waste of effort, others “Could” be included as they enhance what the system could achieve.

Chaseable - It must be possible to trace a requirement both back to its business reason, and through to the design and testing documentation. Without the ability to chase them through it is impossible to compare any documentation to see if they have been implemented.

Construction Characteristics- Even with a set of requirements which communicate well and can be controlled there is still the issue of how they affect the developers. The two key characteristics are if the requirements are:

Credible - What is asked for is technically possible.
Clean - They do not have any implementation decisions.

Technical feasibility means comparing the requirements logical model, with what is currently technically possible. There are many times when what is wanted is well beyond what can be delivered at the moment. An example from the past was ambitious websites, when users had slow dial-up lines. The websites were not technically feasible as users could not access them.

Achievable feasibility means comparing the time, resources, quality and scope of the projects and assessing the risk of ever achieving it.

Clean - A clean set of requirements is one where only the logical structure has been defined, and decisions about physical design and implementation have been left out. The more physical design decisions that are taken by the users the fewer the options that are available to the developers to deliver what is needed, and the more likely that a poor quality system will result.

1191649002

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: Qualities of Good requirement
« Reply #13 on: October 23, 2019, 05:07:35 pm »
What is requirement elicitation ? and Requirement Engineering >

1190686707

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: Qualities of Good requirement
« Reply #14 on: December 14, 2019, 11:56:19 am »
In requirements engineering, requirements elicitation is the practice of researching and discovering the requirements of a system from users, customers, and other stakeholders.[1] The practice is also sometimes referred to as "requirement gathering".

The term elicitation is used in books and research to raise the fact that good requirements cannot just be collected from the customer, as would be indicated by the name requirements gathering. Requirements elicitation is non-trivial because you can never be sure you get all requirements from the user and customer by just asking them what the system should do or not do (for Safety and Reliability). Requirements elicitation practices include interviews, questionnaires, user observation, workshops, brainstorming, use cases, role playing and prototyping.

Before requirements can be analyzed, modeled, or specified they must be gathered through an elicitation process. Requirements elicitation is a part of the requirements engineering process, usually followed by analysis and specification of the requirements.