An information retrieval system to manage program maintenance reports in a data processing shop

ABSTRACT

Programming maintenance is a routine process in a data processing shop. Programming maintenance in most cases is performed as either a routine task or to fix a problem. In either case, care must be taken when applying programming maintenance. This is because programming maintenance has the possibility of undoing earlier programming maintenance changes. A programmer should examine earlier programming maintenance before applying new maintenance. The programmer can also gain valuable knowledge of the overall structure of the programming by examining past programming maintenance. Many data processing shops recognize the importance of documenting programming maintenance descriptions. In fact, some data processing shops require that any programming maintenance that is applied must be documented in the program before it is installed into production. Although this is a convenient place to store the programming maintenance descriptions, there are no efficient and/or effective procedures to facilitate searching. This paper discusses an information retrieval system to assist in managing programming maintenance descriptions in a data processing shop that manages student records.

REFERENCES

• 1: Jim Cowie , Wendy Lehnert, Information extraction, Communications of the ACM, v.39 n.1, p.80-91, Jan. 1996 [doi>10.1145/234173.234209]
• 2: Eastman, Caroline M. <u>Computational Information Retrieval</u>. Manuscript August 1997.
• 3: Darren R. Hardy , Michael F. Schwartz, Customized information extraction as a basis for resource discovery, ACM Transactions on Computer Systems (TOCS), v.14 n.2, p.171-199, May 1996 [doi>10.1145/227695.227697]
• 4: Peter W. Foltz , Susan T. Dumais, Personalized information delivery: an analysis of information filtering methods, Communications of the ACM, v.35 n.12, p.51-60, Dec. 1992 [doi>10.1145/138859.138866]
• 5: David D. Lewis , Karen Spärck Jones, Natural language processing for information retrieval, Communications of the ACM, v.39 n.1, p.92-101, Jan. 1996 [doi>10.1145/234173.234210]