By Topic

Improve Your Requirements: Quantify Them

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
$31 $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

1 Author(s)

One of the biggest challenges requirements analysts face is quantifying requirements. Analysts frequently ask how to do this, what techniques support it, and most importantly, where the numbers come from. Alas, quantifying your requirements is more easily said than done. Most people would say that it shows that the software complies with the requirements - that it's sufficiently fast, reliable, usable, and so forth. No doubt this is important, but showing compliance supports downstream development rather than the requirements process itself. However, quantification is also integral to challenging, and thus improving, requirements during your requirements process. Successful quantification can motivate people to find ways to deliver on these requirements by giving them clear targets to work toward. Although quantifying requirements can be difficult, several techniques can help. The author discusses two such techniques - Volere and Planguage

Published in:

Software, IEEE  (Volume:23 ,  Issue: 6 )