D


data. See also information

backdated, 109

backing up, 123

configurable authorization to, 314

derived, 121

disaster recovery, 237

historic, 121

restricting access to, 308, 310–311

segregated, 261–262

unaddable, 262

data access, recording unsuccessful, 148

data archiving requirement pattern, 110–117

data consistency, 123

data description for archiving, 112

data display, types of, 86

data durability, 123

data entities. See also living entities

categorization of, 119–120

naming, 122, 130

data entity domain, 29

data entity requirement pattern, 119–154

data entry function, testing user registration as, 295

data format error response time, 200

data husbandry, 85

data longevity requirement pattern, 107–110

data loss, 123, 124

data modification, archiving and, 115

data protection, 123, 287, 290–292

data recovery, 123, 124

data storage, 107, 108. See also data archiving

data stores, 122, 126–127, F-56

data structure, 136

data structure requirement pattern, 94–96

data type requirement pattern, 86–94

data types

in calculation formulas, 103

for different organizations, 260

data warehouse, 164

database

ACID properties of, 123, 154

backing up of, 110

CRUD operations, 154

estimating disk space needed for, 216

recording events in, 151

specifying a widely used, 68

as storage mechanism, 120, 154

dates, 88, 89–90

of each version released, F-52

event, 151

report, 166

systemwide aspects of, 93

unparochialness and, 259

date display formats, 90

day one considerations for user registration, 287, 294

Daylight Saving Time, 90

de-authentication of users, 298, 299–300

default language of a system, 274

default multiness instances, 268

definitions

in a glossary, 14, F-44, F-45, F-46

of requirements. See requirement definitions

delays, warning users about, 203

deliberate shutdowns, 231

delivery mechanisms for reports, 190

denial-by-default rule, 305–306, 308, 310

dependencies, 16, 45, F-59

de-registration of users, 287, 290

derived data, 121

descriptive placeholders, 46

design patterns, 20, 21, 42

designers, constraining, F-9

destination of archived data, 112–113

detailed requirements, 4, F-3, F-27

details in a requirement definition, F-42

developers

constraining, F-9

guidance to, 47, 48

using requirements, F-3

writing in the language of, 28–29

development

approaches, 5–6, F-6

facilities, 69

splitting between multiple teams, 54

technology, 66, 70

devolution of information, 135

dexterity, accessibility and, 171, 174, 182

dialects, 259, 272

diminishing returns, availability increases and, 220

disabilities, people with, 168, 169

disaster recovery systems, 237

disclaimers

regarding the glossary, F-44

stating, 13, F-33

discounts, specifying, 334

Discussion section in requirement pattern, 21, 24

disk space needed, estimating, 216

display format, 91, 99

display of data, 86

distinct user experiences, 261, 267–269, 271

distinctive requirement IDs, 13, F-37

distributed office scalability, 243

divertive performance patterns, 192

divertive requirement pattern, 32, 36

Document history section of requirements specification, 15, F-51–F-53

document library scalability, 243

document management system, 154

document purpose, F-30

Document purpose section, 12–13, F-32–F-33

document templates, 123

documentary efficiency, 9

documentation

accessibility of, 175, 184

of interfaces, 57, 61

purpose of, F-24

unparochial, 258

documentation requirement pattern, 81–84

domains

assigning requirement patterns to, 29–31

compared to requirement pattern groups, 32

creating new, 44–45

infrastructures in, 30

as a source of candidate infrastructures, F-64

specifying, 22

domain expert, F-15

domain specification, 37

downtime

business impact of, 221, 223–224

causes of, 221, 225

levels of, 218

reducing, 225–235

scheduled, 219

tolerated, 222

draft requirements specification, writing, 8, F-18–F-19

drivers

configuration information for, 248, 249–250

extendability requirements and, 247, 249

installation requirements for, 251–252, 253

switching between, 253

system requirements for, 250–251

third-party, development requirements, 252

upgrading, 253

driving entity, 215–216

durability of data, 123

duration start trigger, 108

dynamic capacity, 47

dynamic capacity requirement pattern, 212–215

dynamic users, counting, 213

dynamic Web functions, 222




Microsoft Press - Software Requirement Patterns
Software Requirement Patterns (Best Practices)
ISBN: 0735623988
EAN: 2147483647
Year: 2007
Pages: 110

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net