Chapter 3

The requirements workflow

1

Chapter Objectives
UP requirements workflow Importance of requirements Defining requirements Functional and non-functional requirements Finding requirements
2

The Requirements workflow

Most work done in Inception and Elaboration phases

Requirements
High-level specifications of what the system should do (not how it should do it) A system has different stakeholders Requirements engineering:
Eliciting, documenting, prioritizing, often negotiating requirements of various stakeholders.

Two types of requirements

Functional requirements ( what the system will do) Non-functional requirements (constraints on the system)

Requirements model in our book

Requirements workflow detail - UP

Requirements workflow extensions in our textbook

Find functional requirements Find non-functional requirements Prioritize requirements Trace requirements to use cases

Defining requirements

Organizing requirements

Requirements attributes
Capture additional information about requirements Priority is one of the most common attributes MoSCoW criteria can be used to assign priority

10

RUP requirements attributes

11

Finding requirements
Three filters of distortion Deletion info is filtered out Distortion info is modified Generalization info is abstracted

12

Finding requirements
Interviews
Set any preconception aside Ask context-free questions Listen Have patience

Questionnaires Requirements workshop

Brainstorming

13