You are on page 1of 1

Requirements

Requirement
ID
Description
Rationale

Version
History

The motivation for the requirement and its priority.

Acceptance criteria
Priority

The priority of the requirement (MoSCoW).

Owner / Source

The owner or source of the requirement (Function, role, issuer/representative, policy, legislation).

Supporting materials

Schemes, documents providing a context and/or details.


What - Requirement

Requirements types
Constraints
Assessment/Audit
Fiduciary
requirements

What

Goals
Business requirements
Process

Customer requirements
Process requirements
...

Service requirements
Performance Test
Disaster Recovery Test
Production Acceptance Test

Non-functional
requirements
Performance
Availability
Reliability
Maintainability
Serviceability
...

Service

Functional requirements
User requirements
...

System requirements
System

User Acceptance Test

What

Regression Test
ComponentTest

Useability requirements
...

Description

What

How

Integration Test

How

Business

Service

Kano

MoSCoW priorities
Priority

How

Scope

Must have

In scope

Should have

In scope

Could have

Desirable but not necessary.

If time and budget permit

Wont have

Nice to have that may be considered for the future (not now).

Not in scope

System

Satisfaction
ent

tem

Exci

rfo

Indifferent
ic

s
Ba

Re

ve

Pe

rse

Questionable

Siemons Info

ce

an

rm

Fulfilment

Policies

How - Solution

You might also like