#40 – SOFTWARE INFORMATION SOURCES – CAPERS JONES

Posted on by

Capers Jones pixABSTRACT
This list of software information sources is provided as a public service by Namcook Analytics LLC.  Since this report consists primarily of citations to published books, articles, and web sites it is not copyrighted and may be freely distributed.  However the books and articles themselves normally are copyrighted so permissions would be needed to use the actual books and publications shown in this report.

Reference lists such as this are not static since new books and articles are published on a daily basis.  The intent is to produce new versions of this report, probably on an annual basis, if interest is sufficient.

This listing is organized by topic, and some books cover more than a single topic so they appear in multiple sections of the report.  The literature cited in this report ranges from materials copyrighted in the 1970’s through new materials copyrighted in 2014.

Table of Contents

Amazon Books on Software Measurement
Amazon Books on Software Cost Estimation                                                                          Books with Quantitative Data                                                                                                  Books on Measurement and Metrics                                                                                    Books on Architecture, Requirements, and Design                                                            Books on Software Risk Control                                                                                                Books on Software Quality Control                                                                                    Books on Software Security, Hacking, and Malware PreventionBooks on Software Engineering and Programming
Books on Software Development Methods
Books on Software Deployment, Customer Support, and Maintenance
Books on Social Issues in Software Engineering
Books on Cloud Software Development
Web Sites
Software Standards Organizations
Software Certification Organizations Amazon books on “Software Measurements”

Note:  This section lists the titles and authors of books that appear based on a query in Amazon for “software measurement.”  The Amazon results will change frequently.  New books come out almost every month.  Software measurement is a weak link in the chain of software engineering technologies.  Software measurement suffers from “leakage” of historical data and also from the use of invalid metrics such as “lines of code” and “cost per defect” neither of which produce valid economic results.

  1. Applied Software Measurement, Capers Jones
  2. The Economics of Software Quality, Capers Jones & Olivier Bonsignour
  3. Assessment and Control of Software Risks, Capers Jones
  4. Patterns of Software Systems Failure and Success, Capers Jones
  5. Critical Problems in Software Measurement, Capers Jones
  6. Software Engineering Economics; Barry Boehm
  7. Software Measurement, Christof Ebert and Reiner Dumke
  8. Measuring the Software Process, William A. Florac
  9. The Software IP Detective’s Handbook, William Zeidman
  10. Software Measurement and Estimation, Linda Laird and M. Carol Brennan
  11. How to Observe Software Systems, Gerald Weinberg
  12. Responding to Significant Software Results, Gerald Weinberg
  13. Best Practices in Software Measurement, Christof Ebert and Reiner Dumke
  14. Practical Software Measurement, John McGarry and David Card
  15. Controlling Software Projects, Tom DeMarco
  16. Value Based Software Engineering, Arum, Boehm, and Erdogmus
  17. Practical Software Metrics, Robert Grady
  18. Software Metrics, Ravindranath Pandian
  19. Function Point Analysis, David Garmus and David Herron
  20. Applied Statistics for Software Managers, K. Maxwell
  21. Software Metrics: Establishing a Company-Wide Program; R. Grady and D. Caswell
  22. The IT Measurement Compendium, Manfred Bundschuh and Carol Dekkers
  23. Making Software Measurement Work, William Hetzel
  24. Software Engineering Measurements, John C. Munson
  25. Object Oriented Test and Measurement, Lee Atchison
  26. Software Product and Process Measurement; Alain Abran et al
  27. A Framework of Software Measurement, Horst Zuse
  28. The Software Measurement Guidebook, John Gaffney
  29. Object-Oriented Software Metrics, Mark Lorenz and Jeff Kidd
  30. IT Measurement: Advice from the Experts; IFPUG authors
  31. Software Metrics for Product Assessment, Richard Bache and Gualtiero Bazzano
  32. Derivation and Validation of Software Metrics, Martin Shepard and Darrel Ince
  33. Software Metrics: A Practitioners Guide; K.H. Moller and Daniel Paulish
  34. Foundations of Empirical Software Engineering; Basili, Boehm, Rombach, Zelkowitz
  35. Practical Software Measurement, Bob Hughes
  36. Software Measurement: A Visualizaton Toolkit; Ellis, Fujiwara, Kuo, Simmons
  37. Measurement as a Powerful Software Management Tool, Nickolas Ashley
  38. Measurement for Software Control and Assurance, B.A. Kitchenham and B. Littlewood
  39. Software Metrics: Measurement for Software Process Improvement
  40. Investigations in Software Measurement, Alain Abran
  41. Practical Implementation of Software Metrics, Paul Goodman
  42. Software Metrics: A Rigorous and Practical Approach, N. Fenton and L. Pfleeger
  43. Managing Software Quality:  A Measurement Framework; Richard Nance
  44. Software Process Improvement: Metrics, Measurement, and Modeling; Haug et al
  45. The Effectiveness of Software Project Management; Christopher Cullen
  46. The IFPUG Guide to IT and Software Measurement; IFPUG authors
  47. Quality Software Management; First-Order Measurement, Gerald Weinberg
  48. Metrics and Models in Software Quality Engineering, Dr. Steve Kan
  49. Software Performance and Scalability; Henry Liu
  50. Mastering Software Quality Assurance, Murali Chemuturi
  51. Six Sigma Software Quality Improvement; Vic Nanda, Jeffrey Robinson
  52. Software Verification and Validation; Steven R. Ratkin
  53. A Practical Guide for Measuring Usability, Jeff Sauro
  54. Joe Celko’s Data Measurement and Standards in SQL; Joe Celko
  55. Oracle Database Performance and Scalability, Henry H. Liu
  56. Agile Analysis, a Value-Driven Approach; Ken Collier
  57. Project Management Metrics, KPIs, and Dashboards, Harold Kerzner
  58. Entropy-Based Measurement for Software; Ozgur Aktunc
  59. ISO/IEC 14143-1:1998; Software Measurement, Functional Size Measurement
  60. IT Governance Metrics, Measurement, and Benchmarking, Blokdijk and Menken
  61. Object-Oriented Design Metrics; Scott Whitmire
  62. Quality Software Project Management, Donald Shafer, Isabell Shafer
  63. Handbook of Software Quality Assurance. G. Gordon Schulmeyer
  64. Software Engineering Reviews and Audits, Boyd L. Summers
  65. Managing the Development of Software-Intensive Systems; James McDonald
  66. Scaling Lean and Agile Development; Craig Larman and Bas Vodde
  67. Practical Software Measurement, Card, Layman, Clark, Dean, Hall, McGarry
  68. Antipatterns: Identification, Refactoring, and Management, Phillip Laplante
  69. Portfolio Performance Measurement and Benchmarking, Christopherson et al
  70. Software Reliability Engineering, John Musa
  71. Software Metrics and Software Methodology, Alain Abran
  72. Measuring the Software Process, David Garmus and David Herron
  73. ROI of Software Process Improvement, David Rico and Roger Pressman
  74. Agile Estimating and Planning, Mike Cohn
  75. Software Sizing, Estimation, and Risk Management, Dan Galorath
  76. Process Improvements and CMMI® for Systems and Software, Kenett and Baker

Amazon Books on “Software Cost Estimation”
This section discusses the topic of software estimation based on an Amazon search using the phrase “software cost estimation”.  Automated parametric estimation tends to be more accurate than manual estimates above 250 function points in size.  Manual estimates grow progressively optimistic as size increases.

