Thursday, November 29, 2007

Requirements Gathering Activities

A user will tell you anything you ask about, but nothing more

Conceptually, requirements analysis includes three types of activity:

Eliciting Requirements

The task of communicating with customers and users to determine what their requirements are.

Analyzing Requirements

Determining whether the stated requirements are unclear, incomplete, ambiguous, or contradictory, and then resolving these issues.

Recording Requirements

Requirements may be documented in various forms, such as natural-language documents, use cases, user stories, or process specifications.

No comments: