6:9
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, and in some cases deliberately obfuscatory code may be found.[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]
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[citation needed] 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:
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]
The profession of programmer–archaeologist features prominently in Vernor Vinge's A Deepness in the Sky. [14]
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.
By: Wikipedia.org
Edited: 2021-06-18 19:19:13
Source: Wikipedia.org
