Engineering Experience Base Maintenance Knowledge

The value of a corporate information system such as an experience base tends to degrade with time. To keep the value of such a system, maintenance is an essential. Maintenance should not simply happen ad-hoc but systematically and based on specific maintenance knowledge. As a jump-start for maintenance, maintenance knowledge should be available right from the start of continuous operation. This paper describes how to systematically develop ("to engineer") such maintenance knowledge during buildup of the corporate information system.

[1]  John J. Marciniak,et al.  Encyclopedia of Software Engineering , 1994, Encyclopedia of Software Engineering.

[2]  Alain Abran,et al.  BALANCED SCORECARDS AND GQM: WHAT ARE THE DIFFERENCES? , 2000 .

[3]  Kai Romhardt,et al.  Die Organisation aus der Wissensperspektive : Möglichkeiten und Grenzen der Intervention , 1998 .

[4]  Barry Smyth,et al.  Competence-guided Editing Methods for Lazy Learning , 2000, ECAI.

[5]  Tim Menzies,et al.  Knowledge maintenance: the state of the art , 1999, The Knowledge Engineering Review.

[6]  David C. Wilson,et al.  Categorizing Case-Base Maintenance: Dimensions and Directions , 1998, EWCBR.

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

[8]  Kai Romhardt.  Die Organisation aus der Wissensperspektive , 1998 .

[9]  Thomas Roth-Berghofer,et al.  On Quality Measures for Case Base Maintenance , 2000, EWCBR.

[10]  Ralph Bergmann,et al.  Experience Management: Foundations, Development Methodology, and Internet-Based Applications , 2002 .

[11]  E. Ziegel,et al.  The Balanced Scorecard , 1998 .

[12]  E. Ziegel,et al.  Balanced Scorecard , 2019, Encyclopedia of Public Administration and Public Policy, Third Edition.

[13]  D. L. Flarey.  Reengineering the Corporation , 1994 .

[14]  E. Burton Swanson,et al.  The dimensions of maintenance , 1976, ICSE '76.

[15]  Carsten Tautz,et al.  Improving Organizational Memories Through User Feedback , 2000 .

[16]  Victor R. Basili,et al.  A reference architecture for the component factory , 1992, TSEM.

[17]  Sean Breen,et al.  Developing Industrial Case-Based Reasoning Applications: The INRECA Methodology , 1999 .

[18]  R. Dorf,et al.  The Balanced Scorecard: Translating Strategy Into Action , 1997, Proceedings of the IEEE.

[19]  H. D. Rombach,et al.  THE EXPERIENCE FACTORY , 1999 .

[20]  Carsten Tautz,et al.  Practical Evaluation of an Organizational Memory Using the Goal-Question-Metric Technique , 1999, XPS.

[21]  Raimund L. Feldmann,et al.  Guidelines for Evaluation and Improvement of Reuse and Experience Repository Systems through Measurement Programs , 2000 .

[22]  Carsten Tautz,et al.  Costumizing software engineering experience management systems to organizational needs , 2001 .

[23]  Janet L. Kolodner,et al.  Case-Based Reasoning , 1989, IJCAI 1989.

[24]  Carsten Tautz,et al.  Systematic Maintenance of Corporate Experience Repositories , 2001, Comput. Intell..

[25]  Mike Bourne,et al.  Translating strategy into action , 1998 .

[26]  Carsten Tautz,et al.  A Case-Based Reasoning Approach for Managing Qualitative Experience , 2000 .

[27]  Frank Puppe,et al.  XPS-99: Knowledge-Based Systems. Survey and Future Directions , 1999, Lecture Notes in Computer Science.