calculations, 102–107
calculation formula, subcalculations, 103, 106
calculation formula requirement pattern, 102–107
calendar date, 88, 259
calendar time period, 336–337
candidate glossary terms, 14, F-45
candidate infrastructures, building a list of, F-64
candidate multinesses, 264–265
candidate patterns, multiple variants of, 44
candidate requirement pattern, 43
candidate solutions, F-10
capacity, patterns for, 47
capitalization, F-41, F-48
capped data line in reports, 167
card number format, 92
case of alphabetic characters, 87
case-sensitive identifiers, 98
cash withdrawal limit, 142
catch-alls, pervasive requirements as, 27
categorization of data entities, 119–120
certification authority (CA) interface, 56
change history for living entities, 131
changes, listing in the document history, F-52
changing passwords, 287, 289
characters, 87, 88
character sets, allowing, 87
charging fees over time, 333
charts in reports, 164
check digits, 89
chronicles, 121, 144–153
chronicle entries for reports, 190
chronicle requirement pattern, 144–153
circumstances of approval, 319
classes of users, 285
classification lists, format of, 23
classification of requirement patterns, 23, 33–35
codes of conduct, as standards, 71
coding standards, compliance with, 76
cognitive abilities (accessibility), 171, 174, 182
collaboration over contracts, F-23
collaborative approach, 8, F-17, F-18, F-19
color, use of, 180, 183
commenting, of source code, 83
commercial domain, 29–30, 325
commercial requirement pattern, 325–340
commercial systems
availability of, 217
detailed requirements specification for, 79
importance of transactions in, 134
performance types in, 191
common data for living entities, 131
common inquiry characteristics, 159, 161
common requirements, 10, F-26
communication links, F-56
communication medium, 60
communications, disaster recovery, 237
communications mechanism, interfaces involving, 58
company coding standards, compliance with, 76
company financial information, restricting access to, 311
company standards, 71
company Web style guidelines, compliance with, 76
company-specific requirement patterns, 43
compatible technology, 70
completeness
of chronicles, 145
of requirements, 40
complex transactions, 134–135, 138
compliance
with accessibility standards, 169, 170, 175, 184
with data longevity regulations, 107
demands for a standard, 73
comply-with-standard requirement pattern, 26, 71–79
component status inquiry, 159
components of a system, 15, F-55
compound data item, 95
compound data types, 88
comprehensive inquiries, 159, 160
computer literacy, accessibility and, 171, 174
conciseness of identifiers, 97
conciseness of requirement IDs, 13, F-37
confidentiality of reports, 166
configurable authorization, 47, 281, 282, 313–318
configurable authorization requirement pattern, 313–318
configuration, 120
of drivers, 248, 251–252, 253
multiness requirements and, 263, 264
configuration entities, 138, 141, 142
configuration files, 123
configuration requirement pattern, 37, 138–144
configuration values
changing, 139–140, 143, 144, 149
content requirements, 141
defining, 140
examples of, 142
flexibility of, 138
hard-coded, avoidance of, 138–139, 143
representative, 141
storing, 140
systemwide, 138, 139
templates for, 142
Considerations for development section, 21, 28–29, 40, 48
Considerations for testing section, 21, 29, 40, 48
consistency
of data, 123
of glossary terms, F-49
maintaining, 14, F-48
promoted by requirement patterns, 19
consolidation of fees/taxes, 338
constraints, F-54
contact details, 96
Content section, 21, 24, 47
context diagrams
advantages of, F-57
comparing for old and new systems, F-58
defined, F-54–F-55
in every requirements specification, 52
kinds of information on, 15–16, F-55–F-56
notable points about, F-57
samples, 52, 53
context of data types, 92
Context section of a requirements specification, 15–17, F-30, F-53–F-68
continuity of IDs, 99, 101
contradictions, resolving, F-43
core database, 124
core terms in a glossary, F-48
corporate restructuring, 245
cosmetic script, 181
cost-benefit analysis, 45
countries
differences between, 258–260
installing systems in different, 255
ISO 3166 standard, 76
CPU cycle rate, throughput targets and, 207
cross-instance access, 270
cross-instance conversion, 270
CRUD operations, 154
cultural differences, unparochialness and, 259
currency details
configuration values for, 142
ISO 4, 217
multiness in, 267
number types for, 87
unparochialness and, 258
customers
putting in control, F-5
using requirements, F-3
customer agreement, F-26
customer capacity, 216
customer details, storing, 130
customer number, 100
customer orders, archiving of, 113
customer password format requirement, 288
customer scalability, 243
customer service, accessible, 184
customer support for multiness instances, 268