One important point: the outputs from modern parametric estimation tools are often more accurate than “historical data.”  Historical data leaks and is woefully incomplete; omitting unpaid overtime and the work of management and many specialists.

  1. Estimating Software Costs, Capers Jones
  2. Practical Software Project Estimation, Peter Hill
  3. Managing the Black Hole, Gary Gack
  4. Software Sizing, Estimation, and Risk Management, Dan Galorath
  5. Software Engineering Economics, Barry Boehm
  6. Software Estimation: Demystifying the Black Art; Steve McConnell
  7. Estimating Software Intensive Systems, Richard D. Stutzke
  8. Software Project Cost and Schedule Estimating, W. Roetzheim and R. Beasley
  9. Cost Estimation with COCOMO II, Barry Boehm et al
  10. Software Estimation Best Practices, Murali Chemuturi
  11. Software Cost Estimation and Sizing Methods, Shari Lawrence Pfleeger
  12. Cost Estimation for Software Development, Bernard Londeix
  13. Agile Estimating and Planning, Mike Cohn
  14. IT Project Estimation, Paul Coombs
  15. Software Measurement and Estimation, Linda Laird and M. Carol Brennan
  16. Software Project Estimation by Analogy, Mohammad Azzeh
  17. Project Estimating and Cost Management, Parviz Read
  18. Cost Estimation in Software Product Line Engineering, Sebastian Rosensteiner
  19. An Approach to Software Cost Estimation, U.S. Government
  20. Cost Estimation Techniques for Web Projects, Emelia Mendez
  21. Software Metrics:  A Guide to Planning, Analysis, and Application, C.R. Pandian
  22. Practices for Scaling Lean and Agile Development, Craig Larman and Bas Vodde
  23. Modern Tools to Support DoD Software…., Jo Anne Lane and Barry Boehm
  24. How to Save a Failing Project, R. Young, S. Brady, D. Nagle
  25. Value Based Software Engineering, Biffi, Arum, Boehm, and Erdogmus
  26. Software Project Dynamics, T. Abdel-Hamid and Stuart Madnick
  27. Reuse Based Software Engineering, Hafedh Mili et al
  28. Essentials of Software Project Management, Richard Bechtold
  29. Systems Management for Information Technology and Software Engineering, A. Sage
  30. New Trends in Software Process Modeling, Silvia T. Acuna
  31. Software Management, Donald Reifer
  32. Project Management the Agile Way, John C. Goodpasture
  33. Risk Management Processes for Software Engineering Models, Marian Myerson
  34. Trustworthy Systems Through Quantitative Software Engineering, L. Bernstein and C.M. Yunhas

Books with Quantitative Data
The software industry is weak in reliable quantitative data.  These books and references contain more quantitative data than most.  Both quality and productivity are best measured using function points metrics.  For productivity work hours per function point and function points per month are effective.  For quality defects per function point not only work but allow the inclusion of requirements and design defects.  Older metrics such as “lines of code” and “cost per defect” violate standard economic principles and generate incorrect values much of the time.

  1. Boehm, Barry Dr.; Software Engineering Economics; Prentice Hall, Englewood Cliffs, NJ; 1981; 900 pages.
  2. Booch Grady, Object Solutions: Managing the Object-Oriented Project; Addison Wesley, Reading, MA; 1995.
  3. Multiple authors; Capability Maturity Model Integration; Version 1.1; Software Engineering Institute; Carnegie-Mellon Univ.; Pittsburgh, PA; March 2003.
  4. Brooks, Fred: The Mythical Man-Month, Addison-Wesley, Reading, Mass., 1974, rev. 1995.
  5. Charette, Bob; Software Engineering Risk Analysis and Management; McGraw Hill, New York, NY; 1989.
  6. Charette, Bob; Application Strategies for Risk Management; McGraw Hill, New York, NY; 1990.
  7. Cohn, Mike; Agile Estimating and Planning; Prentice Hall PTR, Englewood Cliffs, NJ; 2005; ISBN 0131479415.
  8. DeMarco, Tom; Controlling Software Projects; Yourdon Press, New York; 1982; ISBN 0-917072-32-4; 284 pages.
  9. Ewusi-Mensah, Kweku;  Software Development Failures; MIT Press, Cambridge, MA; 2003; ISBN 0-26205072-2276 pages.
  10. Gack, Gary; Managing the Black Hole – The Executives Guide to Project Risk; The Business Expert Publisher; Thomson, GA; 2010; ISBSG10: 1-935602-01-2.
  11. Galorath, Dan; Software Sizing, Estimating, and Risk Management:  When Performance is Measured Performance Improves;  Auerbach Publishing, Philadelphia; 2006; ISBN 10: 0849335930; 576 pages.
  12. Glass,  R.L.; Software Runaways:  Lessons Learned from Massive Software Project Failures;  Prentice Hall, Englewood Cliffs; 1998.
  13. Hill, Peter R.  Practical Software Project Estimation; McGraw Hill, 2010
  14. Harris, Michaael; Herron, David; and Iwanicki, Stacia; The Business Value of IT: Managing Risks, Optimizing Performance, and Measuring Results; CRC Press (Auerbach), Boca Raton, FL: ISBN 13: 978-1-4200-6474-2; 2008; 266 pages.
  15. Humphrey, Watts; Managing the Software Process; Addison Wesley, Reading, MA; 1989.
  16. Johnson, James et al; The Chaos Report; The Standish Group, West Yarmouth, MA; 2000.
  17. Jones, Capers and Bonsignour, Olivier; The Economics of Software Quality; Addison Wesley Longman, Boston, MA; ISBN 10: 0-13-258220—1; 2011; 585 pages.
  18. Jones, Capers; Software Engineering Best Practices; McGraw Hill, New York, NY; ISBN 978-0-07-162161-8; 2010; 660 pages.
  19. Jones, Capers; Estimating Software Costs; McGraw Hill, New York; 2007; ISBN 13-978-0-07-148300-1.
  20. Jones, Capers; Assessment and Control of Software Risks; Prentice Hall, 1994;  ISBN 0-13-741406-4; 711 pages.
  21. Jones, Capers; Patterns of Software System Failure and Success;  International Thomson Computer Press, Boston, MA;  December 1995; 250 pages; ISBN 1-850-32804-8; 292 pages.
  22. Jones, Capers; Software Assessments, Benchmarks, and Best Practices;  Addison Wesley Longman, Boston, MA; ISBN 0-201-48542-7; 2000; 657 pages.
  23. Jones, Capers; Program Quality and Programmer Productivity; IBM Technical Report TR 02.764, IBM San Jose, CA; January 1977.
  24. Jones, Capers; Programming Productivity; McGraw Hill, New York; ISBN 0-07-032811-0; 1986.
  25. Jones, Capers; “Estimating and Measuring Object-Oriented Software”; American Programmer; 1994.
  26. Jones, Capers; “Why Flawed Software Projects are not Cancelled in Time”; Cutter IT Journal; Vol. 10, No. 12; December 2003; pp. 12-17.
  27. Jones, Capers; “Software Project Management Practices:  Failure Versus Success”;
  28. Crosstalk, Vol. 19, No. 6; June 2006; pp4-8.
  29. Laird, Linda M and Brennan, Carol M; Software Measurement and Estimation: A Practical Approach; John Wiley & Sons, Hoboken, NJ; 2006; ISBN 0-471-67622-5; 255 pages.
  30. Park, Robert E. et al; Software Cost and Schedule Estimating – A Process Improvement Initiative; Technical Report CMU/SEI 94-SR-03; Software Engineering Institute, Pittsburgh, PA; May 1994.
  31. Park, Robert E. et al; Checklists and Criteria for Evaluating the Costs and Schedule Estimating Capabilities of Software Organizations; Technical Report CMU/SEI 95-SR-005; Software Engineering Institute, Pittsburgh, PA; January 1995.
  32. McConnell; Software Estimating: Demystifying the Black Art; Microsoft Press, Redmund, WA; 2006.
  33. Roetzheim, William H. and Beasley, Reyna A.; Best Practices in Software Cost and Schedule Estimation; Prentice Hall PTR, Saddle River, NJ; 1998.
  34. Strassmann, Paul; Information Productivity; Information Economics Press, Stamford, Ct; 1999.
  35. Strassmann, Paul; Information Payoff; Information Economics Press, Stamford, Ct; 1985.
  36. Strassmann, Paul; Governance of Information Management: The Concept of an Information Constitution; 2nd edition; (eBook); Information Economics Press, Stamford, Ct; 2004.
  37. Strassmann, Paul; The Squandered Computer; Information Economics Press, Stamford, CT; 1997.
  38. Stukes, Sherry, Deshoretz, Jason, Apgar, Henry and Macias, Ilona; Air Force Cost Analysis Agency Software Estimating Model Analysis ;  TR-9545/008-2; Contract F04701-95-D-0003, Task 008; Management Consulting & Research, Inc.; Thousand Oaks, CA 91362; September 30 1996.
  39. Symons, Charles R.: Software Sizing and Estimating—Mk II FPA (Function Point Analysis), John Wiley & Sons, Chichester, U.K., ISBN 0-471-92985-9, 1991.
  40. Wellman, Frank, Software Costing: An Objective Approach to Estimating and Controlling the Cost of Computer Software, Prentice Hall, Englewood Cliffs, NJ, ISBN 0-138184364, 1992.
  41. Whitehead, Richard; Leading a Development Team; Addison Wesley, Boston, MA; 2001; ISBN 10: 0201675267; 368 pages.
  42. Yourdon, Ed; Death March – The Complete Software Developer’s Guide to Surviving “Mission Impossible” Projects; Prentice Hall PTR, Upper Saddle River, NJ; ISBN 0-13-748310-4; 1997; 218 pages.
  43. Yourdon, Ed; Outsource:  Competing in the Global Productivity Race; Prentice Hall PTR, Upper Saddle River, NJ; ISBN 0-13-147571-1; 2005; 251 pages.

