Software Engineering Process Development

Be ingenious

Customer: Tier 1 Supplier to the automotive industry

Market: European market

BRACE execution: Development Process & Toolchain competence cluster with assistence of the Functional Safety competence cluster

Cluster Location: Customer site

In the world of automotive software the time-to-market for new software is getting ever shorter, while the complexity of the product is rapidly increasing. The challenges are in the legislation demands as well as market requests for incorporating standards such as Automotive SPICE and Functional Safety (ISO 26262) into the process.

The main requirements for the software development process were:

  • A process according to state of the art European standards and techniques (the supplier has origins in Asia).
  • A process capable of handling A-Spice level three projects.
  • A process fully compliant to ISO 26262.
  • A process capable of dealing with A-Supplier as well as B-Supplier type projects.
  • A process that remains lean and flexible and supports short-loop development of software.
  • A process that allows world-scale co-located development- and sharing of software.

The software process is being developed through several stages. The first stage was the gathering of requirements on the process, creating the Business Environment Description in which the process shall operate and designing the top-level process flow, work product descriptions and phase-split of the process.

The second stage of the development is the creation of the supporting tool chain, templates, guidelines and related work product which will combine into what the users will practically “experience”.

The third stage is a series of process pilot projects by which the process will be tested and further improved after which in the final stage the process will be assessed by A-Spice and ISO 26262 assessors.

The process layout is based on the classic “V-Model” in order to be recognisable for Automotive OEM’s and for ease of integration with A-Spice and ISO 26262. Much of the process however is based on Agile/SCRUM methodologies in order to provide a flexible and team-driven process that is able to cope with changes and dynamic project circumstances.