Skip to main content
Article thumbnail
Location of Repository

Comprehension, Use Cases and Requirements

By Keith T. Phalp, A. Adlem, Sherry Jeary and Jonathan Vincent


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.\ud 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

Topics: csi
Publisher: The British Computer Society
Year: 2009
OAI identifier:

Suggested articles


  1. (1996). A “landscape” view of reading: fluctuating patterns of activation and the construction of a stable memory representation.
  2. (1988). A field study of the software design process for large systems. doi
  3. (1996). A model of narrative comprehension and recall.
  4. (2002). An introduction to requirements engineering. doi
  5. (1996). Are good texts always better? Interactions of text coherence, background knowledge, and levels of understanding in learning from text. doi
  6. (1994). Choice of passive voice is affected by verb type and animacy. doi
  7. (1994). Constructing inferences during narrative text comprehension. doi
  8. (1997). Discourse comprehension. doi
  9. (1996). Effects of prior knowledge on text comprehension: a simple modeling approach.
  10. (1996). Extending capacityconstrained construction integration: toward “smarter” and flexible models of text comprehension.
  11. (2003). Introduction to the handbook of discourse processes. doi
  12. (1987). Knowledge organization and text organization. doi
  13. (2002). Language comprehenders mentally represent the shapes of objects. doi
  14. (1996). Learning from text: Effects of prior knowledge and text coherence. doi
  15. (1996). Metaphor as a constraint on text
  16. (1995). Pronominalization and discourse coherence, discourse structure and pronoun interpretation. doi
  17. (1992). Pronoun resolution and discourse models. doi
  18. (1996). Pronoun resolution without pronouns: some consequences of memory-based text processing. doi
  19. (1993). Pronouns, names, and the centering of attention in discourse. doi
  20. (1995). Pronouns, passives, and discourse coherence. doi
  21. (2003). Quantitative cognitive models of text and discourse processing.
  22. (1998). Software Runaways. doi
  23. (1983). Strategies of Discourse Comprehension: doi
  24. (2003). Text comprehension.
  25. (1997). The Cambridge encyclopedia of language. 2 nd ed. Cambridge: doi
  26. (1997). The Cambridge encyclopedia of language. 2nd ed. Cambridge: doi
  27. (1968). The choice of the passive voice in a communicative task. doi
  28. (2001). The effect of implied orientation derived from verbal context on picture recognition. doi
  29. (2003). The misinterpretation of noncanonical sentences. doi
  30. (2001). The psychology of language: From data to theory. 2 nd ed. doi
  31. (2001). The psychology of language: From data to theory. 2nd ed. doi
  32. (1996). The structure-building framework: what it is, what it might also
  33. (1978). Toward a model of text comprehension and production. doi
  34. (2000). Use cases: requirements in context. London: doi
  35. (1991). Using Kintsch’s computational model to improve instructional text: effects of repairing inference calls on recall and cognitive structures. doi
  36. (2001). Writing effective use cases. doi
  37. (2001). Writing effective use cases. London:

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.