KNOC: A Knowledge-Oriented Cooperative Software Development Process

Software systems have become one of the most valuable assets of modern organizations, where they play a critical role in supporting operational and decision processes. Nevertheless, despite the large part of organizations' resources invested in information technology, development of software systems faces many problems recognized by the termsoftware crisis. To reduce the economic and social impacts of this crisis, one widely acknowledged approach has been to improve software processes and software development methods supporting them. However, as stressed by many authors, such solutions of the software crisis are partial and incomplete and present many weaknesses related to their technical orientation. In this paper, we present a knowledge-oriented and cooperative software development framework process in order to improve the existing solutions of the software crisis. This framework considers software systems as an accumulation of knowledge. It proposes a cooperative guidance to gather the knowledge necessary to software products design and distributed among various stakeholders.

[1]  Kyle Eischen.  Software Development: An Outsider's View , 2002, Computer.

[2]  R. Coase.  The Nature of the Firm , 1937 .

[3]  R. Solow.  We’d better watch out , 1987 .

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

[5]  W. Wayt Gibbs,et al.  Software's Chronic Crisis , 1994 .

[6]  O. Williamson.  The Modern Corporation: Origins, Evolution, Attributes , 1981 .

[7]  Brian Fitzgerald,et al.  An empirical investigation into the adoption of systems development methodologies , 1998, Inf. Manag..

[8]  M. Resnick.  Distributed Constructionism , 1996, ICLS.

[9]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[10]  Mark Lycett,et al.  Migrating Agile Methods to Standardized Development Practice , 2003, Computer.

[11]  Kalle Lyytinen,et al.  Different perspectives on information systems: problems and solutions , 1987, CSUR.

[12]  Kenneth L. Kraemer,et al.  Information technology and economic performance , 2003, ACM Comput. Surv..

[13]  Peter G. Neumann,et al.  Computer-related risks , 1994 .

[14]  Phillip G. Armour.  The Business of Software: the case for a new business model , 2000, CACM.

[15]  Johan F. Hoorn,et al.  Distributed cognition , 2005, Cognition, Technology & Work.

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

[17]  Benn R. Konsynski,et al.  Information systems and decision processes , 1992 .

[18]  Phillip G. Armour.  The case for a new business model. , 2000 .

[19]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach (McGraw-Hill Series in Computer Science) , 2004 .

[20]  Thomas A. Peters,et al.  Computerization and Controversy: Value Conflicts and Social Choices (2nd Ed.), edited by Rob Kling , 1996, Journal of the American Society for Information Science.

[21]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[22]  R. Kling,et al.  Book Review: Computerization and Controversy: Value Conflicts and Social Choices , 1991 .

[23]  Stuart E. Madnick,et al.  Software Project Dynamics: An Integrated Approach , 1991 .

[24]  Brian Fitzgerald,et al.  Formalized systems development methodologies: a critical perspective , 1996, Inf. Syst. J..

[25]  Daniel C. Edelson,et al.  Proceedings of the 1996 international conference on Learning sciences , 1996 .

[26]  Carlo Ghezzi,et al.  A framework for formalizing inconsistencies and deviations in human-centered systems , 1996, TSEM.

[27]  E. K. Gannett,et al.  THE INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS , 1965 .

[28]  Claudine Toffolon,et al.  The software engineering global model , 2002, Proceedings 26th Annual International Computer Software and Applications.

[29]  Jim Highsmith,et al.  Agile Software Development Ecosystems , 2002 .