By Topic

Card Sorts to Acquire 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
$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)
Maiden, N. ; City Univ. London, London

This paper deals with a requirement acquisition techniques card sorts. One reason is that requirements projects are often constrained by software solutions such as components, off-the-shelf packages, and application features. More and more projects need to acquire requirements to select between available solutions. This is where card sorts come in. During a card sort, one or more stakeholders work with a set of cards or objects, each of which rep resents an item. A card sort treats the item names as given, and the stakeholders should already be familiar with the items. As the name suggests, stakeholders sort the item (cards) into categories. Card sorts encourage stakeholders to verbalize information about categories of items and criteria that discriminate between them.

Published in:

Software, IEEE  (Volume:26 ,  Issue: 3 )