for many good reasons.The following examples ofnegative consequences
that occur if requirements engineering is not performed illustrate the posi-
tive reasons to perform requirements engineering:
■
There are no documented requirements to base testing on.
■
There are no agreed-upon requirements to control scope-creep.
■
There are no documented requirements to base the customer
training or customer support activities on.
■
It is very difficult to manage project schedule and cost without
clear and documented requirements.
It is thus clear that it is extremely unwise to base software development
without any requirements engineering activities.
At the other end ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month, and much more.