Advertisement

Software Professionals’ Attitudes Towards Video as a Medium in Requirements Engineering

  • Oliver KarrasEmail author
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 11271)

Abstract

In requirements engineering (RE), knowledge is mainly communicated via written specifications. This practice is cumbersome due to its low communication richness and effectiveness. In contrast, videos can transfer knowledge more richly and effectively. However, video is still a neglected medium in RE. We investigate if software professionals perceive video as a medium that can contribute to RE. We focus on their attitudes towards video as a medium in RE including its strengths, weaknesses, opportunities, and threats. We conducted a survey to explore these attitudes with a questionnaire. 64 out of 106 software professionals completed the survey. The respondents’ overall attitude towards video is positive. 59 of them stated that video has the potential to improve RE. However, 34 respondents also mentioned threats of videos for RE. We identified the strengths, weaknesses, opportunities, and threats of videos for RE from the point of view of software professionals. Video is a medium with a neglected potential. Software professionals do not fundamentally reject videos in RE. Despite the strengths and opportunities of video, the stated weaknesses and threats impede its application. Based on our findings, we conclude that software professionals need guidance on how to produce and use videos for visual communication to take full advantage of the currently neglected potential.

Keywords

Requirements engineering Video Attitude SWOT Survey 

Notes

Acknowledgment

This work was supported by the Deutsche Forschungsgemeinschaft (DFG) under ViViReq, Grant No.: 289386339, (2017–2019).

References

  1. 1.
    ISO/IEC/IEEE 29148:2011: Systems and Software Engineering - Life Cycle Processes - Requirements Engineering (2011)Google Scholar
  2. 2.
    Abad, Z.S.H., Noaeen, M., Ruhe, G.: Requirements engineering visualization: a systematic literature review. In: 24th IEEE International Requirements Engineering Conference (2016)Google Scholar
  3. 3.
    Al-Rawas, A., Easterbrook, S.: Communication problems in requirements engineering: a field study (1996)Google Scholar
  4. 4.
    Baum, T., Leßmann, H., Schneider, K.: The choice of code review process: a survey on the state of the practice. In: Felderer, M., Méndez Fernández, D., Turhan, B., Kalinowski, M., Sarro, F., Winkler, D. (eds.) PROFES 2017. LNCS, vol. 10611, pp. 111–127. Springer, Cham (2017).  https://doi.org/10.1007/978-3-319-69926-4_9CrossRefGoogle Scholar
  5. 5.
    Brill, O., Schneider, K., Knauss, E.: Videos vs. use cases: can videos capture more requirements under time pressure? In: Wieringa, R., Persson, A. (eds.) REFSQ 2010. LNCS, vol. 6182, pp. 30–44. Springer, Heidelberg (2010).  https://doi.org/10.1007/978-3-642-14192-8_5CrossRefGoogle Scholar
  6. 6.
    Carter, L.R., Karatsolis, A.: Lessons from trying to develop a robust documentation exemplar. In: Proceedings of the 27th ACM International Conference on Design of Communication (2009)Google Scholar
  7. 7.
    Creighton, O., Ott, M., Bruegge, B.: Software cinema - video-based requirements engineering. In: 14th IEEE International Requirements Engineering Conference (2006)Google Scholar
  8. 8.
    Feeney, W.: Documenting software using video. In: IEEE Workshop on Software Engineering Technology Transfer (1983)Google Scholar
  9. 9.
    Fricker, S., Glinz, M.: Comparison of requirements hand-off, analysis, and negotiation: case study. In: IEEE 18th International Conference on Requirements Engineering (2010)Google Scholar
  10. 10.
    Fricker, S.A., Grau, R., Zwingli, A.: Requirements engineering: best practice. In: Fricker, S.A., Thümmler, C., Gavras, A. (eds.) Requirements Engineering for Digital Health, pp. 25–46. Springer, Cham (2015).  https://doi.org/10.1007/978-3-319-09798-5_2CrossRefGoogle Scholar
  11. 11.
    Karras, O.: Survey data - attitudes towards video as a medium in requirements engineering (2018).  https://doi.org/10.5281/zenodo.1404742
  12. 12.
    Karras, O., Kiesling, S., Schneider, K.: Supporting requirements elicitation by tool-supported video analysis. in: 24th IEEE International Requirements Engineering Conference (2016)Google Scholar
  13. 13.
    Karras, O., Schneider, K.: Software professionals are not directors: what constitutes a good video? In: 26th IEEE International Requirements Engineering Conference Workshops (2018)Google Scholar
  14. 14.
    Karras, O., Unger-Windeler, C., Glauer, L., Schneider, K.: Video as a by-product of digital prototyping: capturing the dynamic aspect of interaction. In: 25th IEEE International Requirements Engineering Conference Workshops (2017)Google Scholar
  15. 15.
    Klünder, J., Karras, O., Kortum, F., Schneider, K.: Forecasting communication behavior in student software projects. In: 12th International Conference on Predictive Models and Data Analytics in Software Engineering (2016)Google Scholar
  16. 16.
    Lethbridge, T.C., Singer, J., Forward, A.: How software engineers use documentation: the state of the practice. IEEE Softw. 6, 35–39 (2003)CrossRefGoogle Scholar
  17. 17.
    Owens, J., Millerson, G.: Video Production Handbook, 5th edn. Focal Press, Oxford (2011)Google Scholar
  18. 18.
    Robson, C., McCartan, K.: Real World Research. Wiley, Hoboken (2016)Google Scholar
  19. 19.
    Saldaña, J.: The Coding Manual for Qualitative Researchers. Sage, London (2015)Google Scholar

Copyright information

© Springer Nature Switzerland AG 2018

Authors and Affiliations

  1. 1.Software Engineering GroupLeibniz Universität HannoverHannoverGermany

Personalised recommendations