R

range, expressing frequency as, 23

rationale of a requirement, F-42

readability of a requirement, F-34

rearchiving, 114

recent orders inquiry, 159

recorded event inquiry, 152

recovery of data, 123

refactoring, 239

reference numbering scheme, F-49

referenced requirements, 80–81

referenced specification, 79, 80

references

for calculation formulas, 103

details required, F-50–F-51

to other glossaries, F-44

withholding, F-49

References section of a requirements specification, 14–15, F-49–F-51

Refers to requirement pattern relationship, 32, 33

refer-to-requirements requirement pattern, 79–81

refinement requirements, 35–36

reflective monitoring of throughput, 210

refreshing user interface, 157, 159, 177, 188

regions, installing systems in varied geographic, 255

registering users, 284

registration, process of, 285

regulations

accessibility, 169, 170, 184

data longevity, 107, 109

rejection, during approval process, 320

"Related patterns" in section in requirement pattern, 22

relationships between requirements, F-43

relative volumes for throughput, 205, 206

releases, as independent of priority levels, F-40

relevance of glossary terms, 14, F-45

reliability

of chronicles, 145

system, 231

reloading of archived data, 116–117

remote access

facilities, 234–235

restricting access to, 311

removing requirements, F-38

renumbering requirements, F-38

reorganizing organizations, 329

repetition, avoiding, 7, F-48

repetitive strain injury, accessibility concerns and, 171, 174

replay attack on an inter-system interface, 305

replication of hardware, 231

reports

access control, 190

availability, 233

content requirements, 164–165, 190

defined, 189

delivery mechanisms for, 190

designing, 162, 190

dynamic use, 214

format considerations, 167, 190

multiness requirements and, 263

purging, 190

recipients of, 163, 166, 190

scalability requirements and, 245

scheduling of, 190

size limits on, 244

static capacity, 217

report design changes, recording, 149

report design tool, 190

report fee requirement, 335

report instance, 189

report requirement pattern, 161–168

report run request, recording, 149

reporting infrastructure, 31, 155, 189–190

representative configuration values, 141

Request For Comment (RFC) standards, 74

requirements

arguments against specifying, F-4

audiences for, F-3

case for specifying, F-4

compared to requirement patterns, 21

defined, 4, F-2, F-8

grouping by functional area, 41

identifying, 9, F-24

impact of an agile outlook on, F-23

indications of pattern use, 40

introducing a variety into, 41

items given for each, F-36–F-43

lack of confidence in, F-4

levels of detail for, 4, F-3

nonfunctional, F-40

not specifying for an infrastructure, F-66

overall approaches to, 3, F-1

presenting in a specification, F-34

prioritizing, F-39

proportion covered by patterns, 41

putting customer in control, F-5

referencing an infrastructure, F-65

referencing applicable, 80

refinements of the main, 35–36

reflecting business rules, 38

relationships, F-43

removing, F-38

requirement patterns when defining, 39

responsibility for overall organization of, F-27

specifying, 4–5, F-3, F-28, F-64

treating constraints as, F-54

types of, 19

writing down during extreme programming, 10, F-26

requirement definitions, 13, F-33, F-35–F-36, F-42–F-43

Requirement format section, 13–14, F-33–F-43

requirement IDs, 13, F-33

example of, F-35

grouping, F-37

qualities of, F-36–F-43

requirement pattern classifications, 34

requirement pattern domains. See domains

requirement pattern groups, 31–32, 33

requirement pattern use cases, 37–38

requirement priority. See priority of a requirement

requirement summary. See summary description

requirement template, 24, 46–47

requirement patterns. See also specific names of requirement patterns

access control, 281

applicability of, 24

in association with extreme programming, 10, F-26

benefits of using, 19, 40–41

classifications of, 33–35

commercial, 325

contents of, 21–29

data entity, 119–154

defined, 19

diversity of approaches to, 36–37

drawbacks of, 41

and extreme programming, F-25–F-26

finding candidate, 43–44

flexibility, 239–279

fundamental, 51–84

information, 85–117

misapplying, 41

naming, 21

performance, 191–238

refining, 42

relationships between, 32–38

relationships with domains and infrastructures, 30, 31

during requirement definition, 39

reviewing, 48

sections of, 21

sources of, 20

specifying better in the future, 44

tailoring, 41–42

use cases for, 37–38

user function, 155–190

using after the fact, 40

using and producing, 39–48

using to consider completeness, 40

writing, 21, 42–48

requirements approaches, diversity of, 36

Requirements Management Tools Survey, F-2

requirements process, 7–8, F-12–F-14, F-15

requirements specifications

contents of, 11–18, F-29–F-71

defined, 4, F-2

essential items of information in, F-33

example for infrastructures, F-66

example text for, F-35–F-36

formal and informal parts of, F-11–F-12

for an infrastructure, F-65, F-67

introduction of, F-33

language, 22

organizing, 11, F-29–F-30

reviewing, 8, 40, F-19

as a source of candidate infrastructures, F-64–F-65

suggested structure for, 11, F-29–F-30

requirements-take-too-long argument, F-4

resilience, 57, 58

resource checker utility, 269

resources, managing multiple sets of, 269

response time

evaluating, 203–204

scalability and, 242

response time requirement pattern, 195–204

responsiveness over plan, agile exhortation, F-23

restatement of a formal requirement, F-42

restoring data, 123

restructuring, corporate, 245

revenue model, 331–332

review cycles, F-20–F-21

reviewers, F-19, F-20

reviews, feedback from, 48

Revise after review step, 8, F-20–F-21

RFC (Request For Comment) standards, 74

roles, assigning to users, 285

rolling window, 188

rounding, 103

rule IDs, 100

run time, infrastructures used during, F-63