Skip to main content
SpringerLink
Log in

Challenges of Establishing Traceability in the Automotive Domain

  • Conference paper
  • First Online:
Software Quality. Complexity and Challenges of Software Engineering in Emerging Technologies (SWQD 2017)

Part of the book series: Lecture Notes in Business Information Processing ((LNBIP,volume 269))

Included in the following conference series:

Abstract

Traceability, i.e., relationships between artifacts in software development, is prescribed by quality standards such as ISO 26262 and therefore mandatory for automotive companies that develop safety-critical systems. However, establishing traceability is a challenge for many automotive companies. The objective of this study is to identify traceability challenges and solutions in this domain and compare these challenges and solutions with the ones in literature. To achieve this, we conducted a case study with a large automotive supplier to discover their traceability challenges and a tertiary literature review on existing traceability literature surveys to identify reported challenges and their solutions. We found 13 challenges from the literature study, of which ten were also found at the company. Three challenges are solved at the company with solutions that correlate with those proposed in literature, three are partially solved while four are still unsolved even though there are solutions in literature.

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

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    http://tinyurl.com/j7dlco3.

  2. 2.

    http://www-03.ibm.com/software/products/en/ratidoor.

  3. 3.

    http://open-services.net.

  4. 4.

    http://www.omg.org/spec/ReqIF/1.1/.

