Ambiguous Requirements:

Sometimes users write ambiguous statements, which have multiple interpretations.

That’s causes difficulty for the developer. And results in failure of project.
Example: The system shall allow the teacher to upload file quickly.
1) What verses How:
Sometimes user write the requirement with “How”. How the system perform task?
They have to sure that they not mention “How”. They have to mention “What”. What
are needs?
Example: The system shall use Gmail to send mail for verification.
2) Using Conjunctions:
When User uses conjunctions (and, or etc.) in requirement. That’s a bad requirement.
One requirement must have only one functionality.
Example: The system shall book online appointment of doctor for user and the system
shall also prescribe medicine for user.
1) Not using shall/will:
Sometimes users not used shall/will. It is compulsory that requirement is written with
will/shall. Because system is not developed, system will be developed in future so we
have to use will/shall.
Example: The UCP portal system allow the teachers to upload files (ppt, .cpp, zip, word,
excel).
2) Noise:
Sometimes users used technical terms in requirement which have not any relevant
information in a document.
Example: The beauty camera shall allow the user to use professional mode.