Skip to main content

Platform Assessment – Challenges and Recommendations Regarding Automotive SPICE©

  • Conference paper
  • First Online:
Systems, Software and Services Process Improvement (EuroSPI 2024)

Part of the book series: Communications in Computer and Information Science ((CCIS,volume 2179))

Included in the following conference series:

  • 578 Accesses

Abstract

With Automotive SPICE® PAM v4.0 [1], the assessment effort increases compared to the previous versions. In addition, many customers require more than one assessment per individual project - and each assessment is supposed to evaluate the entire product. This contradicts the approach of many automotive suppliers to develop diverse platforms and thus reduce the workload of individual development teams [12]. Based on the experience gained during more than 100 Automotive SPICE® assessments, intention is to present an approach to reunite the controversial points of view in a meaningful way. After defining the platforms where this approach is applicable, it will be used for selected processes to present practises that would have to be specifically considered by the assessor team in an Automotive SPICE® (in addition to the familiar VDA guidelines) on the part of a platform project and on the part of a customer (application) project to bring both sides back together.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Similar content being viewed by others

Notes

  1. 1.

    For a definition of platform and a declaration, which type platforms are considered in this article, Sect. 3.1 General.

  2. 2.

    The mentioned base and generic practises refer to Automotive SPICE® PAM v4.0 [1].

  3. 3.

    E.g.: It should be clearly defined, which artefacts will be delivered by a platform project at a release and especially, if a customer project wants to detach itself from the platform project (e.g.: how to receive code, is there any transition phase or transfer of knowledge planned?

  4. 4.

    If there is no budget planned, foreseen, and approved, customer projects will face difficulties whenever any change (e.g.: bug fixing) is needed in the scope of work of the platform project).

  5. 5.

    If the responsibilities and activities for operation and withdrawal of a platform project are not clearly defined, also BP7 of the project management process (MAN.3) should be downrated.

References

  1. Automotive SPICE® 4.0, Process Assessment Model, VDA QMC Working Group 13, 2023-11-29

    Google Scholar 

  2. Automotive SPICE® for Cybersecurity, Joint Quality Management in the Supply Chain, 1st edition, (August 2021)

    Google Scholar 

  3. Automotive SPICE® Guidelines, Process assessment using the Automotive SPICE PAM 4.0, 2nd revised edition (November 2023)

    Google Scholar 

  4. Automotive SPICE® 3.1, Process Assessment Model, VDA QMC Working Group 13, 2017-11-01

    Google Scholar 

  5. Automotive SPICE® Guidelines, Process assessment using Automotive SPICE in the development of software-based systems, 1st edition (September 2017)

    Google Scholar 

  6. Müller M., Hörmann K., Dittmann L., Zimmer J.: Automotive SPICE in der Praxis, dpunkt.verlag 2. Auflage 2016 (2016)

    Google Scholar 

  7. ISO/IEC/IEEE 15288:2023, Systems and software engineering – System life cycle processes. https://www.iso.org/standard/81702.html

  8. PRM/PAM Agile SPICE™, Version: 1.3, 24.03.2023

    Google Scholar 

  9. ISO 26262-1, Road vehicles – Functional safety – Part 1: Vocabulary. https://www.iso.org/standard/68383.html

  10. ISO/SAE 21434:2021, Road vehicles – Cybersecurity engineering. https://www.iso.org/standard/70918.html

  11. Korsaa, M., et al.: The SPI manifesto and the ECQA SPI manager certification scheme. J. Softw. Evol. Process 24(5), 525–540 (2012)

    Article  Google Scholar 

  12. Bachmann, V., Messnarz, R.: Improving the software development for multiple projects by applying a platform strategy for mechatronic systems. J. Softw. Evol. Process 24(5), 541–549 (2012)

    Article  Google Scholar 

  13. Dreves, R., Haunert, L., Karner, C., Mayer, R., Mergen, S., Sechser, B.: Metrics traceability between customer projects and platform projects. In: Walker, A., O'Connor, R., Messnarz, R. (eds.) Systems, Software and Services Process Improvement. EuroSPI 2019. Communications in Computer and Information Science, vol. 1060. Springer, Chambridge (2019). https://doi.org/10.1007/978-3-030-28005-5_27

  14. Ekert, D., Steger, B., Messnarz, R.: Functional roadmap - scheduling in complex mechatronic projects In: Barafort, B., O'Connor, R.V., Poth, A., Messnarz, R. (eds.) Systems, Software and Services Process Improvement. EuroSPI 2014. Communications in Computer and Information Science. Springer, Chambridge (2014)

    Google Scholar 

  15. Steger B., Ekert D., Messnarz R., Stolfa J., Stolfa S., Velart Z.: Metrics and dashboard for level 2 – experience. In: Yilmaz M., Niemann J., Clarke P., Messnarz R. (eds.) Systems, Software and Services Process Improvement. EuroSPI 2020. Communications in Computer and Information Science, vol. 1251. Springer, Chambridge (2020). https://doi.org/10.1007/978-3-030-56441-4_49

  16. Wegner, T., et al.: Enough assessment guidance, it’s time for improvement – a proposal for extending the VDA guidelines. In: Yilmaz, M., Niemann, J., Clarke, P., Messnarz, R. (eds.) Systems, Software and Services Process Improvement. EuroSPI 2020. Communications in Computer and Information Science, vol. 1251. Springer, Cham (2020). https://doi.org/10.1007/978-3-030-56441-4_34

  17. Messnarz, R., et al.: An interpretation of the PIM.3 process improvement process – results of the iNTACS process expert training developer group for PIM.3. In: Yilmaz, M., Clarke, P., Messnarz, R., Wöran, B. (eds.) Systems, Software and Services Process Improvement. EuroSPI 2022. Communications in Computer and Information Science, vol. 1646. Springer, Cham (2022). https://doi.org/10.1007/978-3-031-15559-8_21

  18. Korsaa, M., et al.: The people aspects in modern process improvement management approaches. J. Softw. Evol. Process 25(4), 381–391 (2013). Special Issue: Selected Industrial Experience Papers of EuroSPI 2010

    Google Scholar 

  19. Pisano, G.P.: You Need an Innovation Strategy, It’s the only way to make sound trade-off decisions and choose the right practices. Harvard Bus. School Mag. 93, 44–54 (2015)

    Google Scholar 

  20. Messnarz, R.: Process improvement guidance for successful automotive SPI implementation. J. Softw. Evol. Process 35(8) e2373 (2023). Special Issue: EuroSPI

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Thomas Wegner .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2024 The Author(s), under exclusive license to Springer Nature Switzerland AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Richerzhagen, M., Braunersreuther, M., Patrick, G., Wegner, T., Steger, B. (2024). Platform Assessment – Challenges and Recommendations Regarding Automotive SPICE©. In: Yilmaz, M., Clarke, P., Riel, A., Messnarz, R., Greiner, C., Peisl, T. (eds) Systems, Software and Services Process Improvement. EuroSPI 2024. Communications in Computer and Information Science, vol 2179. Springer, Cham. https://doi.org/10.1007/978-3-031-71139-8_28

Download citation

  • DOI: https://doi.org/10.1007/978-3-031-71139-8_28

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-031-71138-1

  • Online ISBN: 978-3-031-71139-8

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics