Software Modernization Decision Criteria: An Empirical Study

Koskinen, Jussi; Ahonen, Jarmo J.; Sivula, Henna; Tilus, Tero; Lintinen, Heikki; Kankaanpää, Irja

doi:10.1109/csmr.2005.50

Cited by 25 publications

(20 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Correlation for all but one replacement initiation factor, i.e. end of vendor support (R The amount of factors influencing evolution initiation decision is significantly smaller than given before (see Koskinen et al 2005). The results strengthen the previous findings of the importance of engaging both business and technical aspects in evolution decision making (see Aversano et al 2004, Bergey et al 1997).…”

Section: Discussionsupporting

confidence: 81%

“…Another observation is that the modernisation decision criteria reported by Koskinen et al (2005) correspond to replacement initiation factors better than modernisation triggers found in this study. Correlation for all but one replacement initiation factor, i.e.…”

Section: Discussionmentioning

confidence: 49%

“…Table 4 lists the decision criteria reported by Koskinen et al (2005), which are in the text denoted with D, and the findings of this study, denoted with M IF (modernisation initiation factors) and R IF (replacement initiation factors) in a descending order of importance. An interesting finding was that system usability, which was listed as the most objective, end of vendor support, and gaining competitive advantage.…”

Section: Discussionmentioning

confidence: 99%

“…Aversano et al (2004) propose that prior to modernisation decision the technical and the business value of the existing system should be assessed. Koskinen et al (2005) list twenty decision criteria influencing modernisation decision making, the ten most important criteria being: system usability, end of technological support, changes in business processes, maintenance costs, system correctness, system efficiency, expected remaining system lifetime, size of required changes, application domain expertise of maintainers, and delocalized system logic.…”

Section: Evolution Options and Decision Makingmentioning

confidence: 99%

See 3 more Smart Citations

LEGACY SYSTEM EVOLUTION - A Comparative Study of Modernisation and Replacement Initiation Factors

Kankaanpää¹,

Tiihonen²,

Ahonen³

et al. 2007

Proceedings of the Ninth International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Abstract:Decisions regarding information system evolution strategy become topical as the organisation's information systems age and start to approach the end of their life cycle. An interview study was conducted in order to compare factors influencing modernisation and replacement initiation. System age, obsolete technology and high operation or maintenance costs were identified as triggers for both modernisation and replacement projects. The results show that the most prevalent individual reason for modernisation initiative is business development. Common initiation factors for replacement projects were end of vendor support and system's inability to respond to organisation's business needs.

show abstract

Section: Discussionsupporting

confidence: 81%

Section: Discussionmentioning

confidence: 49%

Section: Discussionmentioning

confidence: 99%

Section: Evolution Options and Decision Makingmentioning

confidence: 99%

See 2 more Smart Citations

LEGACY SYSTEM EVOLUTION - A Comparative Study of Modernisation and Replacement Initiation Factors

Kankaanpää¹,

Tiihonen²,

Ahonen³

et al. 2007

Proceedings of the Ninth International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

show abstract

“…We have observed that there is a clear absence of empirical research that measures these benefits, although limited research has been validated with industrial case studies to assess the applicability. Research Paper Cost reduction [8], [24], [7], [11], [27], [28], [29], [30], [31], [32], [33], [34], [35], [4], [36], [37], [38] Increased reusability [8], [24], [29], [30], [34], [35], [37], [39] Increased agility [8], [24], [23], [29], [30], [40], [35], [39] Increased flexibility [8], [24], [23], [11], [28], [32], [37] Improved performance [29], [40], [41], [33], [34], [35], [37] Increased maintainability …”

Section: B Benefits Of Software Modernizationmentioning

confidence: 99%

Does software modernization deliver what it aimed for? A post modernization analysis of five software modernization case studies

Khadka

Shrestha

Klein

et al. 2015

2015 IEEE International Conference on Software Maintenance and Evolution (ICSME)

View full text Add to dashboard Cite

Abstract-Software modernization has been extensively researched, primarily focusing on observing the associated phenomena, and providing technical solutions to facilitate the modernization process. Software modernization is claimed to be successful when the modernization is completed using those technical solutions. Very limited research, if any, is reported with an aim at documenting the post-modernization impacts, i.e., whether any of the pre-modernization business goals are in fact achieved after modernization. In this research, we attempt to address this relative absence of empirical study through five retrospective software modernization case studies. We use an explanatory case study approach to document the pre-modernization business goals, and to decide whether those goals have been achieved. The intended benefits for each of the five cases we considered were all (partially) met, and in most cases fully. Moreover, many cases exhibited a number of unintended benefits, and some reported detrimental effects of modernization.

show abstract