The knowledge-gap reduction in software engineering

Many 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 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 a knowledge-oriented software development process to help organizations in reducing the software crisis impacts.

[1]  野中 郁次郎,et al.  The knowledge-creating company , 2008 .

[2]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[3]  H. Simon,et al.  Models of Bounded Rationality: Empirically Grounded Economic Reason , 1997 .

[4]  Howard Baetjer,et al.  Software as capital - an economic perspective on software engineering , 1997 .

[5]  Barbara Emmons.  Requirements management , 2002 .

[6]  Karlheinz Kautz,et al.  The Failure to Introduce System Development Methods: A Factor-Based Analysis , 1993, Diffusion, Transfer and Implementation of Information Technology.

[7]  Ikujiro Nonaka,et al.  Theory of Organisational Knowledge Creation”. Organisation Science. , 1994 .

[8]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[9]  Dorothy E. Leidner,et al.  Review: Knowledge Management and Knowledge Management Systems: Conceptual Foundations and Research Issues , 2001, MIS Q..

[10]  Hisashi Q. Higuchi.  On the nature of , 1999 .

[11]  Claudine Toffolon,et al.  KNOC: A Knowledge-Oriented Cooperative Software Development Process , 2007, ISD.

[12]  Mauri Laitinen,et al.  Thinking objectively: software process improvement in the small , 2001, CACM.

[13]  Michael H. Zack,et al.  Managing Codified Knowledge , 1999 .

[14]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[15]  Natalia Juristo Juzgado,et al.  Understanding the Customer: What Do We Know about Requirements Elicitation? , 2008, IEEE Software.

[16]  H. Demsetz,et al.  Production, Information Costs, and Economic Organization , 1975, IEEE Engineering Management Review.

[17]  U. Yeliz Eseryel,et al.  Knowledge management and knowledge management systems , 2005 .

[18]  P. Vigneswara Ilavarasan,et al.  Is software work routinized? Some empirical observations from Indian software industry , 2003, J. Syst. Softw..

[19]  Barry Boehm,et al.  A view of 20th and 21st century software engineering , 2006, ICSE.

[20]  C. P. Goodman,et al.  The Tacit Dimension , 2003 .

[21]  M. C. Jensen,et al.  Harvard Business School; SSRN; National Bureau of Economic Research (NBER); European Corporate Governance Institute (ECGI); Harvard University - Accounting & Control Unit , 1976 .

[22]  Walt Scacchi,et al.  Process Models in Software Engineering , 2001 .

[23]  P. Kidwell,et al.  The mythical man-month: Essays on software engineering , 1996, IEEE Annals of the History of Computing.

[24]  Colin J. Neill,et al.  Requirements Engineering: The State of the Practice , 2003, IEEE Softw..

[25]  Björn Regnell,et al.  Market-Driven Requirements Engineering for Software Products , 2005 .

[26]  Rudy Hirschheim,et al.  Information Systems and User Resistance: Theory and Practice , 1988, Comput. J..

[27]  R. Müller,et al.  On the nature of the project as a temporary organization , 2003 .

[28]  Roel Wieringa,et al.  Guest Editors' Introduction: Stakeholders in Requirements Engineering , 2007, IEEE Software.

[29]  Keith Mattacks,et al.  Managing Knowledge Work , 2003 .

[30]  Simon Wiedemann,et al.  Requirements Management , 2008 .

[31]  Salem Ben Dhaou Dakhli,et al.  The Solution Space Organization: Linking Information Systems Architecture and Reuse , 2008, ISD.

[32]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[33]  Claudine Toffolon,et al.  The Software Dimensions Theory , 2000, ICEIS.

[34]  F. Blackler.  Knowledge, Knowledge Work and Organizations: An Overview and Interpretation , 1995 .