KBRAS: Knowledge-based Requirements Acquisition System

One of the problems currently facing developers of software systems is the acquisition of software requirements. This paper presents an approach to the automation of an interactive elicitation of the requirements from domain users. The Knowledge-based Requirements Acquisition System (KBRAS) automates the process of acquiring software requirements by providing users with several powerful eliciting and modeling facilities. It focuses particularly on how to bridge the gap between the informal and formal specifications.

[1]  Robert Balzer,et al.  Kestrel Institute: REPORT ON A KNOWLEDGE-BASED SOFTWARE ASSISTANT , 1986 .

[2]  Stephen Fickas,et al.  Automating the Transformational Development of Software , 1985, IEEE Transactions on Software Engineering.

[3]  Philip J. Barnard,et al.  Approximate Modelling of Cognitive Activity with and Expert System: A Theory-Based Strategy for Developing an Interactive Design Tool , 1988, Computer/law journal.

[4]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[5]  Barry W. Boehm,et al.  Verifying and Validating Software Requirements and Design Specifications , 1989, IEEE Software.

[6]  Mehdi T. Harandi,et al.  Knowledge-based software design using design schemas , 1987, ICSE '87.

[7]  John Mylopoulos,et al.  Knowledge Representation as the Basis for Requirements Specifications , 1985, Computer.

[8]  Dzenan Ridjanovic,et al.  On the Design and Specification of Database Transactions , 1982, On Conceptual Modelling.

[9]  Dewayne E. Perry,et al.  Software interconnection models , 1987, ICSE '87.

[10]  Hajime Enomoto,et al.  Software development process from natural language specification , 1989, ICSE '89.

[11]  Richard C. Waters,et al.  The Programmer's Apprentice: a research overview , 1988, Computer.

[12]  Allen Newell,et al.  Human Problem Solving. , 1973 .

[13]  Robert B Miller,et al.  A METHOD FOR MAN-MACHINE TASK ANALYSIS , 1953 .

[14]  Victor R. Basili,et al.  Software errors and complexity: an empirical investigation0 , 1984, CACM.

[15]  Alexander Borgida,et al.  Knowledge representations as the basis for requirements specifications , 1986 .

[16]  John H. Boose,et al.  Personal Construct Theory and the Transfer of Human Expertise , 1984, AAAI.

[17]  Guido Persch.  Automating the transformational development of software , 1987 .

[18]  Ronald J. Brachman,et al.  What IS-A Is and Isn't: An Analysis of Taxonomic Links in Semantic Networks , 1983, Computer.

[19]  Kacem Zeroual,et al.  Reasoning on requirement specifications: a deductive approach , 1989, [1989] Proceedings of the Thirteenth Annual International Computer Software & Applications Conference.

[20]  Victor R. Basili,et al.  Software errors and complexity: an empirical investigation , 1993 .

[21]  Robert Balzer,et al.  A 15 Year Perspective on Automatic Programming , 1985, IEEE Transactions on Software Engineering.

[22]  Martin S. Feather,et al.  Implementing Specification Freedoms , 1986, Sci. Comput. Program..