J. S. Poulin and J. M. Caruso. Determining the value of a corporate reuse program. In Proceedings of the International Software Metrics Symposium, pages 16--27. IEEE Computer Society Press, May 1993.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....source lines we count and which not. Furthermore, to be able to compare our measurements with reuse levels of other groups and institutes, we need to conform to a standard counting model. To that end, we will use the notion of Reused Source Instructions (RSI) and the reuse percent metric Reuse [119], which is defined as: Reuse = RSI Total Statements # Thus, a Reuse of 100 corresponds to programs consisting of solely reused source code, while a Reuse of 0 corresponds to programs that have been written completely from scratch. RSI corresponds to software that complies to a number of ....

J. S. Poulin and J. M. Caruso. Determining the value of a corporate reuse program. In Proceedings of the International Software Metrics Symposium, pages 16--27. IEEE Computer Society Press, May 1993.

....single program. It means that the savings that the reuse of the interface would produce would have to be compared to this high cost linked to developing a system instead of to the cost of developing a simple software program. 18 Chapter 4 Reusing Code Vs. Designing for Reuse Poulin and Caruso [Pou14] presented a concept to distinguish among different ways to reuse code. There is the ad hoc reuse, also called unplanned reuse. This category of reuse consists in simply recovering old code trying to save new development effort, but without a clear reuse policy. The second category one can ....

Jeffrey S. Poulin, Joseph M. Caruso; "Determining the Value of a Corporate Reuse Program"; International Business Machines IEEE, 1993

....in their projects. 3. Value A large, generalized, and robust component provides more economic benefit to the organization than small, specific components. A recognition program for suppliers should consider the three criteria above; the Source Instructions Reused by Others (SIRBO) metric [24] provides an excellent way to recognize part suppliers. To calculate the SIRBO for a supplier, multiply the size (in lines of code) of each component the individual contributes by the number of products or organizations actually using it. The supplier accrues points based on total SIRBO. Using ....

....for individual recognition. Recognizing reusers also helps create a demand for reusable components that leads to financial benefits. The benefits correlate directly to the amount of software consumed by the reuser. Reused Source Instructions (RSI) provides an excellent metric for rewarding reusers [24]. To calculate the RSI for a reuser, simply count the number of lines of code in each reused component. The reuser receives credit for RSI the first time a component appears in a new product; RSI do not increase from using the same component over and over. The recognition program normally assigns ....

Poulin, Jeffrey S. and Joseph M. Caruso, "Determining the Value of a Corporate Reuse Program," Proceedings of the IEEE Computer Society International Software Metrics Symposium, Baltimore, MD, 21-22 May 1993, pp. 16-27.

....a similar effort: Lesson #1 Start early To succeed in program to program reuse one must start early; it requires 6 12 months to establish a formal agreement between two programs. While many visionaries readily support the fundamental concepts of software reuse and its associated benefits [4], the majority of people actually working on DoD contracts remain highly skeptical of this new way of doing business. These people recognize the important unresolved issues in working with other programs and experience shows that they have well founded concerns. Lesson #2 Address technical and ....

Poulin, Jeffrey S. and Joseph M. Caruso, "Determining the Value of a Corporate Reuse Program," Proceedings of the IEEE Computer Society International Software Metrics Symposium, Baltimore, MD, 21-22 May 1993, pp. 16-27.

.... of this effect, I take the position (in the form of a hypothesis) that until we develop a comprehensive system of measuring and combining reuse in each phase of the software development lifecycle: HO: total cross lifecycle reuse level of code reuse Observations show Reuse Percent (Reuse ) [8] as the most widely used and reported reuse metric. Reuse has an advantage in that managers can easily gather data for, calculate, and understand the metric. This position paper assumes a systematic method of determining what to count (a reuse definition) 9] and does not attempt to address the ....

J. Poulin and J. Caruso, "Determining the Value of a Corporate Reuse Program," in Proceedings of the IEEE Computer Society International Software Metrics Symposium, (Baltimore, MD, 21-22 May 1993), pp. 16--27, 21-22 May 1993.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC