Who exactly determines the specific boundary between a simple list of software features and a rigorous Requirements Engineering process? Furthermore, this discipline involves the systematic elicitation, analysis, specification, and validation of what a system must actually do to satisfy its stakeholders. Why is failing to bridge the gap between vague business needs and precise technical requirements considered the primary cause of project failure?