search for books and compare prices
Tables of Contents for Industrial Strength Software
Chapter/Section Title
Page #
Page Count
Foreword
xi
2
Preface
xiii
PART I. MANAGEMENT VIEW OF SOFTWARE DEVELOPMENT
1
26
Chapter 1. The Management Questions
3
8
How can I pick the beef out of the hash?
4
1
What is the beef?
5
1
Is there a software crisis?
6
1
Has anyone actually managed software successfully?
7
4
Chapter 2. You Have To Have Software
11
6
Competitive advantage
12
1
Impact of information technology
13
4
Chapter 3. Planning Software Development
17
10
Estimating production
18
2
Estimating a development project
20
1
Estimating software development
20
5
Using the estimates
25
2
PART II. PATTERN OF MEASUREMENT
27
50
Chapter 4. The Rhythm and Pattern of Software
29
8
Management numbers increase with size
30
3
Source lines per person-month is a poor metric
33
2
Management numbers vary widely at same size
35
2
Chapter 5. The Pattern of Complexity
37
6
Aspects of complexity
37
1
What the database shows
38
5
Chapter 6. Calibrating The Software Process
43
8
Fourth factor
44
2
A larger concept of productivity
46
2
Calibrating your own index
48
3
Chapter 7. Valuing Attributes by calibration
51
4
Chapter 8. Estimating Size
55
8
The main ideas
56
1
Beyond the basic estimate
57
6
Chapter 9. The Fifth Factor: Manpower Buildup
63
6
Manpower buildup
64
1
Manpower buildup index
65
1
Management influence
65
4
Chapter 10. Standardize, Discipline, and Use Measurements
69
8
Standardize the metrics
70
4
Discipline your organization
74
1
Make metrics usable
74
3
PART III. PROJECT MANAGEMENT
77
78
Chapter 11. Planning Effort and Schedule
79
6
Visualizing effort and time
81
2
Locating the practical region
83
2
Chapter 12. The Impossible Region: Keep out!
85
8
Locating the impossible region
87
1
Dealing with business pressures
88
5
Chapter 13. Risk Is Ever Present
93
8
The uncertainty of minimum development time
94
1
Dealing with uncertainty
94
2
Getting risk in the picture
96
2
Using point estimates
98
3
Chapter 14. Trade Time for Effort
101
6
The tradeoff region
101
2
The impractical region
103
1
The truth about "reducing the cycle"
104
3
Chapter 15. The Effects of Smaller Development Teams
107
6
Chapter 16. Operating within Constraints
113
8
Picking your battles
113
2
Optimizing the solution
115
2
Dealing with Windows-NT constraints
117
4
Chapter 17. Bounding Risk
121
6
Consistency check
121
1
Risk profiles
122
5
Chapter 18. Planning the Work
127
8
Reports and presentations
128
6
A broad plan
134
1
Chapter 19. Working the Plan
135
8
Pick key factors
136
1
Measure key factors
137
1
Project key factors
137
2
Measure actuals
139
1
Compare actuals against the plan
139
2
A note on the mechanics
141
2
Chapter 20. "I Always Felt Frustrated"
143
4
Chapter 21. Shining Shadow Loses Its Luster
147
8
PART IV. RELIABILITY
155
52
Chapter 22. The Path To Quality
157
8
Inspection
157
2
Statistical process control
159
2
Beyond inspection to quality
161
1
Good requirements, good quality
162
1
Lessons learned
163
2
Chapter 23. A Measure of Software Quality
165
8
A software measure
165
3
Projecting the software measure
168
2
Rate forecasting
170
3
Chapter 24. Plan Project To Minimize Defects
173
8
Development time: more is better
173
2
Effort
175
2
Size
177
1
Process productivity and manpower buildup
177
1
Delivery date
178
3
Chapter 25. Institute Early Inspection
181
8
Testing
182
1
Upstream efforts
183
1
Inspection lessons: early and often is best
184
2
Contrarians
186
3
Chapter 26. Achieving Quality
189
6
Control against projections
189
2
Prevent defects
191
4
Chapter 27. Coping with Maintenance
195
6
What is it?
195
1
Why is it so difficult to "understand"?
196
1
Why do programmers introduce new defects?
197
1
How do errors get corrected?
197
1
When is it modification?
198
1
When is it time to replace the system?
199
2
Chapter 28. Better, Faster, and Cheaper
201
6
PART V. PROCESS IMPROVEMENT PHASE
207
90
Chapter 29. A CEO Thinks About Process Improvement
209
4
Chapter 30. Process Productivity Marches On
213
10
The productivity record
213
2
Potential gains
215
1
The decade of the 1990s
216
7
Chapter 31. Process Improvement Yields Results
223
8
What you gain
224
5
Raytheon increases productivity
229
1
The bleak side
229
2
Chapter 32. Plan To Improve The Process
231
6
Do what you know you should
231
2
Do what software people know
233
1
If it's so easy...
234
3
Chapter 33. Measure, Plan, Invest, Remeasure, Invest Again
237
8
The way to process improvement
238
1
A way to start
239
1
Action team loop
239
2
Management support loop
241
4
Chapter 34. Simplify the Project
245
8
Simplify requirements
246
1
Develop incrementally
247
1
Discipline change
248
1
Make subsystems independent
249
4
Chapter 35. The Process of Reusing Software
253
10
Reuse increases code-production rate
253
3
Reuse improves management numbers
256
1
Costs of reuse
257
1
Strategies of reuse
258
2
The possibilities
260
3
Chapter 36. The Process of Business Reengineering
263
8
Focus on value
265
1
Information up and down
266
1
Information enables reengineering
267
1
Object technology targets reuse
268
3
Chapter 37. People Process
271
6
Enhance people's capability
272
2
One on one
274
1
Executive briefing
275
2
Chapter 38. Leveraging People's Capabilities
277
8
Capture knowledge in software
277
2
Support makes a difference
279
2
Keeping up
281
1
One company's experience
282
3
Chapter 39. Get Up-to-Date
285
6
Use modern programming practices
285
1
Use third-generation languages
286
1
Use fourth-generation languages
287
1
Use application generators
287
1
Consider outsourcing
288
1
Move to interactive development
288
1
Computer-aided software engineering
288
1
Document efficiently
289
1
Client-server systems
289
2
Chapter 40. You Make It Happen
291
6
Bibliography
297
4
Index
301