Adeel Ahmad
ABSTRACT
The software evolution is often a continuous process necessary to avoid a short longevity of software use. Its control has recently received renewed attention to minimize unexpected difficult situations resulting from software changes. An applied change on a software artefact can propagate its impact on several other components of whole system. This impact can be considered from structural, qualitative, functional, logical or behavioural point of view. In this paper, we describe a Generic Model of Software Evolution for better change impact analysis through different links between concerned software artefacts. The software evolution control requires a large set of knowledge describing exhaustively software application targeted by change. This knowledge set is built in reference to the proposed model for software evolution. It leads toward the design of knowledge-based expert systems to help in the analysis of change impact flow.
- A. Ahmad, H. Basson, and M. Bouneffa. Software evolution control: Towards a better identification of change impact propagation. In ICET'08: Proceedings of the 4th IEEE International Conference on Emerging Technologies, pages 286--291. IEEE Computer Society, October 2008.Google Scholar
Cross Ref
- A. Ahmad, H. Basson, and M. Bouneffa. Rule-based approach for software evolution management. In IEEE APSSC 2009: IEEE Asia-Pacific Services Computing Conference, December 2009.Google Scholar
- A. Ahmad, H. Basson, L. Deruelle, and M. Bouneffa. Towards a better control of change impact propagation. In INMIC'08: 12th IEEE International Multitopic Conference, pages 286--291. IEEE Computer Society, December 2008.Google ScholarCross Ref
- A. Ahmad, H. Basson, L. Deruelle, and M. Bouneffa. A knowledge-based framework for software evolution control. In INFORSID'09: 28th Conference on Informatique des organisation et systèmes d'information et de décision, pages 286--291, Toulouse, France, May 2009. IRIT Press (www.irit.fr).Google Scholar
- B. W. Boehm, J. R. Brown, and M. Lipow. Quantitative evaluation of software quality. In ICSE '76: Proceedings of the 2nd international conference on Software engineering, pages 592--605, Los Alamitos, CA, USA, 1976. IEEE Computer Society Press. Google ScholarDigital Library
- J. P. Cavano and J. A. McCall. A framework for the measurement of software quality. SIGSOFT Softw. Eng. Notes, 3(5):133--139, 1978. Google ScholarDigital Library
- S. Chulani and B. Boehm. Modeling software defect introduction and removal: Coqualmo, 1999.Google Scholar
- M. D'Ambros and M. Lanza. Reverse engineering with logical coupling. In WCRE '06: Proceedings of the 13th Working Conference on Reverse Engineering, pages 189--198, Washington, DC, USA, 2006. IEEE Computer Society. Google ScholarDigital Library
- M. Dowson. Software process themes and issues, 1993.Google Scholar
- K. Ishikawa. What Is Total Quality Control?: The Japanese Way. Prentice Hall, March 1985.Google Scholar
- H. Kagdi, S. Yusuf, and J. I. Maletic. Mining sequences of changed-files from version histories. In MSR '06: Proceedings of the 2006 international workshop on Mining software repositories, pages 47--53, New York, NY, USA, 2006. ACM. Google ScholarDigital Library
- B. Kitchenham, S. Linkman, A. Pasquini, and V. Nanni. The squid approach to defining a quality model. Software Quality Control, 6(3):211--233, 1997. Google ScholarDigital Library
- B. Kitchenham and L. Pickard. owards a constructive quality model part 2: Statistical techniques for modeling software quality in the esprit request project. Software Engineering Journal, July 1987.Google Scholar
- B. Kitchenham and J. Walker. The meaning of quality. In Software Engineering 86: Proceedings of BCS-IEE Software Engineering 86 Conference, Southampton, England, September 1986.Google Scholar
- M. M. Lehman and J. F. Ramil. Rules and tools for software evolution planning and management, November 2001. Google ScholarDigital Library
- M. Lungu, M. Lanza, T. Girba, and R. Heeck. Reverse engineering super-repositories. In Reverse Engineering, 2007. WCRE 2007. 14th Working Conference on, pages 120--129, 2007. Google ScholarDigital Library
- F. M. Refactoring: Improving the Design of Existing Code. Addison Wesley Object Technology Series, July 1999.Google Scholar
- J. A. Mccall, J. P. Cavano, and G. Walters. Factors in software quality. 1, 2, and 3, November 1977.Google Scholar
- K. Pulford, A. Kuntzmann-Combelles, and S. Shirlaw, editors. A quantitative approach to software management: the AMI handbook. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 1995. Google ScholarDigital Library
- J. I. Rumbaugh J. and B. G. The Unified Modeling Language Reference Manual, 2nd edition. The Addison-Wesley Professional, May 2005. Google ScholarDigital Library
- F. Van Rysselberghe and S. Demeyer. Studying software evolution information by visualizing the change history. In ICSM '04: Proceedings of the 20th IEEE International Conference on Software Maintenance, pages 328--337, Washington, DC, USA, 2004. IEEE Computer Society. Google ScholarDigital Library
- R. Vidgen, J. Wood, and A. Wood-Harper. Customer satisfaction: the need for multiple perspectives of information system quality. Software Quality Management II, 1, 1994.Google Scholar
Index Terms
- Software evolution modelling: an approach for change impact analysis
Recommendations
Software evolution: background, theory, practice
Special issue: Contribution to computing scienceThis paper opens with a brief summary of some 30 years of study of the software evolution phenomenon. The results of those studies include the SPE program classification, a principle of software uncertainty and laws of E-type software evolution. The ...
Evaluating Software Evolution Based on Pattern Mining
Internetware '17: Proceedings of the 9th Asia-Pacific Symposium on InternetwareSoftware systems need constantly maintaining or adapting to continuously meet the changing business requirements. The process of maintenance or adaptation is software evolution. In general, people hope to evaluate software evolution for guiding software ...
Software Maintenance versus Software Evolution: An Approach to Software Systems Evolution
ECBS '96: Proceedings of the IEEE Symposium and Workshop on Engineering of Computer Based SystemsSoftware development is traditionally conceived as a process where the software development team elaborates, implements and maintains executable models of Information Systems (in the broad sense). In this paper we present an evolutionary view of the ...
Comments