Analogical retrieval in reuse-oriented requirements engineering

Computational mechanisms are presented for analogical retrieval of domain knowledge as a basis for intelligent tool-based assistance for requirements engineers. A first mechanism, called the domain matcher, retrieves object system models which describe key features for new problems. A second mechanism, called the problem classifier, reasons with analogical mappings inferred by the domain matcher to detect potential incompleteness, overspecification and inconsistencies in entered facts and requirements. Both mechanisms are embedded in AIR, a toolkit that provides co-operative reuse-oriented assistance for requirements engineers.

[1]  Panos Constantopoulos,et al.  Similarity for Analogical Software Reuse: A Conceptual Modelling Approach , 1993, CAiSE.

[2]  Hans Albrecht Schmid,et al.  Software Reuse through Building Blocks , 1987, IEEE Software.

[3]  Rubén Prieto-Díaz Implementing faceted classification for software reuse , 1991, CACM.

[4]  Janis A. Bubenko,et al.  Theories underlying requirements engineering: an overview of NATURE at Genesis , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[5]  Bruce A. Burton,et al.  The Reusable Software Library , 1987, IEEE Software.

[6]  Russell Greiner,et al.  Learning by Understanding Analogies , 1986, Artif. Intell..

[7]  K. Branting,et al.  Building Explanations from Rules and Structured Cases , 1991, Int. J. Man Mach. Stud..

[8]  Brian Falkenhainer,et al.  The Structure-Mapping Engine: Algorithm and Examples , 1989, Artif. Intell..

[9]  Paul Thagard,et al.  Analogical Mapping by Constraint Satisfaction , 1989, Cogn. Sci..

[10]  Peter Freeman,et al.  Classifying Software for Reusability , 1987, IEEE Software.

[11]  Matthias Jarke,et al.  Telos: representing knowledge about information systems , 1990, TOIS.

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

[13]  Neil A. M. Maiden,et al.  Requirements critiquing using domain abstractions , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[14]  Bertrand Meyer,et al.  On Formalism in Specifications , 1985, IEEE Software.

[15]  Mary Shaw Heterogeneous design idioms for software architecture , 1991, Proceedings of the Sixth International Workshop on Software Specification and Design.

[16]  Neil A. M. Maiden,et al.  Bridging the requirements gap: policies, goals and domains , 1993, Proceedings of 1993 IEEE 7th International Workshop on Software Specification and Design.

[17]  G. Lakoff,et al.  Women, Fire, and Dangerous Things: What Categories Reveal about the Mind , 1988 .

[18]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[19]  D. Gentner Structure‐Mapping: A Theoretical Framework for Analogy* , 1983 .

[20]  Neil A. M. Maiden,et al.  Exploiting reusable specifications through analogy , 1992, CACM.

[21]  Gerhard Fischer,et al.  Domain-oriented design environments , 1992, Proceedings of the Seventh Knowledge-Based Software Engineering Conference.

[22]  Matthias Jarke,et al.  Computational Mechanisms for Distributed Requirements Engineering , 1995, SEKE.

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

[24]  Martin S. Feather,et al.  Representation and Presentation of Requirements Knowledge , 1992, IEEE Trans. Software Eng..