A Process for Identifying Relevant Information for a Repository: A Case Study for Testing Techniques

One major issue in managing software engineering knowledge is the construction of information repositories for software development artifacts (techniques, products, processes, tools, and so on). But how does one package each artifact so that the package contains the appropriate information to understand and use the artifact? What is the appropriate characterization schema? This chapter proposes an empirical and iterative process to identify the information that should be used to characterize a software engineering artifact, using theoretical knowledge, practical experience, and expert opinion to generate a schema. The ultimate goal is to improve the schema and the package contents based upon it experience in their application. The proposed process has been applied to define a characterization schema for testing techniques. Nowadays, there are numerous testing techniques available for generating test cases. However, many of them are never used, while a few are used over and over again. Testers have little (if any) information about the available techniques, their usefulness and, generally, how suited they are to the project at hand. This lack of information means less appropriate decisions on which testing techniques to use. This chapter also shows this characterization schema and discusses the information it contains and why it is included in the schema.

[1]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[2]  Scott Henninger,et al.  Accelerating the successful reuse of problem solving knowledge through the domain lifecycle , 1996, Proceedings of Fourth IEEE International Conference on Software Reuse.

[3]  Neil A. M. Maiden,et al.  ACRE: selecting methods for requirements acquisition , 1996, Softw. Eng. J..

[4]  Victor R. Basili,et al.  Support for comprehensive reuse , 1991, Softw. Eng. J..

[5]  M. Lindvall,et al.  Knowledge management in software engineering , 2002, IEEE Software.

[6]  Victor R. Basili Implementing the Experience Factory concepts as a set of Experience Bases , 2001, SEKE.

[7]  Christiane Gresse von Wangenheim,et al.  REMEX - A Case-Based Approach for Reusing Software Measurement Experienceware , 1999, ICCBR.

[8]  Carsten Tautz,et al.  Systematic Population, Utilization, and Maintenance of a Repository for Comprehensive Reuse , 1999, SEKE.

[9]  Ricardo Miranda Barcia,et al.  Goal-Oriented and Similarity-Based Retrieval of Software Engineering Experienceware , 1999, SEKE.

[10]  R. Prieto-Diaz,et al.  Classification of reusable modules , 1989 .

[11]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[12]  Luc Lamontagne,et al.  Case-Based Reasoning Research and Development , 1997, Lecture Notes in Computer Science.

[13]  Veikko Seppänen,et al.  Toward a Practical Solution for Capturing Knowledge for Software Projects , 2002, IEEE Softw..

[14]  Norman E. Fenton,et al.  Software Measurement: Uncertainty and Causal Modeling , 2002, IEEE Softw..

[15]  Andreas Birk,et al.  Modelling the application domains of software engineering technologies , 1997, Proceedings 12th IEEE International Conference Automated Software Engineering.

[16]  Rubén Prieto-Díaz,et al.  Software reusability , 1993 .