ISO/IEC 15504

Print Print
Reading time 14:14

ISO/IEC 15504 Information technology – Process assessment, also termed Software Process Improvement and Capability Determination (SPICE), is a set of technical standards documents for the computer software development process and related business management functions. It is one of the joint International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) standards, which was developed by the ISO and IEC joint subcommittee, ISO/IEC JTC 1/SC 7.[1]

ISO/IEC 15504 was initially derived from process lifecycle standard ISO/IEC 12207 and from maturity models like Bootstrap, Trillium and the Capability Maturity Model (CMM).

ISO/IEC 15504 has been superseded by ISO/IEC 33001:2015 Information technology – Process assessment – Concepts and terminology as of March, 2015.[2]


ISO/IEC 15504 is the reference model for the maturity models (consisting of capability levels which in turn consist of the process attributes and further consist of generic practices) against which the assessors can place the evidence that they collect during their assessment, so that the assessors can give an overall determination of the organization's capabilities for delivering products (software, systems, and IT services).[3]


A working group was formed in 1993 to draft the international standard and used the acronym SPICE.[4][5] SPICE initially stood for Software Process Improvement and Capability Evaluation, but in consideration of French concerns over the meaning of evaluation, SPICE has now been renamed Software Process Improvement and Capability Determination.[citation needed] SPICE is still used for the user group of the standard, and the title for the annual conference. The first SPICE was held in Limerick, Ireland in 2000, SPICE 2003 was hosted by ESA in the Netherlands, SPICE 2004 was hosted in Portugal, SPICE 2005 in Austria, SPICE 2006 in Luxembourg, SPICE 2007 in South Korea, SPICE 2008 in Nuremberg, Germany and SPICE 2009 in Helsinki, Finland.

The first versions of the standard focused exclusively on software development processes. This was expanded to cover all related processes in a software business, for example project management, configuration management, quality assurance, and so on. The list of processes covered grew to cover six areas: organizational, management, engineering, acquisition supply, support, and operations.

In a major revision to the draft standard in 2004, the process reference model was removed and is now related to the ISO/IEC 12207 (Software Lifecycle Processes). The issued standard now specifies the measurement framework and can use different process reference models. There are five general and industry models in use.

Part 5 specifies software process assessment and part 6 specifies system process assessment.

The latest work in the ISO standards working group includes creation of a maturity model, which is planned to become ISO/IEC 15504 part 7.

The standard

The Technical Report (TR) document for ISO/IEC TR 15504 was divided into 9 parts. The initial International Standard was recreated in 5 parts. This was proposed from Japan when the TRs were published at 1997.

The International Standard (IS) version of ISO/IEC 15504 now comprises 6 parts. The 7th part is currently in an advanced Final Draft Standard form[6] and work has started on part 8.

Part 1 of ISO/IEC TR 15504 explains the concepts and gives an overview of the framework.

Reference model

ISO/IEC 15504 contains a reference model. The reference model defines a process dimension and a capability dimension.

The process dimension in the reference model is not the subject of part 2 of ISO/IEC 15504, but part 2 refers to external process lifecycle standards including ISO/IEC 12207 and ISO/IEC 15288.[7] The standard defines means to verify conformity of reference models.[8]


The process dimension defines processes divided into the five process categories of:

  • customer-supplier
  • engineering
  • supporting
  • management
  • organization

With new parts being published, the process categories will expand, particularly for IT service process categories and enterprise process categories.

Capability levels and process attributes

For each process, ISO/IEC 15504 defines a capability level on the following scale:[3]

Level Name
5 Optimizing process
4 Predictable process
3 Established process
2 Managed process
1 Performed process
0 Incomplete process

The capability of processes is measured using process attributes. The international standard defines nine process attributes:

  • 1.1 Process performance
  • 2.1 Performance management
  • 2.2 Work product management
  • 3.1 Process definition
  • 3.2 Process deployment
  • 4.1 Process measurement
  • 4.2 Process control
  • 5.1 Process innovation
  • 5.2 Process optimization

Each process attribute consists of one or more generic practices, which are further elaborated into practice indicators to aid assessment performance.

Rating scale of process attributes

Each process attribute is assessed on a four-point (N-P-L-F) rating scale:

  • Not achieved (0–15%)
  • Partially achieved (>15–50%)
  • Largely achieved (>50–85%)
  • Fully achieved (>85–100%).

The rating is based upon evidence collected against the practice indicators, which demonstrate fulfillment of the process attribute.[9]


ISO/IEC 15504 provides a guide for performing an assessment.[10]

This includes:

  • the assessment process
  • the model for the assessment
  • any tools used in the assessment

Assessment process

Performing assessments is the subject of parts 2 and 3 of ISO/IEC 15504.[11] Part 2 is the normative part and part 3 gives a guidance to fulfill the requirements in part 2.

One of the requirements is to use a conformant assessment method for the assessment process. The actual method is not specified in the standard although the standard places requirements on the method, method developers and assessors using the method.[12] The standard provides general guidance to assessors and this must be supplemented by undergoing formal training and detailed guidance during initial assessments.

