Show simple item record

The knowledge-gap reduction in software engineering

dc.contributor.authorBen Dhaou Dakhli, Salem
dc.contributor.authorBen Chouikha, Mouna
dc.date.accessioned2012-03-05T15:39:44Z
dc.date.available2012-03-05T15:39:44Z
dc.date.issued2008
dc.identifier.urihttps://basepub.dauphine.fr/handle/123456789/8361
dc.language.isoenen
dc.subjectKnowledgeen
dc.subjectGapen
dc.subjectSoftware Engineeringen
dc.subjectInformation systemsen
dc.subject.ddc651en
dc.subject.classificationjelM15en
dc.subject.classificationjelL86en
dc.titleThe knowledge-gap reduction in software engineeringen
dc.typeCommunication / Conférence
dc.description.abstractenMany papers proposed in the software engineering and information systems literature are dedicated to analysis of software projects missing their schedules, exceeding their budgets, delivering software products with poor quality and in some cases even wrong functionality. The expression “software crisis” has been coined since the late 60’s to illustrate this phenomenon. Various solutions has been proposed by academics and practitioners in order to deal with the software crisis, counter these trends and improve productivity and software quality. Such solutions recommend software process improvement as the best way to build software products needed by modern organizations. Among the well-known solutions, many are based either on software development tools or on software development approaches, methods, processes, and notations. Nevertheless, the scope of these solutions seems to be limited and the improvements they provide are often not significant. We think that since software artifacts are accumulation of knowledge owned by organizational stakeholders, the software crisis is due to a knowledge gap between resulting from the discrepancy between the knowledge integrated in software systems and the knowledge owned by organizational actors. In particular, integrating knowledge management in software development process permits reducing the knowledge gap through building software products which reflect at least partly the organization’s know-how. In this paper, we propose a framework which provides a definition of knowledge based on information systems architecture and describes how to deal with the knowledge gap of a knowledge oriented software development process which may help organizations in reducing the software crisis impacts.en
dc.identifier.citationpages-en
dc.description.sponsorshipprivateouien
dc.subject.ddclabelSystèmes d'informationen
dc.relation.conftitleMCIS 2008 conferenceen
dc.relation.confdate2008-10
dc.relation.confcityHammameten
dc.relation.confcountryTunisieen


Files in this item

FilesSizeFormatView

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record