2016 IEEE 24th International Requirements Engineering Conference (RE) (2016)
Sept. 12, 2016 to Sept. 16, 2016
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/RE.2016.37
With the emergence and spread of agile processes, the practices of writing and maintaining documentation have drastically changed in the last decade. In this work, we performed a qualitative study to explore the current practices for managing two related types of software documentation: requirements and acceptance tests. We interviewed twenty practitioners from seventeen business units in fifteen companies to investigate the companies' practices for writing, maintaining and linking requirements and acceptance test documentation. The study yields interesting and partially unexpected results. For example, we had expected that tests would be more extensively documented than requirements, while we found a strong linear correlation between the number of requirements and tests in our sample. We also found that technical people are usually not involved in the requirements engineering activities, which often results in misunderstood or underestimated requirements. Acceptance tests are written, in many cases, based on requirements that are not necessarily detailed enough. Also, acceptance tests are not regularly maintained, which occasionally results in confusing features and bugs.
Companies, Interviews, Documentation, Software, Testing, Requirements engineering
S. Hotomski, E. B. Charrada and M. Glinz, "An Exploratory Study on Handling Requirements and Acceptance Test Documentation in Industry," 2016 IEEE 24th International Requirements Engineering Conference (RE), Beijing, China, 2016, pp. 116-125.