What is a requirement that reflects a stakeholder's desires more than their actual needs?

A stated requirement is a requirement that captures a stakeholder's desires rather than their actual needs. This type of requirement often represents what stakeholders express in the form of requests or suggestions without fully understanding the underlying needs or the context of the project. Stated requirements can sometimes be characterized by a focus on specific features or functionalities they want, which may not accurately align with what is essential for the success of the project or the true objectives.

In the context of requirements gathering and elicitation, distinguishing between stated requirements and actual needs is crucial for ensuring that the end product meets the genuine demands and goals of stakeholders. This understanding allows business analysts and project teams to refine and validate requirements, ensuring they translate the desires into meaningful and beneficial outcomes.

Other types of requirements, such as functional and non-functional requirements, are typically derived from a deeper analysis of stakeholder needs and objectives, focusing on the "what" of the system (functional) or the "how" it should perform (non-functional). Transition requirements concern the needs associated with moving from one state or system to another, which is different from the more desire-driven nature of stated requirements.