requirements
DESCRIPTION
REQUERIMIENTOSTRANSCRIPT
-
Siemons Info
Requirements
Process
Requirements types
Service
System
Goals
Business requirements
Service requirements
System requirements
Policies
Constraints
Non-functionalrequirements
Kano
Ful
lmen
t
Satisfaction
Basic
Exciteme
nt
Perfo
rman
ce
Indierent
Reversed
Questionable
PerformanceAvailabilityReliabilityMaintainabilityServiceability...
Useability requirements...
User Acceptance Test
Integration Test
ComponentTest
Assessment/Audit
Performance Test
Disaster Recovery Test
Production Acceptance Test
VersionHistory
Functional requirementsUser requirements...
Customer requirementsProcess requirements...
Regression Test
Fiduciaryrequirements
RequirementID
Description
Rationale 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
SystemServiceBusiness
What
How
WhatHow
How
What - Requirement How - Solution
MoSCoW prioritiesPriority Description Scope
M Must have In scope
S Should have In scope
C Could have Desirable but not necessary. If time and budget permit
W Wont have Nice to have that may be considered for the future (not now). Not in scope