August 2004
Intermediate to advanced
656 pages
15h 28m
English
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.
One of the biggest problems with software requirements, especially requirements stated ...
Read now
Unlock full access