Books on Measurements and Metrics
The software industry has had endemic problems with very bad measurement practices.  Measuring productivity with “lines of code” and trying to measure quality with “cost per defect” are bad enough to be viewed as professional malpractice.  But both have been in continuous use for more than 50 years but always produce distorted and incorrect results.

Function point metrics are the best choice for economic analysis of software. They are also the best choice for quality analysis.  Function points support activity-based cost analysis as well as benchmarks.

Another endemic measurement problem, poorly covered in the literature, is “leakage” from software historical data.  The most common omissions from productivity data are

  1. Abran, Alain and Dumke, Reiner R; Innovations in Software Measurement; Shaker-Verlag, Aachen, DE; ISBN 3-8322-4405-0; 2005; 456 pages.
  2. Abran, Alain; Bundschuh, Manfred; Dumke, Reiner; Ebert; Christof; and Zuse, Horst; Software Measurement News; Vol. 13, No. 2, Oct. 2008 (periodical).
  3. Bundschuh, Manfred and Dekkers, Carol; The IT Measurement Compendium; Springer-Verlag, Berlin, DE; ISBN 978-3-540-68187-8; 2008; 642 pages.
  4. Chidamber, S.R. & Kemerer, C.F.; “A Metrics Suite for Object-Oriented Design”; IEEE Trans. On Software Engineering; Vol. SE20, No. 6; June 1994; pp. 476-493.
  5. Dumke, Reiner; Braungarten, Rene; Büren, Günter; Abran, Alain; Cuadrado-Gallego, Juan J; (editors); Software Process and Product Measurement; Springer-Verlag, Berlin; ISBN 10: 3-540-89402-0; 2008; 361 pages.
  6. Ebert, Christof and Dumke, Reiner; Software Measurement: Establish, Extract, Evaluate, Execute; Springer-Verlag, Berlin, DE; ISBN 978-3-540-71648-8; 2007; 561 pages.
  7. Garmus, David & Herron, David; Measuring the Software Process:  A Practical Guide to Functional Measurement;  Prentice Hall, Englewood Cliffs, NJ; 1995.
  8. Garmus, David and Herron, David; Function Point Analysis – Measurement Practices for Successful Software Projects; Addison Wesley Longman, Boston, MA; 2001; ISBN 0-201-69944-3;363 pages.
  9. IFPUG Counting Practices Manual, Release 4, International Function Point Users Group, Westerville, OH; April 1995; 83 pages.
  10. International Function Point Users Group (IFPUG); IT Measurement – Practical Advice from the Experts; Addison Wesley Longman, Boston, MA; 2002; ISBN 0-201-74158-X; 759 pages.
  11. Jones, Capers; Applied Software Measurement; McGraw Hill, 3rd edition, 2008; ISBN 978-0-07-150244-3; 662 pages.
  12. Jones, Capers: “Sizing Up Software;” Scientific American Magazine, Volume 279, No. 6, December 1998; pages 104-111.
  13. Jones; Capers; “A Short History of the Lines of Code Metric”; Version 4.0; May 2008; Capers Jones & Associates LLC; Narragansett, RI; 15 pages (monograph).
  14. Kemerer, C.F.; “Reliability of Function Point Measurement – A Field Experiment”; Communications of the ACM; Vol. 36; pp 85-97; 1993.
  15. Parthasarathy, M.A.; Practical Software Estimation – Function Point Metrics for Insourced and Outsourced Projects; Infosys Press, Addison Wesley, Upper Saddle River, NJ; 2007; ISBN 0-321-43910-4.
  16. Putnam, Lawrence H.; Measures for Excellence — Reliable Software On Time, Within Budget; Yourdon Press – Prentice Hall, Englewood Cliffs, NJ; ISBN 0-13-567694-0; 1992; 336 pages.
  17. Putnam, Lawrence H and Myers, Ware.;  Industrial Strength Software – Effective Management Using Measurement; IEEE Press, Los Alamitos, CA; ISBN 0-8186-7532-2; 1997; 320 pages.
  18. Stein, Timothy R; The Computer System Risk Management Book and Validation Life Cycle; Paton Press, Chico, CA; 2006; ISBN 10: 1-9328-09-5; 576 pages.
  19. Stutzke, Richard D; Estimating Software-Intensive Systems; Addison Wesley, Upper Saddle River, NJ; 2005; ISBN 0-201-70312-2; 918 pages.

Books on Architecture, Requirements, and Design
The set of books on architecture, requirements, and design is one of the more mature topics, having originated as long ago as the 1950’s.  When considering these topics, books on requirements are plentiful and often quite good.  Books on design are less common, but also quite good.  Books on architecture are sparse and while some are good, this field is still maturing.  Software engineering architecture lacks a formal taxonomy of software project types and classes and with the exception of patterns is sparse on reuse.

All books in this section share a common failing.  Software is highly dynamic; all of the books use static diagrams and text.  It is technically possible to build an animated, 3D, requirements prototype tool that can simulate software applications when they are operating.

It is also technically possible to build a dynamic project planning tool that can simulate the continuous growth of features over time and also show a gradual increase in cyclomatic complexity or entropy as applications age.

