An experiment on the impact of transparency on the effectiveness of requirements documents

Show simple item record Tu, Yu-Cheng en Tempero, Ewan en Thomborson, Clark en 2016-09-12T04:04:49Z en 2016-06 en
dc.identifier.citation Empirical Software Engineering, 2016, 21 (3), pp. 1035 - 1066 (32) en
dc.identifier.issn 1382-3256 en
dc.identifier.uri en
dc.description.abstract Effective communication is important to successful software development, but it is difficult to achieve. We believe transparency — the visibility of information to stakeholders — is an important factor in the effectiveness of communication in software projects. We theorise that more effective communication results from more transparent requirements documents. To test our theory, we conducted an experiment. We developed an operational definition of transparency with three attributes: accessibility, understandability, and relevance. We had students and software practitioners use requirements documents of differing levels of transparency based on these attributes to answer questions. We found that participants with the more transparent document spent less time, answered more questions correctly, and were more confident about their answers, than participants with the less transparent document. The results of our experiment provide evidence that our view of transparency may help evaluate the effectiveness of documents as a form of communication. Further work is needed to reproduce our results, and to determine whether they are generalizable to other types of stakeholders and forms of communication. en
dc.description.uri en
dc.language English en
dc.publisher Springer en
dc.relation.ispartofseries Empirical Software Engineering en
dc.rights Items in ResearchSpace are protected by copyright, with all rights reserved, unless otherwise indicated. Previously published items are made available in accordance with the copyright policy of the publisher. Details obtained from en
dc.rights.uri en
dc.title An experiment on the impact of transparency on the effectiveness of requirements documents en
dc.type Journal Article en
dc.identifier.doi 10.1007/s10664-015-9374-8 en
pubs.issue 3 en
pubs.begin-page 1035 en
pubs.volume 21 en
dc.description.version AM - Accepted manuscript en en
pubs.end-page 1066 en
pubs.publication-status Published en
dc.rights.accessrights en
pubs.subtype Article en
pubs.elements-id 477392 en Science en School of Computer Science en
dc.identifier.eissn 1573-7616 en
pubs.record-created-at-source-date 2016-09-12 en 2015-02-26 en

Files in this item

Find Full text

This item appears in the following Collection(s)

Show simple item record


Search ResearchSpace