Transition Packages for Expediting Technology Adoption: The Prototype Requirements Management Transition Package
[Top] [Prev] [Next] [Bottom] [PDF]
|
REPORT DOCUMENTATION PAGE |
Form Approved OMB No. 0704-0188 |
||
|
Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. |
|||
1. agency use only (leave blank) |
2. report date July 1998 |
3. report type and dates covered Final |
|
4. title and subtitle |
5. funding numbers C — F19628-95-C-0003 |
||
6. author(s) |
|
||
7. performing organization name(s) and address(es) Software Engineering Institute |
8. performing organization |
||
9. sponsoring/monitoring agency name(s) and address(es) HQ ESC/AXS |
10. sponsoring/monitoring |
||
11. supplementary notes |
|||
12.a distribution/availability statement Unclassified/Unlimited, DTIC, NTIS |
12.b distribution code |
||
13. abstract (maximum 200 words)This report describes the experience of building and evaluating a prototype transition package for organizations implementing processes in support of the Requirements Management Key Process Area of the Software Engineering Institute’s Software Capability Maturity ModelSM. This report also describes the theories that led to the project and states our conclusions based on evaluation and review of the prototype by users typical of the audience targeted for transition packages. Feedback from these users indicated that they were typical "early or late majority" adopters, and that they found the transition package helpful for orientation and education as part of implementing requirements management practices in their organizations. We argue in this report that transition packages, as part of a complete "whole product" that includes training and consulting, can be an effective mechanism for expediting the diffusion, adoption, and implementation of important technologies. Finally, we describe what we now know about creating transition packages and how they might be used. |
|||
14. subject terms: transition package; technology transition; process improvement; whole product; technology adoption; technology transition; diffusion of innovation; implementation; software engineering; requirements management; process action teams; change agents; software engineering process group |
15. number of pages |
||
|
|
16. Price Code |
||
17. security classification UNCLASSIFIED |
18. security classification UNCLASSIFIED |
19. security classification UNCLASSIFIED |
20. limitation of abstract UL |
|
NSN 7540-01-280-5500 |
|
|
Standard Form 298 (Rev. 2-89) |