A case study in systematic improvement of language for requirements

Proceedings of the IEEE International Conference on Requirements Engineering

Volumn , Issue , 2006, Pages 6-15

  Wasson, Kimberly S ^a  

^a University of Virginia   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMMUNICATING REQUIREMENTS; SYSTEMATIC IMPROVEMENT;

COGNITIVE SYSTEMS; COMMUNICATION SYSTEMS; PROJECT MANAGEMENT; REQUIREMENTS ENGINEERING; SEMANTICS;

LINGUISTICS;

EID: 34748829296     PISSN: 1090705X     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/RE.2006.5     Document Type: Conference Paper

References (18)

1. D. Berry. The importance of ignorance in requirements engineering. Journal of Systems and Software, 28:179-184, 1995.
2. D. Gause and G. Weinberg, Exploring Requirements: Quality Before Design, Dorset House, 1989.
3. C. Goddard, Semantic Analysis, Oxford University Press, Oxford, 1998.
4. Goddard, C. and Wierzbicka, A., eds., Semantic and Lexical Universals, John Benjamins Publishing Company, Amsterdam, 1994.
5. K. S. Hanks, and J. C. Knight, "Improving Communication of Critical Domain Knowledge in High-Consequence Software Development: an Empirical Study." 21st International System Safety Conference (ISSC'03), Ottawa, Canada (August, 2003)
6. K. Hanks, J. Knight, and C.M. Holloway. The Role of Natural Language in Accident Investigation and Reporting Guidelines. Proc. 2002 Workshop on the Investigation and Reporting of Incidents and Accidents, Glasgow, July 2002.
7. K.S. Hanks, J.C. Knight, and E.A. Strunk, "A Linguistic Analysis of Requirements Errors and Its Application," University of Virginia, Department of Computer Science, Technical Report CS-2001-30, November 2001.
8. K.S. Hanks, J.C. Knight, and E.A. Strunk, "Erroneous Requirements: A Linguistic Basis for Their Occurrence and an Approach to Their Reduction," Proc. 26th NASA Goddard Software Eng Workshop, IEEE, Greenbelt, MD, Nov., 2001.
9. Heninger, K., "Specifying Requirements for Complex Systems: New Techniques and Their Applications", IEEE Transactions on Software Engineering, SE-6(1):2-12, 1980.
10. Jackson, M., Software Requirements and Specifications, Addison-Wesley, Wokingham, 1995.
11. E. Kamsties, D. Berry and B. Paech, Detecting Ambiguities in Requirements Documents Using Inspections, Proc. First Workshop on Inspection in Software Engineering (WISE'01), July 23, 2001, Paris, pp. 68-80.
12. Oxford Paperback Dictionary, Oxford University Press, Oxford, 1979.
13. Pressman, R., Software Engineering: A Practitioner's Approach (5th ed.), McGraw-Hill, Boston, 2001.
14. Sommerville, I. and Sawyer, P., Requirements Engineering: A Good Practice Guide, John Wiley and Sons, Chichester, 1997.
15. K. Wasson, "Partial Reductive Paraphrase: Toward More Transparent Requirements," University of Virginia Department of Computer Science Technical Report CS-2004-16, May 2004.
16. K. Wasson, K. Schmid, R, Lutz, and J. Knight. Using Occurrence Properties of Defect Report Data to Improve Requirements. Proc. 13th IEEE Requirements Engineering Conference (RE'05), Aug 29-Sept 2, 2005, Paris, pp. 253-262.
17. K. A. Weiss, N. Leveson, K. Lundqvist, N. Farid, and M. Stringfellow, "An Analysis of Causation in Aerospace Accidents," Space, 2001, Aug., 2001.
18. R. K. Yin, Case Study Research: Design and Methods, 3e, Sage Publications, Thousand Oaks, 2003.