ISO IEC 90003 2014 Outline of Software Quality Management Standard

 This page presents an outline of the ISO IEC 90003 quality standard for software products.
For a more detailed version, please see ISO IEC 90003 2014 Translated into Plain English.

4. Systemic requirements and guidelines

4.1  Organizational requirements and guidelines

4.2  Documentation requirements and guidelines

4.2.1  Prepare quality documents.

4.2.2  Develop a quality manual.

4.2.3  Control quality documents.

4.2.4  Maintain quality records.  Show that requirements are being met.  Demonstrate that your QMS is effective.  Control record retention and disposition.

5. Management requirements and guidelines

5.1  Commitment requirements and guidelines

5.2  Customer requirements and guidelines

5.3  Policy requirements and guidelines

5.4  Planning requirements and guidelines

5.4.1  Establish quality objectives.

5.4.2  Carry out quality planning.

5.5  Managerial requirements and guidelines

5.5.1  Clarify responsibility and authority.

5.5.2  Appoint management representative.

5.5.3  Establish internal communications.

5.6  Review requirements and guidelines

5.6.1  Perform reviews at planned intervals.

5.6.2  Examine management review inputs.

5.6.3  Generate management review outputs.

6. Resource requirements and guidelines

6.1  Allocation requirements and guidelines

6.2  Personnel requirements and guidelines

6.2.1  Provide competent personnel.

6.2.2  Meet competence requirements.

6.3  Infrastructure requirements and guidelines

6.4  Environmental requirements and guidelines

7. Realization requirements and guidelines

7.1  Planning requirements and guidelines

7.1.1  Use life cycle models to plan work.

7.1.2  Carry out software quality planning.

7.2  Customer requirements and guidelines

7.2.1  Determine requirements related to products.  Determine customer-related requirements.  Determine additional product requirements.

7.2.2  Consider your product-oriented requirements.  Review contractual issues and concerns.  Evaluate risk before agreeing to supply software.  Appoint someone to represent the customer.

7.2.3  Establish effective customer communications.  Consider the type and extent of your contractual obligations.  Schedule joint reviews during software development projects.  Communicate with customers during operations and maintenance.

7.3  Development requirements and guidelines

7.3.1  Plan product design and development activities.  Plan the design and development of software products.  Plan your review, verification, and validation activities.  Plan your design and development work assignments.  Plan design and development boundaries and interfaces.

7.3.2  Define product design and development inputs.

7.3.3  Generate product design and development outputs.

7.3.4  Perform product design and development reviews.

7.3.5  Conduct product design and development verifications.

7.3.6  Carry out product design and development validations.  Carry out planned software validation activities.  Carry out planned software testing activities.

7.3.7  Control product design and development changes.

7.4  Purchasing requirements and guidelines

7.4.1  Manage purchasing process.  Control purchased products and services.  Control the use of external resources.

7.4.2  Clarify purchasing information.

7.4.3  Verify purchased products.

7.5  Production requirements and guidelines

7.5.1  Control production and service provision.  Control software production and service activities.  Control software build and release activities.  Control software replication activities.  Control software product delivery activities.  Control software product installation activities.  Control software operation and support activities.  Control software product maintenance activities.

7.5.2  Validate processes if outputs cannot be verified.

7.5.3  Identify your products and establish traceability.  Use configuration management to identify and track software.  Clarify scope of software configuration management process.  Establish a process to trace your software components.

7.5.4  Protect customer property supplied for products.

7.5.5  Preserve software products and components.

7.6  Measurement requirements and guidelines.

8. Remedial requirements and guidelines

8.1  Planning requirements and guidelines

8.2  Research requirements and guidelines

8.2.1  Monitor and measure customer satisfaction.

8.2.2  Perform internal audits at planned intervals.

8.2.3  Find out if processes achieve planned results.

8.2.4  Verify that quality requirements are being met.

8.3  Control requirements and guidelines

8.4  Analytical requirements and guidelines

8.5  Implementation requirements and guidelines

8.5.1  Improve quality management system.

8.5.2  Correct actual nonconformities.

8.5.2  Prevent potential nonconformities.


 If you'd like to see how we've translated each of the above sections into
Plain English, please check out our detailed ISO IEC 90003 web page.


Introduction to ISO IEC 90003 2014

Overview of ISO IEC 90003 2014 Standard

Plain English ISO IEC 90003 2014 Definitions

ISO IEC 90003 2014 versus ISO IEC 90003 2004

ISO IEC 90003 2014 Translated into Plain English

ISO IEC 90003 2014 Quality Management Checklist

Skills and Knowledge Internal Auditors Should Have

ISO IEC 90003 2014 Software Management Audit Tool

How to Carry Out an ISO IEC 90003 2014 Gap Analysis

Updated on January 30, 2017. First published on December 27, 2016.

Home Page

Our Libraries

A to Z Index


How to Order

Our Products

Our Prices


Praxiom Research Group Limited                 780-461-4514

Legal Restrictions on the Use of this Page
Thank you for visiting this webpage. You are, of course, welcome to view our material as often
as you wish, free of charge. And as long as you keep intact all copyright notices, you are also
welcome to print or make one copy of this page for your own personal, noncommercial,
home use. But, you are not legally authorized to print or produce additional copies or to
copy and paste any of our material onto another web site or to republish it in any way.

Copyright 2016 - 2017 by Praxiom Research Group Ltd. All Rights Reserved.

Praxiom Research
        Group Limited