Guide To Software Quality Assurance Plans
Planning for software quality assurance lecture 6. 1. Planning for Software Quality Assurance By Mr. Fazal Wahab. Importance of SQAP SQA plan provides a road map for instituting software quality assurance. The plan serves as a template for SQA activities that are instituted for each software project. define the techniques, procedures, and methodologies that will be used to assure timely delivery of the software that meets specified requirements within project resources.
Software Quality Assurance Planning What is not tracked is not done” The Goals of Software Quality Assurance: To improve software quality by appropriately monitoring both the software and the development process that produces it. To ensure full compliance with the established standards and procedures for the software and the software process.
Software Quality Assurance Readings Topics Description 1. Introduction. Wiegers, K., Software Development, July 1994. Article also available from the author's web site:.
Humphrey, W., Crosstalk-The Journal of Defense Software Engineering, June 2008, pp 4-9. Web site of Crosstalk:. Fairley, E.,R., Willshire, M.,J., IEEE Software, March/April 2004, (Optional). Leveson, N. G., Turner, C.
S., IEEE Computer, Volume 26 Issue 7, July 1993, Pages 18-41, (Optional). (Optional) 2. Ethics.,.
Approaches to good software quality assurance practices in support of IEEE Std 730-1989, IEEE Standard for Software Quality Assurance Plans, are identified.
- There are two important reasons for Software Quality Assurance (SQA). Specifications, design documei_ts, test plans, and client manuals.
- The software quality assurance (SQA) plan is to provide a guideline for. For Software Quality Assurance Plans, ANSI/IEEE Std 730-1989; IEEE Guide for.
Wiegers, K, The Journal of the Quality Assurance Institute, July 1997,. Gotterbarn, D., IEEE Software, Nov./Dec. (Optional) 3. Software Engineering Body of Knowledge (SWEBOK) and Cost of Quality Guide to the Software Engineering Body of Knowledge (SWEBOK). Bourque, P., Abran, A., Dupuis, R., IEEE Software, Nov./Dec.
1999,. April, Wallace & Reeker, SWEBOK -. Cost of Quality Reifer, D., DACS Newsletter, STN 7-2, June 2004. Introduction to Software Quality., Internal and External Quality Characteristics. Standards and Models. ISO/IEC 12207 Standard for Software Life Cycle Processes, Sections 1 to 4,. ISO/IEC 90003 Guidelines for the Application of ISO9001 to computer software,.
CMMI,. Laporte, C.Y., Alexandre, S, Renault, A., IEEE Computer, March 2008, Volume 41, number 3, pp 82- 85 6.
Reviews and Audits. IEEE 1028 Standard for Software Reviews, Sections 4 to 8. Crawford, S., AT&T Bell Laboratories. Allen, M., Bug Tracking Basics, Software Testing & Quality Engineering (STQE) Magazine, May-June 2002, 7 pages.
(optional). Mirrer, B., STQE Magazine, September/October 2000. (optional).
IEEE 1058- 1998, IEEE Standard for Software Project Management Plans, Section 4.7.5 Reviews and audits plan 4.7.6 Problem resolution plan. Inspections.
IEEE 1028 Standard for Software Reviews, sections 1, 2, 3, 6. Wiegers, K., Software Development, October 2001.
Quality Assurance Activities and Process. ISO 9001:2008. Configuration Management. IEEE 730- 2002, IEEE Standard for Software Quality Assurance Plans, Section 4.4.2.6 Software Configuration Management Plan. Casavecchia, D., ACS Defense Inc., Crosstalk, November 2002. Rinko-Gay, W., STQE Magazine, July/August 2002. (optional).
ISO/IEC 12207- 1995, Software life-cycle processes, Section 6.2 Configuration management Process. IEEE 828 Standard for Configuration Management Plans. Sections 1 to 6. IEEE 1058- 1998, IEEE Standard for Software Project Management Plans, Section 4.7.1 Configuration management plan. (optional) 10. Verification and Validation. Wallace D., Ippolito L., Cuthill B., NIST Special Publication 500-234, March 29, 1996.
IEEE 1012 IEEE Standard for Software Verification and Validation Plans, sections 1 to 7. Dustin, E., Software Testing & Quality Engineering (STQE) Magazine, May/June 2002. (optional). Council, B., Software Testing & Quality Engineering (STQE) Magazine, July/August 2000. (optional). IEEE 1058- 1998, IEEE Standard for Software Project Management Plans, Section 4.7.2 Verification and validation plan.
(optional) 11. Measurement. IEEE 1058- 1998, IEEE Standard for Software Project Management Plans, Section 4.5.3.6 Metrics collection plan. International Software Benchmarking Standards Group, (optional).
Allison, A., Software Testing & Quality Engineering (STQE) Magazine, January-February 2002, pp. Kaner, C., Software Testing & Quality Engineering (STQE) Magazine, March/April 2002. Risks. IEEE 1058- 1998, IEEE Standard for Software Project Management Plans, Section 4.5.4 - Risk management plan.
ISO/CEI 16085, Risk Management. (optional). IEEE 1490-2003, IEEE Guide - Adoption of PMI Standard A Guide to the Project Management Body of Knowledge, Project Management Institute. Chapter 11, Project Risk Management. (optional) 13. Suppliers.
IEEE 1058- 1998, IEEE Standard for Software Project Management Plans, Section 4.7.7 Subcontractor management plans. SQA Plan. IEEE 730 Standard for Software Quality Assurance Plans. IEEE 730.1- 1995 (withdrawn) Guide for Software Quality Assurance Planning. Sections 1 to 3. IEEE 1058- 1998, IEEE Standard for Software Project Management Plans, Section 4.7.4 Quality assurance plan, 4.5.3.4 Quality control plan, 4.6.4 Product acceptance plan. (optional) 15.
Software Quality Assurance Agile
Lessons Learned (Retrospective). Wiegers, Karl E., Rothman, Johanna, Looking Back, Looking Ahead, Article available from the author's web site: or Wiegers, Karl, and Johanna Rothman.
Guide To Software Quality Assurance Plan
Looking Back, Looking Ahead, Software Development, vol. 2 (February 2001), pp. Wiegers, Karl E., Project Retrospective Procedure, Article available from the author's web site.