Skip to Main Content
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.