𝔖 Scriptorium
✦   LIBER   ✦

πŸ“

Software Reuse: Guidelines and Methods

✍ Scribed by James W. Hooper, Rowena O. Chester (auth.)


Publisher
Springer US
Year
1991
Tongue
English
Leaves
192
Series
Software Science and Engineering
Edition
1
Category
Library

⬇  Acquire This Volume

No coin nor oath required. For personal study only.

✦ Synopsis


Observers in the present usually have an advantage when it comes to interpreting events of the past. In the case of software reuse, howΒ­ ever, it is unclear why an idea that has gained such universal accepΒ­ tance was the source of swirling controversy when it began to be taken seriously by the software engineering community in the mid-1980's. From a purely conceptual point of view, the reuse of software deΒ­ signs and components promises nearly risk-free benefits to the develΒ­ oper. Virtually every model of software cost and development effort predicts first-order dependencies on either products size or the numΒ­ ber of steps carried out in development. Reduce the amount of new product to be developed and the cost of producing the product deΒ­ creases. Remove development steps, and total effort is reduced. By reusing previously developed engineering products the amount of new product and the number of development steps can be reduced. In this way, reuse clearly has a major influence on reducing total development cost and effort. This, of course, raises the issue of from whence the reused products arise. There has to be a prior investment in creating "libraries of reuse products before reuse can be successfuL . . " How can organizations with a "bottom line" orientation be enticed into contributing to a reuse venture? Fortunately, the economics of reuse l resembles many other financial investment situations .

✦ Table of Contents


Front Matter....Pages i-xvi
Background and Introduction....Pages 1-15
Managerial Guidelines....Pages 17-50
Technical Guidelines....Pages 51-136
Getting Started....Pages 137-140
Back Matter....Pages 141-180

✦ Subjects


Software Engineering/Programming and Operating Systems


πŸ“œ SIMILAR VOLUMES


Software Reuse
✍ Bernard Coulange (auth.) πŸ“‚ Library πŸ“… 1998 πŸ› Springer-Verlag London 🌐 English

<p>Software Reuse is a state of the art book concerning all aspects of software reuse. It does away with the hype and shows the reality. Different techniques are presented which enable software reuse and the author demonstrates why object-oriented methods are better for reuse than other approaches.

Software Requirements: Encapsulation, Qu
✍ Rick Lutowski πŸ“‚ Library πŸ“… 2005 πŸ› Auerbach Publications 🌐 English

Software Requirements: Encapsulation, Quality, and Reuse describes how to make requirements easy to change by using encapsulation. It introduces the Freedom methodology that shows how to encapsulate requirements thereby promoting reuse and quality. Encapsulating requirements reduces software life cy

Software Requirements: Encapsulation, Qu
✍ Rick Lutowski πŸ“‚ Library πŸ“… 2005 🌐 English

Software Requirements: Encapsulation, Quality, and Reuse describes how to make requirements easy to change by using encapsulation. It introduces the Freedom methodology that shows how to encapsulate requirements thereby promoting reuse and quality. Encapsulating requirements reduces software life cy

Integrated Software Reuse: Management an
✍ Paul Walton πŸ“‚ Library πŸ“… 2020 πŸ› Routledge 🌐 English

Published in 1993. Software reuse has been shown to achieve improvements in productivity, quality and timeliness of software. The collection of papers in this book were given at a seminar organized by UNICOM and the British Computer Society Software Reuse Specialist Group. They address the reasons w

Quality Software Through Reuse and Integ
πŸ“‚ Library πŸ“… 2017 πŸ› Bouabana-Tebibel, Thouraya, Rubin, Stuart H., Spri 🌐 English

<p><p>This book presents 13 high-quality research articles that provide long sought-after answers to questions concerning various aspects of reuse and integration. Its contents lead to the inescapable conclusion that software, hardware, and design productivity – including quality attributes – is not