are currently building up a solution. In section 3, we
introduce the company environment being exploited
as a case study and then we describe our in-progress
solution, in terms of a compound gathering those pil-
lars. Finally, in section 4, we present our concluding
remarks.
2 FOUNDATIONS
In this section we present the main pillars, from liter-
ature, on which we are building a solution towards a
mechanism to motivate knowledge sharing in a Se-
mantic Wiki-based Experience Repository. Firstly,
from Software Engineering (and under a KM perspec-
tive), we borrow the Experience Factory approach
(Basili et al., 1994). Then, Wikis (Leuf and Cunning-
ham, 2001) are being considered for their increas-
ing use worldwide also within organizational context,
and particularly Semantic Wikis (Schaffet, 2006) for
their more expressiveness power. Finally, a mecha-
nism to encourage participation in on-line commu-
nities (Cheng and Vassileva, 2006) is being adapted
from educational context to fit our purposes.
2.1 The Experience Factory
Experience Factory is an example of a knowledge
management approach for software organizations.
The Experience Factory (Basili et al., 1994) is defined
as a logical and/or physical organization that supports
project developments by analyzing and synthesizing
all kinds of experience, acting as a repository for such
experience, and supplying that experience to various
projects on demand. It packages experience by build-
ing informal, formal or schematized, and productized
models and measures of various software processes,
products, and other forms of knowledge via people,
documents, and automated support. The main idea is
that organizationsneed to learn from their past experi-
ences in order to deliver products faster, cheaper, and
with higher quality than before.
The Experience Factory is supported by a
methodological approach named Quality Improve-
ment Paradigm (QIP). QIP emphasizes the continu-
ous improvement by learning from experience, at the
level of organizations. It builds on experimentation
and application of measurement. QIP consists of the
following six steps (Basili et al., 1994): (i) charac-
terize, understand the environment based on avail-
able models, data, etc.; (ii) set goals, on the basis
of the initial characterization set quantifiable goals
for success and improvement; (iii) choose process,
on the basis of the characterization and of the goals,
choose the appropriate process to improve; (iv) ex-
ecute, execute the process constructing the products
and providing project feedback based upon the data
on goal achievement that are being collected; (v) an-
alyze, at the end of each specific project, analyze the
data and the information gathered to evaluate the cur-
rent practices, identify problems, record findings, and
make recommendations for future projects improve-
ment; (vi) package, consolidate the experience gained
in the form of new, or updated and refined, models
and other forms of structured knowledge gained from
this and prior projects, and store it in an experience
base so it is available for future projects.
A more recent approach to the Experience Factory
was proposed on the basis that it takes a relatively
long time to generate experience packages available
for the organization, since the data collected from
the projects need sophisticated analysis and synthesis
phases (Basili et al., 2001).
2.2 Semantic Wikis
Wikis are initiatives about the collective organization
of non-structured information on the Web, that are
widely used by domain experts. The first Wiki (Wiki-
WikiWeb) was conceived by Cunningham in 1995 as
a freely expansible interconnected collection of Web
pages, a hypertext system to store and modify infor-
mation - a database, where each page is easily ed-
itable by any user that has access to a Web browser
capable of dealing with forms (Leuf and Cunning-
ham, 2001). In (Schaffet, 2006), the author points to
a variety of uses for Wiki systems, as: encyclopedia
systems like Wikipedia, coordination in software de-
velopment, project management, personal knowledge
management and collaborative editing.
The above mentioned uses of Wiki systems have
increasingly been brought to workplace, both in small
and large companies. As highlighted in (Leuf and
Cunningham, 2001), “the workplace wiki provides a
central repository allowing distributed updates for ev-
eryone [...]”. On the other hand, as the authors advise,
other applications might be more convenient when-
ever rigid format adherence is required or if security
is a concern. Success uses of Wiki in large compa-
nies are reported (e.g. in Motorola), with pros and
cons in terms of people who showed resistant to the
tool, missing features, as well as its effectiveness as a
communication tool for relatively small size group.
More recently, a case study based on Wikis in a
small size company was conducted by Chau and his
team (Chau and Maurer, 2005). Their work was re-
lated to information organization in experience repos-
itories (on software development) specifically lying
ICEIS 2008 - International Conference on Enterprise Information Systems
572