This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Tribal Memory
March/April 2008 (vol. 25 no. 2)
pp. 16-17
As the code written today becomes part of tomorrow's inexorably growing legacy, preserving these stories becomes increasingly important. It's costly to rely upon informal storytelling to preserve and communicate important decisions; it's incredibly costly to try to recreate those decisions and their rationale when the storytellers themselves are gone. Insofar as a software development organization can preserve its stories in a system's written architecture, it can make evolving that system materially easier.
Index Terms:
system architecture, legacy code, stakeholder dialogue
Citation:
Grady Booch, "Tribal Memory," IEEE Software, vol. 25, no. 2, pp. 16-17, March-April 2008, doi:10.1109/MS.2008.52
Usage of this product signifies your acceptance of the Terms of Use.