Generating Product Requirements

Generating Product Requirements
in a Heavyweight/Non-Incremental Process

Computer Science Department

bernstdh@jmu.edu

A Reminder

Product Design:
- Analysis - understanding the problem (i.e., eliciting needs)
- Resolution - creating a solution (i.e., generating product requirements)
Resolution in a Heavyweight/Non-Incremental Process:
- Generate alternative products (i.e., alternative sets of requirements)
- Evaluate the alternative products
- Select a particular product

Generating Alternative Requirements

Within the Team:
- Team Brainstorming
- Individual Brainstorming
- Modeling
Using External Sources:
- Users and Other Stakeholders
- Experts
- Competitive and/or Similar Products
- Props and Metaphors

Organizing Alternative Requirements (and Generating More)

Create a Classification Tree:
- Leaves contain similar alternatives
- Branch at major differences
Fill-In the Classification Tree:
- Look for gaps in the tree
- Attempt to create alternatives that fill the gaps

An Example Classification Tree

Note: The information in parentheses provides a link back to the stakeholders' needs list.

Evaluation

Comparing Alternatives

Selection

Stakeholder Selection:
- Appropriate for overarching design alternatives
Designer Selection:
- Appropriate for low-level alternatives (assuming stakeholders have been involved)

Requirements Validation

Requirements Verification

There's Always More to Learn