Software archaeology

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Software archaeology or software archeology is the study of poorly documented or undocumented legacy software implementations, as part of software maintenance.[1][2] Software archaeology, named by analogy with archaeology,[3] includes the reverse engineering of software modules, and the application of a variety of tools and processes for extracting and understanding program structure and recovering design information.[1][4] Software archaeology may reveal dysfunctional team processes which have produced poorly designed or even unused software modules.[5] The term has been in use for decades,[6] and reflects a fairly natural metaphor: a programmer reading legacy code may feel that he or she is in the same situation as an archaeologist exploring the rubble of an ancient civilization.[7]

Techniques

A workshop on Software Archaeology at the 2001 OOPSLA (Object-Oriented Programming, Systems, Languages & Applications) conference identified the following software archaeology techniques, some of which are specific to object-oriented programming:[7]

More generally, Andy Hunt and Dave Thomas note the importance of version control, dependency management, text indexing tools such as GLIMPSE and SWISH-E, and "[drawing] a map as you begin exploring."[7]

Like true archaeology, software archaeology involves investigative work to understand the thought processes of one's predecessors.[7] At the OOPSLA workshop, Ward Cunningham suggested a synoptic signature analysis technique which gave an overall "feel" for a program by showing only punctuation, such as semicolons and curly braces.[8] In the same vein, Cunningham has suggested viewing programs in 2 point font in order to understand the overall structure.[9] Another technique identified at the workshop was the use of aspect-oriented programming tools such as AspectJ to systematically introduce tracing code without directly editing the legacy program.[7]

Network and temporal analysis techniques can reveal the patterns of collaborative activity by the developers of legacy software, which in turn may shed light on the strengths and weaknesses of the software artifacts produced.[10]

Michael Rozlog of Embarcadero Technologies has described software archaeology as a six-step process which enables programmers to answer questions such as "What have I just inherited?" and "Where are the scary sections of the code?"[11] These steps, similar to those identified by the OOPSLA workshop, include using visualization to obtain a visual representation of the program's design, using software metrics to look for design and style violations, using unit testing and profiling to look for bugs and performance bottlenecks, and assembling design information recovered by the process.[11] Software archaeology can also be a service provided to programmers by external consultants.[12]

Mitch Rosenberg of InfoVentions.net, Inc. claims that the first law of software archaeology (he calls it code or data archaeology) is:

Everything that is there is there for a reason, and there are 3 possible reasons:

  1. It used to need to be there but no longer does
  2. It never needed to be there and the person that wrote the code had no clue
  3. It STILL needs to be there and YOU have no clue

The corollary to this "law" is that, until you know which was the reason, you should NOT modify the code (or data).

Software archaeology has continued to be a topic of discussion at more recent software engineering conferences.[13]

See also

References

  1. ↑ 1.0 1.1 Gregorio Robles, Jesus M. Gonzalez-Barahona, and Israel Herraiz, "An Empirical Approach to Software Archaeology," Poster Proceedings of the International Conference on Software Maintenance, 2005.
  2. ↑ "Agile Legacy System Analysis and Integration Modeling" by Scott W. Ambler at agilemodeling.com, accessed 20 August 2010: "Without accurate documentation, or access to knowledgeable people, your last resort may be to analyze the source code for the legacy system... This effort is often referred to as software archaeology."
  3. ↑ Bryon Moyer, "Software Archeology: Modernizing Old Systems," Embedded Technology Journal, March 4, 2009.
  4. ↑ Richard Hopkins and Kevin Jenkins, Eating the IT Elephant: Moving from greenfield development to brownfield, Addison-Wesley, 2008, ISBN 0-13-713012-0, p. 93.
  5. ↑ Diomidis Spinellis and Georgios Gousios, Beautiful Architecture, O'Reilly, 2009, ISBN 0-596-51798-X, p. 29.
  6. ↑ An early discussion is Judith E. Grass, "Object-Oriented Design Archaeology with CIA++," Computing Systems, Vol. 5, No. 1, Winter 1992.
  7. ↑ 7.0 7.1 7.2 7.3 7.4 Andy Hunt and Dave Thomas, "Software Archaeology", IEEE Software, vol. 19, no. 2, pp. 20-22, Mar./Apr. 2002, doi:10.1109/52.991327.
  8. ↑ Ward Cunningham, "Signature Survey: A Method for Browsing Unfamiliar Code," Workshop Position Statement, Software Archeology: Understanding Large Systems, OOPSLA 2001.
  9. ↑ "Software Archeology" on John D. Cook's blog The Endeavour, November 10, 2009.
  10. ↑ Cleidson de Souza, Jon Froehlich, and Paul Dourish, "Seeking the Source: Software Source Code as a Social and Technical Artifact," Proceedings of the 2005 International ACM SIGGROUP Conference on Supporting Group Work, pp. 197-206.
  11. ↑ 11.0 11.1 Michael Rozlog, "Software Archeology: What Is It and Why Should Java Developers Care?," article on java.sys-con.com, January 28, 2008.
  12. ↑ Simon Sharwood, Raiders of the Lost Code, ZDNet, November 3, 2004.
  13. ↑ For example, the 32nd ACM/IEEE International Conference on Software Engineering in Cape Town, South Africa in May 2010.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Software_archaeology&oldid=644245204"