The assessment process can be generalized as the following steps:

  • initiate an assessment (assessment sponsor)
  • select assessor and assessment team
  • plan the assessment, including processes and organizational unit to be assessed (lead assessor and assessment team)
  • pre-assessment briefing
  • data collection
  • data validation
  • process rating
  • reporting the assessment result

An assessor can collect data on a process by various means, including interviews with persons performing the process, collecting documents and quality records, and collecting statistical process data. The assessor validates this data to ensure it is accurate and completely covers the assessment scope. The assessor assesses this data (using his expert judgment) against a process's base practices and the capability dimension's generic practices in the process rating step. Process rating requires some exercising of expert judgment on the part of the assessor and this is the reason that there are requirements on assessor qualifications and competency. The process rating is then presented as a preliminary finding to the sponsor (and preferably also to the persons assessed) to ensure that they agree that the assessment is accurate. In a few cases, there may be feedback requiring further assessment before a final process rating is made.[13]

Assessment model

The process assessment model (PAM) is the detailed model used for an actual assessment. This is an elaboration of the process reference model (PRM) provided by the process lifecycle standards.[14]

The process assessment model (PAM) in part 5 is based on the process reference model (PRM) for software: ISO/IEC 12207.[15]

The process assessment model in part 6 is based on the process reference model for systems: ISO/IEC 15288.[16]

The standard allows other models to be used instead, if they meet ISO/IEC 15504's criteria, which include a defined community of interest and meeting the requirements for content (i.e. process purpose, process outcomes and assessment indicators).

Tools used in the assessment

There exist several assessment tools. The simplest comprise paper-based tools. In general, they are laid out to incorporate the assessment model indicators, including the base practice indicators and generic practice indicators. Assessors write down the assessment results and notes supporting the assessment judgment.

There are a limited number of computer based tools that present the indicators and allow users to enter the assessment judgment and notes in formatted screens, as well as automate the collated assessment result (i.e. the process attribute ratings) and creating reports.

Assessor qualifications and competency

For a successful assessment, the assessor must have a suitable level of the relevant skills and experience.

These skills include:

  • personal qualities such as communication skills.
  • relevant education and training and experience.
  • specific skills for particular categories, e.g. management skills for the management category.
  • ISO/IEC 15504 related training and experience in process capability assessments.

The competency of assessors is the subject of part 3 of ISO/IEC 15504.

In summary, the ISO/IEC 15504 specific training and experience for assessors comprise:

  • completion of a 5-day lead assessor training course
  • performing at least one assessment successfully under supervision of a competent lead assessor
  • performing at least one assessment successfully as a lead assessor under the supervision of a competent lead assessor. The competent lead assessor defines when the assessment is successfully performed. There exist schemes for certifying assessors and guiding lead assessors in making this judgement.[12]


