|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Valuing Design Repair
January/February 2008 (vol. 25 no. 1)
pp. 76-77
| ASCII Text | x | ||
| Rebecca J. Wirfs-Brock, "Valuing Design Repair," IEEE Software, vol. 25, no. 1, pp. 76-77, January/February, 2008. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2008.26, author = {Rebecca J. Wirfs-Brock}, title = {Valuing Design Repair}, journal ={IEEE Software}, volume = {25}, number = {1}, issn = {0740-7459}, year = {2008}, pages = {76-77}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2008.26}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Valuing Design Repair IS - 1 SN - 0740-7459 SP76 EP77 EPD - 76-77 A1 - Rebecca J. Wirfs-Brock, PY - 2008 KW - antipattern VL - 25 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2008.26
While a style guide typically covers good practices—what to do and what to avoid —an antipattern is somewhat more ambitious. It seeks to explain how good intentions can go awry and suggest meaningful ways to repair broken systems. The point isn't so much to say "do this" or "avoid doing that" as to suggest ways to prevent a problem or to skillfully apply a set of corrective actions.
Index Terms:
antipattern
Citation:
Rebecca J. Wirfs-Brock, "Valuing Design Repair," IEEE Software, vol. 25, no. 1, pp. 76-77, Jan.-Feb. 2008, doi:10.1109/MS.2008.26
Usage of this product signifies your acceptance of the Terms of Use.