Abstract
This paper presents the results of an investigation of natural language specifications created in industrial projects in Germany. One goal of the investigation was to gain an insight into the state of the practice. The objects of the investigation were the requirements documents and the requirements processes. The following aspects were uppermost in my mind when examining the requirements documents: structure of the documents, kinds of information found in the documents, and notations used to express the information. When interviewing the system analysts, the following aspects were most important: usage of tools, change management, communication with the customers, and verification and validation of the documents.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Gaudel M-C. Formal specification techniques. In: Proceedings of the 16th international conference on software engineering Sorrento, Italy, 1621 May 1994, pp 223–227
Rumbaugh J, Jacobson I, Booch G. The unified modeling language, documentation set 1.0. Rational Software Corporation, Santa Clara, 1997.
Dorfman M, Thayer R. Standards, guidelines and examples on system and software requirements engineering. IEEE Computer Society, New York 1990
IEEE. IEEE recommended practice for software requirements specifications. IEEE STD 830-1993, IEEE Computer Society, New York, 1993
DeMarco T. Structured analysis and system specification. Prentice-Hall, Englewood Cliffs, NJ, 1982
Coad P, Yourdon E. Object-oriented analysis (2nd edn). Prentice-Hall, Englewood Cliffs, NJ, 1991
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Melchisedech, R. Investigation of requirements documents written in natural language. Requirements Eng 3, 91–97 (1998). https://doi.org/10.1007/BF02919968
Issue Date:
DOI: https://doi.org/10.1007/BF02919968