Boundary objects in Agile practices: continuous management of systems engineering artifacts in the automotive domain

ABSTRACT

Automotive companies increasingly include proven agile methods in their plan-driven system development. The adoption of agile methods impacts not only the way individuals collaborate, but also the management of artifacts like requirements, test cases, safety documentation, and models. While practitioners aim to reduce unnecessary documentation, there is a lack of guidance for automotive companies with respect to what artifacts are needed and how to manage them. To close this knowledge gap and create practical guidelines, we conducted a design-science study together with 53 practitioners from six automotive companies. Using interviews, surveys, and focus groups, we analyzed categories of artifacts and practical challenges to create applicable guidelines to collaboratively manage artifacts in agile automotive contexts. Our findings indicate that different practices are required to manage artifacts that are shared among different teams within the company (boundary objects) and those that are relevant within a specific team (locally relevant artifacts).

References

1. Julian M. Bass. 2016. Artefacts and agile method tailoring in large-scale offshore software development programmes. Information and Software Technology 75 (2016), 1--16.
2. Johan Kaj Blomkvist, Johan Persson, and Johan Åberg. 2015. Communication through Boundary Objects in Distributed Agile Teams. In Proceedings of the 33rd Annual ACM Conference on Human Factors in Computing Systems (CHI'15). ACM, New York, NY, USA, 1875--1884.
3. John W. Creswell. 2008. Research Design: Qualitative, Quantitative, and Mixed Methods Approaches (3 ed.). Sage Publications Ltd., London, England.
4. Joseph D'Ambrosio and Grant Soremekun. 2017. Systems engineering challenges and MBSE opportunities for automotive system design. In International Conference on Systems, Man, and Cybernetics (SMC). IEEE, 2075--2080.
5. Philipp Diebold, Thomas Zehler, and Dominik Richter. 2017. How do agile practices support automotive SPICE compliance?. In Proceedings of the International Conference on Software and System Process (ICSSP'17). ACM, New York, NY, USA, 80--84.
6. Torgeir Dingsøyr, Nils Brede Moe, Tor Erlend Faegri, and Eva Amdahl Seim. 2018. Exploring software development at the very large-scale: a revelatory case study and research agenda for agile method adaptation. Empirical Software Engineering 23, 1 (Feb 2018), 490--520.
7. Tore Dybå and Torgeir Dingsøyr. 2008. Empirical studies of agile software development: A systematic review. Information and Software Technology 50, 9--10 (2008), 833--859.
8. Christof Ebert and John Favaro. 2017. Automotive Software. IEEE Software 34, 3 (may 2017), 33--39.
9. Ulf Eliasson, Rogardt Heldal, Patrizio Pelliccione, and Jonn Lantz. 2015. Architecting in the Automotive Domain: Descriptive vs Prescriptive Architecture. In Proceedings of the 12th Working IEEE/IFIP Conference on Software Architecture (WICSA'15). IEEE, 115--118.
10. Geir K. Hanssen, Aiko Fallas Yamashita, Reidar Conradi, and Leon Moonen. 2009. Maintenance and agile development: Challenges, opportunities and future directions. In Proceedings of the 25th IEEE International Conference on Software Maintenance (ICSM'09). IEEE, 487--490.
11. Rogardt Heldal, Patrizio Pelliccione, Ulf Eliasson, Jonn Lantz, Jesper Derehag, and Jon Whittle. 2016. Descriptive vs Prescriptive Models in Industry. In Proceedings of the 19th International Conference on Model Driven Engineering Languages and Systems (MODELS 2016). ACM, New York, NY, USA, 216--226.
12. Alan R. Hevner, Salvatore T. March, Jinsoo Park, and Sudha Ram. 2004. Design Science in Information Systems Research. MIS Quarterly 28 (2004), 75--105.
13. Dan X. Houston. 2014. Agility beyond software development. In Proceedings of the International Conference on Software and System Process (ICSSP'14). ACM, New York, NY, USA, 65--69.
14. Markus Hummel, Christoph Rosenkranz, and Roland Holten. 2013. The role of communication in agile systems development: An analysis of the state of the art. Business and Information Systems Engineering 5, 5 (2013), 343--355.
15. Tuomo Kähkönen. 2004. Agile Methods for Large Organizations - Building Communities of Practice. In Proceedings of the Agile Development Conference. IEEE, 2--10.
16. Mira Kajko-Mattsson. 2008. Problems in agile trenches. In Proceedings of the 2nd International Symposium on Empirical Software Engineering and Measurement (ESEM'08). ACM, New York, NY, USA, 111.
17. Marco Kuhrmann, Philipp Diebold, Jürgen Münch, Paolo Tell, Kitija Trektere, Fergal McCaffery, Garousi Vahid, Michael Felderer, Oliver Linssen, Eckhart Hanser, and Christian Prause. 2018. Hybrid Software Development Approaches in Practice: A European Perspective. IEEE Software PP, 99 (2018).
18. Lina Lagerberg, Tor Skude, Par Emanuelsson, Kristian Sandahl, and Daniel Stahl. 2013. The impact of agile principles and practices on large-scale software development projects: A multiple-case study of two projects at Ericsson. In International Symposium on Empirical Software Engineering and Measurement. IEEE, 348--356.
19. Dean Leffingwell. 2007. Scaling Software Agility: Best Practices for Large Enterprises (The Agile Software Development Series). Addison-Wesley Professional.
20. Rensis Likert. 1932. A technique for the measurement of attitudes. Archives of Psychology 22, 140 (1932), 5--55.
21. Thomas W. Malone and Kevin Crowston. 1994. The Interdisciplinary Study of Coordination. Comput. Surveys 26, 1, Article 1 (March 1994), 33 pages.
22. Joseph Alex Maxwell. 2012. Qualitative Research Design: An Interactive Approach. SAGE Publications.
23. Robert L. Nord and James E. Tomayko. 2006. Software architecture-centric methods and agile development. IEEE Software 23, 2 (March 2006), 47--53.
24. Wanda J. Orlikowski and JoAnne Yates. 1994. Genre Repertoire: The Structuring of Communicative Practices in Organizations. Administrative Science Quarterly 39, 4 (1994), 541--574.
25. Lars Pareto, Peter Eriksson, and Staffan Ehnebom. 2010. Architectural Descriptions as Boundary Objects. In Proceedings of the 13th International Conference on Model Driven Engineering Languages and Systems (MODELS 2010). Springer Berlin Heidelberg, Berlin, Heidelberg, 406--419.
26. Kai Petersen and Claes Wohlin. 2010. The effect of moving from a plan-driven to an incremental software development approach with agile practices: An industrial case study. Empirical Software Engineering 15, 6 (2010), 654--693.
27. Christian R. Prause and Zoya Durdik. 2012. Architectural design and documentation: Waste in agile development?. In Proceedings of the International Conference on Software and System Process (ICSSP'12). IEEE, 130--134.
28. Alexander Pretschner, Manfred Broy, Ingolf H. Krüger, and Thomas Stauner. 2007. Software engineering for automotive systems: A roadmap. In Future of Software Engineering (FoSE'07). IEEE, 55--71.
29. Per Runeson and Martin Höst. 2009. Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering 14, 2 (19 Dec 2009), 131--164.
30. Andreas Rüping. 2003. Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (1 ed.). Wiley Publishing.
31. Ken Schwaber and Mike Beedle. 2001. Agile Software Development with Scrum (1 ed.). Prentice Hall PTR.
32. Bran Selic. 2009. Agile documentation, anyone? IEEE Software 26, 6 (2009), 11--12.
33. Susan Leigh Star and James R. Griesemer. 1989. Institutional Ecology, 'Translations' and Boundary Objects: Amateurs and Professionals in Berkeley's Museum of Vertebrate Zoology, 1907--39. Social Studies of Science 19, 3 (1989), 387--420.
34. Monica Chiarini Tremblay, Alan R. Hevner, and Donald J. Berndt. 2010. The Use of Focus Groups in Design Science Research. In Integrated Series in Information Systems. Springer US, 121--143.
35. Stefan Voigt, Jörg von Garrel, Julia Müller, and Dominic Wirth. 2016. A Study of Documentation in Agile Software Projects. In Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM '16). ACM, New York, NY, USA, Article 4, 6 pages.

Index Terms

• Software and its engineering

  • Software creation and management

    • Collaboration in software development

    • Software development process management

      • Software development methods

        • Agile software development

    • Software post-development issues

      • Documentation