Software has done much more to support virtual reality for the film and game industries, and for aeronautical and automotive engineering, than for itself.   In 2014 software tends to use only static and fairly primitive diagramming techniques instead of using the richness of animation, full color, and 3D representations.

  1. Ambler, S.; Process Patterns – Building Large-Scale Systems Using Object Technology; Cambridge University Press; SIGS Books; 1998.
  2. Artow, J. & Neustadt, I.; UML and the Unified Process; Addison Wesley, Boston, MA; 2000.
  3. Bass, Len, Clements, Paul, and Kazman, Rick; Software Architecture in Practice; Addison Wesley, Boston, MA; 1997; ISBN 13: 978-0201199307; 452 pages.
  4. Berger, Arnold S.; Embedded Systems Design: An Introduction to Processes, Tools, and Techniques; CMP Books; 2001; ISBN 10-1578200733.
  5. Booch, Grady; Jacobsen, Ivar, and Rumbaugh, James; The Unified Modeling Language User Guide; Addison Wesley, Boston, MA; 2nd edition 2005.
  6. Cohn, Mike; User Stories Applied: For Agile Software Development; Addison Wesley, Boston, Ma; 2004; ISBN 0-321-20568.
  7. Fernandini, Patricial L; A Requirements Pattern; Succeeding in the Internet Economy; Addison Wesley, Boston, MA;  2002; ISBN 0-201-7386-0; 506 pages.
  8. Gamma, Erich; Helm, Richard; Johnson, Ralph; Vlissides, John; Design Patterns: Elements of Reusable Object Oriented Design; Addison Wesley, Boston MA; 1995.
  9. Inmon William H, Zachman, John, and Geiger, Jonathan G; Data Stores, Data Warehousing, and the Zachman Framework; McGraw Hill, New York; 1997; ISBN 10: 0070314292; 358 pages.
  10. Marks, Eric and Bell, Michael; Service-Oriented Architecture (SOA): A Planning and Implementation Guide for Business and Technology; John Wiley & Sons, New York; 2006; ISBN 10: 0471768944; 384 pages.
  11. Orr, Ken; Structured Requirements Definition; Ken Orr and Associates, Inc, Topeka, KS; 1981; ISBN 0-9605884-0-X; 235 pages.
  12. Robertson, Suzanne and Robertson, James; Mastering the Requirements Process; 3rd edition; 2013; Addison Wesley, Boston, MA; ISBN 10-321-81574-2; 539 pages.
  13. Martin, James & McClure, Carma;  Diagramming Techniques for Analysts and Programmers; Prentice Hall, Englewood Cliffs, NJ; 1985; ISBN 0-13-208794-4; 396 pages.
  14. Warnier, Jean-Dominique; Logical Construction of Systems; Van Nostrand Reinhold, London, UK; ISBN 0-4442-22556-3; 177 pages.
  15. Wiegers, Karl E; Software Requirements; 3rd edition; 2013; Microsoft Press, Bellevue, WA; ISBN 978-0-7356-5; 637 pages.

Books on Software Risk Control
Software risks have been endemic since the industry began.  They grew worse when applications increased in size past 10,000 function points.  They grew much worse when the web opened up software to hackers, viruses, worms, denial of service, identity theft, and other forms of malware.  Risks today seem to be getting worse faster than risk solutions can contain them.

Risks also include a smorgasbord of various kinds of litigation including but not limited to patent violations by patent trolls; legitimate patent litigation; breach of contract litigation for outsource contracts; and less common forms of litigation such as violations of non-compete agreements, violations of non-disclosure agreements; and violations Sarbanes-Oxley regulations.  In some cases if software causes death or injury, there may also be criminal charges.

  1. Anderson, David and Reinertson, Donald; Kanban:  Successful Evolutionary Change for your Technology; Blue Hole Press, 2010.
  2. Boehm, Barry; Software Risk Management; IEEE Computer Society Press; 1989.
  3. Charette, Bob; Software Engineering Risk Analysis and Management; McGraw Hill, New York, NY; 1989.
  4. Charette, Bob; Application Strategies for Risk Management; McGraw Hill, New York, NY; 1990.
  5. Constantine, Larry L; Beyond Chaos:  The Expert Edge in Managing Software Development;    ACM Press, 2001.
  6. DeMarco, Tom and Lister, Tim; Waltzing with Bears:  Managing Risks on Software Projects; Dorset House Press, NY; 2003.
  7. Denne, Mark and Cleland-Hung, Jane; Software by Numbers:  Low-Risk, High-Return Development; Prentice Hall, 2003.
  8. Duvall, Paul M. et al; Continuous Integration:  Improving Software Quality and Reducing Risks; Addison Wesley, 2007.
  9. Ewusi-Mensah, Kweku; Software Development Failures; The MIT Press, Cambridge, MA; 2003 Jindal.
  10. Fairbanks, George H; Just Enough Software Architecture:  A Risk-Driven Approach;  Marshall and Brainard, 2010.
  11. Glass, Robert; Software Runaways:  Monumental Software Disasters; Prentice Hall, 1997.
  12. Hall, Elaine; Managing Risks: Methods for Software Systems Development; Addison Wesley, 1998.
  13. Jones, Capers; Assessment and Control of Software Risks; Prentice Hall, Englewood Cliffs, 1993.
  14. Jones, Capers; Patterns of Software Development Failure and Success; International Thomson Computer Press; 1995.
  15. Karolak, Dale Walter; Software Engineering Risk Management; Wiley IEEE Computer Society; 1995.
  16. McConnell, Steve; Software Project Survival Guide; Microsoft Press; 1997.
  17. Ould, Martin; Managing Software Quality and Business Risk; Wiley, 1999.
  18. Pandian, Ravindranath; Applied Software Risk Management:  A Guide for Software Risk Managers; Auerbach Publications, 2006.
  19. Stepanek, George; Software Project Secrets:  Why Software Projects Fail;  Apress, 2012.
  20. Stein, Timothy; The Computer System Risk Management and Validation Cycle; Paton Press, Chico, CA; 2006.
  21. Trendowicz, Adam;  Software Cost Estimating, Benchmarking, and Risk Assessment; Springer, 2013.
  22. Weinberg, Gerald; Why Software Gets in Trouble; Amazon e-books; 2011.
  23. Yourdon, Ed; Death March: The Complete Software Developer’s Guide to Surviving “Mission Impossible” Projects; Prentice Hall, 1997.
  24. Zeidman, Bob; The Software IP Detective’s Handbook; Prentice Hall, Upper Saddle River NJ; 2011.
  25. Zoelick, Bill; CyberRegs:  A Business Guide to Web, Property, Privacy, and Patents; Addison Wesley, 2001.

Books on Software Quality Control
Software quality control is a chronic problem for software engineering.  For many years software projects focused exclusively on testing and ignored alternate quality methods such as inspections and static analysis.  In reality a synergistic combination of defect prevention, pre-test defect removal, and formal testing are needed to achieve defect removal efficiency levels in the 99% range.  Testing alone seldom tops 85% and many forms of testing are only about 35% efficient in finding bugs.

Quality measurements are also poor.  Many companies do not start measuring quality until testing and hence ignore requirements and design defects.  Most companies ignore defects found privately via desk checking and unit test.  There are many other topics that need additional coverage such as the effectiveness of static analysis, additional data on inspections, and solid data on “pair programming” results where the bulk of the literature compares only one programming against two programmers and ignores other topics such as inspections, static analysis, cyclomatic complexity, and others that have a known impact on defects.

