Software Reuse Case Study; TRILLIUM
Abstract
DoD has identified software reuse as a central strategy for improving the quality, timeliness and cost efficiency of its weapons, command and control and other automated information systems. However, to reap full benefits from software reuse technology, DoD must change the way it does business. The question is how. This study provides a commercial example in which software reuse is specifically gauged and encouraged as a means to improve quality, timeliness and life-cycle cost. TRILLIUM's recommended software reuse practices are based upon over ten years of successful experience. Reuse is not isolated, but viewed as one of several activities, all of which are needed to ensure software capability. Further, evidence suggests that TRILLIUM has been widely adopted by managers and practitioners throughout Bell's supplier organizations (who have chosen to market TRILLIUM to their customers). As such, this example appears to provide the right goals, long-term experience base and successful approach for getting effective software reuse into practice. While there are clear differences between DoD and Bell, we believe that the experiences and lessons learned by Bell and its suppliers can provide perspective and insights to those who develop and implement DoD policy.
Document Details
- Document Type
- Technical Report
- Publication Date
- Sep 13, 1993
- Accession Number
- ADA276108
Entities
People
- David Dikel
- George Demarco
- Jonathan Lichtenstein
- Jonathan Rosoff
- Paul Kengor
Organizations
- International Business Machines Corporation (Armonk, NY)