Software Requirements Essentials: Core Practices for Successful Business Analysis

Index

Numbers

• 5 Whys, 15–16

A

• abbreviations, defining in glossary, 129

• abstraction levels of requirements, 111–112

• acceptance

  • criteria, 57, 79, 111–112, 113, 135–136

  • tests, 135–136

• acronyms, defining in glossary, 127, 129

• action enabler, as business rule type, 122

• active voice, writing in, 110

• activity diagram, 87

• agile projects

  • baselines on, 143–144, 146

  • data interfaces and, 66

  • minimum viable product, 104

  • nonfunctional requirements on, 71–72

  • prioritization on, 98, 101

  • product owner, 8, 41

  • prototyping on, 92

  • requirements management on, 152–153

  • use cases on, 50

  • user stories and, 50, 78, 110–111

• alternative flow, use case, 48–49

• ambiguity, in requirements, 109

• analysis, requirements

  • activities, 76

  • defined, 5–6, 75

  • of individual requirements, ...