Software+process+improvement

The value of software used to control various components and systems within a vehicle continues to increase dramatically. To meet the need for quality improvements, the industry has identified CMMI and Automotive SPICE (developed using ISO/IEC 15504) as useful tools.

Print this page Save as PDF

Purpose

The industry has recognised the use of CMMI to help improve the organisational maturity levels of software design processes to ensure the reliability of new components and system.

Primarily within Europe, there is a strong move to introduce the Automotive SPICE tool on a project basis, as a maturity model for rating and improving process capability and subsequently to improve the quality and reliability of embedded software in automotive components and systems.

Many OEM’s (original equipment manufacturer) are using these tools to assess supplier capabilities and are requiring the achievement of specific maturity levels.

There is a possibility that Automotive SPICE will become a third party certification tool in the near future.

Benefits

Used throughout the world, CMMI and Automotive SPICE are proven approaches to conducting assessments of software development capabilities and process related risks, providing guidance for improving organisational processes and the ability to manage development, acquisition, and maintenance of products or services.

CMMI and Automotive SPICE define relevant actions for improvement and help drive these improvements through the organisation.

The assessments provide a systematic insight into real software and system process progress and can be tailored to focus on high priority business needs. By doing so they lead to a timely recognition of software and system process problems and the subsequent escalation of the risks involved.

As a result your organisation will experience an increase in performance with a clear definition of the return on investment and the opportunity to optimise the use of resources and skills.

Benefits to the automotive industry at large include:

  • Early identification and timely escalation of risks and unrealistic planning

  • Continuous insight into project progress

  • Transparency and alignment of projects between the manufacturer, supplier and service provider to ensure commitments are met

  • Objective comparison of the capability of software processes at various suppliers