16 Requirements Engineering for Software and Systems
helping the requirements engineer understand what they need and want (elic- ◾
itation and validation)
helping the requirements engineer understand what they don’t want (elicita- ◾
tion and validation)
providing domain knowledge when necessary and possible ◾
alerting the requirements engineer quickly and clearly when they discover ◾
that they or others have made mistakes
alerting the requirements engineer quickly when they determine that changes ◾
are necessary (really necessary)
controlling their urges to have “aha moments” that cause major scope creep ◾
sticking to all agreements ◾
In particular, the customer is responsible for answering the following four ques-
tions, with the requirements engi ...