An approach for estimating the time needed to perform code changes in business applications

Business applications automate various business processes within an organization. Business analysts frequently modify business processes to maintain a competitive edge. Estimating the time needed to modify a business process is not a trivial task, since changes to the business process result in changes to the source code of which the business analyst has limited knowledge. We propose a change impact metric which estimates the code to be modified as a result of a business process change. We demonstrate the effectiveness of our proposed change impact metric through a case study, using seven large business applications from the OFBiz open source project.

[1]  Charles W. Butler,et al.  Design complexity measurement and testing , 1989, CACM.

[2]  Lionel C. Briand,et al.  Automating impact analysis and regression test selection based on UML designs , 2002, International Conference on Software Maintenance, 2002. Proceedings..

[3]  Ying Zou,et al.  Supporting Change Impact Analysis for Service Oriented Business Applications , 2007, International Workshop on Systems Development in SOA Environments (SDSOA'07: ICSE Workshops 2007).

[4]  Thierry Bodhuin,et al.  Assessment and impact analysis for aligning business processes and software systems , 2005, SAC '05.

[5]  Jeff Offutt,et al.  Change impact analysis of object-oriented software , 1998 .

[6]  Mette Asmild,et al.  Using Data Envelopment Analysis in software development productivity measurement , 2006, Softw. Process. Improv. Pract..

[7]  Harry M. Sneed Impact analysis of maintenance tasks for a distributed object-oriented system , 2001, Proceedings IEEE International Conference on Software Maintenance. ICSM 2001.

[8]  Giuliano Antoniol,et al.  Maintaining traceability during object-oriented software evolution: a case study , 1999, Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360).

[9]  Ying Zou,et al.  An approach for estimating code changes in e-commerce applications , 2008, 2008 10th International Symposium on Web Site Evolution.

[10]  M. Lipow,et al.  Number of Faults per Line of Code , 1982, IEEE Transactions on Software Engineering.

[11]  Samuel Ajila,et al.  Software maintenance: An approach to impact analysis of objects change , 1995, Softw. Pract. Exp..

[12]  Andrea De Lucia,et al.  Recovering Traceability Links using Information Retrieval: a Controlled Experiment , 2007 .

[13]  Sallie M. Henry,et al.  The evaluation of software systems' structure using quantitative software metrics , 1984, Softw. Pract. Exp..

[14]  Giuliano Antoniol,et al.  Recovering Traceability Links between Code and Documentation , 2002, IEEE Trans. Software Eng..

[15]  Shawn A. Bohner,et al.  A framework for software maintenance metrics , 1990, Proceedings. Conference on Software Maintenance 1990.

[16]  Haider Bilal Ripple Effect : A Complexity Measure for Object Oriented Software , 2006 .

[17]  Harvey P. Siy,et al.  Predicting Fault Incidence Using Software Change History , 2000, IEEE Trans. Software Eng..

[18]  Andrian Marcus,et al.  Recovering documentation-to-source-code traceability links using latent semantic indexing , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[19]  Ying Zou,et al.  Model-driven business process recovery , 2004, 11th Working Conference on Reverse Engineering.

[20]  Pnina Soffer Scope analysis: identifying the impact of changes in business process models , 2005, Softw. Process. Improv. Pract..

[21]  Michelle L. Lee,et al.  CHANGE IMPACT ANALYSIS OF OBJECT-ORIENTED , 1998 .

[22]  Lionel C. Briand,et al.  Impact analysis and change management of UML models , 2003, International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings..

[23]  Thierry Bodhuin,et al.  Supporting impact analysis: a semi-automated technique and associated tool , 1995, Proceedings of International Conference on Software Maintenance.

[24]  Doris L. Carver,et al.  Analyzing the impact of changing requirements , 2001, Proceedings IEEE International Conference on Software Maintenance. ICSM 2001.

[25]  John W. Daly,et al.  Evaluating inheritance depth on the maintainability of object-oriented software , 2004, Empirical Software Engineering.

[26]  Jonathan I. Maletic,et al.  Combining Single-Version and Evolutionary Dependencies for Software-Change Prediction , 2007, Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007).

[27]  Frank S. de Boer,et al.  Change impact analysis of enterprise architectures , 2005, IRI -2005 IEEE International Conference on Information Reuse and Integration, Conf, 2005..

[28]  Sue Black,et al.  Computing ripple effect for software maintenance , 2001, J. Softw. Maintenance Res. Pract..

[29]  John W. Daly,et al.  The effect of inheritance on the maintainability of object-oriented software: an empirical study , 1995, Proceedings of International Conference on Software Maintenance.

[30]  Ying Zou,et al.  Recovering Workflows from Multi Tiered E-commerce Systems , 2007, 15th IEEE International Conference on Program Comprehension (ICPC '07).

[31]  Frans L. Leeuw,et al.  Evaluation Systems , 2008 .

[32]  Michael A. Hoffman Automated impact analysis of object-oriented software systems , 2003, OOPSLA '03.

[33]  Emilia Mendes,et al.  Web Metrics-Estimating Design and Authoring Effort , 2001, IEEE Multim..

[34]  Chris F. Kemerer,et al.  A Metrics Suite for Object Oriented Design , 2015, IEEE Trans. Software Eng..

[35]  Harry M. Sneed Estimating the costs of software maintenance tasks , 1995, Proceedings of International Conference on Software Maintenance.

[36]  Gregg Rothermel,et al.  An empirical comparison of dynamic impact analysis algorithms , 2004, Proceedings. 26th International Conference on Software Engineering.

[37]  Richard C. Holt,et al.  Predicting change propagation in software systems , 2004, 20th IEEE International Conference on Software Maintenance, 2004. Proceedings..