Note:  This section includes one classic fiction book often used as a training manual for quality by major corporations:  Robert Pirsig’s classic Zen and the Art of Motorcycle Maintenance.

  1. Beck, Kent; Test-Driven Development; Addison Wesley, Boston, MA; 2002; ISBN 10: 0321146530; 240 pages.
  2. Chelf, Ben and Jetley, Raoul; “Diagnosing Medical Device Software Defects Using Static Analysis”; Coverity Technical Report, San Francisco, CA; 2008.
  3. Chess, Brian and West, Jacob; Secure Programming with Static Analysis; Addison Wesley, Boston, MA; 20007; ISBN 13: 978-0321424778; 624 pages.
  4. Cohen, Lou; Quality Function Deployment – How to Make QFD Work for You; Prentice Hall, Upper Saddle River, NJ; 1995; ISBN 10: 0201633302; 368 pages.
  5. Crosby, Philip B.; Quality is Free; New American Library, Mentor Books, New York, NY; 1979; 270 pages.
  6. Everett, Gerald D. And McLeod, Raymond; Software Testing; John Wiley & Sons, Hoboken, NJ; 2007; ISBN 978-0-471-79371-7; 261 pages.
  7. Firesmith, Donald G.; Common System and Software Testing Pitfalls; Addison Wesley; 2014; ISBN -10-0-13=374855-3; 294 pages.
  8. Gack, Gary; Applying Six Sigma to Software Implementation Projects; http://software.isixsigma.com/library/content/c040915b.asp.
  9. Gilb, Tom and Graham, Dorothy; Software Inspections; Addison Wesley, Reading, MA;  1993; ISBN 10: 0201631814.
  10. Hallowell, David L.; Six Sigma Software Metrics, Part 1.; http://software.isixsigma.com/library/content/03910a.asp.
  11. International Organization for Standards; ISO 9000 / ISO 14000; http://www.iso.org/iso/en/iso9000-14000/index.html.
  12. Jones, Capers and Bonsignour, Olivier; The Economics of Software Quality; Addison Wesley Longman, 2012; ISBN-10 0-13-258220-1; 587 pages..
  13. Jones, Capers;  Software Quality – Analysis and Guidelines for Success; International Thomson Computer Press, Boston, MA; ISBN 1-85032-876-6; 1997; 492 pages.
  14. Kan, Stephen H.; Metrics and Models in Software Quality Engineering, 2nd edition;  Addison Wesley Longman, Boston, MA; ISBN 0-201-72915-6; 2003; 528 pages.
  15. Land, Susan K; Smith, Douglas B; Walz, John Z; Practical Support for Lean Six Sigma Software Process Definition: Using IEEE Software Engineering Standards; WileyBlackwell; 2008; ISBN 10: 0470170808; 312 pages.
  16. Mosley, Daniel J.; The Handbook of MIS Application Software Testing; Yourdon Press, Prentice Hall; Englewood Cliffs, NJ; 1993; ISBN 0-13-907007-9; 354 pages.
  17. Myers, Glenford; The Art of Software Testing; John Wiley & Sons, New York; 1979; ISBN 0-471-04328-1; 177 pages.
  18. Nandyal; Raghav; Making Sense of Software Quality Assurance; Tata McGraw Hill Publishing, New Delhi, India; 2007; ISBN 0-07-063378-9; 350 pages.
  19. Pirsig, Robert M.; Zen and the Art of Motorcycle Maintenance; Harper Torch; originally 1974 but republished dozens of times.  This book is widely used as a training manual for software quality because it shows the ethics and value of quality in an unusual context.
  20. Radice, Ronald A.; High Qualitiy Low Cost Software Inspections;  Paradoxicon Publishingl Andover, MA; ISBN 0-9645913-1-6; 2002; 479 pages.
  21. Wiegers, Karl E.; Peer Reviews in Software – A Practical Guide;  Addison Wesley Longman, Boston, MA; ISBN 0-201-73485-0; 2002; 232 pages.

Books on Software Security, Hacking, and Malware Prevention
The books in this section are increasing in importance and relevance on a daily basis.  Never in human history has so much valuable information been stored in a fashion that allows theft from thousands of miles away.  Cyber security, cyber war fare, and cyber defenses are main stream topics in 2014 and will stay that way probably forever.

Note:  although not a book the Congressional Cyber Caucus founded by Representatives Jim Langevin from Rhode Island and Mike McCaul from Texas provides an excellent weekly summary of both corporate and government cyber security issues.  The URL is:  cybercaucus.langevin.house.gov.  This is one of the best sources of current data on cyber security issues.

  1. Acohido, Byron and Swartz, John: Zero Day Threat: The Shocking Truth of How Banks and Credit Bureaus Help Cyber Crooks Steal Your Money and Identity; Union Square Press; ISBN 10: 140275695X; 2008; 304 pages.
  2. Allen, Julia; Barnum, Sean; Ellison, Robert; McGraw, Gary; and Mead, Nancy; Software Security: A Guide for Project Managers (An SEI book sponsored by the Department of Homeland Security); Addison Wesley Professional, Boston, MA; ISBN 032150917X; 2008.
  3. Anley, Chris, Heasman, John, Lindner, Felix, and Richarte, Gerardo; The Shellcoders Handbook: Discovering and Exploiting Security Holes; Wiley, New York; ISBN 10: 047008023X; 2007; 718 pages.
  4. Chess, Brian; Secure Programming with Static Analysis; Addison Wesley Professional, Boston, MA; ISBN 10: 0321424778; 2007; 624 pages.
  5. Dowd, Mark, McDonald, John, and Schuh, Justin; The Art of Software Security Assessment: Identifying and Preventing Software Vulnerabilities; Addison Wesley Professional, Boston, Ma; ISBN 10: 0321444426; 2006; 1200 pages.
  6. Ericson, John; Hacking: The Art of Exploitation; 2nd edition; No Starch Press; ISBN 10: 1593271441; 2008; 488 pages.
  7. Gallager, Tom; Landauer, Lawrence; and Jeffries, Brian;  Hunting Security Bugs; Microsoft Press, Redmond WA; ISBN 10: 0735621879; 2006; 592 pages.
  8. Hamer-Hodges, Ken; Authorization Oriented Architecture – Open Application Networking and Security in the 21st Century; Auerbach Publications, Philadelphia, PA; to be published in December 2009; ISBN 10: 1439800545; pages nnn. (To be published in 2009)
  9. Hogland, Greg and McGraw, Gary; Exploiting Software: How to Break Code; Addison Wesley Professional, Boston, MA; ISBN 10: 0201786598; 2004; 512 pages.
  10. Hogland, Greg and Butler, Jamie; Rootkits: Exploiting the Windows Kernal; Addison Wesley Professional, Boston, MA; ISBN 10: 0321291349; 2005; 352 pages.
  11. Howard, Michael and Lippner, Steve; The Security Development Lifecycle; Microsoft Press, Redmond, WA; ISBN 10:  0735622140; 2006; 352 pages.
  12. Howard, Michael and LeBlanc, David; Writing Secure Code; Microsoft Press, Redmond, WA; ISBN 10:  0735617228; 2003; 798 pages.
  13. Jones, Andy and Ashenden, Debi; Risk Management for Computer Security:  Protecting Your Network and Information Assets; Butterworth-Heinemann; ISBN 10: 0750677953; 2005; 296 pages.
  14. Landoll, Douglas J.; The Security Risk Assessment Handbook: A Complete Guide for Performing Security Risk Assessments; CRC; ISBN 10: 0849339981; 2005; 504 pages.
  15. Mather, Tim; Cloud Security and Privacy:  An Enterprise Perspective on Risks and Compliance; O’Reilly Media; 2009.
  16. McGraw, Gary; Software Security – Building Security In; Addison Wesley Professional, Boston, MA; ISBN 10-0321356705; 2006; 448 pages.
  17. Rice, David: Geekonomics: The Real Cost of Insecure Software; Addison Wesley Professional, Boston, MA; ISBN 10:  0321477898; 2007; 384 pages.
  18. Scambray, Joel: Hacking Exposed Windows: Microsoft Windows Security Secrets and Solutions; 3rd edition; McGraw Hill Osborne, New York, NY; ISBN 10: 007149426X; 2007; 451 pages.
  19. Scambray, Joel: Hacking Exposed Web Applications; 2nd edition; McGraw Hill Osborne, New York, NY; ISBN 10: 0072262990; 2006; 520 pages.
  20. Sherwood, John; Clark, Andrew; and Lynas, David;  Enterprise Security Architecture:  A Business-Driven Approach; CMP; ISBN 10: 157820318X; 2005; 608 pages.
  21. Skudis, Edward and Liston, Tom; Counter Hack Reloaded: A Step-by-Step Guide to Computer Attacks and Effective Defenses; Prentice Hall PTR, Englewood Cliffs, NJ; ISBN 10: 0131481045; 2006; 784 pages.
  22. Skudis, Edward and Zeltzer, Lenny; Malware: Fighting Malicious Code; Prentice Hall PTR, Englewood Cliffs, NJ; ISBN 10: 0131014056; 2003; 676 pages.
  23. Shostack, Adam and Stewart, Andrews; The New School of Information Security; Addison Wesley Professional, Boston, MA; ISBN 10: 0321502787; 2008; 288 pages.
  24. Stuttard, Dafydd and Pinto, Marcus; The Web Application Hackers Handbook: Discovering and Exploiting Security Flaws; Wiley, New York; ISBN 10: 0470170778; 2007; 768 pages.
  25. Szor, Peter; The Art of Computer Virus Research and Defense; Addison Wesley Professional, Boston, Ma; ISBN 10: 0321304543; 2005; 744 pages.
  26. Thompson, Herbert and Chase, Scott: The Software Vulnerability Guide; Charles River Media, Boston, MA; ISBN 10: 1584503580; 2005; 354 pages.
  27. Viega, John and McGraw, Gary; Building Secure Software: How to Avoid Security Problems the Right Way; Addison Wesley Professional, Boston, MA; ISBN 10: 020172152X; 2001; 528 pages.
  28. Whittaker, James A. and Thompson, Herbert H.; How to Break Software Security; Addison Wesley, Boston, MA; ISBN 10: 0321194330; 2003; 208 pages.
  29. Wysopal, Chris; Nelson, Lucas; Zovi, Dino Dai; and Dustin, Elfriede; The Art of Software Security Testing: Identiyfing Software Security Flaws; Addison Wesley Professional, Boston, MA; ISBN 10: 0321304861; 2006; 321 pages.

