Non-functional: performance, safety, security, quality attributes, business rules
Other requirements; appendices (glossary, models, TBD list)
Qualities of a good requirement
Correct · unambiguous · complete · consistent · ranked for importance · verifiable · modifiable · traceable. Write “The system shall …”, one idea, with an ID and a number for every quality.
SDLC models
Model
Use when
Waterfall
requirements fixed and well understood
V-model
fixed requirements and high reliability; a test per phase
Iterative
large system, core requirements known, changes expected
Spiral
large, costly, high-risk; risk analysis every loop
Agile
requirements change; customer available; short sprints
Prototyping
requirements unclear, especially the UI
DFD symbols and rules
Symbol
Yourdon
Gane–Sarson
Process
circle
rounded rectangle
Data store
two parallel lines
open-ended rectangle with ID
External entity
rectangle
rectangle
Data flow
labelled arrow
labelled arrow
Every flow starts or ends at a process. No entity→entity, entity→store, store→entity or store→store flows. Levels must balance. Level 0 has one process and no stores.