It is not uncommon to find that many of today’s data processing systems have been in operation for as many as 30 years. Although the original developers may not have expected their products to be providing useful service in the 1990s, we now know that long lifetimes are an inherent property of many software systems. It is inevitable that any non-trivial system must change over the course of its lifetime. Over a long lifetime, a system will accommodate a large number of changes.
Unable to display preview. Download preview PDF.
References and Further Reading
- Sommerville, I. (1995), Software Engineering, 5th edn. Addison-Wesley, Reading.Google Scholar
- Ulrich, W.M., (1990), The Evolutionary Growth of Software Reengineering and the Decade Ahead. American Programmer, 3 (10), 14–20.Google Scholar
- Tilley, S. (1995), Perspectives on Legacy Systems Reengineering. Reengineering Centre, Software Engineering Institute (SEI), Carnegie Mellon University, USA.Google Scholar
- Arnold, R.S., (1994), A Road Map Guide to Software Reengineering. IEEE Computer Society Press.Google Scholar
- Bennet, K., (editor), (1995) Special edition on legacy systems. IEEE Software, 12 (1).Google Scholar