Books on Software Engineering and Programming
This section of citations includes some of the “classic” books on software engineering and a number of interesting new topics as well.

An underlying problem with all of these books is that custom designs and hand coding are intrinsically inefficient and expensive.  Only construction of applications from libraries of standards reusable components is going to elevate software from a craft to a true engineering field.

  1. Barr, Michael and Massa, Anthony; Programming Embedded Systems: With C and GNU Development Tools; O’Reilly Media; 2006; ISBN 10-0596009836.
  2. Beck, K; Extreme Programming Explained: Embrace Change; Addison Wesley, Boston, MA; 1999.
  3. Bott, Frank; Coleman, A; Eaton, J.; Roland, D; Professional Issues in Software Engineering; Taylor & Francis, 2000; ISBN 10: 0748409513; 384 pages.
  4. Glass, Robert L; Facts and Fallacies of Software Engineering (Agile Software Development); Addison Wesley, Boston, MA; 2002; ISBN 10: 0321117425; 224 pages.
  5. Hans, Professor van Vliet; Software Engineering Principles and Practices; 3rd edition; John Wiley & Sons, London, New York; 2008; ISBN 10: 0470031468; 740 pages.
  6. Hunt, Andrew and Thomas, David: The Pragmatic Programmer; Addison Wesley, Boston, MA; 1999; ISBN 10: 020161622X; 352 pages.
  7. Jacobson, Ivar; Pan-Wei Ng, McMahon, Paul; Spence, Ian; and Lidman, Svante; The Essence of Software Engineering; Applying the SEMAT Kernel;  Addison Wesley, 2013.
  8. Jeffries, R. et al; Extreme Programming Installed; Addison Wesley, Boston; 2001.
  9. Love, Dr. Tom; Object Lessons; Lessons Learned in Object-Oriented Development Projects; SIGS books; 1993; ISBN 0-9627477-3-4; 266 pages.
  10. Marciniak, John J. (Editor); Encyclopedia of Software Engineering;  John Wiley & Sons, New York; 1994; ISBN 0-471-54002; in two volumes.
  11. McConnell, Code Complete; Microsoft Press, Redmond, WA; 1993; ISBN 13-978-1556154843; 886 pages.
  12. Morrison, J. Paul; Flow-Based Programming; A New Approach to Application Development; Van Nostrand Reinhold, New York; 1994; ISBN 0-442-01771-5; 316 pages.
  13. Pressman, Roger; Software Engineering – A Practitioner’s Approach; McGraw Hill, NY; 6th edition, 2005; ISBN 0-07-285318-2.
  14. Sommerville, Ian; Software Engineering; 7th edition; Addison Wesley, Boston, MA; 2004; ISBN 10: 0321210263; 784 pages.
  15. Stephens M. & Rosenberg, D.; Extreme Programming Refactored; The Case Against XP; APress L.P., Berkeley, CA; 2003.

Books on Software Development Methods
Today in 2014 there are more than 35 named software development methods in use throughout the world, and more are likely to appear.  Among the more common development methods in alphabetical order are agile, cowboy, crystal, EVO, extreme programming, iterative, Merise, Prince2, RUP, spiral, waterfall, TSP, and dozens more.

Selecting a software development methodology resembles joining a cult more than it does making a logical decision.  Most companies merely jump onto the current bandwagon, which today in 2014 is agile.  Fortunately agile is a fairly robust method for small projects, but suboptimal for large systems.

There is nothing like the Index Medicus for software engineering.  What would be valuable would be solid empirical results by a university or non-profit that compared the quality and productivity results of a variety of methods including agile, cowboy, Crystal, EVO, extreme programming (XP), Information Engineering (IE), iterative, Merise, pair programming, Prince 2, spiral, waterfall, and many others.

Unfortunately the software industry does not validate methodologies before deploying them.  Popularity rules and therefore methods come and go.  The same is true with programming languages, of which there are now more than 2,500 none of which have been validated as being effective for specific types of applications.

Software engineering needs much better proofs of efficacy for almost everything in actual use:  languages, methods, tools, and metrics.  The two most common metrics “lines of code” and “cost per defect” are both bad enough to be professional malpractice.  Some methods such as pair programming are expensive and inefficient.   A typical application uses about 2.5 different programming  languages and some use more than 12.  Why?   The answer is that “software engineering” is still a craft and lacks the essential concept of using due diligence and proofs before deploying something new.

  1. Boehm, Barry; “A Spiral Model of Software Development and Enhancement”; Proceedings of the Int. Workshop on Software Process and Software Environments; ACM Software Engineering Notes, Aug. 1986, pp. 22-42.
  2. Cockburn, Alistair; Agile Software Development; Addison Wesley, Boston, MA; 2001.
  3. Cohen, D. Lindvall M. & Costa, P. “An Introduction to agile methods”; Advances in Computers, pp. 1-66; 2004; Elsevier Science, New York.
  4. Highsmith, Jim; Agile Software Development Ecosystems; Addison Wesley, Boston, MA; 2002.
  5. Humphrey, Watts; TSP – Leading a Development Team; Addison Wesley, Boston, MA; 2006.
  6. Humphrey, Watts; PSP: A Self-Improvement Process for Software Engineers; Addison Wesley, Upper Saddle River, NJ; 2005; ISBN 0-321-30549-3; 346 pages.
  7. Krutchen, Phillippe; The Rational Unified Process – An Introduction; Addison Wesley, Boston, MA;; 2003; ISBN 10: 0321197704; 336 pages.
  8. Larman, Craig & Basili, Victor; “Iterative and Incremental Development – A Brief History”; IEEE Computer Society; June 2003; pp 47-55.
  9. Love, Tom; Object Lessons; SIGS Books, New York; 1993.
  10. Martin, Robert; Agile Software Development: Principles, Patterns, and Practices; Prentice Hall, Upper Saddle River, NJ; 2002; ISBN 10: 0135974445; 529 pages.
  11. Mills, H.; Dyer, M. & Linger, R.; “Cleanroom Software Engineering”; IEEE Software; 4, 5 (Sept. 1987); pp. 19-25.
  12. Paulk Mark et al;  The Capability Maturity Model; Guidelines for Improving the Software Process; Addison Wesley, Reading, MA; ISBN 0-201-54664-7; 1995; 439 pages.
  13. Rapid Application Development; http://en.wikipedia.org/wiki/Rapid_application_development
  14. Stapleton, J.; DSDM – Dynamic System Development Method in Practice; Addison Wesley; Boston, MA; 1997.

