References – Software Quality Assurance

References

  1. [ABR 15]   ABRAN A. Software Project Estimation: The Fundamentals for Providing High Quality Information to Decision Makers. Wiley-IEEE Computer Society Press, Los Alamitos, CA, 2015, 288 p.
  2. [ABR 93]   ABRAN A. and NGUYENKIM H. Measurement of the maintenance process from a demand-based perspective. Journal of Software Maintenance: Research and Practice, vol. 5, issue 2, 1993, pp. 63–90.
  3. [AGC 06]   Auditor General of Canada. Large IT projects. Office of the Auditor General, Ottawa, Canada, November 2006, Chapter 3. Available at: http://www.oag-bvg.gc.ca/internet/English/parl_oag_200611_03_e_ 14971.html
  4. [ALE 91]   ALEXANDER M. In: The Encyclopedia of Team-Development Activities, edited by J. William Pfeiffer. University Associates, San Diego, CA, 1991.
  5. [AMB 04]   AMBLER S. W. Examining the Big Requirements Up Front Approach. Ambysoft Inc. Available at: www.agilemodeling.com/essays/examiningBRUF.htm
  6. [ANA 04]   ANACLETO A., VON WANGENHEIM C. G., Salviano C. F., and SAVI R. Experiences gained from applying ISO/IEC 15504 to small software companies in Brazil. In: 4th International SPICE Conference on Process Assessment and Improvement, Lisbon, Portugal, April 2004, pp. 33–37.
  7. [APR 97]   APRIL A., ABRAN A., and MERLO E. Process assurance audits: Lessons learned. In: Proceedings of ICSE 98, Kyoto, Japan, April 19–25, 1997.
  8. [APR 00]   APRIL A. and AL-SHUROUGI D. Software product measurement for supplier evaluation. In: FESMA 2000, Madrid, Spain, October 18–20, 2000.
  9. [APR 08]   APRIL A. and ABRAN A. Software Maintenance Management: Evaluation and Continuous Improvement. John Wiley & Sons, Inc., Hoboken, NJ, 2008, 314 p.
  10. [AUS 96]   AUSTIN R. Measuring and Managing Performance in Organizations. Dorset House Publishing, New York, 1996.
  11. [BAB 15]   BABOK, Business Analyst Body of knowledge, v 3.0, International Institute of Business Analysis. Available at: http://www.theiiba.org
  12. [BAS 96]   BASILI V. R., CALDIERA G., and ROMBACH H. D. The experience factory. In: Encyclopedia of Software Engineering, edited by J. J. Marciniak., John Wiley & Sons, New York, 1996, pp. 469–476.
  13. [BAS 10]   BASILI V. R., LINDVALL, M., REGARDIE M., and SEAMAN C. Linking software development and business strategy through measurement. IEEE Computer, vol. 43, issue 4, April 2010, pp. 57–65.
  14. [BEI 90]   BEIZER B. Software Testing Techniques, 2nd edition. Van Nostrand Reinhold Co., International Thomson Press, New York, NY, 1990.
  15. [BLO 11]   BLOCK P. Flawless Consulting: A Guide to Getting Your Expertise Used, 3rd edition. Jossey-Bass/Pfeiffer, San Francisco, CA, 2011.
  16. [BOE 89]   BOEHM B. W. Tutorial: Software Risk Management. IEEE Computer Society, Los Alamitos, CA, 1989.
  17. [BOE 91]   BOEHM B. W. Software risk management: Principles and practices. IEEE Software, vol. 8, issue 1, 1991, pp. 32–41.
  18. [BOE 00]   BOEHM B. W., ABST C., BROWN A., CHULANI, S., CLARK, B. C., HOROWITZ, E., MADACHY, R., REIFER, D. J., STREECE, B. Software Cost Estimation with COCOMO II. Prentice-Hall, Englewood Cliffs, NJ, 2000.
  19. [BOE 01]   BOEHM B. W., BASILI V. Software Defect Reduction Top 10 List, IEEE Computer, vol. 34, January 2001, pp. 135–137.
  20. [BOL 95]   BOLOIX G. and ROBILLARD P. (1995) Software system evaluation framework. Computer Magazine, December 1995, pp. 17–26.
  21. [BOO 94]   BOOCH G. and BRYAN D. Software Engineering with Ada, 3rd edition. Benjamin/Cummings, Redwood City, CA, 1994.
  22. [BOU 05]   BOUSETTA A. and LABRECHE P. Introduction to 6-sygma applied to software, Presentation at Montreal SPIN, Ecole de Technologie Supérieure (ETS), Montreal, Canada, March 2005.
  23. [BRO 02]   BROY M. and DENERT E. (eds.) A history of software inspections. In: Software Pioneers. Springer-Verlag, Berlin, Heidelberg, 2002.
  24. [BRI 16]   BRIDGES W. Managing Transitions—Making the Most of Change, 4th edition. Da Capo Press, Cambridge, MA, 2016.
  25. [BUC 96]   BUCKLEY FLETCHER J. Implementing Configuration Management: Hardware, Software, and Firmware. IEEE Computer Society Press, Los Alamitos, CA, 1996.
  26. [BYR 96]   BYRNES P. and PHILLIPS M. Software Capability Evaluation, Version 3.0, Method Description (CMU/SEI-96-TR-002, ADA309160). Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 1996.
  27. [CAR 92]   CARLETON A. D., PARK R. E., GOETHERT W. B., FLORAC W. A., BAILEY E. K., PFLEEGER S. L. Software Management for DoD Systems: Recommendations for Initial Implementation, SEI Technical Report, USA, September 1992.
  28. [CEG 90]   CEGELEC, Software Validation Phase Procedure, CEGELEC Methodology, 1990.
  29. [CEG 90a]   Software Configuration Management Procedure, CEGELEC Methodology, 1990.
  30. [CEN 01]   EN 50128, Railway applications—Communications, signaling, and processing systems—Software for railway control and protection systems, European Standard, 2001.
  31. [CHA 99]   CHARRETTE R. R. Building bridges over intelligent rivers. American Programmer, September1992, pp. 2–9.
  32. [CHA 06]   CHARETTE R. Focus on Dr. Robert Charette, Master Risk Management Practitioner—A CAI State of Practice Interview, Computer Aid Inc., Allentown, PA, March 2006.
  33. [CHI 02]   CHILLAGERE R., BHANDARI I., CHAAR J., and HALLIDAY, D. Orthogonal defect classification. IEEE Transactions on Software Engineering, vol. 18, issue 11, November 2002, pp. 943–956.
  34. [CHR 08]   CHRISSIS M. B., KONRAD M., and SHRUM S. CMMI, 2nd edition. Pearson Education, Paris, France, 2008.
  35. [COA 03]   COALLIER F. International standardization in software and systems engineering. CrossTalk, The Journal of Defense Soltware Engineering, February 2003, pp. 18–22.
  36. [COB 12]   IT Governance Institute, CobiT, Governance, Control and Audit for Information and Related Technology, version 5, April 2012. Available at: http://www.isaca.org
  37. [COL 10]   Commit-monitor for Subversion Repositories, Version 1.7.0, October 24, 2010. Available at: https://sourceforge.net/projects/commitmonitor/
  38. [CON 93]   Conseil du Trésor. Politique du Conseil du Trésor, numéro NCTTI-26: Évaluation de logiciels- Caractéristiques d'utilisation-Critères d'applicabilité, version 11, février 1993.
  39. [CRO 79]   CROSBY P. B. Quality Is Free. McGraw-Hill, New York, 1979.
  40. [CUR 79]   CURTIS B. In search of software complexity. In: Proceedings of the IEEE/PINY Workshop on quantitative software models, IEEE catalog no TH00067-9, October 1979, pp. 95–105.
  41. [DAV 93]   DAVENPORT T. Process Innovation. Harvard Business School Press, Boston, MA, 1993.
  42. [DAV 06]   DAVIES I., GREEN P., ROSEMANN M., INDULSKA, M., GALLO S. How do Practitioners Use Conceptual Modeling in Practice? Data & Knowledge Engineering, vol. 58, 2006, pp. 358–380.
  43. [DEC 08]   DECKER G. and SCHREITER T. OMG releases BPMN 1.1—What's changed?, Inubit AG, Berlin, Germany M., 2008, pp. 1–9, Available at: http://docplayer.net/15316886-Omg-releases-bpmn-1-1-what-s-changed.html
  44. [DEM 00]   DEMARCO T. and LISTER T. Both sides always lose: Litigation of software-intensive contracts. CrossTalk, The Journal of Defense Soltware Engineering, February 2000, pp. 4–6.
  45. [DES 95]   DESHARNAIS J-M. and ABRAN A. How to successfully implement a measurement program: From theory to practice., In: Metrics in Software Evolution, edited by M. Müllenberg and A. Abran. R. Oldenbourg Verlag, Oldenburg, 1995, pp. 11–38.
  46. [DIA 02]   DIAZ, M. and KING J. How CMM impacts quality, productivity, rework, and the bottom line. CrossTalk, The Journal of Defense Soltware Engineering, March 2002, pp. 9–14.
  47. [DIN 05]   DINGSØYR T. Postmortem reviews: Purpose and approaches in software engineering. Information and Software Technology, vol. 47, issue 5, March 31, 2005, pp. 293–303.
  48. [DIO 92]   DION R. Elements of a process improvement program, Raytheon. IEEE Software, vol. 9, issue 4, July 1992, pp. 83–85.
  49. [DOD 83]   DoD-STD-1679A, Military Standard—Weapon Systems Software Development, Department of Defense, Washington D.C., 1983.
  50. [DOD 09]   Technology Readiness Assessment (TRA) Deskbook, Department of Defense, United States, July 2009.
  51. [DOR 96]   DOROFEE A. J., WALKER, J.A., ALBERTS, C.J., HIGUERA, R.P., MURPHY, R.L., WILLIAMS, R.C. Continuous Risk Management Guidebook, Carnegie Mellon University, Software Engineering Institute, Pittsburgh, PA, 1996.
  52. [DOW 94]   DOWN A., COLEMAN M. and ABSOLON P. Risk Management for Software Projects. McGraw-Hill Book Company, London, 1994.
  53. [EAS 96]   EASTERBROOK S. The role of independent V&V in upstream software development processes. In: Proceedings of the 2nd World Conference on Integrated Design and Process Technology (IDPT), Austin, Texas, USA, December 4, 1996.
  54. [EGY 04]   EGYED A. Identifying requirements conflicts and cooperation. IEEE Software, November/December, 2004.
  55. [EIA 98]   EIA 1998 Electronic Industries Alliance, Systems Engineering Capability Model (EIA/IS-731), Washington, DC, 1998.
  56. [EUR 11]   EUROCAE ED-12C - Software Considerations in Airborne Systems and Equipment Certification, EUROCAE, 17 rue Hamelin, 75783, Paris Cedex, France, 2011.
  57. [FAG 76]   FAGAN M. E. Design and code inspections to reduce errors in program development. IBM System Journal, vol. 15, issue 3, 1976, pp. 182–211.
  58. [FDA 02]   General Principles of Software Validation; Final Guidance for Industry and FDA Staff, U.S. Food and Drug Administration, 2002.
  59. [FEN 07]   FENTON N. and NEIL M. Software Metrics: Roadmap. Queen Mary University, Department of Computer Science, Harlow, UK, 2007.
  60. [FOR 92]   FORNELL G. E. Process for acquiring software architecture, cover letter to draft report, July 10, 1992.
  61. [FOR 05]   FORSBERG K., MOOZ H. and COTTERMAN H. Visualizing Project Management, 3rd edition. John Wiley & Sons, Inc., New York, NY, 2005.
  62. [FRE 05]   FREEMAN S. Toyota attributes Prius shutdowns to software glitch. Wall Street Journal, May 16, 2005.
  63. [GAL 17]   GALIN D. Software Quality: Concepts and Practice. Wiley-IEEE Computer Society Press, Hoboken, New Jersey, 2017, 726 p.
  64. [GAN 04]   GANSSLE J. Disaster redux!, Available at: http://www.embedded.com/ electronics-blogs/break-points/4025051/Disaster-redux-
  65. [GAR 84]   GARVIN D. What does product quality really mean? MIT Sloan Management Review, Fall 1984, pp. 25–45.
  66. [GAR 15]   GARCIA L., LAPORTE C. Y., ARTEAGA J., and BRUGGMANN M. Implementation and certification of ISO/IEC 29110 in an IT startup in Peru. Software Quality Professional Journal, ASQ, vol. 17, issue 2, 2015, pp. 16–29.
  67. [GAU 04]   GAUTHIER R. Une Force en Mouvement, La Boule de Cristal, Centre de recherche informatique de Montreal, 22 janvier 2004.
  68. [GEC 98]   GECK B., GLOGER M., JOCKUSCH, S., LEBSANFT, K., MEHNER, T., PAUL, P., PAULISCH, F., RHEINDT, M., VOLKER, A., WEBER, N. Software@Siemens: Best practices for the measurement and management of processes and architectures. In: Software Process Improvement Conference, Monte Carlo, Monaco, December 1998.
  69. [GEP 04]   GEPPERT L. Lost radio contact leaves pilots on their own. IEEE Spectrum, November 2004.
  70. [GHE 09]   GHEYSENS P. Drill through merges in TFS2010, Into Visual Studio team System, blogging about the current and upcoming release(s), January 5, 2009. Available at: http://intovsts.net/category/version-control/
  71. [GIL 88]   GILB T. Principles of Software Engineering Management. Addison-Wesley, Wokingham, UK, 1988.
  72. [GIL 93]   GILB T. and GRAHAM D. Software Inspection. Addison-Wesley, Wokingham, UK, 1993. ISBN: 0-201-63181-4.
  73. [GIL 08]   GILB T. Review Process Design: Some Guidelines for Tailoring Your Engineering Review Processes for Maximum Efficiency. International Council on Systems Engineering (INCOSE), The Netherlands, June 2008.
  74. [GOT 99a]   GOTTERBARN F. How the new software engineering code of ethics affects you. IEEE Software, vol. 16, issue 6, 1999, pp. 58–64.
  75. [GOT 99b]   GOTTERBARN D., MILLER K., and ROGERSON S. Computer society and ACM approve software engineering code of ethics. IEEE Computer, vol. 32, issue 10, 1999, pp. 84–88.
  76. [GRA 92]   GRADY R. Practical Software Metrics for Project Management and Process Improvement. Prentice-Hall Inc., Englewood Cliffs, NJ, 1992.
  77. [HAI 02]   HAILPERN B. and SANTHANAM P. Software debugging, testing, and verification. IBM Systems Journal, vol. 41, issue 1. Humphrey, W. S. A Discipline for Software Engineering. Addison-Wesley, Reading, MA, 2002.
  78. [HAL 96]   HALEY T. J. Software process improvement at Raytheon. IEEE Software, vol. 13, issue 6, 1996, pp. 33–41, Figure abstracted from IEEE Software.
  79. [HAL 78]   HALSTEAD M. H. Software science: A progress report. In: Proceedings of the U.S. Army/IEEE Second Life-Cycle Management Conference, Atlanta, August 1978, pp. 174–179.
  80. [HEF 01]   HEFNER R. and TAUSER J. Things they never taught you in CMM school. 26th Annual NASA Goddard Software Engineering Workshop, Greenbelt, MD, November 27–29, 2001.
  81. [HEI 14]   HEIMANN, D.I. An Introduction to the New IEEE 730 Standard on Software Quality Assurance. Software Quality Professional (SQP), vol. 16, issue 3, 2014, pp. 26–38.
  82. [HOL 98]   HOLLAND D. Document inspection as an agent of change. In: Dare to be Excellent, edited by A. Jarvis and l. Hayes, Prentice Hall, Upper Saddle River, NJ, 1998.
  83. [HUM 89]   HUMPHREY W. Managing the Software Process. Addison-Wesley, Boston, MA, 1989.
  84. [HUM 00]   HUMPHREY W. S. The Personal Software Process (PSP), CMU/SEI-2000-TR-022, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 2000.
  85. [HUM 02]   HUMPHREY W. S. Winning with Software, An Executive Strategy. Addison-Wesley, Reading, MA, 2002.
  86. [HUM 04]   HUMPHREY W. S. The Quality Attitude, news@sei newsletter, Number 3, 2004.
  87. [HUM 05]   HUMPHREY W. S. PSP: A Self-Improvement Process for Software Engineers. Addison-Wesley, Reading, MA, 2005.
  88. [HUM 07]   HUMPHREY W. S., KONRAD M., and OVER J. PETERSON, W. Future directions in process improvement. CrossTalk, The Journal of Defense Soltware Engineering, February 2007.
  89. [HUM 08]   HUMPHREY W. S. The software quality challenge. CrossTalk, The Journal of Defense Soltware Engineering, June 2008, pp. 4–9.
  90. [IBE 02]   IBERLE K. But will it work for me. In: Proceedings of the Pacific Northwest Software Quality Conference, Portland, United States, 2002, pp. 377–398. Available at: http://www.kiberle.com/publications/
  91. [IBE 03]   IBERLE K. They don't care about quality. In: Proceedings of STAR East, Orlando, United States, 2003. Available at: http://www.kiberle.com/publications/
  92. [IEE 98]   IEEE 1998, Std. 1320.1-1998. IEEE Standard for Functional Modeling Language - Syntax and Semantics for IDEF0, The Institute of Electrical and Electronics Engineers, New York, NY, 1998.
  93. [IEE 98a]   IEEE 1998, Std. 830-1998. IEEE Recommended practice for software requirements, The Institute of Electrical and Electronics Engineers, New York, NY, 1998.
  94. [IEE 98b]   IEEE 1998. Std. 1061-1998. IEEE Standard for a Software Quality Metrics Methodology, New York, NY, 1998.
  95. [IEE 99]   IEEE-CS, IEEE-CS-1999. Software Engineering Code of Ethics and Professional Practice, IEEE-CS/ACM, 1999, https://www.computer.org/ web/education/code-of-ethics
  96. [IEE 07]   IEEE Std 1362-2007. IEEE Guide for Information Technology—System Definition—Concept of operations (ConOps) Document, 2007.
  97. [IEE 08a]   IEEE 829-2008. IEEE Standard for Software and System Test Documentation, IEEE, The Institute of Electrical and Electronics Engineers, New York, NY, 2008.
  98. [IEE 08b]   IEEE 1028, IEEE Standard 1028-2008. IEEE Standard for Software Reviews and Audits, IEEE, The Institute of Electrical and Electronics Engineers, New York, NY, 2008.
  99. [IEE 12]   IEEE Std 1012-2012. IEEE Standard for System and Software Verification and Validation, IEEE, The Institute of Electrical and Electronics Engineers, New York, NY, 2012.
  100. [IEE 12b]   IEEE Std 828-2012. IEEE Standard for Configuration Management in Systems and Software Engineering, IEEE, The Institute of Electrical and Electronics Engineers, New York, NY, 2012.
  101. [IEE 14]   IEEE 730. IEEE Standard for Software Quality Assurance Processes: IEEE, The Institute of Electrical and Electronics Engineers, New York, NY, 2014.
  102. [INC 15]   INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, 4th Edition, Hoboken, NJ, USA: John Wiley and Sons, Inc, ISBN: 978-1-118-99940-0, 304 pages.
  103. [ISO Guide 73]   ISO Guide73:2009. Risk management—Vocabulary, International Organization for Standardization (ISO), Geneva, Switzerland, 2009.
  104. [ISO 01]   ISO/IEC 9126-1:2001. Software Engineering—Product quality—Part 1: Quality model: 2001, International Organization for Standardization (ISO), Geneva, Switzerland, 2001, 25 p.
  105. [ISO 04a]   ISO 17050-1:2004. Conformity assessment–Supplier's declaration of conformity- Part 1: General requirements, International Organization for Standardization (ISO), Geneva, Switzerland, 2004.
  106. [ISO 04b]   ISO 17050-2:2004. Conformity assessment—Supplier's declaration of conformity - Part 2: Supporting documentation, International Organization for Standardization (ISO), Geneva, Switzerland, 2004.
  107. [ISO 05c]   ISO/IEC 27002 :2005. Information technology—Security techniques—Code of practice for information security management, International Organization for Standardization (ISO), Geneva, Switzerland. 2005.
  108. [ISO 05d]   ISO/IEC 17799:2005. Information technology—Security techniques—Code of practice for information security management, International Organization for Standardization (ISO), Geneva, Switzerland, 2005.
  109. [ISO 06a]   ISO/IEC/IEEE 16085:2006. Systems and software engineering—Life cycle processes—Risk management, International Organization for Standardization (ISO), Geneva, Switzerland, 2006.
  110. [ISO 08]   ISO/IEC 26514:2008. Systems and Software Engineering—Requirements for Designers and Developers of User Documentation, International Organization for Standardization (ISO), Geneva, Switzeerland, 2008.
  111. [ISO 09]   ISO/IEC/IEEE 16326. Systems and software engineering—Life cycle processes—Project management, International Organization for Standardization (ISO), Geneva, Switzerland, 2009.
  112. [ISO 09a]   ISO 9004:2009. Managing for the sustained success of an organization—A quality management approach, International Organization for Standardization (ISO), Geneva, Switzerland, 2009.
  113. [ISO 10]   ISO/IEC TR 24774:2010. Software and systems engineering—Life cycle management- Guidelines for process description, International Organization for Standardization (ISO), Geneva, Switzerland, 2010.
  114. [ISO 11e]   ISO/IEC TR 29110-5-1-2:2011. Software Engineering—Lifecycle Profiles for Very Small Entities (VSEs)—Part 5-1-2: Management and Engineering Guide—Basic Profile, International Organization for Standardization (ISO), Geneva, Switzerland. Available for free at: http://standards.iso.org/ittf/ PubliclyAvailableStandards/index.html
  115. [ISO 11f]   ISO/IEC/IEEE 29148:2011. Systems and software engineering—Life cycle processes—Requirements Engineering, International Organization for Standardization (ISO), Geneva, Switzerland, 2011, 54 p.
  116. [ISO 11g]   ISO 19011: 2011. Guidelines for auditing systems, International Organization for Standardization (ISO), Geneva, Switzerland, 2011, 44 p.
  117. [ISO 11h]   ISO/IEC 20000-1:2011. Information technology—Service management—Part 1: Service management system requirements, International Organization for Standardization (ISO), Geneva, Switzerland, 2011.
  118. [ISO 11i]   ISO/IEC 25010:2011. Systems and software engineering–Systems and Software Quality Requirements and Evaluation (SQuaRE)–System and software quality models, International Organization for Standardization (ISO), Geneva, Switzerland, 2011, 34 p.
  119. [ISO 14]   ISO/IEC 90003:2014. Software Engineering—Guidelines for the application of ISO9001:2008 to computer software, International Organization for Standardization (ISO), Geneva, Switzerland, 2014, 54 p.
  120. [ISO 14a]   ISO/IEC 25000:2014. System and software engineering—System and Software Quality Requirements and Evaluation (SQuaRE)—Guide to SQuaRE—Guide de SQuaRE, International Organization for Standardization (ISO), Geneva, Switzerland, 2014, 27 p.
  121. [ISO 15]   ISO 9001. Quality systems requirement—Requirements, International Organization for Standardization (ISO), Geneva, Switzerland, 2015.
  122. [ISO 15a]   ISO 17021-1:2015. Conformity assessment—Requirements for bodies providing audit and certification of management systems—Part 1: Requirements, International Organization for Standardization (ISO), Geneva, Switzerland, 2014, 48 p.
  123. [ISO 15b]   ISO 9000, Quality management system-Fundamentals and vocabulary, International Organization for Standardization (ISO), Geneva, Switzerland, 2015.
  124. [ISO 15c]   ISO/IEC/IEEE 15288: 2015. Systems and software engineering—System life cycle processes, International Organization for Standardization (ISO), Geneva, Switzerland, 2015.
  125. [ISO 16d]   ISO 13485: 2016. Medical devices—Quality management systems—Requirements for regulatory purposes, International Organization for Standardization (ISO), Geneva, Switzerland, 2016.
  126. [ISO 16f]   ISO/IEC TR 29110-1:2016. Systems and software Engineering—Lifecycle Profiles for Very Small Entities (VSEs)—Part 1: Overview, International Organization for Standardization (ISO), Geneva, Switzerland, 2016. Available for free at: http://standards.iso.org/ittf/Publicly AvailableStandards/index.html
  127. [ISO 17]   ISO/IEC/IEEE 12207:2017. Systems and software engineering—Software life cycle processes, International Organization for Standardization (ISO), Geneva, Switzerland, 2017.
  128. [ISO 17a]   ISO/IEC/IEEE 24765:2017. Systems and Software Engineering Vocabulary, International Organization for Standardization (ISO), Geneva, 2017, Available at: www.computer.org/sevocab
  129. [ISO 17b]   ISO/IEC/IEEE 15289: 2017. Systems and software engineering—Content of life cycle information items (documentation), International Organization for Standardization (ISO), Geneva, Switzerland, 2017, 88 p.
  130. [ISO 17c]   ISO/IEC/IEEE 15939:2017. Systems and software engineering—Measurement process, International Organization for Standardization (ISO), Geneva, Switzerland, 2017.
  131. [ISO 17d]   ISO/IEC 20246. Software and Systems Engineering—Work Product Reviews, International Organization for Standardization (ISO), Geneva, Switzerland, 2017, 42 p.
  132. [IST 11]   Standard Glossary of terms Used in Software Testing, version 1.3, International Software Testing Qualifications Board, Brussels, Belgium, 2011. Available at: http://www.glossary.istqb.org
  133. [JAC 07]   JACKSON D., THOMAS M., and MILLET, L. Software for Dependable Systems: Sufficient Evidence?, Committee on Certifiably Dependable Software Systems, National Research Council, ISBN: 0-309-10857-8, 2007, 120 p.
  134. [JON 00]   JONES C. Software Assessments, Benchmarks, and Best Practices. Addison-Wesley, Reading, MA, 2000
  135. [JON 03]   JONES C. Making measurement work. CrossTalk, The Journal of Defense Soltware Engineering, January 2003.
  136. [JPL 00]   Report on the Loss of the Mars Polar Lander and Deep Space 2 Missions, JPL Special Review Board, Jet Propulsion Laboratory, March 2000.
  137. [KAS 00]   KASSE T. and MCQUAID P. Software Configuration Management for Project Leaders, SQP, Software Quality Professional, vol. 2, issue 4, September 2000, pp. 8–19.
  138. [KAS 05]   KASUNIC M. Designing an Effective Survey, Handbook, CMU/SEI-2005-HB-004. Software Engineering Institute, Pittsburg, PA, 2005.
  139. [KAS 08]   KASUNIC M., MCCURLEY J., and ZUBROW D., Can You Trust Your Data? Establishing the Need for a Measurement and Analysis Infrastructure Diagnostic, Technical Note CMU/SEI-2008-TN-028. Software Engineering Institute, Pittsburgh, PA, November 2008.
  140. [KER 01]   KERTH N. Project Retrospective: A Handbook for Team Reviews. Dorset House Publishing, New York, 2001.
  141. [KID 98]   KIDWELL P. A. Stalking the elusive computer bug. IEEE Annals of the History of Computing, vol. 20, issue 4, 1998, pp 5–9.
  142. [KON 00]   KONRAD M. Overview of CMMI Model, Presentation to Montreal SPIN, Montreal, Canada, November 21, 2000.
  143. [KRA 98]   KRASNER H. Using the cost of quality approach for software. CrossTalk, The Journal of Defense Soltware Engineering, vol. 11, issue 11, November 1998.
  144. [LAG 96]   LAGUË B. and APRIL A. 1996. Mapping of the ISO 9125 maintainability internal metrics to an industrial research tool. In: Proceedings of SES 1996, Montreal, Canada, October 21–25, 1996.
  145. [LAN 08]   LAND K., HOBART W., and WALZ J. A Practical Metrics and Measurements Guide For Today's Software Project Manager. IEEE Computer Society ReadyNotes, 2008.
  146. [LAP 97]   LAPORTE C. Y. and PAPICCIO N. L'ingénierie et l'intégration des processus de génie logiciel, de génie systèmes et de gestion de projets. Revue Génie Logiciel, vol. 46, 1997.
  147. [LAP 98]   LAPORTE C. Y. and TRUDEL S. Addressing the people issues of process improvement activities at Oerlikon Aerospace. Software Process-Improvement and Practice, vol. 4, issue 1, 1998, pp. 187–198.
  148. [LAP 03]   BOUCHER G. Risk management applied to the re-engineering of a weapon system. CrossTalk – The Journal of Defense Software Engineering, January 2003.
  149. [LAP 07a]   LAPORTE C. Y., DOUCET M., BOURQUE P., and BELKÉBIR Y. Utilization of a Set of Software Engineering Roles for a Multinational Organization, 8th International Conference on Product Focused Software Development and Process Improvement, PROFES 2007, Riga (Latvia), July 2–4, 2007, pp. 35–50.
  150. [LAP 07b]   LAPORTE C. Y., DOUCET M., ROY D., and DROLET M. Improvement of Software Engineering Performances An Experience Report at Bombardier Transportation—Total Transit Systems Signalling Group, International Council on Systems Engineering (INCOSE) Seventeenth International Symposium, San Diego (CA), USA, June 24–28, 2007.
  151. [LAP 08]   LAPORTE C. Y., ALEXANDRE S., and RENAULT A. Developing international standards for very small enterprises, IEEE Computer, vol. 41, issue 3, March 2008, pp. 98–101.
  152. [LAP 08a]   LAPORTE C. Y., ROY R., and NOVIELI R. La gestion des risques d'un projet de développement et d'implantation d'un système informatisé au Ministère de la Justice du Québec. Revue Génie Logiciel, mars 2008, numéro 84, pp. 2–12.
  153. [LAP 12]   LAPORTE C. Y., BERRHOUMA N., DOUCET M., and PALZA-VARGAS, E. Measuring the cost of software quality of a large software project at Bombardier Transportation. Software Quality Professional Journal, ASQ, vol. 14, issue 3, June 2012, pp 14–31.
  154. [LAP 14]   LAPORTE C.Y., O'CONNOR R. Systems and Software Engineering Standards for Very Small Entities Implementation and Initial Results, QUATIC'2014, 9th International Conference on the Quality of Information and Communications Technology, Guimarães, Portugal, September 23–26, 2014, pp. 38–47.
  155. [LAP 16a]   LAPORTE C. Y. and O'CONNOR R. V. QUATIC'2016, Implementing process improvement in very small enterprises with ISO/IEC 29110—A multiple case study analysis. In: 10th International Conference on the Quality of Information and Communications Technology (QUATIC 2016), Caparica/Lisbon, Portugal, September 6–9, 2016.
  156. [LEV 00]   LEVESON N. G. System safety in computer-controlled automotive systems. Society of Automotive Engineers (SAE) Congress, Detroit, United States, March 2000.
  157. [LEV 93]   LEVESON N. and TURNER C. An investigation of the Therac-25 accidents. IEEE Computer, vol. 26, issue 7, 1993, pp. 18–41.
  158. [MAY 02]   MAY W. A global applying ISO9001:2000 to software products. Quality Systems Update, vol. 12, issue 8, August 2002.
  159. [MCC 76]   MCCABE T. J. A complexity measure. IEEE Transactions on Software Engineering, vol. SE-2, issue 4, November 1976, pp. 308–320.
  160. [MCC 77]   MCCALL J. A., RICHARDS P. K., and WALTERS G. F. Factors in software quality. Griffiths Air Force Base, NY: Rome Air Development Center Air Force Systems Command, Springfield, NY, United States, 1977.
  161. [MCC 04]   MCCONNELL S. Code Complete: A Practical Handbook of Software Construction, 2nd edition. Microsoft Press, 2004, 960 p.
  162. [MCF 03]   MCFALL D., WILKIE F. G., MCCAFFERY F., LESTER N. G., and STERRITT R. Software processes and process improvement in Northern Ireland. In: Proceedings of the 16th International Conference on Software & Systems Engineering and their Applications, ICSSEA 2003, Paris, France, December 1–10, 2003, ISSN: 1637-503.
  163. [MCG 02]   MCGARRY J., CARD D., JONES C., LAYMAN B., CLARK E., DEAN J., and HALL F. Practical Software Measurement: Objective Information for Decision Makers. Addison-Wesley, Washinghton, DC, USA, 2002.
  164. [MCQ 04]   MCQUAID P. and DEKKERS C. Steer clear of hazards on the road to software measurement success. Software Quality Professional Journal, vol. 6, issue 2, 2004, pp. 27–33.
  165. [MIN 92]   MINTZBERG H. Structure in Fives: Designing Effective Organizations, Pearson Education, Boston, MA, 1992, 312 p.
  166. [MOL 13]   MOLL R. Being prepared – A bird's eye view of SMEs and risk management. ISO Focus: International Organization for Standardization, Geneva, Switzerland, February 2013.
  167. [MOR 05]   MORAN T. What's Bugging the High-Tech Car? New York Times, February 6, 2005.
  168. [NAS 04]   NASA, Goddard Space Flight Center, Process Asset Library, ETVX Diagram Template, DSTL 580-TM-011-01, v1.0, Greenbelt, Maryland, 2004.
  169. [NOL 15]   NOLAN A. J., PICKARD A. C., RUSSELL J. L., and SCHINDEL W. D. When two is good company, but more is not a crowd. In: 25th Annual INCOSE International Symposium, Seattle, July 13–16, 2015.
  170. [OBR 09]   O'BRIEN, J. Preparing for an Internal Assessment Interview. CrossTalk Journal of Defense Software Engineering, vol. 22, issue 7, 2009, pp. 26–27.
  171. [OLS 94]   OLSON T. G., REIZER N. R., OVER J. W. A Software Process Framework for the SEI Capability Maturity Model, CMU/SEI-94-HB-01, 1994
  172. [OLS 06]   OLSON T. G. Defining short and usable processes. CrossTalk Journal of Defense Software Engineering, vol. 19, issue 6, 2006, pp. 24–28.
  173. [OMG 11]   Object Management Group, Process Model and Notation (BPMN), version 2.0. Download available at: www.omg.org/spec/BPMN/2.0/PDF//
  174. [OUA 07]   OUANOUKI R. and APRIL A. IT process conformance measurement: A Sarbanes-Oxley requirement. In: Proceeding of the IWSM Mensura, Palma de Mallorca, Spain, November 4–8, 2007. Available at: http:// publicationslist.org.s3.amazonaws.com/data/a.april/ref-197/1111.pdf
  175. [OZ 94]   OZ E. When professional standards are lax: The confirm failure and its lessons. Communications of the ACM, vol. 37, issue 10, 1994, pp. 29–36.
  176. [PAR 92]   PARK R. E. Software Size Measurement: A Framework for Counting Source Statements (CMU/SEI-92-TR-20), Software Engineering Institute, Carnegie Mellon University, Pittburgh, PA, September1992.
  177. [PAR 03]   PARNAS D., and LAWFORD M. The role of inspection in software quality assurance. IEEE Transactions On Software Engineering, vol. 29, issue 8, August 2003.
  178. [PAU 95]   PAULK M., CURTIS, B., CHRISSIS. M.B., WEBER, C. V. The Capability Maturity Model: Guidelines for Improving the Software Process. Addison Wesley, Reading, MA, 1995.
  179. [PMI 13]   A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 5th edition. Project Management Institute, Newtown Square, PA, 2013.
  180. [POM 09]   POMEROY-HUFF M., MULLANEY JULIA L., CANNON R., and SEBERN M. The Personal Software Process Body of Knowledge. Software Engineering Institute, Pittsburgh, PA, Carnegie Mellon University. Version 1–2, CMU/SEI-2009- SR-018, Pittsburgh, PA, 2009.
  181. [PRE 14]   PRESSMAN R. S. Software Engineering – A Practitioner's Approach, 8th edition. McGraw-Hill, 2014, 976 p.
  182. [PSM 00]   Practical Software and Systems Measurement. Department of Defense and US Army, version 4.0b, October 2000.
  183. [RAD 85]   RADICE R. A., ROTH N. K. O'HARA A. C., CIARFELLA W. A. A programming process architecture. IBM Systems Journal, vol. 24, issue 2, 1985, pp. 79–90.
  184. [RAD 02]   RADICE R. High Quality Low Cost Software Inspections. Paradoxicon, Andover, MA, 2002.
  185. [REI 02]   REIFER D. Let the numbers do the talking. CrossTalk, The Journal of Defense Software Engineering, March 2002.
  186. [REI 04]   REICHART G. System architecture in vehicles – The key for innovation, system integration and quality (original in German). In: Proceedings of the 8th Euroforum Jahrestagung, Munich, Germany, February 10–11, 2004.
  187. [RTC 11]   RTCA inc., DO-178C. Software Considerations in Airborne Systems and Equipment Certification. RTCA, Washington, DC, 2011. Available at: www.rtca.org
  188. [SAR 02]   Sarbanes-Oxley act of 2002, public law 107 — July 30, 2002, 107th Congress. Available at: https://www.sec.gov/about/laws/soa2002.pdf
  189. [SCH 00]   SCHULMEYER G. and MACKENZI, G. R. Verification & Validation of Modern Software, Intensive Systems. Prentice Hall, Upper Saddle River, NJ, 2000.
  190. [SCH 11]   SCHAMEL J. How the Pilot's Checklist Came About. Available at: http:// www.atchistory.org/History/checklst.htm
  191. [SEI 00]   Software Engineering Institute. Overview of CMMI Model, Process Areas, Tutorial Module 7, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, 2000.
  192. [SEI 06]   Standard CMMI® Appraisal Method for Process Improvement (SCAMPI) A, Version 1.2: Method Definition Document, CMU/SEI-2006-HB-002, Software Engineering Institute, Pittsburgh, PA, 2006.
  193. [SEI 09]   Software Engineering Institute. The Personal Software Process Body of Knowledge. Carnegie Mellon University, Pittsburgh, PA. Version 1.2, CMU/SEI-2009-SR-018, 2009.
  194. [SEI 10a]   Software Engineering Institute. CMMI® for Development, Version 1.3. CMMI-DEV, V1.3. Carnegie Mellon University, Pittsburgh, PA. Version 1.3, CMU/SEI-2010-TR-033, Pittsburgh, PA, November 2010.
  195. [SEI 10b]   Software Engineering Institute. CMMI for Services, Version 1.3. Carnegie Mellon University, Pittsburgh, PA, 2010. Version 1.3, CMU/SEI-2010-TR-034. Available at: http://www.sei.cmu.edu/reports/ 10tr034.pdf
  196. [SEI 10c]   Software Engineering Institute CMMI for Acquisition, Version 1.3. Carnegie Mellon University, Pittsburgh, PA. Version 1.3, CMU/SEI-2010-TR-032, Carnegie Mellon University, Pittsburgh, 2010. Available at: www.sei.cmu.edu/reports/10tr032.pdf
  197. [SEL 07]   SELBY P. and SELBY R. W. Measurement-driven systems engineering using six sigma techniques to improve software defect detection. In: Proceedings of 17th International Symposium, INCOSE, San Diego, United States, June 2007.
  198. [SHE 01]   SHEARD S. Evolution of the frameworks quagmire. IEEE Computer, vol. 34, issue 7, July 2001, pp. 96–98.
  199. [SHE 97]   SHEPEHRD K. Managing risk. In: Proceedings 28th Annual Seminars & Symposium, Project Management Institute (PMI), Chicago, United States, September 1997, pp. 19–27.
  200. [SHI 06]   SHINTANI K. Empowered engineers are key players in process improvements. In: Proceedings of the First International Research Workshop for Process Improvement in Small Settings Software Engineering Institute, Carnegie Mellon University, CMU/SEI-2006-Special Report-001, Pittsburgh, PA, January 2006, SEI, 2005, pp. 115–116.
  201. [SIL 09]   SILVER B. BPMN Method and Style: A Levels-Based Methodology for BPM Process Modeling and Improvement Using BPMN 2.0. Cody Cassidy Press, Altadena, CA, US, 2009.
  202. [SPM 10]   Software Project Manager Network (SPMN). American Systems, 2010. Available at: http://www.spmn.com
  203. [STS 05]   Software Technology Support Center. Configuration management fundamental. CrossTalk, The Journal of Defense Software Engineering, July 2005, pp. 10–15.
  204. [SUR 17]   SURYN W. ISO/IEC JTC1 SC7 Secretariat Report, Kuantan, Malaysia, May 2017.
  205. [SWE 14]   Guide to the Software Engineering Body of Knowledge, version 3.0. edited by P. Bourque and R. E. Fairley. IEEE Computer Society, 2014, 335 p.
  206. [TIK 07]   The TickIT Guide, version 5.5. British Standards Institute, London, UK, November 2007.
  207. [TYL 10]   TYLOR E. B. Primitive Culture, Researches into the development of mythology, philosophy, religion, language, art and custom, John Murray, Cambridge University Press, Cambridge, UK, 2010, 440 p.
  208. [USC 16]   Statistics About Business Size (including Small Business). US Census Bureau.
  209. [VAN 92]   VANSCOY R. L. Software Development Risk: Opportunity, Not Problem. SEI, CMU/SEI-92-TR-30, Pittsburgh, PA, September 1992.
  210. [WAL 96]   WALLACE D., IPPOLITO L. M., CUTHILL B. B. Reference Information for the Software Verification and Validation Process. National Institute of Standards and Technology (NIST), U.D. Department of Commerce, Special Publication 500-234, 1996. Available at: https://www.nist.gov/publications/ reference-information-software-verification-and-validation-process
  211. [WES 02]   WESTFALL L. Software customer satisfaction. In: Proceedings of the Applications in Software Measurement (ASM) Conference, Anaheim, CA, USA, 2002.
  212. [WES 03]   WESTFALL L. Are we doing well, or are we doing poorly? In: Proceedings of the Applications in Software Measurement (ASM) Conference, San Jose, CA, Unites States, June 2–6, 2003. Available at: www.westfallteam.com/Papers/Are_We_Doing_Well.pdf
  213. [WES 05]   WESTFALL L. 12 Steps to Useful Software Metrics. The Westfall Team, Whitepaper, USA, 2005. Available at: http://www.westfallteam.com/Papers/12_steps_paper.pdf
  214. [WES 10]   WESTFALL L. The Certified Software Quality Engineer Handbook. American Society for Quality, Quality Press, Milwaukee, WI, 2010.
  215. [WIE 96]   WIEGERS K. E. Creating A Software Engineering Culture. Dorset House, New York, 1996, 358p.
  216. [WIE 98]   WIEGERS K. E. Know your enemy: Introduction to risk management. Software Development, vol. 6, issue 10, 1998, pp. 38–42.
  217. [WIE 02]   WIEGERS K. Peer Reviews in Software. Pearson Education, Boston, MA, 2002.
  218. [WIE 03]   WIEGERS K. Software Requirements, 2nd edition. Microsoft Press, Redmond, WA, 2003, 516 p.
  219. [WIE 13]   WIEGERS K. and BEATTY J. Software Requirements, 3rd edition. Microsoft Press, Redmond, WA, 2013, 637 p.