Software processes: live and let die
A.B. Jakobsen · IEEE Software · 2000
RESUMEN Biblioteca de Ciencias y Tecnología Normal Biblioteca de Ciencias y Tecnología 2 0 2007-10-09T13:57:00Z 2007-10-09T13:57:00Z 1 62 343 UCLA 2 1 404 11.6568 Clean Clean 21 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tabla normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} RESUMEN The software business is tough: it requires not only the right product but also the right development process. This article is about the reengineering of a catastrophic software product and the two different reengineering processes the developers used. The author, explaining why one process failed and the other succeeded, asserts that people and processes must match in software development.