Historic Value of In-House Software Systems

“Unlike computer hardware, which is by definition a tangible ‘‘thing’’ that can be readily isolated, identified, and evaluated (and whose maintenance can be anticipated and accounted for), computer software has been inextricably linked to a larger sociotechnical system that includes machines (computers and their associated peripherals), people (users, designers, and developers), and processes (the corporate payroll system, for example). Software maintenance is therefore as much a social as a technological endeavor. Usually what needs to be ‘‘fixed’’ is the ongoing negotiation between the expectations of users, the larger context of use and operation, and the features of the software system in question.”

“Most software maintenance involves what are vaguely referred to … as ‘‘enhancements.’’ Enhancements sometimes involved strictly technical measures— such as implementing performance optimizations—but most often ... termed ‘‘responses to changes in the business environment.’’ This included the introduction of new functionality, as dictated by market, organizational, or legislative developments, but also changes in the larger technological or organizational system in which the software was inextricably bound.”

- N. Ensmenger (2009) “Software as History Embodied”

Every staff member involved in the development and maintenance of in-house software systems has contributed in a significant way to the mission and history of the University of Texas. The story of computing history at UT helps to tell the stories of computing history in higher education nationwide and the software industry at large. Specifically, business logic/software applications created in-house to support mission-critical tasks such as payroll, purchasing and student registration provide evidence of the creative use of technology locally to address new challenges for the university (including business pressures from alternative higher education models) as well as trends, best practices and conventions in software development which place those applications in the larger context of computing history.

The University Archives is dedicated to preserving this layered history.