Is the requirement within the product context? If not, then raise a question because it might be an irrelevant requirement. Is the requirement really a requirement, or is it a solution? Solutions masquerading as requirements are most common in the case of nonfunctional requirements or system constraints. Look at the context of study and ask whether this requirement is a constraint that is imposed by the context. If the answer is yes, then you have a real requirement. If the answer is no, then you have a constraint that has been imposed because of someone's implementation bias or because someone has an incomplete understanding of the context. |