Information systems should contribute to enterprise effectiveness, and usually do so during the operational phase of their lifecycle. From the experience of practitioners, the duration of this lifecycle is often not predetermined, therefore resulting in information systems with a relatively long lifespan and information systems with a relatively short lifespan. An important aspect of application management, is managing the application lifecycle. In the experience of practitioners, deciding the moment to end the lifecycle, refactor it, or leave it be are often not thoroughly researched. The decision to move on to a newer information system is therefore not always sufficiently justified and relies more on a gut feeling. What if the older information system is still able to perform and comply with the changes the enterprise desires? Prolonging the length of an application lifecycle could result in cost reduction in an application portfolio. In this paper, we aim to create a method of assessment of the ability to change of a legacy information system and identifying potential areas in which a legacy information system would need improvement in order to increase this ability to change. [ABSTRACT FROM AUTHOR]