Code reuse

Code reuse is the practice of using existing source code to develop software instead of writing new code. Software reuse is a broader term that implies using any existing software asset to develop software instead of developing it again.^[1][2]: 7 An asset that is relatively easy to reuse and offers significant value is considered to have high reusability.

Code reuse may be achieved different ways depending on a complexity of a programming language chosen and range from a lower-level approaches like code copy-pasting (e.g. via snippets),^[3] simple functions (procedures or subroutines) or a bunch of objects or functions organized into modules (e.g. libraries)^[4][2]: 7 or custom namespaces, and packages, frameworks or software suites in higher-levels.

Code reuse implies dependencies which can make code maintainability harder.^{[citation needed]} At least one study found that code reuse at the class level reduces technical debt.^[5]

Overview

This section needs more citations. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (April 2015) (Learn how and when to remove this message)

Ad hoc code reuse has been practiced from the earliest days of programming. Programmers have always reused sections of code, templates, functions, and procedures. Software reuse as a recognized area of study in software engineering, however, dates only from 1968 when Douglas McIlroy of Bell Laboratories proposed basing the software industry on reusable components.

Code reuse aims to save time and resources and reduce redundancy by taking advantage of assets that have already been created in some form within the software product development process.^[6] The key idea in reuse is that parts of a computer program written at one time can be or should be used in the construction of other programs written at a later time.

Code reuse may imply the creation of a separately maintained version of the reusable assets. While code is the most common resource selected for reuse, other assets generated during the development cycle may offer opportunities for reuse: software components, test suites, designs, documentation, and so on.^[7]

The software library is a good example of code reuse. Programmers may decide to create internal abstractions so that certain parts of their program can be reused, or may create custom libraries for their own use. Some characteristics that make software more easily reusable are modularity, loose coupling, high cohesion, information hiding and separation of concerns.

For newly written code to use a piece of existing code, some kind of interface, or means of communication, must be defined. These commonly include a "call" or use of a subroutine, object, class, or prototype. In organizations, such practices are formalized and standardized by domain engineering, also known as software product line engineering.

The general practice of using a prior version of an extant program as a starting point for the next version, is also a form of code reuse.

Some so-called code "reuse" involves simply copying some or all of the code from an existing program into a new one. While organizations can realize time to market benefits for a new product with this approach, they can subsequently be saddled with many of the same code duplication problems caused by cut and paste programming.

Many researchers have worked to make reuse faster, easier, more systematic, and an integral part of the normal process of programming. These are some of the main goals behind the invention of object-oriented programming, which became one of the most common forms of formalized reuse. A somewhat later invention is generic programming.

Another, newer means is to use software "generators", programs which can create new programs of a certain type, based on a set of parameters that users choose. Fields of study about such systems are generative programming and metaprogramming.

Types of reuse

Concerning motivation and driving factors, reuse can be:

• Opportunistic – While getting ready to begin a project, the team realizes that there are existing components that they can reuse.
• Planned – A team strategically designs components so that they'll be reusable in future projects.

Reuse can be categorized further:

• Internal reuse – A team reuses its own components. This may be a business decision, since the team may want to control a component critical to the project.
• External reuse – A team may choose to license a third-party component. Licensing a third-party component typically costs the team 1 to 20 percent of what it would cost to develop internally.^[8] The team must also consider the time it takes to find, learn and integrate the component.

Concerning form or structure of reuse, code can be:^[9]

• Referenced – The client code contains a reference to reused code, and thus they have distinct life cycles and can have distinct versions.
• Forked – The client code contains a local or private copy of the reused code, and thus they share a single life cycle and a single version.

Fork-reuse is often discouraged because it's a form of code duplication, which requires that every bug is corrected in each copy, and enhancements made to reused code need to be manually merged in every copy or they become out-of-date. However, fork-reuse can have benefits such as isolation, flexibility to change the reused code, easier packaging, deployment and version management.^[9]

Systematic

This section needs expansion. You can help by adding missing information. (April 2015)

Systematic software reuse is a strategy for increasing productivity and improving the quality of the software industry. Although it is simple in concept, successful software reuse implementation is difficult in practice. A reason put forward for this is the dependence of software reuse on the context in which it is implemented. Some problematic issues that need to be addressed related to systematic software reuse are:^[10]

• a clear and well-defined product vision is an essential foundation to a software product line (SPL).
• an evolutionary implementation strategy would be a more pragmatic strategy for the company.
• there exist a need for continuous management support and leadership to ensure success.
• an appropriate organisational structure is needed to support SPL engineering.
• the change of mindset from a project-centric company to a product-oriented company is essential.

Examples

Criticism

Code reuse results in dependency on the component being reused. Rob Pike opined that "A little copying is better than a little dependency". When he joined Google, the company was putting heavy emphasis on code reuse. He believes that Google's codebase still suffers from results of that former policy in terms of compilation speed and maintainability.^[14]

Reusable code requires usually more effort to write and design. Fred Brooks discusses the significantly higher cost associated with that effort in his essays "The Tar Pit" and "No Silver Bullet" The fallacy is that effort is often spent without careful understanding of the mechanisms through which that cost will be redeemed. The justification often comes from incorrectly drawing parallels to reusable parts in a physical manufacturing process. Incorrect because writing code is analogous to design of a single product rather than production of multiple units.

See also

• Don't repeat yourself
• International Conference on Software Reuse
• Inheritance (object-oriented programming)
• Language binding
• Not invented here (antonym)
• Type polymorphism
• Procedural programming
• Reinventing the wheel (antonym)
• Reuse metrics
• Single source of truth
• Software framework
• Virtual inheritance

References

External links

• ReNews – an information site about software reuse and domain engineering
• Software Reuse Tips Article