S

sales tax, 335

sales tax rate, 129

Sarbanes-Oxley Act (SOX), 75

scalability

dynamic capacity and, 212

of an interface, 57

specifying, 205

scalability requirement pattern, 241–246

scaling out, 242

scaling up, 242

scheduling of reports, 190

scope

defined, F-7

of the glossary, F-44

of a glossary definition, F-46

of a glossary term, F-49

of requirement ID uniqueness, F-36–F-37

writing, F-8

scope boundary, 15, F-55, F-56

scope document, F-31–F-32

Scope section of a requirements specification, 15–16, F-53, F-54–F-58

screen

refreshing, 177, 188

returning to previous, 125

screen focus, accessibility requirements, 179

screen size, accessibility requirements, 179

secondary reviewers, F-19

secret information, identifying users, 298

Section 508 of Rehabilitation Act, 170, 175, 186

sections in a requirement pattern, 21

security

against deliberate shutdowns, 231

archiving for, 110

extendability requirements and, 249, 252

of an interface, 57

outlawing bad practices, 293

requirements for good practices, 287, 292–293

requirements for interfaces, 60–61

requirements for reports, 166

as a source of nonfunctional system aspects, F-70

security breaches, helping users to spot, 298, 301–302

security procedures manual, 83

security risks during installation, 276

security violations, recording, 149

segregated data, 261–262, 269–270, 271

selection criteria

for inquiries, 157, 161

for recorded events, 152

semantic requirements, 178, 186

sender, verifying the identity of, 58, 59

sensitive data, recording access to, 148

sensitive information, 292

sensors, data recorded by, 123

separate requirements specification for a standard, 77–78

separator characters, 88

sequence numbers in templates, 25

sequential numbers, allocating, 99, 101

sequential requirement IDs, 13, F-37

sets of requirements, 20

severity level, 145, 150, 152–153

shutdowns, 225, 232. See also failures

"sign off" of requirements, F-21

signed numbers, data type, 87

simple data type, IDs as, 97

simplicity of identifiers, 98

simplification of transactions, 135

simultaneous customer capacity, 213

single requirement for standards compliance, 77

single site, installing system in, 255

sites, scaling number of, 245

sizing model, 195, 211, 216

skeleton pattern, 45

software

for archiving, 116

availability issues related to, 226

changing at both ends of an interface, 59, 60

data types represented in, 94

for drivers, 251–252

extending using, 246

over documentation, agile exhortation, 8, F-23

performance targets for, 192–193

recording changes, 149

scalability requirements and, 245

for system integrity monitoring, 236

writing to support documentation, 83

software download

accessibility concerns, 177

need for, 188

solutions

distinguishing problems from, 9

formulating based on requirements, F-8

not specifying in requirements, 6, F-9

sort order for IDs, 99

sort sequence for inquiries, 157

sound, accessibility concerns and, 171, 174, 181–182

sound alerts, 182

sounds, 123

source code

commenting, 84

documentation, 83, 84

for driver software, 252

SOX (Sarbanes-Oxley Act), 75

specific authorization, 281, 282

specific authorization requirement pattern, 47, 308–313

specific needs for accessibility, 168, 169, 172, 174–175, 178–182

specific privileges, 305

specifications, purpose of, F-2

spelling notes in a glossary, F-47

splitting a requirement pattern in two, 46–47

spreadsheets of mind-boggling complexity, 332

stale user sessions, 213, 215

standards

categories of, 71–72

complying with multiple versions, 72–73

complying with parts of, 73

contents of requirements mandating, 73–74

defined, 71

defining an interface, 55

development considerations, 78–79

for documentation, 82

examples of, 74–77

location of, 74

making accessible, 78

multiple different for the same thing, 72–73

names of, 73

purposes of, 73

as a source of nonfunctional system aspects, F-70

specifying that a system comply with, 71

technology and, 66

testing considerations, 79

versions of, 73

standard patterns, agreement on, 36

standard-related requirements, prioritizing, 78

state transition diagram, 17, F-62–F-63

static capacity requirement pattern, 47, 215–217

statistical functions for viewing chronicles, 152

statistics on requirements for a system, 33–34

stopwatch, recording response times, 203

storage medium for archiving, 112

strategic stratosphere, report design and, 163

"strikethrough" text, F-38

style sheet, 177

subcalculations, in a calculation formula, 103, 106

subtotals on reports, 166

subtransactions, 134

suffix, adding to a previous requirement ID, F-38

suggestions, resolving conflicting, F-21

suitability conditions, 256

summary description, 14, F-34, F-36, F-41

support, accessible, 184

surreptitious unavailability, 221, 224–225, 238

switching time transaction, 200

systems

accommodating old and new interface versions, 59, 60

activities in building new, 5, F-6

availability window of, 208, 219

defined, 4, F-1

describing purpose of, F-31

difficulty of migrating from old, F-58

driver type requirements for, 250–251

at each end of an interface, 55

human being as part of, 171

load on, reducing, 214, 215, 245

monitoring response times within, 202–203

popular times for using, 208

reliability of, 231

replacing existing, F-58

specifying, 6, F-10

system activity inquiry, 143

system building, specificity of, 254

system capacity. See dynamic capacity; static capacity

system clock, data longevity and, 109

system configuration. See configuration

system context diagram. See context diagrams

system defects, testing for, 238

system design, documentation requirement, 83

system designer, F-15

system events, recording significant, 148

system expansion, allowing for. See scalability

system failures, minimizing, 225

system flexibility. See flexibility

system glossary. See glossary

system gone live state, 143

system information, viewing of, 160

system monitor, requirements for, 234

system operation efforts, non-growth in, 244

system performance, 193

system processing state, 143

System Purpose section in requirements specification, 12, F-31–F-32

system resources, freeing up, 214

system threshold, passing of defined, 148

system unavailable page, 224

systematic approach to capturing patterns, 43

system-generated passwords, no access via, 293

systemwide configuration values, 138, 139