Why Bother with Requirements?
Numerous studies have shown that some of the top reasons for the high rate of project failure result directly from requirements problems. Lack of requirements, misunderstood requirements, vague requirements, incomplete requirements, and changing requirements all are major failure points in system development. Such failures waste precious money, resources, and time. You have to know where you are going, or you'll never get there. That is the purpose of requirements.
Sometimes, I hear developers say they don't want to be saddled down with requirements. When asked “Why?” they often respond that they want or need to get started coding. But what will you code? That's like a builder saying he has to hurry up and lay brick, ...
Get UML for Mere Mortals® now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
