F

failures, 231–237

faithful nature of chronicles, 145

federation of systems, 54

fee rates, determinants of, 333

feedback on requirements specification, dealing with, F-21

fee/tax requirement pattern, 330–340

financial data, storage of, 109

financial flows, diagramming, 331–332

financial transaction, 137–138, 158

financial year, 259

flat files, 123, 124

flexibility, 135

of configuration values, 138

described, 239

domain, 29–30

of identifiers, 98

importance of, 239

performance requirements and, 240

as a source of nonfunctional system aspects, F-70

testing, 240

flexibility requirement pattern, 239–279

follow-on requirements, 20, 27, 28, 47, 132

forgotten passwords, handling, 297, 298–299

formal part of a requirements specification, 6–7, F-11–F-12

formal statement of a requirement, F-42

formats

for documentation, 82

for requirement IDs, F-37

framework, compared to infrastructure, F-64

freezing requirement IDs, F-38

frequencies for requirement patterns, 23

full year, storing dates for, 90

functions

authorizing access to, 308, 310, 311

availability goals related to, 225

compared to use cases, F-13

controlling access to, 314

controlling use of, 305

recording, 145

testing access to, 318

user. See user function requirement pattern

for viewing chronicles, 152

functional areas, 41, F-68–F-69

functional area sections in a requirements specification, 12, 17–18, F-30, F-68–F-70

"Functional" requirement pattern classification, 34–35

functional requirements, 4, F-3

functional testing of user authentication, 304

fundamental domain, 29, 51

fundamental requirement patterns, 51–84