References

  1. Broy, M.: Challenges in automotive software engineering. In: Proceedings of the 28th International Conference on Software Engineering, pp. 33–42. ACM (2006)

    Google Scholar 

  2. Pretschner, A., Broy, M., Kruger, I.H., Stauner, T.: Software engineering for automotive systems: a roadmap. In: 2007 Future of Software Engineering, pp. 55–71. IEEE Computer Society (2007)

    Google Scholar 

  3. IEEE: Standard glossary of software engineering terminology. IEEE Std 610.12-1990, pp. 1–84, December 1990

    Google Scholar 

  4. Salem, A.M.: Improving software quality through requirements traceability models. In: IEEE International Conference on Computer Systems and Applications, pp. 1159–1162. IEEE (2006)

    Google Scholar 

  5. Egyed, A., Biffl, S., Heindl, M., Grünbacher, P.: A value-based approach for understanding cost-benefit trade-offs during automated software traceability. In: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 2–7. ACM (2005)

    Google Scholar 

  6. Nair, S., de la Vara, J.L., Sen, S.: A review of traceability research at the requirements engineering conference re@ 21. In: 2013 21st IEEE International Requirements Engineering Conference (RE), pp. 222–229. IEEE (2013)

    Google Scholar 

  7. International Organization for Standardization: Road Vehicles - Functional Safety. ISO26262:2011, November 2011

    Google Scholar 

  8. VDA QMC Working Group 13/Automotive SIG: Automotive SPICE Process Assessment/Reference Model. Technical report, Automotive Special Interest, Group (2015)

    Google Scholar 

  9. Javed, M.A., Zdun, U.: A systematic literature review of traceability approaches between software architecture and source code. In: Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering, p. 16. ACM (2014)

    Google Scholar 

  10. Runeson, P., Höst, M.: Guidelines for conducting and reporting case study research in software engineering. Empirical Softw. Eng. 14(2), 131–164 (2009)

    Article  Google Scholar 

  11. Gotel, O., et al.: Traceability fundamentals. In: Cleland-Huang, J., Gotel, O., Zisman, A. (eds.) Software and Systems Traceability, pp. 3–22. Springer, Heidelberg (2012)

    Chapter  Google Scholar 

  12. Petersen, K., Feldt, R., Mujtaba, S., Mattsson, M.: Systematic mapping studies in software engineering. In: 12th International Conference on Evaluation and Assessment in Software Engineering, vol. 17, pp. 1–10 (2008)

    Google Scholar 

  13. Spanoudakis, G., Zisman, A.: Software traceability: a roadmap. Handb. Softw. Eng. Knowl. Eng. 3, 395–428 (2005)

    Article  Google Scholar 

  14. Winkler, S., Pilgrim, J.: A survey of traceability in requirements engineering and model-driven development. Softw. Syst. Model. (SoSyM) 9(4), 529–565 (2010)

    Article  Google Scholar 

  15. Kannenberg, A., Saiedian, H.: Why software requirements traceability remains a challenge. CrossTalk J. Def. Softw. Eng. 22(5), 14–19 (2009)

    Google Scholar 

  16. Gotel, O., Cleland-Huang, J., Hayes, J.H., Zisman, A., Egyed, A., Grünbacher, P., Antoniol, G.: The quest for ubiquity: a roadmap for software and systems traceability research. In: 2012 20th IEEE International Requirements Engineering Conference (RE), pp. 71–80. IEEE (2012)

    Google Scholar 

  17. Von Knethen, A., Paech, B.: A survey on tracing approaches in practice and research. Frauenhofer Institut Experimentelles Software Engineering, IESE-Report No. 95 (2002)

    Google Scholar 

  18. Ramesh, B.: Factors influencing requirements traceability practice. Commun. ACM 41(12), 37–44 (1998)

    Article  Google Scholar 

  19. Regan, G., McCaffery, F., McDaid, K., Flood, D.: The barriers to traceability and their potential solutions: towards a reference framework. In: 2012 38th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), pp. 319–322. IEEE (2012)

    Google Scholar 

  20. Torkar, R., Gorschek, T., Feldt, R., Svahnberg, M., Raja, U.A., Kamran, K.: Requirements traceability: a systematic review and industry case study. Int. J. Softw. Eng. Knowl. Eng. 22(03), 385–433 (2012)

    Article  Google Scholar 

  21. De Lucia, A., Fasano, F., Oliveto, R.: Traceability management for impact analysis. In: Frontiers of Software Maintenance, FoSM 2008, pp. 21–30. IEEE (2008)

    Google Scholar 

  22. Cleland-Huang, J., Gotel, O.C., Huffman Hayes, J., Mäder, P., Zisman, A.: Software traceability: trends and future directions. In: Proceedings of the on Future of Software Engineering, pp. 55–69. ACM (2014)

    Google Scholar 

  23. Cleland-Huang, J., Czauderna, A., Gibiec, M., Emenecker, J.: A machine learning approach for tracing regulatory codes to product specific requirements. In: Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering, vol. 1, pp. 155–164. ACM (2010)

    Google Scholar 

  24. Borg, M., Runeson, P., Ardö, A.: Recovering from a decade: a systematic mapping of information retrieval approaches to software traceability. Empirical Softw. Eng. 19(6), 1565–1616 (2014)

    Article  Google Scholar 

  25. Galvão, I., Goknil, A.: Survey of traceability approaches in model-driven engineering. In: Proceedings - IEEE International Enterprise Distributed Object Computing Workshop, pp. 313–324. EDOC (2007)

    Google Scholar 

  26. Gotel, O.C., Finkelstein, A.C.: An analysis of the requirements traceability problem. In: Proceedings of the First International Conference on Requirements Engineering, pp. 94-101. IEEE (1994)

    Google Scholar 

  27. Rempel, P., Mäder, P., Kuschke, T., Philippow, I.: Requirements traceability across organizational boundaries - a survey and taxonomy. In: Doerr, J., Opdahl, A.L. (eds.) REFSQ 2013. LNCS, vol. 7830, pp. 125–140. Springer, Heidelberg (2013). doi:10.1007/978-3-642-37422-7_10

    Chapter  Google Scholar 

  28. Königs, S.F., Beier, G., Figge, A., Stark, R.: Traceability in systems engineering-review of industrial practices, state-of-the-art technologies and new research solutions. Adv. Eng. Inf. 26(4), 924–940 (2012)

    Article  Google Scholar 

  29. Asuncion, H.U., Asuncion, A.U., Taylor, R.N.: Software traceability with topic modeling. In: Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering, vol. 1, pp. 95–104. ACM (2010)

    Google Scholar 

  30. Cuddeback, D., Dekhtyar, A., Hayes, J.H.: Automated requirements traceability: the study of human analysts. In: 2010 18th IEEE International Requirements Engineering Conference (RE), pp. 231–240. IEEE (2010)

    Google Scholar 

  31. Mäder, P., Gotel, O., Philippow, I.: Enabling automated traceability maintenance through the upkeep of traceability relations. In: Paige, R.F., Hartman, A., Rensink, A. (eds.) ECMDA-FA 2009. LNCS, vol. 5562, pp. 174–189. Springer, Heidelberg (2009). doi:10.1007/978-3-642-02674-4_13

    Chapter  Google Scholar 

  32. Drivalos-Matragkas, N., Kolovos, D.S., Paige, R.F., Fernandes, K.J.: A state-based approach to traceability maintenance. In: Proceedings of the 6th ECMFA Traceability Workshop, pp. 23–30. ACM (2010)

    Google Scholar 

  33. Arkley, P., Riddle, S.: Overcoming the traceability benefit problem. In: Proceedings of the 13th IEEE International Conference on Requirements Engineering, pp. 385–389. IEEE (2005)

    Google Scholar 

  34. Pedreira, O., García, F., Brisaboa, N., Piattini, M.: Gamification in software engineering-a systematic mapping. Inf. Softw. Technol. 57, 157–168 (2015)

    Article  Google Scholar 

  35. Seaman, C.B.: Qualitative methods in empirical studies of software engineering. IEEE Trans. Softw. Eng. 25(4), 557–572 (1999)

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Chalmers Institute of Technology and University of Gothenburg, Gothenburg, Sweden

    Salome Maro, Miroslaw Staron & Jan-Philipp Steghöfer

Authors
  1. Salome Maro
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Miroslaw Staron
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Jan-Philipp Steghöfer
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Salome Maro .

Editor information

Editors and Affiliations

  1. Institute of Software Technology and Interactive Systems, Vienna University of Technology, Vienna, Austria

    Dietmar Winkler

  2. Institute of Software Technology and Interactive Systems, Vienna University of Technology, Vienna, Austria

    Stefan Biffl

  3. Software Quality Lab GmbH, Linz, Austria

    Johannes Bergsmann

Rights and permissions

Reprints and permissions

Copyright information

© 2017 Springer International Publishing AG

About this paper

Cite this paper

Maro, S., Staron, M., Steghöfer, JP. (2017). Challenges of Establishing Traceability in the Automotive Domain. In: Winkler, D., Biffl, S., Bergsmann, J. (eds) Software Quality. Complexity and Challenges of Software Engineering in Emerging Technologies. SWQD 2017. Lecture Notes in Business Information Processing, vol 269. Springer, Cham. https://doi.org/10.1007/978-3-319-49421-0_11

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-49421-0_11

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-49420-3

  • Online ISBN: 978-3-319-49421-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation