[1]In software engineering, maintenance is generally defined as any development, enhancement, correction, or adaptation after the initial release of a software product [13, 26]. It includes anything required to keep the system running or to continue access by users over time. According to Schach [26], maintenance consumes about 65% of a software product's cost.

[2]The development and continued existence of institutions and their technologies interact. This is something of a paradox in that we need to know the future in order to design the systems for it. It is worth considering Callon's tale of technological innovation [6]. In his analysis, designers of technical systems are forced to predict the future, since their designs succeed or fail based on their understanding of the potential future. While developing technical solutions, we are forced to confront the sociological issues. We would extend this to argue that the futures come to exist in interaction with the technologies. In short, the sociological and the technical possibilities and constraints are intertwined.

[3]It may be possible that new forms of control and maintenance will arise, but there is no evidence of this as of the present. Developing institutional practices without an institution would be difficult.