Centering: a framework for modeling the local coherence of discourse
Computational Linguistics
Guiding the construction of textual use case specifications
Data & Knowledge Engineering - Special jubilee issue: DKE 25
Program design by informal English descriptions
Communications of the ACM
AbstFinder, A Prototype Natural Language Text Abstraction Finder for Use in Requirements Elicitation
Automated Software Engineering
SEW '01 Proceedings of the 26th Annual NASA Goddard Software Engineering Workshop
Market research for requirements analysis using linguistic tools
Requirements Engineering
Modeling Interactions using Role-Driven Patterns
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Translation of Textual Specifications to Automata by Means of Discourse Context Modeling
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
Scenario Analysis: Generation of Possible Scenario Interpretations and their Visualization
REV '09 Proceedings of the 2009 Fourth International Workshop on Requirements Engineering Visualization
NLDB'09 Proceedings of the 14th international conference on Applications of Natural Language to Information Systems
| Hi-index | 0.00 |
Requirements engineering, the first phase of any software development project, is the Achilles' heel of the whole development process, as requirements documents are often inconsistent and incomplete. In industrial requirements documents natural language is the main presentation means. In such documents the system behavior is specified in the form of use cases and their scenarios, written as a sequence of sentences in natural language. For the authors of requirements documents some facts are so obvious that they forget to mention them. This surely causes problems for the requirements analyst. Missing information manifests itself, for example, in sentences in passive voice: such sentences just say that some action is performed, but they do not say who performs the action. In the case of requirement analysis this poses a serious problem, as in every real system there is an actor for every performed action. There already exists an approach able to guess missing actors and actions. However, the existing approach is able to handle sentences containing exactly one verb only. The approach presented in this paper extends the existing one by treatment of compound sentences and passive voice. Feasibility of the presented approach to the treatment of passive and conjunctions was confirmed in a case study.