July 2001
Intermediate to advanced
656 pages
15h 51m
English
Investigating and asking about goals rather than tasks and procedures encourages a focus on the essence of the requirements—the intent behind them. For example, during a requirements workshop, the cashier may say one of his goals is to “log in.” The cashier was probably thinking of a GUI, dialog box, user ID, and password. This is a mechanism to achieve a goal, rather than the goal itself. By investigating up the goal hierarchy (“What is the goal of that goal?”), the system analyst arrives at a mechanism-independent goal: “identify myself and get authenticated,” or an even higher goal: “prevent theft ...”.
This discovery process can open up the vision ...
Read now
Unlock full access