Technical requirements for the implementation of an experience base
Broomé, Mikael and Runeson, Per LU
(2000)
11th International Conference on Software Engineering and Knowledge Engineering, SEKE 1999
In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
1756.
p.87-102
- Abstract
Reuse of different types of experience is a key issue in successful improvement in software engineering. The approach taken in the Quality Improvement Paradigm (QIP) and its supporting organisation, tile Experience Factory (EF), is to define an Experience Base (EB), where all types of reusable objects are organised and stored. The objects may be of any type related to software development, for example, code, methods, quality models and specifications. Furthermore, not only objects identical to the target object needed can be reused, but also similar ones. This paper defines important concepts in a reuse context, elaborates a reuse scenario from which the requirements for the implementation of an Experience Base are derived. A list of 22... (More)
Reuse of different types of experience is a key issue in successful improvement in software engineering. The approach taken in the Quality Improvement Paradigm (QIP) and its supporting organisation, tile Experience Factory (EF), is to define an Experience Base (EB), where all types of reusable objects are organised and stored. The objects may be of any type related to software development, for example, code, methods, quality models and specifications. Furthermore, not only objects identical to the target object needed can be reused, but also similar ones. This paper defines important concepts in a reuse context, elaborates a reuse scenario from which the requirements for the implementation of an Experience Base are derived. A list of 22 technical requirements is defined which cover the functional aspects related to the use of an Experience Base. The evaluation of three alternative implementation approaches are presented as an example: two database alternatives and one based on Case-Based Reasoning (CBR). Future work is to investigate the costs for extending the functionality to fulfil the requirements and to use the requirements in a real setting.
(Less)
- author
- Broomé, Mikael
and Runeson, Per
LU
- organization
- publishing date
- 2000
- type
- Chapter in Book/Report/Conference proceeding
- publication status
- published
- subject
- host publication
- Learning Software Organizations : Methodology and Applications - 11th International Conference on Software Engineering and Knowledge Engineering, SEKE 1999, Proceedings - Methodology and Applications - 11th International Conference on Software Engineering and Knowledge Engineering, SEKE 1999, Proceedings
- series title
- Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
- editor
- Ruhe, Gunther and Bomarius, Frank
- volume
- 1756
- pages
- 16 pages
- publisher
- Springer
- conference name
- 11th International Conference on Software Engineering and Knowledge Engineering, SEKE 1999
- conference location
- Kaiserslautern, Germany
- conference dates
- 1999-06-16 - 1999-06-19
- external identifiers
-
- scopus:84957810715
- ISSN
- 0302-9743
- 1611-3349
- ISBN
- 3540414304
- 9783540414308
- DOI
- 10.1007/bfb0101415
- language
- English
- LU publication?
- yes
- additional info
- Publisher Copyright: © Springer-Verlag Berlin Heidelberg 2000.
- id
- 91f19679-066a-4b35-b427-42f3e09dd284
- date added to LUP
- 2022-10-19 11:42:27
- date last changed
- 2024-04-04 08:49:21
@inproceedings{91f19679-066a-4b35-b427-42f3e09dd284,
abstract = {{<p>Reuse of different types of experience is a key issue in successful improvement in software engineering. The approach taken in the Quality Improvement Paradigm (QIP) and its supporting organisation, tile Experience Factory (EF), is to define an Experience Base (EB), where all types of reusable objects are organised and stored. The objects may be of any type related to software development, for example, code, methods, quality models and specifications. Furthermore, not only objects identical to the target object needed can be reused, but also similar ones. This paper defines important concepts in a reuse context, elaborates a reuse scenario from which the requirements for the implementation of an Experience Base are derived. A list of 22 technical requirements is defined which cover the functional aspects related to the use of an Experience Base. The evaluation of three alternative implementation approaches are presented as an example: two database alternatives and one based on Case-Based Reasoning (CBR). Future work is to investigate the costs for extending the functionality to fulfil the requirements and to use the requirements in a real setting.</p>}},
author = {{Broomé, Mikael and Runeson, Per}},
booktitle = {{Learning Software Organizations : Methodology and Applications - 11th International Conference on Software Engineering and Knowledge Engineering, SEKE 1999, Proceedings}},
editor = {{Ruhe, Gunther and Bomarius, Frank}},
isbn = {{3540414304}},
issn = {{0302-9743}},
language = {{eng}},
pages = {{87--102}},
publisher = {{Springer}},
series = {{Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)}},
title = {{Technical requirements for the implementation of an experience base}},
url = {{http://dx.doi.org/10.1007/bfb0101415}},
doi = {{10.1007/bfb0101415}},
volume = {{1756}},
year = {{2000}},
}