By Topic

Do you really need formal requirements?

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
B. Lawrence ; Coyote Valley Software Consulting, USA ; D. Jackson

Informal methods, such as heuristics to identify users and choose system attributes and functions, can be a highly effective approach for developing requirements. More formal methods may not be necessary. The paper discusses the reasons for spending valuable resources on a requirements effort in the first place: to improve everyone's understanding of the customer's problem; to reduce the risk of uncertainty and ambiguity about that problem; and to provide a foundation for validating your design

Published in:

IEEE Software  (Volume:13 ,  Issue: 2 )