Books Software Deployment, Customer Support, and Maintenance
Maintenance, enhancement, and “brownfield” development or mixing new applications into a stew of aging legacy software is severely underrepresented in the software literature.  Although in 2014 maintenance programmers are more numerous than development programmers, books on development outnumber books on maintenance by about 20 to 1.

  1. Arnold, Robert S.; Software Reengineering; IEEE Computer Society Press, Los Alamitos, CA; 1993; ISBN 0-8186-3272-0; 600 pages.
  2. Arthur, Lowell Jay; Software Evolution – The Software Maintenance Challenge; John Wiley & Sons, New York; 1988; ISBN 0-471-62871-9; 254 pages.
  3. Gallagher, R.S.; Effective Customer Support; International Thomson Computer Press, Boston, MA; 1997; ISBN 1-85032-209-0; 480 pages.
  4. Parikh, Girish; Handbook of Software Maintenance; John Wiley & Sons, New York; 1986; ISBN 0-471-82813-0; 421 pages.
  5. Pigoski, Thomas M.; Practical Software Maintenance – Best Practices for Managing Your Software Investment; IEEE Computer Society Press, Los Alamitos, CA; 1997; ISBN 0-471-17001-1; 400 pages.
  6. Sharon, David; Managing Systems in Transition – A Pragmatic View of Reengineering Methods; International Thomson Computer Press, Boston, MA; 1996; ISBN 1-85032-194-9; 300 pages.
  7. Takang, Armstrong and Grubh, Penny; Software Maintenance Concepts and Practice; International Thomson Computer Press, Boston, MA; 1997; ISBN 1-85032-192-2; 256 pages.
  8. Ulrich, William M.; Legacy Systems: Transformation Strategies; Prentice Hall, Upper Saddle River, NJ; 2002; ISBN 10: 013044927X; 448 pages.

Books on Social Issues in Software Engineering
So long as software is a team activity involving as many as several hundred workers and more than 125 occupation groups, social topics are extremely important.  That being said, social topics are also underreported in the literature.   Worse, some of the literature is weak such as the curious reports on “pair programming” which fail to compare pairs against other methods such as inspections and static analysis.

One important non-software book is included in this section.  Paul Starr’s Pulitzer-Prize winning book on The Social Transformation of American Medicine.  This is a great book that shows a path followed by medical practice that might also be followed by software engineering.  There was a time when medicine was more chaotic and unstructured even than software.  Starr’s book shows how the AMA improved medical education, reduced medical quackery, and gradually introduced board certifications and licensing.  Over a period of about 100 years medicine evolved from a low-status craft to the top rung of professional status.  We could use many of the same approaches to improve software.

  1. Brooks, Fred; The Mythical Manmonth; 2nd edition; Addison Wesley, Boston, MA; 1995; ISBN 10: 0201835959; 336 pages.
  2. Campbell-Kelly, Martin; A History of the Software Industry:  from Airline Reservations to Sonic the Hedgehog; The MIT Press, Cambridge, MA; 2003; ISBN 0-262-03303-8; 372 pages.
  3. DeMarco, Tom; Peopleware: Productive Projects and Teams; Dorset House, New York, NY; 1999; ISBN 10: 0932633439; 245 pages.
  4. Glass, Robert L; Software Creativity; 2nd edition; developer.*books, Atlanta, GA; 2006; ISBN 978-0-9772133-1-3; 456 pages.
  5. Humphrey, Watts; Winning with Software: An Executive Strategy; Addison Wesley, Boston, MA; 2002; ISBN 0-201-77639-1; 228 pages.
  6. Johnson, James et al; The Chaos Report; The Standish Group, West Yarmouth, MA; 2007.
  7. Jones, Capers; The Technical and Social History of Software Engineering; Addison Wesley, 2014; ISBN 10-0-321-90342-0; 451 pages.
  8. Jones, Capers; “How Software Personnel Learn New Skills”, 6th edition; July 2008; Capers Jones & Associates LLC; Narragansett, RI.; 25 pages (monograph).
  9. Jones, Capers; Conflict and Litigation Between Software Clients and Developers; Software Productivity Research, Inc.; Narragansett, RI; 2008; 45 pages (monograph).
  10. Jones, Capers; “Preventing Software Failure: Problems Noted in Breach of Contract Litigation”; Capers Jones & Associates, Narragansett, RI; 2008; 25 pages.
  11. Kuhn, Thomas; The Structure of Scientific Revolutions; University of Chicago Press, Chicago, IL; 1996; ISBN 0-22645807-5; 212 pages.
  12. Krasner, Herb; “Accumulating the Body of Evidence for the Payoff of Software Process Improvement – 1997;” Krasner Consulting, Austin, TX.
  13. Starr, Paul; The Social Transformation of American Medicine; Basic Books; Perseus Group; 1982; ISBN 0-465-07834-2.  NOTE:  This book won a Pulitzer Prize in 1982 and is highly recommended as a guide for improving both professional education and professional status.  There is much of value for the software community.
  14. Weinberg, Gerald M.; The Psychology of Computer Programming; Van Nostrand Reinhold, New York; 1971; ISBN 0-442-29264-3; 288 pages.
  15. Weinberg, Gerald M; Becoming a Technical Leader; Dorset House; New York; 1986; ISBN 0-932633-02-1; 284 pages.
  16. Yourdon, Ed; The Decline and Fall of the American Programmer; Prentice Hall, 1993.
  17. Yourdon, Ed; The Rise and Resurrection of the American Programmer; Prentice Hall, Prentice Hall, 1996.
  18. Yourdon, Ed; Outsource:  Competing in the Global Productivity Race; Prentice Hall, 2004.
  19. Yourdon, Ed; CIOs at Work; Apress, 2011.
  20. Yourdon, Ed; Death March – The Complete Software Developer’s Guide to Surviving “Mission Impossible” Projects; Prentice Hall PTR, Upper Saddle River, NJ; ISBN 0-13-748310-4; 1997; 218 pages.
  21. Zoellick; Bill; CyberRegs – A Business Guide to Web Property, Privacy, and Patents; Addison Wesley, Boston, MA; 2002; ISBN 0-201-72230-5; 307 pages.

Books on Cloud Software Development
This section is the shortest in this bibliography since cloud computing is the most recent topic of those discussed.  However cloud computing is clearly the way of the future so many new citations will occur in 2014 and beyond.  Already more than 100 books are out on cloud topics so this section only scratches the surface.

  1. Buya, Rajkumar; Vecchiola, Christian; Selvi, S. Thamari; Mastering Cloud Computing:  Foundations and Application Programming; Morgan Kaufman; 2013.
  2. Erl, Thomas; SOA Design Patterns; Prentice Hall, 2009.
  3. Linthicum, David; Cloud Computing and SOA Convergence in Your Enterprise:  A step-by-step guide; Addison Wesley, 2009.
  4. Mather, Tim; Cloud Security and Privacy:  An Enterprise Perspective on Risks and Compliance; O’Reilly Media; 2009.
  5. Mulholland, Andy; Pyke Jon; and Fingar, Peter; Enterprise Cloud Computing:  A Strategy for Business and Technology Leaders; Meghan-Kiffer Press; 2010.
  6. Reese, George; Cloud Application Architectures:  Building Applications and Infrastructure in the Cloud; O’Reilly Media; 2009.
  7. Sama, David Y; Implementing and Developing Cloud Computing Applications; Auerbach publications, 2010.
  8. Sitaram, Dinkar; Moving to the Cloud:  Developing Apps in the New World of Cloud Computing; Syngress, 2011.
  9. Buya, Rajkumar; Vecchiola, Christian; Selvi, S. Thamari; Mastering Cloud Computing:  Foundations and Application Programming; Morgan Kaufman; 2013.

