Editing Code reuse (section)

==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.<ref>{{cite book |last=McConnell |first=Steve |title=Rapid Development: Taming Wild Software Schedules |year=1996 |publisher=Pearson Education |isbn=978-1-55615-900-8 |url-access=registration |url=https://archive.org/details/rapiddevelopment00mcco }}</ref> 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:<ref name="sharednow.blogspot.com">{{cite web |last=Colombo |first=F. |year=2011 |title=It's not just reuse |work=SharedNow.blogspot |url=http://sharednow.blogspot.com/2011/05/its-not-just-reuse.html}}</ref>
* 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.<ref name="sharednow.blogspot.com"/>