A major activity in software development is to obtain knowledge and insights about the application domain. Even though this is supported by a wide range of tools and techniques, a lot of knowledge remains implicit in the resulting artefacts (e.g. class diagrams). Examples of such implicit knowledge are amongst others the links between the different artefacts, the knowledge that is lost as a result of iterative refinements, and the knowledge that is regarded common sense by the involved parties. Most of this knowledge resides in the heads of the stakeholders, the domain experts, and the developers. As it is likely that they can no longer remember it or that they are no longer available when software reuse and maintenance activities are initiated, this poses a problem. In this paper we present a part of ongoing research in which we focus on our use of an ontology as a medium to tackle this problem. Making the different kinds of knowledge explicit will be accomplished by representing them as concepts in the ontology. Subsequently we will link these concepts to the artefacts created during analysis, design and implementation. This enables a bi-directional navigation between the concepts and the artefacts which consequently will serve as a vehicle to start reuse and maintenance activities.
[1]
Tom Mens,et al.
Supporting software evolution with intentional software views
,
2002,
IWPSE '02.
[2]
Thomas R. Gruber,et al.
Toward principles for the design of ontologies used for knowledge sharing?
,
1995,
Int. J. Hum. Comput. Stud..
[3]
V. R. Benjamins,et al.
WonderTools? A comparative study of ontological engineering tools
,
2000,
Int. J. Hum. Comput. Stud..
[4]
John F. Sowa,et al.
Conceptual Structures: Information Processing in Mind and Machine
,
1983
.
[5]
Donald J. Reifer,et al.
Practical software reuse
,
1997
.
[6]
Henrik Eriksson,et al.
Knowledge modeling at the millennium : The design and evolution of Protégé-2000
,
1999
.