Software Process Quality: Management and Control

✍ Scribed by Alexander Soifer, Branko Grünbaum, Peter Johnson, Cecil Rousseau

• Publisher: CRC Press, Marcel Dekker
• Year: 1999
• Tongue: English
• Leaves: 242
• Series: Computer Aided Engineering (New York, N.Y.), 6.
• Edition: 1
• Category: Library

✦ Synopsis

Using actual examples of software process improvement from the private sector and government, this work demonstrates how quality systems, measurement techniques and performance evaluations work. It presents a methodology for analyzing an ongoing software development process and establishing a rational plan for process improvement.

✦ Table of Contents

Software Process Quality: Management & Control......Page 1
Copyright......Page 4
Series Introduction......Page 7
Foreword......Page 8
Preface......Page 10
Contents......Page 14
1.1 Introduction......Page 15
1.2 Software Quality Program......Page 17
1.2.1 Requirements Management......Page 19
1.2.2 Methodology Establishment and Implementation......Page 21
1.2.3 Evaluation of Process and Product Quality......Page 27
References......Page 31
2.1.1 Definitions of Quality......Page 34
2.1.2 Overview of Quality Management......Page 37
2.1.4 Organizing For Quality Management......Page 38
2.2 Improvement Process......Page 42
2.2.1 Problem Recognition......Page 43
2.2.2 Selection of an Improvement Project......Page 45
2.2.3 Structured Diagnosis......Page 46
2.2.4 Preparing People--Guidelines for Introducing Change......Page 47
2.2.5 Process Improvement Projects......Page 49
2.2.6 Maintaining the Level of Improvement......Page 50
2.2.7 Quality Gets Results......Page 52
2.2.8 Senior Management Involvement......Page 54
2.3.1 Overview of Process Management......Page 55
2.3.2 Strategic Quality Planning......Page 57
2.3.3 Software Process Issues in Strategic Quality Planning......Page 59
2.3.4 Software Process Management Principles......Page 61
2.3.5 The Unique Characteristics of Software Development and Maintenance Processes......Page 64
2.4 Summary......Page 66
References......Page 67
3.1 ISO Standards......Page 68
3.2 Software Engineering Institute's Capability Maturity Model (CMM)......Page 71
3.2.1 Key Process Areas as Road Maps......Page 77
3.2.2 The CMM as an Assessment Tool......Page 79
3.3.1 Developing a Long-Range Action Plan for Process Improvement......Page 85
3.3.1.1 Develop Project Proposals......Page 88
3.3.1.2 Analyze Impact......Page 89
3.3.1.3 Analyze Risk......Page 92
3.3.1.4 Rank Proposed Projects......Page 93
3.3.1.5 Estimate Cost and Schedule......Page 95
3.3.1.6 Obtain Management Commitment......Page 96
3.3.2 Work Environment Factors Affecting Process Improvement Plan Implementation......Page 98
3.3.2.1 Facilities......Page 99
3.3.2.2 Software Tools......Page 100
3.3.2.3 Personnel Resources......Page 101
3.3.2.4 Management Policies......Page 103
3.3 Managing Improvement Projects......Page 104
3.4 Summary......Page 106
References......Page 107
4.1 Introduction......Page 109
4.2 Definitions......Page 110
4.3 Measures for Software Process Control & Improvement......Page 111
4.3.1 Size......Page 113
4.3.5 Cost......Page 114
4.4.1 Attributes......Page 115
4.4.2.1 Positive Impact Factors......Page 117
4.4.2.2 Negative Impact Factors......Page 118
4.5 Measurement Programs Iimplementation Steps......Page 119
4.5.1.1 Reasons for Implementation......Page 120
4.5.1.2 Questions to Help Identify Goals......Page 121
4.5.1.3 Identification of Sponsors......Page 122
4.5.1.4 Identification of Roles and Responsibilities......Page 124
4.5.2.2 Definition of Software Metrics......Page 126
4.5.3.1 Organizing for Just-in-Time Training and Education Processes......Page 128
4.5.3.2 Reporting and Publishing Results......Page 129
4.5.4.2 Managing with Metrics......Page 130
4.6.1 Example 1: Staffing Profiles......Page 131
4.6.2 Example 2: Software Size......Page 133
4.6.3 Example 3: Problem Report Tracking......Page 134
4.6.4 Example 4: Control Charts of Newly Opened Bugs (by week)......Page 135
4.6.5 Example 5: Control Charts of Closed Bugs (by week)......Page 138
References......Page 139
5.1 Introduction......Page 140
5.1.1 Dimensions of Product Quality......Page 141
5.1.2 Assessing Product Quality......Page 142
5.1.2.2 Defect Density......Page 143
5.1.2.4 Cyclomatic Complexity......Page 145
5.1.2.6 Software Maturity Index......Page 147
5.2 Software Specifications Metrics......Page 148
5.2.1 Introduction to Software Specifications Metrics......Page 149
5.2.2 Overview of the Specification Metrics Methodology......Page 150
5.2.3.1 Identifying Specification Sentences......Page 151
5.2.3.1.1 Referencing Sentence.......Page 152
5.2.3.2 Attribute Definitions......Page 153
5.2.3.2.7 Destination of Object.......Page 154
5.2.4 Specification Metrics Definition......Page 155
5.2.5 Metric Evaluation Criteria......Page 157
5.3.1 Readability of Software Documentation and Technical Manuals......Page 160
5.3.2.1 The Flesch Reading Grade Level Metric......Page 161
5.3.2.3 The Passive Sentences Metric......Page 162
References......Page 163
6.1 Introduction......Page 165
6.2 Hitachi Software Engineering Case Study......Page 167
6.3 Definitions of Software Reliability......Page 169
6.4 Software Reliability Models......Page 170
6.4.1 The Jelinski and Moranda ‘‘De-Eutrophication’’ Model......Page 171
6.4.2 The Lipow Extension Model......Page 175
6.4.3 A Case Study of the Lipow Model......Page 176
6.4.4 Pragmatic Software Reliability Estimation......Page 178
6.4.5 Data Domain Models Using Statistically Designed Testing Experiments......Page 180
6.5 Software Reliability Estimation & Tracking......Page 182
6.6 Hitachi Software Engineering Case Study Revisited......Page 183
6.7 Summary......Page 185
References......Page 186
7.1 Introduction to Software Reviews......Page 188
7.2 Management Reviews......Page 189
7.3.1 Software Walkthroughs......Page 191
7.3.2 Software Inspections......Page 193
7.3.3 Differences Between Walkthroughs and Inspection......Page 194
7.4.1 Checklists and Checksheets......Page 196
7.4.2 Pareto Chart Analysis......Page 199
7.4.3 The M-Test......Page 202
7.5 Limitations of Software Inspection Processes......Page 206
7.6 Assessing Software Inspection Processes with STAM......Page 209
References......Page 214
8.1 Introduction......Page 216
8.2.2.1 Middle Management Discussion Group......Page 217
8.2.2.2 Requirements and Customer Interface Functional Area Representative (FAR) Discussion Group......Page 219
8.2.2.3 Software Design and Coding FAR Discussion Group......Page 220
8.2.3 Positioning MIO in the Context of Other Software Organizations......Page 222
8.2.4 Launching the MIO Metrics Program......Page 224
8.3 Genetic Software Development Management Dashboards......Page 225
8.4 Software Development Management Dashboard Case Study: SPMN Main Control Panel......Page 226
8.4.1 Progress......Page 227
8.4.2 Change......Page 234
8.4.3 Staff......Page 235
8.4.4 Risk......Page 236
8.4.5 Quality......Page 239
8.5 Chapter Summary......Page 240
References......Page 242