The idea of software reuse is fundamentally simple: build software assets (code, libraries, frameworks, services, applications even) that can be used over and over again. Software reuse aims to allow reuse of software assets across projects and provides several benefits. Reduction in development and testing time, increased quality, ability to release new products and services quicker to the marketplace are all benefits of software reuse. Reuse has a rich history with the software community. Achieving success with software reuse isn't easy and needs several orchestrated activities to get the full benefits. To see a list of common reasons why reuse fails see here:
http://softwarereuse.wordpress.com/2009/04/12/top-reasons-why-systematic-software-reuse-efforts-fail/
Vijay Narayanan
http://softwarereuse.wordpress.com
yes
Will Tracz has written: 'Designing software for reuse' -- subject(s): Computer programs, Computer programming, Revisions 'Tutorial: Software Reuse'
Neil Lester has written: 'Assisting the software reuse process through classification and retrieval of software models'
The main application of knowledge management software is to identify, share, distribute and reuse information for various purposes. It is mainly useful for business, small and large organizations to promote reuse and share knowledge among individuals.
If something is in the public domain, then it is not copyrighted. Creative commons also has a license for any software developer who wants to let others reuse their code.
Domain Analysis is the process that identifies the relevant objects of an application domain. The goal of Domain Analysis is Software Reuse. The higher is the level of the life-cycle object to reuse, the larger are the benefits coming from its reuse, the harder is the definition of a workable process.
The purpose of asset recovery software programs is to help companies identify, reuse, and divest idle assets. HP is one of the most popular companies that offer this software. For more information check out their official website.
Edward A. Addy has written: 'Experience report' -- subject(s): Computer program integrity, Computer programming, Software engineering, Software development tools, Program verification (Computers), Design analysis 'The need for V&V in reuse-based software engineering' -- subject(s): Computer programming, Architecture (Computers), Programming environments, Software develocment tools, Software engineering 'V&V within reuse-based software engineering' -- subject(s): Computer programming, Proving, Software reuse, Software engineering
Use Metrics to Manage
1. If computer source code is not available. 2. Where lack of tool support. 3. Where original software is seen as more challenging. 4. Where engineers are not more confident of finding a component of software
can you reuse a nickel?
Assess reuse risks and cost