Home / BA / How can you say that a requirement is good or perfect?

How can you say that a requirement is good or perfect?

As a Business analyst the most important aspect is Requirement engineering. A business analyst have to make sure that the requirements are actually belongs to client. At the time of requirement gathering business analyst is using various elicitation technique and ensure that the all the requirements are useful, and gathered requirement will satisfy the client’s need.

To make sure that requirements are good enough and perfect a business analyst should have to involve in requirement engineering. After the gathering of requirement he has to sort the requirement in such a way that eliminate duplicates and keep the original or unique one.

And After the sorting the requirements Prioritization of requirements should be the next stage, in which BA has to use Prioritization techniques such as MoSCoW technique and 100 dollars test and Top 10 requirements.

And at the last stage of the requirement engineering is Validation of requirement which is most important for ensure that our requirement of the particular project is perfect.

Validation of requirement means requirements should be complete, consistent, feasible, modifiable, independent and testable. And Requirement validation confirms that the written requirements agree with the stakeholder’s request and will satisfy to the client/SH.

There are various methods and techniques for validation of requirements that will ensure that the project requirements are perfect and good.

  • CUCV
  • CAE
  • APVU
  1. FURPS

FURPS validation technique represents a model for classifying software quality attributes like functional and non functional requirements. Here the acronym for FURPS is

Functionality– This says about feature set, capabilities, generality and security of the project. What is in the project.

Usability- This says about the human factor, consistency and documentation and overall usability.

Reliability– This says about the frequency, recoverability and accuracy, means how fast and recovery of the system can be done after the crash.

Performance– This says about speed, efficiency, and resource consumption. And  how the system/project will work.

Supportability- This says about extendable, enhance able, testable, adaptability, and maintain serviceability and portability. Example is Extension


CUCV validation technique represents that quality which a good and perfect requirement should compulsorily have, CUCV stands for

Clarity– Clarity of requirements says about the transparency should be there, what is exact requirement of the stakeholder.

Understandable– This means the requirement should be understandable by the all team members and for developers.

Consistency– This means the requirements should be complete, means no information should be left, undetermined or unrelated until the project has completed.

Verifiable– This says about that requirement should be cross checked in present as well as in future by the developer that what code has written that code are  matching with the developed code or not.


This validation method represents the perfection quality of requirements

Complete– This says about completeness of the requirement, whatever the requirement is that should complete in whole. Which complete the project?

Accurate- This says about the accuracy of the project, expectation of the stakeholder and delivered product should be accurate and same.

Executable- This says that the project result should be executable by the client. All known requirements should be documented.


This validation methodology represents the quality of requirements which should be available in every project. This is the most important validation method for any project. SMART plays a major role in project success. Business analyst is used this techniques and ensure that requirement gathered by him/her are perfect.

SMART stands for

Specific– This feature is says about that the requirement should have only one meaning. That shouldn’t contradict by its own meaning.

Measurable- This says that requirement should be measurable means, within 30days the project will be completed or within 5 days that particular requirement should complete.

Attainable- The requirement should be re-checkable means feasibility and fits within the project funding and time frame.

Realistic– This says that the requirement should be realistic, means there will be no imagination while gathering the requirement form the client.

Traceable/Time bound- This is the success of any project, Requirements should be traceable and in time bound, means you are able to check that where you are and what are the requirement are still left for completion and after hoe many time this will be completed.


These methodologies of validation requirements are also helpful for confirming that requirements are perfect

APVU stands for

Authorized- This says that requirement should be authorized by the senior management or can says authorized by client as well.

Prioritized- Before validation requirements should be prioritized means as BA you should know that which requirement should come first.

Verifiable –The requirement should met the purpose of why they have been created.

Unique- This says that requirement should be unique, this helps in project success, there will be no duplicate.

There are few many acronyms which will ensure that the requirements are perfect and good


  • Positively stated
  • Understood
  • Relevant
  • Ethical


  • Collaborative
  • Limited
  • Emotional
  • Appreciable
  • Refinable

These above mentioned methodologies are clearly mentioning that if these are included in any project, then requirements will always be perfect and good.

About Vidhi Sohni

Check Also

Explain SRS and Its Key Elements

Introduction: Clear and concise communication is the cornerstone of successful software development projects. Software Requirement …

Leave a Reply

Watch Dragon ball super