Prefactoring

Prefactoring is the application of past experience to the creation of new software systems. Its relationship to its namesake refactoring is that lessons learned from refactoring are part of that experience.

Experience is captured in guidelines that can be applied to a development process. The guidelines have come from a number of sources, including Jerry Weinberg, Norm Kerth, and Scott Ambler Fact|date=April 2007.

Guidelines

Guidelines include:

* “When You’re Abstract, Be Abstract All the Way”
* “Splitters Can Be Lumped Easier Than Lumpers Can Be Split”
* “Use the Client’s Language”

See also

* Design pattern (computer sciences)

References

*cite book
first = Ken
last = Pugh
author = Ken Pugh
year = 2005
title = Prefactoring
publisher = O'Reilly Media
id = ISBN 0-596-00874-0 ( [http://www.ddj.com/architect/187900423?pgno=3 the book won the Jolt award 2006] )

External links

* [http://www.oreillynet.com/pub/a/network/2005/11/15/what-is-prefactoring.html What Is Prefactoring]