Requirements Classification and Reuse: Crossing Domain Boundaries

A serious problem in the classification of software project artefacts for reuse is the natural partitioning of classification terms into many separate domains of discourse. This problem is particularly pronounced when dealing with requirements artefacts that need to be matched with design components in the refinement process. In such a case, requirements can be described with terms drawn from a problem domain (e.g. games), whereas designs with the use of terms characteristic for the solution domain (e.g. implementation). The two domains have not only distinct terminology, but also different semantics and use of their artefacts. This paper describes a method of cross-domain classification of requirements texts with a view to facilitate their reuse and their refinement into reusable design components.

[1]  W. Lam,et al.  A case-;study of requirements reuse through product families , 1998, Ann. Softw. Eng..

[2]  Maria Grazia Fugini,et al.  Reusing Specifications in OO Applications , 1995, IEEE Softw..

[3]  Alan M. Davis.  Predictions and Farewells , 1998, IEEE Softw..

[4]  K. Ochimizu,et al.  Design of a hyper media tool to support requirements elicitation meetings , 1995, Proceedings Seventh International Workshop on Computer-Aided Software Engineering.

[5]  Gerard Salton,et al.  Automatic Text Processing: The Transformation, Analysis, and Retrieval of Information by Computer , 1989 .

[6]  William B. Frakes,et al.  An Empirical Study of Representation Methods for Reusable Software Components , 1994, IEEE Trans. Software Eng..

[7]  Hermann Kaindl,et al.  The missing link in requirements engineering , 1993, SOEN.

[8]  Victor R. Basili,et al.  Viewing maintenance as reuse-oriented software development , 1990, IEEE Software.

[9]  Bertrand Ibrahim,et al.  A software reuse system based on natural language specifications , 1993, Proceedings of ICCI'93: 5th International Conference on Computing and Information.

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

[11]  Kyo Chul Kang,et al.  Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .

[12]  Jeffrey S. Poulin,et al.  Integrated support for software reuse in Computer-Aided Software Engineering (CASE) , 1993, SOEN.

[13]  M. D. Lubars.  Wide-spectrum support for software reusability , 1988 .

[14]  Yoshihiro Matsumoto,et al.  Some Experiences in Promoting Reusable Software: Presentation in Higher Abstract Levels , 1984, IEEE Transactions on Software Engineering.

[15]  Janis A. Bubenko,et al.  Facilitating "fuzzy to formal" requirements modelling , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[16]  Michael R. Lowry,et al.  Knowledge-based software engineering , 1989 .

[17]  Maria Grazia Fugini,et al.  Retrieval of reusable components in a development information system , 1993, [1993] Proceedings Advances in Software Reuse.

[18]  Alan M. Davis.  More Words Of Wisdom , 1998, IEEE Software.

[19]  B. Allen,et al.  A Knowledge-based Environment For The Development Of Software Parts Composition Systems , 1989, 11th International Conference on Software Engineering.

[20]  Rubén Prieto-Díaz,et al.  DARE: Domain analysis and reuse environment , 1998, Ann. Softw. Eng..

[21]  Hamid Mcheick,et al.  Another nail to the coffin of faceted controlled-vocabulary component classification and retrieval , 1997, SSR '97.

[22]  Guillermo Arango,et al.  Domain Analysis and Software Systems Modeling , 1991 .

[23]  Daniel M. Berry,et al.  The use of a repeated phrase finder in requirements extraction , 1990, J. Syst. Softw..

[24]  Martin Wirsing,et al.  MENU - An Example for the Systematic Reuse of Specifications , 1989, ESEC.

[25]  Martin Fowler,et al.  Analysis patterns - reusable object models , 1996, Addison-Wesley series in object-oriented software engineering.

[26]  Piero Torrigiani,et al.  ASPIS: a knowledge-based CASE environment , 1988, IEEE Software.

[27]  Neil A. M. Maiden,et al.  Analogical Matching For Specification , 1991, Proceedings., 6th Annual Knowledge-Based Software Engineering Conference.

[28]  S. Castano,et al.  The F3 reuse environment for requirements engineering , 1994, SOEN.

[29]  Kathryn P. Yglesias.  Information Reuse Parallels Software Reuse , 1993, IBM Syst. J..

[30]  M. D. Lubars,et al.  Addressing software reuse through knowledge-based design , 1989 .

[31]  Walt Scacchi,et al.  A hypertext system to manage software life cycle documents , 1988 .

[32]  Ruben Prieto-Diaz,et al.  Domain analysis for reusability , 1988 .

[33]  W. Lewis Johnson,et al.  Sharing And Reuse Of Requirements Knowledge , 1991, Proceedings., 6th Annual Knowledge-Based Software Engineering Conference.

[34]  K. P. Yglesias.  Technical forum: information reuse parallels software reuse , 1993 .

[35]  W. W. Agresti,et al.  The Minnowbrook workshop on software reuse: a summary report , 1988 .

[36]  T. Tamai.  Applying the knowledge engineering approach to software development , 1990 .

[37]  Kyo Chul Kang,et al.  A Reuse-based software development methodology , 1988 .

[38]  Barr and Feigenbaum Edward A. Avron,et al.  The Handbook of Artificial Intelligence , 1981 .

[39]  Will Tracz,et al.  Software reuse - emerging technology , 1988 .

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

[41]  Yoshihiro Matsumoto,et al.  Japanese Perspectives in Software Engineering , 1989 .

[42]  Sadahiro Isoda,et al.  Success factors of systematic reuse , 1994, IEEE Software.

[43]  Kacem Zeroual,et al.  KBRAS: Knowledge-based Requirements Acquisition System , 1991, Proceedings., 6th Annual Knowledge-Based Software Engineering Conference.

[44]  Jacob L. Cybulski,et al.  Automating Requirements Refinement with Cross-Domain Requirements Classification , 1999, Australas. J. Inf. Syst..