Preprocessing of Requirements Specification

Authors:
Petr Kroha
Affiliations:
-
Venue:
DEXA '00 Proceedings of the 11th International Conference on Database and Expert Systems Applications
Year:
2000

Citing 11
Cited 2

Object-oriented software engineering

Object-oriented software engineering
Object-oriented analysis (2nd ed.)

Object-oriented analysis (2nd ed.)
Object behavior analysis

Communications of the ACM - Special issue on analysis and modeling in software development
Representation and Presentation of Requirements Knowledge

IEEE Transactions on Software Engineering
Objects and databases

Objects and databases
Why looking isn't always seeing: readership skills and graphical programming

Communications of the ACM
Mastering the requirements process

Mastering the requirements process
Requirements Specification Iteratively Combined with Reverse

SOFSEM '97 Proceedings of the 24th Seminar on Current Trends in Theory and Practice of Informatics: Theory and Practice of Informatics
Object-oriented Database Management Systems for Construction of CASE Environments

DDEXA '93 Proceedings of the 4th International Conference on Database and Expert Systems Applications
Effects of conceptual data modeling formalisms on user validation and analyst modeling of information requirements

Effects of conceptual data modeling formalisms on user validation and analyst modeling of information requirements
A fast and portable realizer for text generation systems

ANLC '97 Proceedings of the fifth conference on Applied natural language processing

Using Adaptive Programming in Legal Advisory Systems

DEXA '02 Proceedings of the 13th International Conference on Database and Expert Systems Applications
From requirements to UML models and back: how automatic processing of text can support requirements engineering

Software Quality Control

Quantified Score

Hi-index	0.00

Visualization

Abstract

In this paper, we discuss the part of the requirements specification process which is located between the textual requirements definition and the semi-formal diagrams of the requirements specification. It concerns the acquisition and the refinement of requirements and the consensus improvement between the analyst and the user. We argue that the existence of a textual description of requirements that represents the analyst's understanding of the problem will improve the efficiency of the requirements validation by the user. A method and a tool are introduced that support the acquisition, refining, and modeling of requirements, and finally the automatic generation of a textual description of the model for the validation.