Page 355 - Software and Systems Requirements Engineering in Practice

d
n
I
e
I n d e x 317 317
x
reviews usage, 224
formal, 186, 195 use case, 105, 107,
hazard analysis, 281 130–132, 145
model, 98 schedule estimation methods, 271
NFRs, 186, 188 schemas, 217
prototypes, 237, 242, 245 “scope creep,” 6
requirements, 6, 41, 66, 69 “scrum of scrums,” 268
risk assessment, 15, 277. See also Scrum sprint, 242
hazard analysis scrum teams, 268
RM. See requirements security, 14, 136
management sequence diagrams, 107–109
ROI (return-on-investment), 214 service-oriented architecture
roles, 4, 200, 208, 262, 266 (SOA), 85
Royce, Walker, 45 severity, 277
rules, 63 Siemens Corporate Research,
RUP (Rational Unified Process) xxii, 4–5
techniques, 7 Six Sigma program, 55
“smart ignoramus,” 41, 68
S SOA (service-oriented
safety, 137 architecture), 85
safety requirements, 14 “softness,” 149
safety-critical system, 277 software architecture, 126
sales organization, 6 software bugs, 129, 209
Sales role, 201 Software by Numbers, 214
Sarbanes-Oxley regulations, software classes, 116, 117
3, 14 software defects. See defects
satisfaction, 137 software developers. See
scalability developers
requirements management, 207 software platforms. See
testing requirements, 227–228 platforms
scenarios, 91–94 software product lines, 176
defining, 237 software requirements
derived from business engineering, 8
goals, 161 software testing, 220. See also
end-to-end, 139, 165–166 requirements-driven system
error, 91 testing
identifying, 237 source code. See code
QAR, 131, 143–145, 171 specification-based testing, 223
QAS, 131, 143–145, 155, 171 spreadsheets, 188, 210
“sunny day,” 128 SRS (Systems Requirements
threat modeling, 284 Specification), 95
types of, 143–145 stability, 137