In our efforts to make system requirements “good,” we often end up making them “bad.” It is proposed that the real goal should be to make requirements BaD—balanced and dynamic. This paper describes why the so-called “good” requirements are really, in the larger sense, bad for success of the system and the organization that sponsors it.
Members-Only Content
This content is restricted to members only.
You must be logged in with an active membership to access this page.
Please click the link below to log in. If you do not have an account or your membership is inactive, you may need to register or renew it.