Domain Knowledge Reuse During Requirements Engineering

The accurate capture, understanding and representation of requirements is a critical step in the construction of effective and usable information systems. This activity is highly cognitive and is people and knowledge intensive; its success or failure is significantly influenced by the skills and especially the previous experience of the development staff involved. Many of the processes of requirements engineering are not well defined and remain difficult and problematic, significantly the initial investigation, elicitation and checking of requirements are poorly supported by current development tools and development methods. This paper describes research within the field of requirements engineering which draws upon AI/KBS research to adopt a knowledge based approach for requirements capture, modelling and validation and encourage the reuse of knowledge about typical information system applications and domains during such activities.

[1]  Guy Fitzgerald,et al.  Feature Analysis of Contemporary Information Systems Methodologies , 1985, Comput. J..

[2]  Neil A. M. Maiden,et al.  Requirements engineering by example: an empirical study , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[3]  Pericles Loucopoulos,et al.  A Knowledge-Based Requirements Engineering Support Environment , 1988 .

[4]  Neil A. M. Maiden,et al.  Analogical specification reuse during requirements analysis , 1992 .

[5]  John Mylopoulos,et al.  Capturing more world knowledge in the requirements specification , 1982, ICSE '82.

[6]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[7]  John T. Nosek,et al.  User Validation of Information System Requirements: Some Empirical Results , 1988, IEEE Trans. Software Eng..

[8]  Henk Sol,et al.  Proc. of the IFIP WG 8.1 working conference on Information systems design methodologies: improving the practice , 1986 .

[9]  Eckhard D. Falkenberg,et al.  Knowledge-Based Information Analysis Support , 1988, DS-3.

[10]  Christiane Floyd,et al.  A Comparative Evaluation of System Development Methods , 1986, Information Systems Design Methodologies: Improving the Practice.

[11]  Pericles Loucopoulos,et al.  Knowledge-Based Support for Requirements Engineering , 1989, CASE.

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

[13]  Richard C. Waters,et al.  The Requirements Apprentice: Automated Assistance for Requirements Acquisition , 1991, IEEE Trans. Software Eng..

[14]  Alan M. Davis,et al.  Guest Editors' Introduction Requirements Engineering , 1991, IEEE Trans. Software Eng..

[15]  Charles J. Fillmore,et al.  THE CASE FOR CASE. , 1967 .

[16]  John F. Sowa,et al.  Conceptual Structures: Information Processing in Mind and Machine , 1983 .

[17]  Michael Lloyd-Williams,et al.  Knowledge-based CASE tools: improving performance using domain-specific knowledge , 1994, Softw. Eng. J..

[18]  William F. Clocksin,et al.  Programming in Prolog , 1981, Springer Berlin Heidelberg.

[19]  Frederick Hayes-Roth,et al.  Rule-based systems , 1985, CACM.