WEB SITES
There are hundreds of software industry and professional associations.  Most have a narrow focus. Most are more or less isolated and have no contact with similar associations.  Exceptions to this rule include the various software process improvement network groups (SPIN) and the various software metrics associations.

This partial listing of software organizations and web sites is to facilitate communication and sharing of data across both organization and national boundaries.  Software is a global industry.  Problems occur from the first day of requirements to the last day of usage, and every day in between.  Therefore mutual cooperation across industry and technical boundaries would benefit software and help it toward becoming a true profession rather than a craft of marginal competence.

What might be useful for the software industry would be reciprocal memberships among the major professional associations along the lines of the American Medical Association.  There is a need for an umbrella organization that deals with all aspects of software as a profession, as does the AMA for medical practice.American Electronics Association (AEA):  www.aeanet.org

  1. (May merge with ITAA)
  2. American Society for Quality:  www.ASQ.org
  3. Anti-Phishing Working Group: www.antiphishing.org 
  4. Association of Computing Machinery:  www.ACM.org
  5. Association of Competitive Technologies (ACT):  www.actonline.org
  6. Association of Information Technology Professionals:  www.aitp.org
  7. Association for Software Testing: www.associationforsoftwaretesting.org
  8. Brazilian Function Point Users Group: www.BFPUG.org
  9. Business Application Software Developers Association:  www.basda.org
  10. Business Software Alliance (BSA):  www.bsa.org
  11. Center for Internet Security: www.cisecurity.org
  12. China Software Industry Association:  www.CSIA.org
  13. Chinese Software Professional Association:  www.CSPA.com
  14. Center for Hybrid and Embedded Software Systems (CHESS):  http//chess.eecs.berkley.edu
  15. Computing Technology Industry Association (CTIA):  www.comptia.org
  16. Embedded Software Association (ESA): www.esofta.com
  17. European Design and Automation Association (EDAA): www.edaa.com
  18. Finnish Software Measurement Association: www.fisma.fi
  19. IEEE Computer Society: www.computer.org
  20. Independent Computer Consultants Association (ICCA): www.icca.org
  21. Information Technology Association of America (ITAA): www.itaa.org
  22. (May merge with AEA)
  23. Information Technology Metrics and Productivity Institute (ITMPI): www.ITMPI.org
  24. InfraGuard: www.InfraGuard.net
  25. Institute of Electrical and Electronics Engineers (IEEE):  www.IEEE.org
  26. Institute for International Research (IIR): eee.irusa.com
  27. International Association of Software Architects:  www.IASAHOME.org
  28. International Software Benchmarking Standards Group (ISBSG): www.ISBSG.org
  29. International Function Point Users Group (IFPUG): www.IFPUG.org
  30. International Institute of  Business Analysis:  www.IIBAorg
  31. Japan Function Point Users Group:  www.jfpug.org
  32. Linux Professional Institute:  www.lpi.org
  33. National Association of Software and Service Companies (India): www.NASCOM.in
  34. Netherlands Software Metrics Association:  www.NESMA.org
  35. Process Fusion: www.process-fusion.com
  36. Programmers’ Guild: www.programmersguild.org
  37. Project Management Institute: www.PMI.org
  38. Russian Software Development Organization (RUSSOFT): www.russoft.org
  39. Society of Information Management (SIM): www.simnet.org
  40. Software and Information Industry Association: www.siia.net
  41. Software Engineering Body of Knowledge www.swebok.org
  42. Software Publishers Association (SPA):  www.spa.org
  43. Software Engineering Institute (SEI): www.sei.cmu.edu
  44. Software Productivity Research (SPR): www.SPR.com
  45. United Kingdom Software Metrics Association:  www.UKSMA.org
  46. U.S. Internet Industry Association (USIIA):  www.usiia.org
  47. Women in Technology International:  www.witi.com
  48. Software Standards Organizations

There are dozens of standards organizations and hundreds of specific standards.  No doubt many of both are valuable.  However, there is a serious shortage of empirical data that demonstrates whether specific standards, such as the famous ISO quality standards, are beneficial, neutral, or harmful.

It would seem to be a useful addition to the standards creation process to ensure efficacy.  At the very least software standards should follow the canon of medical practice; i.e. “first do no harm.”  There is at least anecdotal evidence that the famous ISO 9000 quality standard did not improve quality for software and possible made it worse.

 

International Quality Standards

1

 AIAA standards

2

 ANFIA standards

3

 ANSI standards

4

 ASME standards

5

 British standards

6

 CISQ standards

7

 EAI standards

8

 EIA standards

9

 EN standards

10

 FAA standards

11

 FDA standards

12

 IEC standards

13

 IEEE standards

14

 ISO standards

15

 ISO/IEC standards

16

 JUSA standards

17

 OMG standards

18

 SEMI standards

Software Certification Organizations
There are dozens of organizations that provide some form of certification either for specific tool sets or for some general skill such as counting function points.  No doubt many of these forms of certification are valuable and those who receive the certificates have added skill sets that they did not have before.

However there is a shortage of empirical data that demonstrates the effectiveness of certification in many areas.  For example, in a side-by-side comparison between certified test personnel and uncertified test personnel would the certified group achieve higher levels of test coverage or higher levels of defect removal efficiency?  There is no reliable answer to this question in 2014.

For example there is statistical evidence based on a study commissioned by the Air Force that the higher CMMI levels of 3, 4, and 5 have better quality than levels 1 and 2.  However, the same study showed that the best level 1 organizations had better quality than the worst level 3 organizations.  Even some CMMI level 5 organization occasionally had quality problems; especially those outside the United States.

Certification that imparts or evaluates specific skill sets such as counting function points or fixing Microsoft Windows seem to be effective compared to uncertified personnel.  However it is unknown in 2014 whether certified project managers or certified quality assurance personnel are better or worse than uncertified personnel in performing normal work-related tasks.

 

Professional Certification

1

 Certification – Apple

2

 Certification – Computer Associates

3

 Certification – FAA

4

 Certification – FDA

5

 Certification – Hewlett Packard

6

 Certification – IBM

7

 Certification – Microsoft

8

 Certification – Oracle

9

 Certification – PMI

10

 Certification – QAI

11

 Certification – Red Hat

12

 Certification – RSBC

13

 Certification – SAP

14

 Certification – Sarbanes-Oxley

15

 Certification – SEI

16

 Certification – Sun

17

 Certification – -Symantec

18

 Certification – TickIT

19

 Certification of computing professionals

20

 Certified configuration management specialist

21

 Certified function point analyst

22

 Certified project managers

23

 Certified requirements engineers

24

 Certified scrum master

25

 Certified secure software lifecycle professional

26

 Certified security engineer

27

 Certified SEI appraiser

28

 Certified software architect

29

 Certified software business analyst

30

 Certified software development professional

31

 Certified software engineers

32

 Certified software quality assurance

33

 Certified test managers

34

 Certified testers

35

 Certified webmaster

36

 Certified software auditor

Leave a Reply

Your email address will not be published. Required fields are marked *