Lots of ways that they can fall short

If a requirement is trying to cover too much ground, it’s best to break it down

Cascade from needs to requirements

Syntax schema feels a lot like propositional logic / coding

Told to check requirements quality

Rationale should cover coupled with each requirement

For agile, the user story serves the purpose of requirements

How does uncertainty of what you’re building balance with requirements