Practical software requeriments :
Kovitz, Benjamin L.
Practical software requeriments : a manual of content and style / Benjamin L. Kovitz. - Greenwich : Manning, 1999 - 426 p.
CONTENIDO
PART I GROUNDWORK 1
Chapter 1 Problem solving 3
1.1 The myth of functional decomposition 5
1.2 Problem solving and design patterns 10
1.3 Why software is hard 13
1.4 Pattern composition and decomposition 16
Chapter 2 Problem defining 23
2.1 Requirements and design patterns 23
2.2 Software problems 25
2.3 Requirements engineering 27
2.4 Lessons learned 30
Chapter 3 Two worlds and three designs 33
3.1 The problem domain 33
3.2 Requirements 35
3.3 Interface design 36
3.4 Validation of interfaces and programs 39
3.5 Description 41
3.6 Invention versus validation 43
3.7 What software requirements are not 46
3.8 Summary 52
Chapter 4 Problem framing 55
4.1 The knight's tour 55
4.2 Domains 57
4.3 Shared phenomena 61
4.4 Connection domains 62
4.5 Realized domains 64
4.6 Frame diagrams 65
4.7 From diagram to documentation 69
4.8 Notation summary 70
Chapter 5 Five problem frames 73
5.1 Overview 73
5.2 Information problems 76
5.3 Control problems 83
5.4 Transformation problems 87
5.5 Workpiece problems 89
5.6 Connection problems 91
Chapter 6 Multi-frame problems 97
6.1 Combining problem frames 97
6.2 Inventory control system 98
6.3 Statistics package 102
6.4 Digital answering machine 102
6.5 Compiler 104
6.6 Electronic mail 105
6.7 Satellite reconnaissance 106
PART II CONTENT 111
Chapter 7 Software development 113
7.1 A division of cognitive labor 114
7.2 Analysis 116
7.3 User-interface design 118
7.4 Programming 119
7.5 Testing 121
7.6 User documentation 125
Chapter 8 Two documents 129
8.1 Contents of a requirements document 130
8.2 Contents of a specification 139
Chapter 9 Classes and relations 143
9.1 Two kinds of sets 144
9.2 Classes 146
9.3 All possible values 153
9.4 Impossible values 158
9.5 Relations 160
9.6 Cardinality 162
9.7 Relations as attributes 167
9.8 Uniqueness and functional dependence 173
9.9 Queries 176
9.10 Naming classes, attributes, and relations 180
Chapter 10 Sequences and events 183
10.1 Structure 184
10.2 Events 189
10.3 Event responses 192
10.4 More sequence notations 197
Chapter 11 Causation and control 207
11.1 State transitions 208
11.2 Actions 219
11.3 Dependency 222
11.4 Flow 231
11.5 Rules 233
Chapter 12 Special topics 241
12.1 Elicitation 241
12.2 Object-orientation 243
12.3 Use cases and feature interaction 250
12.4 Reviews 254
12.5 Requirements jargon 256
12.6 Cutting corners 258
12.7 A few good books 261
PART III STYLE 263
Chapter 13 Documentation 265
13.1 Why document? 265
13.2 Broad principles 268
13.3 Decoy text 274
13.4 More common mistakes 279
13.5 Poor uses of documentation 288
Chapter 14 Organization 293
14.1 Content first 293
14.2 Grouping 294
14.3 Sequence 300
14.4 Emphasis 302
Chapter 15 Small Details 305
PART IV EXAMPLES 339
Chapter 16 Bug Log requirements 341
Chapter 17 Bug Log user interface 377
1884777597
SOFTWARE DEVELOPMENT
REQUIREMENTS
DESIGN PATTERN
PROBLEM FRAMING
004.41 K849
Practical software requeriments : a manual of content and style / Benjamin L. Kovitz. - Greenwich : Manning, 1999 - 426 p.
CONTENIDO
PART I GROUNDWORK 1
Chapter 1 Problem solving 3
1.1 The myth of functional decomposition 5
1.2 Problem solving and design patterns 10
1.3 Why software is hard 13
1.4 Pattern composition and decomposition 16
Chapter 2 Problem defining 23
2.1 Requirements and design patterns 23
2.2 Software problems 25
2.3 Requirements engineering 27
2.4 Lessons learned 30
Chapter 3 Two worlds and three designs 33
3.1 The problem domain 33
3.2 Requirements 35
3.3 Interface design 36
3.4 Validation of interfaces and programs 39
3.5 Description 41
3.6 Invention versus validation 43
3.7 What software requirements are not 46
3.8 Summary 52
Chapter 4 Problem framing 55
4.1 The knight's tour 55
4.2 Domains 57
4.3 Shared phenomena 61
4.4 Connection domains 62
4.5 Realized domains 64
4.6 Frame diagrams 65
4.7 From diagram to documentation 69
4.8 Notation summary 70
Chapter 5 Five problem frames 73
5.1 Overview 73
5.2 Information problems 76
5.3 Control problems 83
5.4 Transformation problems 87
5.5 Workpiece problems 89
5.6 Connection problems 91
Chapter 6 Multi-frame problems 97
6.1 Combining problem frames 97
6.2 Inventory control system 98
6.3 Statistics package 102
6.4 Digital answering machine 102
6.5 Compiler 104
6.6 Electronic mail 105
6.7 Satellite reconnaissance 106
PART II CONTENT 111
Chapter 7 Software development 113
7.1 A division of cognitive labor 114
7.2 Analysis 116
7.3 User-interface design 118
7.4 Programming 119
7.5 Testing 121
7.6 User documentation 125
Chapter 8 Two documents 129
8.1 Contents of a requirements document 130
8.2 Contents of a specification 139
Chapter 9 Classes and relations 143
9.1 Two kinds of sets 144
9.2 Classes 146
9.3 All possible values 153
9.4 Impossible values 158
9.5 Relations 160
9.6 Cardinality 162
9.7 Relations as attributes 167
9.8 Uniqueness and functional dependence 173
9.9 Queries 176
9.10 Naming classes, attributes, and relations 180
Chapter 10 Sequences and events 183
10.1 Structure 184
10.2 Events 189
10.3 Event responses 192
10.4 More sequence notations 197
Chapter 11 Causation and control 207
11.1 State transitions 208
11.2 Actions 219
11.3 Dependency 222
11.4 Flow 231
11.5 Rules 233
Chapter 12 Special topics 241
12.1 Elicitation 241
12.2 Object-orientation 243
12.3 Use cases and feature interaction 250
12.4 Reviews 254
12.5 Requirements jargon 256
12.6 Cutting corners 258
12.7 A few good books 261
PART III STYLE 263
Chapter 13 Documentation 265
13.1 Why document? 265
13.2 Broad principles 268
13.3 Decoy text 274
13.4 More common mistakes 279
13.5 Poor uses of documentation 288
Chapter 14 Organization 293
14.1 Content first 293
14.2 Grouping 294
14.3 Sequence 300
14.4 Emphasis 302
Chapter 15 Small Details 305
PART IV EXAMPLES 339
Chapter 16 Bug Log requirements 341
Chapter 17 Bug Log user interface 377
1884777597
SOFTWARE DEVELOPMENT
REQUIREMENTS
DESIGN PATTERN
PROBLEM FRAMING
004.41 K849