table, distinguishing a list of requirements, F-34, F-35
taxes, 330–331
"TBD" paragraphs, removing, F-54
teams, splitting development between multiple, 54
technical data types, 86
technical standards, 71, 72, 76–77
technology
constraints on the user interface, 188
defined, 65
description of, 66
development considerations, 70
examples of, 68–69
for an interface, 55
specifying to build or run a system, 65
usage of, 67
used in development, 66
for user interface infrastructure, 187
versions of, 67
working with a range of, 67
working with multiple, 70
technology requirement pattern, 65–70
telephone numbers, data type 92, 259
templates section of a requirement pattern, 21, 24–25
temporal parochialness, 256, 257
temporary dispensation from compliance to a standard, 73
terminology, variation in, 260
terms
choosing new, F-45–F-46
establishing the meaning of, F-44
in a glossary, 14, F-45
listing alphabetically in a glossary, F-48
of local scope, F-46
test system for external developers interface software, 61
testers, 47, 48, F-15
testing
acceptance, 9, F-25
accessibility, 186
availability, 238
calculation formula, 106–107
chronicle, 153
configuration, 144
considerations for, 29
considerations for interfaces, 65
data archiving, 117
data longevity, 109–110
data structure, 96
data types, 94
of documentation, 84
dynamic capacity, 215
extendability, 253
flexibility, 240
ID, 101
inquiries, 161
of interfaces, 62
living entities, 133, 144
report, 167–168
response time, 204
scalability, 246
static capacity, 217
technology requirements demands on, 70
throughput, 211
transactions, 138
unparochialness, 260–261
using patterns during, 40
testing regime, F-27
tests
exclusions and, F-60
using requirements, F-3
text
display, accessibility requirements, 179, 184
equivalent of cosmetic script, 181
not burying in code, 269
theme
introduction explaining, 30
for a new domain, 44
of patterns in a domain, 29, 32
third-party interface development, 57, 61
third-party system, interfacing to, 54
threshold rates for fees, 333
throughput of an interface, 57
throughput requirement pattern, 204–211
throughput targets
CPU cycle rate and, 207
for inter-system interface, 206
justification for, 209
purpose of, 205
selecting, 205, 206
timeframe for, 208, 209
transactions as, 206
tiered rates for fees, 333
time, 89–90
of system use, 208
systemwide aspects of, 93
time limits for data longevity, 108
time periods, measuring, 337
time, response. See response time
time to detect (availability), 232–234
time to fix (availability), 232, 235–237
time to react (availability), 232, 234–235
time zones, 90, 93, 133, 259
timed changes, 127–128, 129
timed responses, control of, 177
timeless requirements specification, 6, F-11, F-56
timestamps, 88, 90, 92, 153
title for each reference, F-50
"To Be Done" (TBD) paragraph format, F-18
top-level sections of requirements specification, F-29–F-30
totaling levels for reports, 165, 166
traceability, ID facilitating, F-35
traditional approach, 3, F-6
to specifying requirements, 7–8, F-1–F-2, F-12–F-22
traditional documentation, 84
traffic verification and recording, 57, 58–59, 60–61
training for installation, 277
transactions
determining origin of, 206
integrity of, 126
multiness of, 264
requirement pattern for, 133–138
restoring offline, 117
steps in, 125
switching time, 200
as throughput target, 206
transaction data scalability, 244
transaction fee requirement, 334
transaction monitor, 154
transaction number, 125
transaction requirement pattern, 133–138
transference of restrictions, 308, 312
transitions, state, 17, F-62
troubleshooting installation, 276