A Conceptual Framework for Software Technology Transition

Abstract : We present a conceptual framework that integrates and describes the intersections of three life cycles of software technology transition; research and development, new product development, and adoption and implementation in organizations. We then apply the framework to the technology transition experiences of the Software Engineering Institute.

[1]  B. I. Blum,et al.  Characterizing the software process , 1994 .

[2]  Edward B. Roberts,et al.  Entrepreneurs in high technology : lessons from MIT and beyond , 1991 .

[3]  Mark Klein,et al.  A practitioner's handbook for real-time analysis - guide to rate monotonic analysis for real-time systems , 1993, The Kluwer international series in engineering and computer science.

[4]  R. de Tornyay.  Up and running. , 1983, The Journal of nursing education.

[5]  Priscilla Fowler,et al.  for Software Technology Transition , 1994 .

[6]  J. Alexander,et al.  Images of Organization , 1988 .

[7]  Garth Glynn.  Semiformal process model for technology transfer , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[8]  James W. Botkin,et al.  Winning Combinations: The Coming Wave of Entrepreneurial Partnerships Between Large and Small Companies , 1992 .

[9]  Stan Rifkin,et al.  Software Engineering Process Group Guide , 1990 .

[10]  Priscilla J. Fowler,et al.  Toward A Problem Solving Approach To Software Technology Transition , 1992, IFIP Congress.

[11]  Robert B. Grady,et al.  Software Metrics: Establishing a Company-Wide Program , 1987 .

[12]  Edward J. Ottensmeyer.  Third generation R&D: Managing the link to corporate strategy : by Philip A. Roussel, Kamal N. Saad, and Tamara J. Erickson, Harvard Business School Press, Boston, MA, 1991, 192 pp. , 1993 .

[13]  Priscilla J. Fowler,et al.  Technology transfer as a collaboration: the receptor group , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[14]  Geoffrey A. Moore.  Crossing the chasm : marketing and selling technology products to mainstream customers , 1991 .

[15]  Barbara M. Bouldin.  Agents of Change: Managing the Introduction of Automated Tools , 1988 .

[16]  David Rowe,et al.  Up and Running , 1993 .

[17]  A. Chakrabarti,et al.  Implementing routine and radical innovations , 1989 .

[18]  Robert G. Ebenau,et al.  Software Inspection Process , 1993 .

[19]  R. Kanter.  The Change Masters , 1983 .

[20]  Wm. E. Souder,et al.  A guide to the best technology-transfer practices , 1990 .

[21]  D. Gibson,et al.  Technology Transfer: A Communication Perspective , 1990 .

[22]  D. Conner,et al.  Building commitment to organizational change. , 1982 .

[23]  M. Fleischer,et al.  processes of technological innovation , 1990 .

[24]  A. Pearson.  Managing New Product Innovations. , 1989 .

[25]  D. Leonard-Barton,et al.  Implementation as mutual adaptation of technology and organization , 1988 .

[26]  Robert W. Zmud,et al.  Measuring technology incorporation/infusion , 1992 .

[27]  Lawrence B. Mohr,et al.  Conceptual issues in the study of innovation , 1976 .

[28]  Dorothy Leon Ard-Barton.  Implementation Characteristics of Organizational Innovations , 1988 .

[29]  D. Keith Robbins.  Deciding to Innovate: How Firms Justify Advanced Technology , 1988 .

[30]  A B Marmor-Squires,et al.  DoD Related Software Technology Requirements, Practices, and Prospects for the Future , 1984 .