ISO/IEC 15504 can be used in two contexts:

  • Process improvement, and
  • Capability determination (= evaluation of supplier's process capability).

Process improvement

ISO/IEC 15504 can be used to perform process improvement within a technology organization.[17] Process improvement is always difficult, and initiatives often fail, so it is important to understand the initial baseline level (process capability level), and to assess the situation after an improvement project. ISO 15504 provides a standard for assessing the organization's capacity to deliver at each of these stages.

In particular, the reference framework of ISO/IEC 15504 provides a structure for defining objectives, which facilitates specific programs to achieve these objectives.

Process improvement is the subject of part 4 of ISO/IEC 15504. It specifies requirements for improvement programmes and provides guidance on planning and executing improvements, including a description of an eight step improvement programme. Following this improvement programme is not mandatory and several alternative improvement programmes exist.[13]

Capability determination

An organization considering outsourcing software development needs to have a good understanding of the capability of potential suppliers to deliver.

ISO/IEC 15504 (Part 4) can also be used to inform supplier selection decisions. The ISO/IEC 15504 framework provides a framework for assessing proposed suppliers, as assessed either by the organization itself, or by an independent assessor.[18]

The organization can determine a target capability for suppliers, based on the organization's needs, and then assess suppliers against a set of target process profiles that specify this target capability. Part 4 of the ISO/IEC 15504 specifies the high level requirements and an initiative has been started to create an extended part of the standard covering target process profiles. Target process profiles are particularly important in contexts where the organization (for example, a government department) is required to accept the cheapest qualifying vendor. This also enables suppliers to identify gaps between their current capability and the level required by a potential customer, and to undertake improvement to achieve the contract requirements (i.e. become qualified). Work on extending the value of capability determination includes a method called Practical Process Profiles - which uses risk as the determining factor in setting target process profiles.[13] Combining risk and processes promotes improvement with active risk reduction, hence reducing the likelihood of problems occurring.

Acceptance of ISO/IEC 15504

ISO/IEC 15504 has been successful as:

  • ISO/IEC 15504 is available through National Standards Bodies.
  • It has the support of the international community.
  • Over 4,000 assessments have been performed to date.
  • Major sectors are leading the pace such as automotive, space and medical systems with industry relevant variants.
  • Domain-specific models like Automotive SPICE and SPICE 4 SPACE can be derived from it.
  • There have been many international initiatives to support take-up such as SPICE for small and very small entities.

On the other hand, ISO/IEC 15504 may not be as popular as CMMI for the following reasons:

  • ISO/IEC 15504 is not available as free download, but must be purchased from the ISO. (Automotive SPICE, on the other hand, can be freely downloaded from the link supplied below.) CMM, and later CMMI, were originally available as free downloads from the SEI website. However, beginning with CMMI v2.0 a license must now be purchased from SEI.
  • The CMM, and later CMMI, were originally sponsored by the US Department of Defense (DoD). Now, however, DoD no longer funds CMMI or mandates its use.
  • The CMM was created first, and reached critical 'market' share before ISO 15504 became available.
  • The CMM has subsequently been replaced by the CMMI, which incorporates many of the ideas of ISO/IEC 15504, but also retains the benefits of the CMM.

Like the CMM, ISO/IEC 15504 was created in a development context, making it difficult to apply in a service management context. But work has started to develop an ISO/IEC 20000-based process reference model (ISO/IEC 20000-4) that can serve as a basis for a process assessment model. This is planned to become part 8 to the standard (ISO/IEC 15504-8). In addition there are methods available that adapt its use to various contexts.

Further reading

External links

  • ISO/IEC 33001:2015 - Information technology — Process assessment — Concepts and terminology[23]


  1. ^ ISO. "Standards Catalogue: ISO/IEC JTC 1/SC 7". Retrieved 2014-01-06.
  2. ^ 14:00-17:00. "ISO/IEC 33001:2015". ISO. Retrieved 2021-06-02.CS1 maint: numeric names: authors list (link)
  3. ^ a b ISO/IEC 15504-2 Clause 5
  4. ^ "ISO/IEC JTC 1/SC 7 - Software and systems engineering". ISO. Retrieved 2021-06-02.
  5. ^ Rout, Terence P. (2002-01-15), Marciniak, John J. (ed.), "ISO/IEC 15504 and Spice", Encyclopedia of Software Engineering, Hoboken, NJ, USA: John Wiley & Sons, Inc., pp. sof171, doi:10.1002/0471028959.sof171, ISBN 978-0-471-02895-6, retrieved 2021-06-02
  6. ^ DTR, meaning Draft Technical Report
  7. ^ ISO/IEC 15504-2 Clause 6
  8. ^ ISO/IEC 15504-2 Clause 7
  9. ^ ISO/IEC 15504 part 3
  10. ^ ISO/IEC 15504 parts 2 and 3
  11. ^ ISO/IEC 15504-2 Clause 4 and ISO/IEC 15504-3
  12. ^ a b van Loon, 2007a
  13. ^ a b c van Loon, 2007b
  14. ^ ISO 15504-2 Clause 6.2
  15. ^ ISO/IEC 15504-2 Clause 6.3 and ISO/IEC 15504-5
  16. ^ ISO/IEC 15504-6
  17. ^ ISO/IEC 15504-4 Clause 6
  18. ^ ISO/IEC 15504-4 Clause 7
  19. ^ Cass, A.; Volcker, C.; Sutter, P.; Dorling, A.; Stienen, H. (September 2002). "SPiCE in action - experiences in tailoring and extension". Proceedings. 28th Euromicro Conference: 352–360. doi:10.1109/EURMIC.2002.1046215.
  20. ^ Eito-Brun, Ricardo (2013), Woronowicz, Tanja; Rout, Terry; O’Connor, Rory V.; Dorling, Alec (eds.), "Comparing SPiCE for Space (S4S) and CMMI-DEV: Identifying Sources of Risk from Improvement Models", Software Process Improvement and Capability Determination, Berlin, Heidelberg: Springer Berlin Heidelberg, 349, pp. 84–94, doi:10.1007/978-3-642-38833-0_8, ISBN 978-3-642-38832-3, retrieved 2021-06-02
  21. ^ Mesquida, Antoni Lluís; Mas, Antònia; Amengual, Esperança (2011), O’Connor, Rory V.; Rout, Terry; McCaffery, Fergal; Dorling, Alec (eds.), "An ISO/IEC 15504 Security Extension", Software Process Improvement and Capability Determination, Berlin, Heidelberg: Springer Berlin Heidelberg, 155, pp. 64–72, doi:10.1007/978-3-642-21233-8_6, ISBN 978-3-642-21232-1, retrieved 2021-06-02
  22. ^ Schlager, Christian; Messnarz, Richard; Sporer, Harald; Riess, Armin; Mayer, Ralf; Bernhardt, Steffen (2018), Larrucea, Xabier; Santamaria, Izaskun; O'Connor, Rory V.; Messnarz, Richard (eds.), "Hardware SPICE Extension for Automotive SPICE 3.1", Systems, Software and Services Process Improvement, Cham: Springer International Publishing, 896, pp. 480–491, doi:10.1007/978-3-319-97925-0_41, ISBN 978-3-319-97924-3, retrieved 2021-06-02
  23. ^ 14:00-17:00. "ISO/IEC 33001:2015". ISO. Retrieved 2021-06-02.CS1 maint: numeric names: authors list (link)

Edited: 2021-06-18 19:17:49