Non-Functional Requirements Checklist

(based on B. T. Mynatt. Software Engineering with Student Project Guidance. Prentice-Hall. pp. 71-72)

HCI and User Interface Issues

Item	Relevant?	Covered?
users profiled (types, attributes)
i/o devices specified (types, attributes)
training needs described
guessability
learnability
expert user performance (speed of task completion, error types, error rate)
user subjective rating of system

Documentation

Item	Relevant?	Covered?
documentation types identified
audience for eah document given

Hardware/Software

Item	Relevant?	Covered?
target hardware
hardware constraints (memory size, backing store)
operating system(s)
other required software

Performance

Item	Relevant`?	Covered?
speed
throughput
response time
data to be process (size, capacity)

Error Handling and Extreme Conditions

Item	Relevant?	Covered?
response to input errors
response to extreme conditions

System Interfacing

Item	Relevant?	Covered?
input from external systems
output to external systems
restrictions on input/output (format, medium)

Quality Issues

Item	Relevant?	Covered?
reliability
fault trapping
restart time after failure
acceptable downtime (e.g., per 24 hours)
portability

System Modifications

Item	Relevant?	Covered?
system components likely to need subsequent modification
expected modifications

Physical Environment

Item	Relevant?	Covered?
location(s) of target equipment
unusual operating conditions (temperature, vibration, electromagnetic sources)

Security Issues

Item	Relevant?	Covered?
system access control
system backup (frequency)
person(s) responsble for backup
physical access & security

Resources and Management Issues

Item	Relevant?	Covered?
resources to build, install & maintain system (materials, personnel, time, computer resources)
skills and knowldge of developers
project deadlines
budget (hardware, software, personnel, other costs)
responsibility for system installation
responsibility for system maintenance