Legacy systems: Must history repeat itself?
Kulonda, D, Arif, M and Luce, J 2003, 'Legacy systems: Must history repeat itself?' , Journal of Knowledge Management Practice, Dec .
- Accepted Version
Restricted to Repository staff only
Download (102kB) | Request a copy
Legacy software systems are notorious for repeating the mistakes of the past. However, it is entirely possible that the solutions to problems might be available in their past. Maintaining a Lessons Learned (LL) database and consulting it regularly might result in avoiding potential problems. This research uses surveys as a means to obtain LL and corrective actions taken in legacy systems. It also presents three case studies to demonstrate the utility of LL in legacy systems. This research found that LL are used in legacy systems, however their use is not widespread. When employed, the LL process improves a legacy system’s situation and validates the lessons learned tool utilized by hardware engineering projects. In addition, the research shows that problems facing legacy systems are not isolated, but are replicated throughout industry. Preventive Measures as identified in LL, and applied to new efforts can dramatically affect system life cycle costs but this remains to be verified in subsequent research.
|Themes:||Built and Human Environment|
Schools > School of the Built Environment
Schools > School of the Built Environment > Centre for Built Environment Sustainability and Transformation (BEST)
|Journal or Publication Title:||Journal of Knowledge Management Practice|
|Publisher:||The Leadership alliance inc.|
|Funders:||Non funded research|
|Depositing User:||M Arif|
|Date Deposited:||15 Aug 2015 14:49|
|Last Modified:||01 Dec 2015 00:05|
Actions (login required)
|Edit record (repository staff only)|