page count on a report, 164, 167
page throw levels on a report, 165
paper type for a report, 167
parameter values, 138, 195
parent entity, 130
parochial data type definition, 89
parochialness, 256, 257. See also unparochialness
participants in the requirements process, F-15
passive attack on an interface, 60–61
passive reviewers of a requirements specification, F-19
passwords
changing, 287, 289
criteria for acceptable, 288–289
generating initial, 287
system-generated, 293
password entry, recording incorrect, 149
password format, criteria for, 287, 288–289
password guesser utility, 289
pattern author, 23
"Pattern classifications" in a requirement pattern, 23
pattern manifestation, 22
pattern name, 21
patterns, 20, 43. See also requirement patterns
peak customer capacity, 213
peak minute, calculating throughput for, 208
peak period, 213
pending actions, 128, 129
people over processes, agile exhortation, F-23
percentages, as data type 87, 218
performance
common issues with, 192–195
defined, 191–192
degrading of, 225, 244
flexibility and, 240
as a source of nonfunctional system aspects, F-70
transactions and, 137
performance domain, 29–30, 191–238
performance requirement patterns, 191–238
performance targets, 192, 193–194
PERL scripts, 69
permissions. See privileges
personal contact details, data structure for, 96
personal name details, data structure for, 96
"Pervasive" requirement pattern classification, 35
pervasive requirements
alerting readers to the presence of, 28
defined, 20, 27
grouping related, 27
for inquiries, 159, 161
for living entities, 131–132
for reports, 166–167, 168
writing, 47
post codes, unparochialness and, 259
postmortem, 42
power users, accessibility concerns and, 171, 174
preciseness of requirement patterns, 20
precision
of calculations, 103
of a glossary definition, 14, F-46
preemptive corrections, 225
preferences of users, 285
Prepare step in requirements process, 7, F-16–F-17
presentation unit, 176
preset thresholds, passing, 145
previous screen, returning to, 125
pricing changes, 129
primary programming language, 69
primary reviewers of requirements specification, F-19
principles, regarding requirements specification, 6–7, F-9
priorities, F-40–F-41
prioritizing requirements, 14
priority of a requirement, F-34, F-36, F-39–F-41, F-43
privacy requirements for reports, 166
privileges, 305
privilege types inquiry, 317
problems
distinguishing from solutions, 9
specifying, 6, F-9
procedures manual, documentation requirement, 83
processing abilities, accessibility concerns and, 171, 174, 182
processing load, 215
product mailing list, customers joining, 133
product restarts, need for, 229
production line, non-interference with, 139–140
programming language, 69, 188
progress bar, displaying, 204
project manager, F-3, F-15
proof of existence archiving, 111
prospective installations, scope of, 255
protection of data, 123
prototypes, developing, F-14
pseudo-localization, testing, 271
punctuation, unparochialness and, 259