Estimation of the business value of software modernizations

Article · January 2004with752 Reads
ELTIS is a research project aiming at supporting the process of selecting software modernization strategies and estimating the business value of modernizations. The project is funded by TEKES (National Technology Agency of Finland) and Finnish software industry. Modernizations are large-scale changes of information systems which are performed in order to keep it operational and competitive. Determination of the business value of software and its modernizations is an important but difficult problem. Both software suppliers and their user organizations enter decision making processes while considering possible modernizations. Decisions are typically made by groups of experts in a complex organizational setting. Relevant decision criteria of the software supplier include software maintenance benefits, risks, and costs. These issues include the effects of possible related reengineering and other factors. This position paper shortly describes our project, work done so far, and our research agenda: we aim at empirical data gathering and long-term iterative process improvement in co-operation with software industry.
    • "The successive changes in a software system degrade its quality, and thus, a new and improved system should replace the previous one. However, the wholesale replacement of these systems from scratch is risky since it has a great impact in technological, human and economic terms [7] [16]. The technological and human point of view is affected since replacement would involve retraining all the users in order to understand the new system and the new technology, or the new system may lack specific functionalities that are missing due to the technological changes. "
    [Show abstract] [Hide abstract] ABSTRACT: Companies have a vast number of existing software systems, which are not immune to software erosion and ageing as a consequence of uncontrolled maintenance over time. Currently, there are several metrics to measure and quantify software erosion, which also recommends some maintenance actions to deal with software erosion. Unfortunately, there are many symptoms at the same time and several possible maintenance actions that could be carried out. As a consequence, this uncertain environment implies that the best set of actions is unknown and cannot be certainly linked to specific detected erosion symptoms. This paper provides a fuzzy rule-based system to address that challenge. The system is divided into two levels: the first one recognizes precise software erosion metrics and provides fuzzy software erosion symptoms; and the second one takes the fuzzy symptoms and finally obtains fuzzy maintenance actions. This system is therefore a decision-making mechanism to select the best set of actions depending on the specific software erosion symptoms. This system has been implemented using the Matlab Fuzzy Logic Toolbox and it was simulated using Simulink.
    Full-text · Article · Apr 2011 · Software Practice and Experience
    • "re-implementation of the system with an improved design or a better technology). However, software modernization involves an important risk, i.e., the loss of business knowledge that was progressively embedded in enterprise information systems [12]. This is valuable knowledge since it implicitly represents the organization's business processes, and must therefore be preserved when modernizing the respective information systems. "
    [Show abstract] [Hide abstract] ABSTRACT: Legacy information systems age over time as a consequence of the uncontrolled maintenance and need to be modernized. Process mining allows the discovery of business processes embedded in legacy information systems, which is necessary to preserve the legacy business knowledge, and align them with the new, modernized information systems. There are two main approaches to address the mining of business processes from legacy information systems: (i) the static approach that only considers legacy source code's elements from a syntactical viewpoint; and (ii) the dynamic approach, which also considers information derived by system execution. Unfortunately, there is a lack of empirical evidence facilitating the selection of one of them. This paper provides a formal comparison of the static and dynamic approach through a case study. This study shows that the static approach provides better performance, while the dynamic approach discovers more accurate business processes.
    Full-text · Conference Paper · Jan 2011 · Software Practice and Experience
  • [Show abstract] [Hide abstract] ABSTRACT: Business processes have become one of the key assets of organization, since these processes allow them to discover and control what occurs in their environments, with information systems automating most of an organization's processes. Unfortunately, and as a result of uncontrolled maintenance, information systems age over time until it is necessary to replace them with new and modernized systems. However, while systems are aging, meaningful business knowledge that is not present in any of the organization's other assets gradually becomes embedded in them. The preservation of this knowledge through the recovery of the underlying business processes is, therefore, a critical problem. This paper provides, as a solution to the aforementioned problem, a model-driven procedure for recovering business processes from legacy information systems. The procedure proposes a set of models at different abstraction levels, along with the model transformations between them. The paper also provides a supporting tool, which facilitates its adoption. Moreover, a real-life case study concerning an e-government system applies the proposed recovery procedure to validate its effectiveness and efficiency. The case study was carried out by following a formal protocol to improve its rigor and replicability. Copyright © 2011 John Wiley & Sons, Ltd.
    Full-text · Article · Feb 2012