Foreword |
|
xv | |
Preface |
|
xvii | |
Acknowledgments |
|
xxi | |
About the Authors |
|
xxiii | |
|
SECTION I STRATEGY AND BASICS OF QUALITY AND PROCESS IMPROVEMENT |
|
|
|
The Strategic Role of Systems and Software Quality |
|
|
3 | (28) |
|
|
3 | (2) |
|
|
5 | (3) |
|
Strategic Planning Models |
|
|
8 | (3) |
|
Elements of System and Software Quality |
|
|
11 | (8) |
|
Requirements Establishment and Control |
|
|
14 | (1) |
|
Methodology Establishment and Implementation |
|
|
14 | (1) |
|
|
15 | (3) |
|
Interactions among System Quality Program Elements |
|
|
18 | (1) |
|
Deployment of Strategic Quality Goals |
|
|
19 | (2) |
|
Strategic Maps and Balanced Scorecards |
|
|
21 | (5) |
|
|
26 | (2) |
|
|
28 | (3) |
|
Basic Elements of Continuous Process Improvement |
|
|
31 | (34) |
|
|
31 | (1) |
|
Continuous Improvement Infrastructures |
|
|
31 | (6) |
|
Process Improvement Projects and Measurement Programs |
|
|
37 | (4) |
|
Six Sigma (DMA=C and DFSS Methodology) |
|
|
41 | (5) |
|
Enterprise Knowledge Development (EKD) |
|
|
46 | (7) |
|
EKD Actor and Role Components |
|
|
48 | (1) |
|
The Actor and the Actor's Role |
|
|
48 | (1) |
|
The Actor-Role Relationship |
|
|
49 | (1) |
|
The Role-Role Relationship |
|
|
49 | (1) |
|
|
50 | (1) |
|
Guidelines for the Actor-Role Diagram |
|
|
50 | (1) |
|
Examples of Actor-Role Diagrams |
|
|
51 | (1) |
|
EKD Role-Activity Diagram |
|
|
51 | (2) |
|
|
53 | (7) |
|
|
54 | (1) |
|
|
54 | (6) |
|
|
60 | (1) |
|
|
60 | (5) |
|
SECTION II ASSESSMENT AND MEASUREMENT IN SYSTEMS AND SOFTWARE DEVELOPMENT |
|
|
|
CMMI, People CMM, Personal and Team Software Process, eSCM, ITIL, and ISO Standards |
|
|
65 | (50) |
|
|
65 | (1) |
|
Capability Maturity Model Integration (CMMI) |
|
|
66 | (17) |
|
|
66 | (2) |
|
|
68 | (1) |
|
|
68 | (1) |
|
|
69 | (7) |
|
|
76 | (1) |
|
|
77 | (1) |
|
CMMI for Acquisition (CMMI-ACQ) |
|
|
77 | (2) |
|
CMMI for Services (CMMI-SVC) |
|
|
79 | (1) |
|
SCAMPI Class A Appraisal Methodology |
|
|
80 | (2) |
|
SCAMPI B and C Appraisals |
|
|
82 | (1) |
|
|
83 | (4) |
|
Personal and Team Software Process |
|
|
87 | (4) |
|
|
87 | (3) |
|
|
90 | (1) |
|
eSourcing Capability Model (eCSM) |
|
|
91 | (5) |
|
Barriers to Successful Sourcing Relationships |
|
|
91 | (1) |
|
eSCM for Service Providers |
|
|
92 | (2) |
|
eSCM for Client Organizations |
|
|
94 | (1) |
|
eSCM Capability Determinations |
|
|
95 | (1) |
|
Information Technology Infrastructure Library (ITIL) |
|
|
96 | (4) |
|
|
96 | (3) |
|
|
99 | (1) |
|
Connections between ITIL and eSCM |
|
|
100 | (1) |
|
|
100 | (9) |
|
|
100 | (3) |
|
|
103 | (2) |
|
|
105 | (1) |
|
|
106 | (3) |
|
ISO Standard Interrelationships |
|
|
109 | (1) |
|
|
109 | (2) |
|
|
111 | (4) |
|
System and Software Measurement Programs |
|
|
115 | (46) |
|
|
115 | (1) |
|
Defining Measures for Process Control and Improvement |
|
|
115 | (9) |
|
|
121 | (1) |
|
|
122 | (1) |
|
|
123 | (1) |
|
|
123 | (1) |
|
|
123 | (1) |
|
|
123 | (1) |
|
Effectiveness of Process Measurement Programs |
|
|
124 | (5) |
|
|
124 | (3) |
|
|
127 | (1) |
|
|
127 | (1) |
|
|
127 | (1) |
|
|
128 | (1) |
|
Measurement Program Implementation Steps |
|
|
129 | (10) |
|
|
130 | (1) |
|
Reasons for Implementation |
|
|
130 | (1) |
|
Questions to Help Identify Goals |
|
|
131 | (1) |
|
Identification of Sponsors |
|
|
131 | (2) |
|
Identification of Roles and Responsibilities |
|
|
133 | (2) |
|
|
135 | (1) |
|
Analysis of Audience and Identification of Target Metrics |
|
|
135 | (1) |
|
|
135 | (2) |
|
|
137 | (1) |
|
Organizing for Just-in-Time Training and Education Processes |
|
|
137 | (1) |
|
Reporting and Publishing Results |
|
|
138 | (1) |
|
|
138 | (1) |
|
|
138 | (1) |
|
|
139 | (1) |
|
|
139 | (10) |
|
Measurement Program Case Studies |
|
|
140 | (1) |
|
An Effective Measurement Program |
|
|
140 | (1) |
|
An Ineffective Measurement Program |
|
|
141 | (1) |
|
Beneficial Measurement Examples |
|
|
141 | (1) |
|
|
141 | (1) |
|
|
142 | (2) |
|
|
144 | (1) |
|
Control Charts of Newly Opened Bugs, by Week |
|
|
145 | (3) |
|
Control Charts of Closed Bugs, by Week |
|
|
148 | (1) |
|
|
149 | (1) |
|
Measurement and the CMMI High Maturity Practices |
|
|
149 | (6) |
|
|
151 | (2) |
|
|
153 | (2) |
|
|
155 | (1) |
|
|
155 | (1) |
|
|
156 | (5) |
|
SECTION III IMPROVEMENTS AND TESTING OF SYSTEMS AND SOFTWARE |
|
|
|
System and Software Development Process Improvement |
|
|
161 | (30) |
|
|
161 | (1) |
|
Implementing System and Software Process Improvement |
|
|
161 | (18) |
|
Developing a Long-Range Action Plan for Process Improvement |
|
|
162 | (13) |
|
Work Environment Factors Affecting Process Improvement Plan Implementation |
|
|
175 | (1) |
|
|
175 | (1) |
|
Software Tools to Facilitate Process Implementation |
|
|
176 | (1) |
|
|
177 | (1) |
|
|
178 | (1) |
|
Managing Improvement Projects |
|
|
179 | (2) |
|
Roles and Responsibilities and Specifying Mission Statements |
|
|
181 | (2) |
|
Criteria for Team Composition |
|
|
183 | (1) |
|
Launching Improvement Teams |
|
|
184 | (1) |
|
Managing Improvement Teams |
|
|
184 | (1) |
|
|
184 | (5) |
|
|
189 | (1) |
|
|
189 | (2) |
|
System and Software Testing Strategies |
|
|
191 | (58) |
|
|
191 | (1) |
|
Designing a Test Strategy |
|
|
192 | (10) |
|
|
192 | (8) |
|
``Pre-Alpha'': Early Testing before Feature Freeze |
|
|
200 | (1) |
|
``Alpha'': Feature Freeze |
|
|
201 | (1) |
|
``Validation and Beta'': Development Is Complete |
|
|
201 | (1) |
|
Implementing a Test Strategy |
|
|
202 | (10) |
|
Ten Steps for Time-to-Market and Quality Improvement |
|
|
202 | (1) |
|
Build and Development Product Version Plans |
|
|
203 | (1) |
|
Main Phases in the Test Plan |
|
|
204 | (1) |
|
Monitoring and Controlling the Test Process |
|
|
205 | (1) |
|
|
205 | (3) |
|
Defects by Severity/Status |
|
|
208 | (4) |
|
|
212 | (6) |
|
|
212 | (3) |
|
Modeling of Incremental Software and System Control |
|
|
215 | (1) |
|
Modeling of Test Processes |
|
|
216 | (2) |
|
|
218 | (3) |
|
Accumulated Lines of Code and Accumulated Defects per Build |
|
|
218 | (1) |
|
|
219 | (1) |
|
New Severity I through Severity 3 Defects per Build |
|
|
220 | (1) |
|
Assessing Testing Effectiveness and Efficiency |
|
|
221 | (7) |
|
The Software Trouble Assessment Matrix (STAM) |
|
|
221 | (1) |
|
A STAM Analysis of Release 7.0 |
|
|
222 | (1) |
|
Comparing Releases with a STAM Analysis |
|
|
222 | (6) |
|
Software Reliability Models |
|
|
228 | (1) |
|
|
229 | (1) |
|
|
229 | (3) |
|
Software Reliability Models |
|
|
232 | (13) |
|
|
233 | (2) |
|
A Case Study of the Lipow Model |
|
|
235 | (2) |
|
|
237 | (1) |
|
|
238 | (1) |
|
The Musa-Okomoto Logarithmic Model |
|
|
238 | (1) |
|
The Yamada S-Shaped NHPP Models |
|
|
238 | (1) |
|
|
239 | (1) |
|
|
239 | (1) |
|
|
239 | (1) |
|
Estimation for Model Parameters and Semi-Parametric Control |
|
|
240 | (1) |
|
Point Estimation for NHPP Model Parameters |
|
|
240 | (1) |
|
A General Approach for Parameter Estimation |
|
|
240 | (3) |
|
The Shiryayev-Roberts Semi-Parametric Procedure |
|
|
243 | (2) |
|
|
245 | (4) |
|
System and Software Beta and Usability Programs |
|
|
249 | (50) |
|
|
249 | (1) |
|
|
250 | (9) |
|
Introduction to Beta Planning |
|
|
250 | (5) |
|
Beta Test Standard Operating Procedure |
|
|
255 | (4) |
|
Beta Test Data Collection and Analysis |
|
|
259 | (13) |
|
|
259 | (2) |
|
Beta Test Survey Data Analysis |
|
|
261 | (8) |
|
|
269 | (3) |
|
Beta Test Risk and Usability Analysis |
|
|
272 | (9) |
|
Introduction to Risk Management |
|
|
273 | (1) |
|
|
273 | (1) |
|
|
274 | (6) |
|
Risk Monitoring and Control |
|
|
280 | (1) |
|
|
281 | (7) |
|
Introduction to Usability |
|
|
281 | (1) |
|
A Case Study: Web Usability Analytics |
|
|
282 | (1) |
|
A DSUID Implementation Framework: The Seven Layers Model |
|
|
283 | (2) |
|
DSUID Modeling Techniques |
|
|
285 | (3) |
|
Determining Readiness Success Criteria |
|
|
288 | (4) |
|
Mapping Goals to Strategic Objectives |
|
|
288 | (2) |
|
Using QFD to Establish Readiness Criteria |
|
|
290 | (2) |
|
Managing Readiness Reviews |
|
|
292 | (1) |
|
|
293 | (1) |
|
|
294 | (5) |
|
SECTION IV MANAGING AND REPORTING DATA, AND A COMPREHENSIVE CASE STUDY |
|
|
|
Data Reporting and Analysis |
|
|
299 | (32) |
|
|
299 | (1) |
|
Designing a Data Reporting System |
|
|
300 | (5) |
|
Defining the Data to Collect |
|
|
300 | (1) |
|
Establishing the Data Center |
|
|
301 | (2) |
|
|
303 | (1) |
|
Data Storage and Analysis |
|
|
303 | (1) |
|
|
304 | (1) |
|
Operating a Data Reporting System |
|
|
305 | (3) |
|
|
305 | (1) |
|
|
306 | (1) |
|
|
306 | (2) |
|
Power Failure Considerations |
|
|
308 | (1) |
|
|
308 | (3) |
|
Reporting on Findings and Consequences |
|
|
311 | (2) |
|
|
313 | (12) |
|
|
325 | (4) |
|
|
329 | (2) |
|
Systems Development Management Dashboards and Decision Making |
|
|
331 | (40) |
|
|
331 | (1) |
|
Introduction to Systems Development Management Dashboard |
|
|
332 | (1) |
|
A Systems Development Management Dashboard Case Study |
|
|
332 | (15) |
|
|
334 | (5) |
|
|
339 | (3) |
|
|
342 | (2) |
|
|
344 | (2) |
|
|
346 | (1) |
|
Additional Metrics at the PMO Level |
|
|
347 | (14) |
|
Profit from New Products and Systems |
|
|
349 | (1) |
|
|
350 | (1) |
|
|
351 | (1) |
|
New Product/System Quality |
|
|
352 | (2) |
|
Uniqueness of Products/Systems |
|
|
354 | (1) |
|
|
355 | (1) |
|
New Product/System Break-Even Time |
|
|
356 | (1) |
|
New Product/System Introduction Rate |
|
|
357 | (1) |
|
|
358 | (2) |
|
|
360 | (1) |
|
Risk Management and Optimizing Decisions with Data |
|
|
361 | (7) |
|
Uncertainty Models and Risk Management |
|
|
361 | (2) |
|
Bayes Methods in Risk Management |
|
|
363 | (2) |
|
Financial Engineering and Risk Management |
|
|
365 | (2) |
|
Black Swans and the Taleb Quadrants |
|
|
367 | (1) |
|
|
368 | (1) |
|
|
369 | (2) |
|
A Case Study: The Journey of Systems, Inc. to CMMI® Level 5 |
|
|
371 | (34) |
|
|
371 | (1) |
|
Background of Systems, Inc |
|
|
371 | (10) |
|
The Systems, Inc. SCAMPI Appraisal |
|
|
373 | (1) |
|
Some Background on the Need for an Appraisal |
|
|
373 | (1) |
|
Appraisal Interviews at Systems, Inc |
|
|
373 | (1) |
|
Middle Management Discussion Group |
|
|
373 | (2) |
|
Requirements and Customer Interface Functional Area Representative (FAR) Discussion Group |
|
|
375 | (1) |
|
Software Design and Coding FAR Discussion Group |
|
|
375 | (2) |
|
Benchmarking of Systems, Inc |
|
|
377 | (4) |
|
Strategic Planning for Process Improvement at Systems, Inc |
|
|
381 | (20) |
|
The Systems, Inc. Software Development Challenge |
|
|
381 | (3) |
|
|
384 | (1) |
|
|
385 | (1) |
|
|
386 | (1) |
|
Meetings/Activities in Scrum |
|
|
386 | (2) |
|
|
388 | (1) |
|
Scaling Scrum in Big Projects |
|
|
389 | (1) |
|
EKD, Patterns, and Scrum at Systems, Inc |
|
|
389 | (10) |
|
The Systems, Inc. Measurement Program |
|
|
399 | (2) |
|
|
401 | (2) |
|
|
403 | (2) |
Index |
|
405 | |