Understand the Real Problem
The first step in solving a technical problem, or any problem for that matter, is to first understand what that problem really is. This may seem rather obvious, but it's surprising how often the technical solutions don't really solve the actual problem. In software, understanding the real problem means eliciting, analyzing, specifying, and validating the requirements. This book isn't a tutorial on software requirements; there are already several good books on that topic (see, for example, [Gause89], [Robertson99], and [Wiegers03]). A few of the most important guidelines are worth mentioning here.
AMBIGUITY IN REQUIREMENTS STATEMENTS
One of the biggest problems with software requirements, especially requirements stated ...
Get Return on Software: Maximizing the Return on Your Software Investment 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.
