![]() |
Technology Transfer |
Problem |
Improving productivity, lowering development costs, and improving the quality of software products all depend upon the introduction of new technology (new software tools, new hardware, and new processes) to the development process. Industry, unfortunately, often believes in the folklore that there is a magic "silver bullet" that will solve this problem. Instead, the introduction of new technology is a slow, costly, and time consuming activity. What is the best way to address technology transfer within the software development domain? |
Goal |
To develop an understanding (e.g., a process model) that describes the introduction of new technology within a software development organization and to develop a theory that can be used to help improve this technology transfer process. |
Keywords |
Experimentation, innovation, technology insertion |
Participants |
Marvin Zelkowitz |
References |
![]() This represents a NASA-wide study of software engineering technology transfer across NASA. it describes in detail the steps various groups took in evaluating, prototyping, and inserting new technology into their development organization. Technologies such as Ada, Cleanroom, CLIPS, TAE, inspections, and object oiented design are discussed. ( Postscript )
This is a condensed version of the above NASA technical report.
This describes a model of technology innovation in the software development domain. It introduces two concepts: Process horizon (the idea that there is a limit to process complexity in any environment. If passed, errors result) and technological drift (the idea that all environments are improving over time due to general development of new technology. It is important to measure a given environment's deviation from this general trend.)
|