{"references": ["[1] \"ISO/IEC 25010:2011: Systems and software engineering \u2013 Systems and software product quality requirements and evaluation (square) \u2013 System and software quality models\", 2011.", "[2] M. Glinz, \"A Glossary of Requirements Engineering Terminology\", 2014.", "[3] M. Luisa, F. Mariangela, and N. I. Pierluigi, \"Market research for requirements analysis using linguistic tools\", Requirements Engineering, vol. 9, no. 1, pp. 40\u201356, 2004.", "[4] S. Fricker and M. Glinz, \"Comparison of Requirements Hand-off, Analysis, and Negotiation: Case Study,\" in 2010 IEEE 18th International Conference on Requirements Engineering (RE).", "[5] M. Wieczorek, D. Vos, and H. Bons, Systems and Software Quality: The next step for industrialisation. Berlin, Heidelberg, s.l.: Springer Berlin Heidelberg, 2014.", "[6] S. W. Ambler, Agile modeling: Effective practices for eXtreme programming and the unified process. New York: Wiley, 2002.", "[7] S. A. Fricker, K. Schneider, F. Fotrousi, and C. Thuemmler, \"Workshop videos for requirements communication,\" Requirements Engineering, 2015.", "[8] C. Rupp, Requirements-Engineering und -Management: Aus der Praxis von klassisch bis agil, 6th Edition, M\u00fcnchen: Hanser, 2014.", "[9] M. Jirotka and P. Luff, \"Supporting requirements with video-based analysis,\" IEEE Software, vol. 23, no. 3, pp. 42\u201344, 2006.", "[10] F. Brun-Cottan and P. Wall, \"Using video to re-present the user,\" Commun. ACM, vol. 38, no. 5, pp. 61\u201371, 1995.", "[11] T. DeMarco and C. Geertgens, \"Experience Report: Use of Video for Program Documentation,\" in Proceedings of the 12th international conference on Software engineering, Los Alamitos, CA: IEEE Computer Society Press, 1990, pp. 126\u2013128.", "[12] O. Brill, K. Schneider, and E. Knauss, \"Videos vs. Use Cases: Can Videos Capture More Requirements under Time Pressure?,\" in Lecture Notes in Computer Science, Requirements Engineering: Foundation for Software Quality, D. Hutchison et al. , Eds, Berlin, Heidelberg: Springer Berlin Heidelberg, 2010, pp. 30\u201344.", "[13] O. Creighton, M. Ott, and B. Bruegge, \"Software Cinema-Video-based Requirements Engineering,\" in 14th IEEE International Requirements Engineering Conference, pp. 109\u2013118.", "[14] K. Schneider, \"Anforderungskl\u00e4rung mit Videoclips,\" in GI-Edition Proceedings, vol. 159, Software Engineering 2010: Fachtagung des GI-Fachbereichs Softwaretechnik, Paderborn, G. Engels and M. Luckey, Eds, Bonn: Ges. f\u00fcr Informatik, 2010.", "[15] P. J. Guo, J. Kim, and R. Rubin, \"How video production affects student engagement,\" in the first ACM conference, pp. 41\u201350.", "[16] E. Lackner, M. Ebner, and M. Kopp, \"How to MOOC? A pedagogical guideline for practitioners,\" 2014.", "[17] W. E. Mackay, \"Ethics, lies and videotape\u2026,\" in the SIGCHI conference, pp. 138\u2013145.", "[18] C. Plaisant and B. Shneiderman, \"Show Me! Guidelines for Producing Recorded Demonstrations,\" in 2005 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC'05), pp. 171\u2013178.", "[19] L. R. Carter and A. Karatsolis, \"Lessons from trying to develop a robust documentation exemplar,\" in the 27th ACM international conference, p. 199.", "[20] K. Schneider, \"Rationale as a By-Product,\" in Rationale Management in Software Engineering, A. H. Dutoit, R. McCall, I. Mistr\u00edk, and B. Paech, Eds: Springer Berlin Heidelberg, 2006", "[21] E. Sauerwein, Das Kano-Modell der Kundenzufriedenheit: Reliabilit\u00e4t und Validit\u00e4t einer Methode zur Klassifizierung von Produkteigenschaften. Univ., Diss. \u2013 Innsbruck, 1998. Wiesbaden: Dt. Univ.-Verl, 2000."]}

Requirements for a software product are mainly shared through a textual specification. One key ability in successful software organizations is a good requirements communication based on understandable information. Developers can only implement a useful and satisfying software product if they obtain and understand requirements properly. One challenge of writing requirements is to describe complex and interactive contents in an understandable manner. Videos offer a large potential to achieve such an easy-to-understand representation. Attached videos can enhance the reader’s understanding by using them as supplementary material for specifications. Despite their large potential, videos are not an established part of requirements specifications: The effort to produce videos is high, the corresponding motivation is low and the use of videos is cumbersome due to missing links between requirements and videos. We propose guidelines to support the identification of content which is appropriate to be supplemented by videos. We develope a starting set of guidelines that consider the different information types of a requirements specification with their presentation modes and characteristics. This paper presents an overview of our findings about improving the content-related linking between requirements and videos. We discuss the perspectives, advantages and obstacles for enhancing the comprehensibility of textual requirements conveyed by videos.