Phalp, K. T., Adlem, A., Jeary, S. and Vincent, J., 2009. Comprehension, Use Cases and Requirements. In: Dawson, R., Ross, M. and Staples, G., eds. Software Quality in the 21st Century: Software Quality Management XVII. The British Computer Society, pp. 207-218.
This is the latest version of this eprint.
Full text available as:
|PDF (Version accepted for SQM conference) - Submitted Version|
Official URL: http://sqm.lboro.ac.uk/
Within requirements engineering it is generally accepted that in writing specifications (or indeed any requirements phase document), one attempts to produce an artefact which will be simple to comprehend for the user. That is, whether the document is intended for customers to validate requirements, or engineers to understand what the design must deliver, comprehension is an important goal for the author. Indeed, advice on producing ‘readable’ or ‘understandable’ documents is often included in courses on requirements engineering. However, few researchers, particularly within the software engineering domain, have attempted either to define or to understand the nature of comprehension and it’s implications for guidance on the production of quality requirements. In contrast, this paper examines thoroughly the nature of textual comprehension, drawing heavily from research in discourse process, and suggests some implications for requirements (and other) software documentation. In essence, we find that the guidance on writing requirements, often prevalent within software engineering, may be based upon assumptions which are an oversimplification of the nature of comprehension. Furthermore, that these assumptions may lead to rules which detract from the quality of the requirements document and, thus, the understanding gained by the reader. Finally the paper suggests lessons learned which may be useful in formulating future guidance for the production of requirements documentation.
|Item Type:||Book Section|
|Number of Pages:||230|
|Uncontrolled Keywords:||comprehension, requirements, use cases, software quality, quality assurance, quality, understanding, specification|
|Subjects:||Generalities > Computer Science and Informatics|
|Group:||School of Design, Engineering & Computing > Software Systems Research Centre|
|Deposited By:||Dr Keith Phalp|
|Deposited On:||03 Oct 2009 14:14|
|Last Modified:||07 Mar 2013 15:15|
Available Versions of this Item
- Comprehension, Use Cases and Requirements. (deposited 04 Aug 2009 18:13)
- Comprehension, Use Cases and Requirements. (deposited 03 Oct 2009 14:14) [Currently Displayed]
Document DownloadsMore statistics for this item...
|Repository Staff Only -|
|BU Staff Only -|
|Help Guide -||Editing Your Items in BURO|