Log in

Relevant bibliographies by topics / Software maintenance and evolution / Journal articles

Journal articles on the topic 'Software maintenance and evolution'

To see the other types of publications on this topic, follow the link: Software maintenance and evolution.

Author: Grafiati

Published: 4 June 2021

Last updated: 11 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Software maintenance and evolution.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

1

Chapin, Ned, Joanne E. Hale, Khaled Md Khan, Juan F. Ramil, and Wui-Gee Tan. "Types of software evolution and software maintenance." Journal of Software Maintenance and Evolution: Research and Practice 13, no. 1 (January 2001): 3–30. http://dx.doi.org/10.1002/smr.220.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Carver, Jeffrey C., and Alexander Serebrenik. "Software Maintenance and Evolution and Automated Software Engineering." IEEE Software 35, no. 2 (March 2018): 102–4. http://dx.doi.org/10.1109/ms.2018.1661318.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Von Mayrhauser, A., and A. M. Vans. "Program comprehension during software maintenance and evolution." Computer 28, no. 8 (1995): 44–55. http://dx.doi.org/10.1109/2.402076.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Seaman, Carolyn B. "Managing Corporate Information Systems Evolution and Maintenance." Journal of Software Maintenance and Evolution: Research and Practice 18, no. 4 (2006): 307–9. http://dx.doi.org/10.1002/smr.331.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Buckley, Jim. "Requirements-Based Visualization Tools for Software Maintenance and Evolution." Computer 42, no. 4 (April 2009): 106–8. http://dx.doi.org/10.1109/mc.2009.127.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Coplien, James O. "ISHMAEL: An Integrated Software/Hardware Maintenance and Evolution Environment." AT&T Technical Journal 70, no. 1 (January 2, 1991): 52–63. http://dx.doi.org/10.1002/j.1538-7305.1991.tb00497.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Harman, M., B. Korel, and P. K. Linos. "Guest Editorial: Special Issue on Software Maintenance and Evolution." IEEE Transactions on Software Engineering 31, no. 10 (October 2005): 801–3. http://dx.doi.org/10.1109/tse.2005.113.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Penta, Massimiliano Di, and Jonathan I. Maletic. "Guest editorial: special section on software maintenance and evolution." Empirical Software Engineering 20, no. 2 (March 29, 2015): 410–12. http://dx.doi.org/10.1007/s10664-015-9382-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Kwon, Oh Cheon, Cornelia Boldyreff, and Malcolm Munro. "Software Configuration Management for a Reusable Software Library within a Software Maintenance Environment." International Journal of Software Engineering and Knowledge Engineering 08, no. 04 (December 1998): 483–515. http://dx.doi.org/10.1142/s0218194098000273.

Full text

Abstract:

Software Configuration Management and software reuse are now generally considered to be important technologies in software engineering. Both have been proposed for making a significant improvement in productivity and quality. However, these two technologies have been investigated separately. In order to make Software Configuration Management and reuse more effective, both approaches require to be introduced into a development or maintenance environment together. The authors have developed a process model for Maintenance with Reuse (MwR) to support Software Configuration Management for a reuse library within a maintenance environment. As software reuse and Software Configuration Management as well as software reuse and software maintenance have many similarities in their activities, and these areas can therefore be integrated within a software maintenance environment. An integrated approach to the common areas of these different activities will greatly contribute to the productivity and quality of software. This paper will address an integrated approach that can overcome some of the barriers that exist in software maintenance and reuse. A process model of an integrated approach has been created and validated using Process Weaver. In order for the reuse library to allow accesses from many potential reusers, the process model has been implemented on the WWW. The paper describes an integrated process model and its prototype to support change and version control for evolution of software components within both a reuse library and a legacy system.

APA, Harvard, Vancouver, ISO, and other styles

10

RILLING, JUERGEN, RENÉ WITTE, PHILIPP SCHUEGERL, and PHILIPPE CHARLAND. "BEYOND INFORMATION SILOS — AN OMNIPRESENT APPROACH TO SOFTWARE EVOLUTION." International Journal of Semantic Computing 02, no. 04 (December 2008): 431–68. http://dx.doi.org/10.1142/s1793351x08000567.

Full text

Abstract:

Nowadays, software development and maintenance are highly distributed processes that involve a multitude of supporting tools and resources. Knowledge relevant for a particular software maintenance task is typically dispersed over a wide range of artifacts in different representational formats and at different abstraction levels, resulting in isolated 'information silos'. An increasing number of task-specific software tools aim to support developers, but this often results in additional challenges, as not every project member can be familiar with every tool and its applicability for a given problem. Furthermore, historical knowledge about successfully performed modifications is lost, since only the result is recorded in versioning systems, but not how a developer arrived at the solution. In this research, we introduce conceptual models for the software domain that go beyond existing program and tool models, by including maintenance processes and their constituents. The models are supported by a pro-active, ambient, knowledge-based environment that integrates users, tasks, tools, and resources, as well as processes and history-specific information. Given this ambient environment, we demonstrate how maintainers can be supported with contextual guidance during typical maintenance tasks through the use of ontology queries and reasoning services.

APA, Harvard, Vancouver, ISO, and other styles

11

Moonen, Leon, and Lori Pollock. "Introduction to the special issue on software maintenance and evolution." Journal of Software: Evolution and Process 28, no. 7 (July 2016): 510–11. http://dx.doi.org/10.1002/smr.1798.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

CANFORA, GERARDO, FILIPPO LANUBILE, and GIUSEPPE VISAGGIO. "IESEM: INTEGRATED ENVIRONMENT FOR SOFTWARE EVOLUTION MANAGEMENT." International Journal of Software Engineering and Knowledge Engineering 05, no. 01 (March 1995): 49–71. http://dx.doi.org/10.1142/s0218194095000046.

Full text

Abstract:

Software evolution has no common paradigm which practitioners can adhere to. On the contrary, there is a wide range of models, methods, techniques, and tools which are selected according to the specific task, the application domain, the professional experience, and the organizational culture. We argue that different approaches and technologies may be combined into a unique platform to satisfy the needs of software systems which evolve over long periods of time. This paper presents the Integrated Environment for Software Evolution Management (IESEM) which includes software repositories, reverse engineering tools, rationale capture tools, software measurement tools, and a user-friendly interface. It can manage heterogeneous systems characterized by various design methods and programming languages. IESEM is based on a central repository which stores software engineering artifacts, program code, design, and implementation decisions in the form of a traceability graph. The repository stores also software measures computed both from programs and external CASE repositories. Measures are used to control software degradation during its evolution and to support decisions based on quality factors. The key concepts of IESEM, its design, and implementation are presented. The use of IESEM during development and maintenance is discussed. A case study shows IESEM's effectiveness in performing maintenance tasks.

APA, Harvard, Vancouver, ISO, and other styles

13

Spinellis, Diomidis, Panos Louridas, and Maria Kechagia. "Software evolution: the lifetime of fine-grained elements." PeerJ Computer Science 7 (February 9, 2021): e372. http://dx.doi.org/10.7717/peerj-cs.372.

Full text

Abstract:

A model regarding the lifetime of individual source code lines or tokens can estimate maintenance effort, guide preventive maintenance, and, more broadly, identify factors that can improve the efficiency of software development. We present methods and tools that allow tracking of each line’s or token’s birth and death. Through them, we analyze 3.3 billion source code element lifetime events in 89 revision control repositories. Statistical analysis shows that code lines are durable, with a median lifespan of about 2.4 years, and that young lines are more likely to be modified or deleted, following a Weibull distribution with the associated hazard rate decreasing over time. This behavior appears to be independent from specific characteristics of lines or tokens, as we could not determine factors that influence significantly their longevity across projects. The programing language, and developer tenure and experience were not found to be significantly correlated with line or token longevity, while project size and project age showed only a slight correlation.

APA, Harvard, Vancouver, ISO, and other styles

14

Seinturier, Lionel, and Mark van den Brand. "Preface to the special section on software evolution, adaptability, and maintenance." Science of Computer Programming 78, no. 8 (August 2013): 969–70. http://dx.doi.org/10.1016/j.scico.2013.02.008.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Angerer, Florian, Andreas Grimmer, Herbert Prähofer, and Paul Grünbacher. "Change impact analysis for maintenance and evolution of variable software systems." Automated Software Engineering 26, no. 2 (February 7, 2019): 417–61. http://dx.doi.org/10.1007/s10515-019-00253-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Hayashi, Shinpei, and Michael L. Collard. "Special Issue: International Conference on Software Maintenance and Evolution (ICSME 2019)." Science of Computer Programming 212 (December 2021): 102706. http://dx.doi.org/10.1016/j.scico.2021.102706.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Guéhéneuc, Yann-Gaël, and Tom Mens. "Introduction to the special issue on software maintenance and evolution research." Empirical Software Engineering 20, no. 5 (August 15, 2015): 1193–97. http://dx.doi.org/10.1007/s10664-015-9398-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Li, Jing Lei. "Retrieval and Modelling of Software Evolution Process Component." Applied Mechanics and Materials 241-244 (December 2012): 2867–71. http://dx.doi.org/10.4028/www.scientific.net/amm.241-244.2867.

Full text

Abstract:

As more and more successful software systems become legacy systems,the importance and popularity of software evolution increase[1]. In order to make the mature software systems as components, so that they can be re-assembled and maintenance as automobile parts. In this context, the software evolution process component formal definition is designed based on this background. And then define the component model. Based on the questions in component retrieval, faceted classification of the Components and the theory of tree matching algorithm is discussed and analyzed. The Retrieval of Software Evolution Process Component is designed with the theory of tree matching algorithm so as to support the software evolution process modelling.

APA, Harvard, Vancouver, ISO, and other styles

19

Donzelli, Paolo. "Tailoring the software maintenance process to better support complex systems evolution projects." Journal of Software Maintenance and Evolution: Research and Practice 15, no. 1 (January 2003): 27–40. http://dx.doi.org/10.1002/smr.266.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Benestad, Hans Christian, Bente Anda, and Erik Arisholm. "Understanding software maintenance and evolution by analyzing individual changes: a literature review." Journal of Software Maintenance and Evolution: Research and Practice 21, no. 6 (November 2009): 349–78. http://dx.doi.org/10.1002/smr.412.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Arcelli Fontana, Francesca, Marco Zanoni, Andrea Ranchetti, and Davide Ranchetti. "Software Clone Detection and Refactoring." ISRN Software Engineering 2013 (March 19, 2013): 1–8. http://dx.doi.org/10.1155/2013/129437.

Full text

Abstract:

Several studies have been proposed in the literature on software clones from different points of view and covering many correlated features and areas, which are particularly relevant to software maintenance and evolution. In this paper, we describe our experience on clone detection through three different tools and investigate the impact of clone refactoring on different software quality metrics.

APA, Harvard, Vancouver, ISO, and other styles

22

Park, Jaeyong, Seok-Won Lee, and David C. Rine. "UML design pattern metamodel-level constraints for the maintenance of software evolution." Software: Practice and Experience 43, no. 7 (October 3, 2011): 835–66. http://dx.doi.org/10.1002/spe.1116.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Alenezi, Mamdouh, and Fakhry Khellah. "Evolution Impact on Architecture Stability in Open-Source Projects." International Journal of Cloud Applications and Computing 5, no. 4 (October 2015): 24–35. http://dx.doi.org/10.4018/ijcac.2015100102.

Full text

Abstract:

Software systems usually evolve constantly, which requires constant development and maintenance. Subsequently, the architecture of these systems tends to degrade with time. Therefore, stability is a key measure for evaluating an architecture. Open-source software systems are becoming progressively vital these days. Since open-source software systems are usually developed in a different management style, the quality of their architectures needs to be studied. ISO/IEC SQuaRe quality standard characterized stability as one of the sub-characteristics of maintainability. Unstable software architecture could cause the software to require high maintenance cost and effort. In this work, the authors propose a simple, yet efficient, technique that is based on carefully aggregating the package level stability in order to measure the change in the architecture level stability as the architecture evolution happens. The proposed method can be used to further study the cause behind the positive or negative architecture stability changes.

APA, Harvard, Vancouver, ISO, and other styles

24

Lu, Chih-Wei, William C. Chu, Chih-Hung Chang, Don-Lin Yang, and Wen-Da Lian. "Integrating diverse paradigms in evolution and maintenance by an XML-based unified model." Journal of Software Maintenance and Evolution: Research and Practice 15, no. 3 (2003): 111–44. http://dx.doi.org/10.1002/smr.272.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Malhotra, Ruchika, and Megha Khanna. "Analyzing Evolution Patterns of Object-Oriented Metrics." International Journal of Rough Sets and Data Analysis 6, no. 3 (July 2019): 49–66. http://dx.doi.org/10.4018/ijrsda.2019070104.

Full text

Abstract:

Software evolution is mandatory to keep it useful and functional. However, the quality of the evolving software may degrade due to improper incorporation of changes. Quality can be monitored by analyzing the trends of software metrics extracted from source code as these metrics represent the structural characteristics of a software such as size, coupling, inheritance etc. An analysis of these metric trends will give insight to software practitioners regarding effects of software evolution on its internal structure. Thus, this study analyzes the trends of 14 object-oriented (OO) metrics in a widely used mobile operating system software, Android. The study groups the OO metrics into four dimensions and analyzes the trends of these metrics over five versions of Android software (4.0.2-4.3.1). The results of the study indicate certain interesting patterns for the evaluated dimensions, which can be helpful to software practitioners for outlining specific maintenance decisions to improve software quality.

APA, Harvard, Vancouver, ISO, and other styles

26

Dit, Bogdan, Evan Moritz, Mario Linares-Vásquez, Denys Poshyvanyk, and Jane Cleland-Huang. "Supporting and accelerating reproducible empirical research in software evolution and maintenance using TraceLab Component Library." Empirical Software Engineering 20, no. 5 (December 13, 2014): 1198–236. http://dx.doi.org/10.1007/s10664-014-9339-3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Pazos, Florencio, and Monica Chagoyen. "Characteristics and evolution of the ecosystem of software tools supporting research in molecular biology." Briefings in Bioinformatics 20, no. 4 (January 16, 2018): 1329–36. http://dx.doi.org/10.1093/bib/bby001.

Full text

Abstract:

Abstract Daily work in molecular biology presently depends on a large number of computational tools. An in-depth, large-scale study of that ‘ecosystem’ of Web tools, its characteristics, interconnectivity, patterns of usage/citation, temporal evolution and rate of decay is crucial for understanding the forces that shape it and for informing initiatives aimed at its funding, long-term maintenance and improvement. In particular, the long-term maintenance of these tools is compromised because of their specific development model. Hundreds of published studies become irreproducible de facto, as the software tools used to conduct them become unavailable. In this study, we present a large-scale survey of >5400 publications describing Web servers within the two main bibliographic resources for disseminating new software developments in molecular biology. For all these servers, we studied their citation patterns, the subjects they address, their citation networks and the temporal evolution of these factors. We also analysed how these factors affect the availability of these servers (whether they are alive). Our results show that this ecosystem of tools is highly interconnected and adapts to the ‘trendy’ subjects in every moment. The servers present characteristic temporal patterns of citation/usage, and there is a worrying rate of server ‘death’, which is influenced by factors such as the server popularity and the institutions that hosts it. These results can inform initiatives aimed at the long-term maintenance of these resources.

APA, Harvard, Vancouver, ISO, and other styles

28

WARD, M. P., and K. H. BENNETT. "FORMAL METHODS TO AID THE EVOLUTION OF SOFTWARE." International Journal of Software Engineering and Knowledge Engineering 05, no. 01 (March 1995): 25–47. http://dx.doi.org/10.1142/s0218194095000034.

Full text

Abstract:

There is a vast collection of operational software systems which are vitally important to their users, yet are becoming increasingly difficult to maintain, enhance, and keep up to date with rapidly changing requirements. For many of these so-called legacy systems, the option of throwing the system away and rewriting it from scratch is not economically viable. Methods are therefore urgently required which enable these systems to evolve in a controlled manner. The approach described in this paper uses formal proven program transformations, which preserve or refine the semantics of a program while changing its form. These transformations are applied to restructure and simplify the legacy systems and to extract higher-level representations. By using an appropriate sequence of transformations, the extracted representation is guaranteed to be equivalent to the code. The method is based on a formal wide spectrum language, called WSL, with an accompanying formal method. Over the last ten years we have developed a large catalog of proven transformations, together with mechanically verifiable applicability conditions. These have been applied to many software development, reverse engineering, and maintenance problems. In this paper, we focus on the results of using this approach in the reverse engineering of medium scale, industrial software, written mostly in languages such as assembler and JOVIAL. Results from both benchmark algorithms and heavily modified, geriatric software are summarized. We conclude that formal methods have an important practical role in software evolution.

APA, Harvard, Vancouver, ISO, and other styles

29

Schlie, Alexander, Safa Bougouffa, Juliane Fischer, Ina Schaefer, and Birgit Vogel-Heuser. "Change analysis on evolving PLC software in automated production systems." at - Automatisierungstechnik 66, no. 10 (October 25, 2018): 806–18. http://dx.doi.org/10.1515/auto-2018-0037.

Full text

Abstract:

Abstract Control software for automated Production Systems (aPSs) becomes increasingly complex. Respective systems undergo constant evolution. Yet, proper documentation may not always be present, entailing maintenance issues in the long run. While manual examination of software for aPSs is an error-prone task, static analysis can improve system quality. However, it has not been applied to describe software evolution by means of changed systems artifacts. The authors address this issue and perform change analyses on IEC61131-3 projects, identifying introduced and removed systems artifacts as well as existing ones affected. By that, the authors aim to support sustainable evolution. Two feasibility studies, implemented independently, but for the same evolution scenarios for an automation plant, are used for evaluation. The technique is shown to be efficient and highly precise.

APA, Harvard, Vancouver, ISO, and other styles

30

Laser, Marcelo Schmitt, Elder Macedo Rodrigues, Anderson Domingues, Flavio Oliveira, and Avelino F. Zorzo. "Research Notes on the Architectural Evolution of a Software Product Line." International Journal of Software Engineering and Knowledge Engineering 25, no. 09n10 (November 2015): 1753–58. http://dx.doi.org/10.1142/s0218194015710126.

Full text

Abstract:

This work presents an experience report on the architectural decisions taken in the evolution of a Software Product Line (SPL) of Model-based Testing tools (PLeTs). This SPL was partially designed and developed with the intention of minimizing effort and time-to-market during the development of a family of performance testing tools. With the evolution of our research and the addition of new features to the SPL, we identified limitations in the initial architectural design of PLeTs’ components, which led us to redesign its Software Product Line Architecture (SPLA). In this paper, we discuss the main issues that led to changes in our SPLA, as well as present the design decisions that facilitate its evolution in the context of an industrial environment. We will also report our experiences on architecture modifications in the evolution of our SPL with the intention of allowing easier maintenance in a volatile development environment.

APA, Harvard, Vancouver, ISO, and other styles

31

Wilson, Leon A., Maksym Petrenko, and Václav Rajlich. "Using Concept Maps to Assist Program Comprehension and Concept Location: An Empirical Study." Journal of Information & Knowledge Management 11, no. 03 (September 2012): 1250018. http://dx.doi.org/10.1142/s0219649212500189.

Full text

Abstract:

Program comprehension is an integral part of the evolution and maintenance of large software systems. As it is increasingly difficult to comprehend these systems completely, programmers have to rely on a partial and as-needed comprehension. We study partial comprehension and programmer learning with the use of concept maps as a tool for capturing programmer knowledge during concept location, which is one of the tasks of software evolution and maintenance, and it is a prerequisite of a software change. We conduct a user study to measure the performance of programmers using concept maps to assist with locating concepts. The results demonstrate that programmer learning occurs during concept location and that concept maps assisted programmers with capturing programmer learning and successful concept location.

APA, Harvard, Vancouver, ISO, and other styles

32

Falah, Bouchaib, Sara El Alaoui, and Hajar Abbadi. "Investigating the Effect of Software Complexity Metrics on Software Cost." Applied Mechanics and Materials 548-549 (April 2014): 1319–25. http://dx.doi.org/10.4028/www.scientific.net/amm.548-549.1319.

Full text

Abstract:

Nowadays, software is expected to have an extended lifespan, which makes the evaluation of its complexity at the early stages critical in upcoming maintenance. Indeed, complexity is proportional to the evolution of software. Software metrics were introduced as tools that allow us to obtain an objective measurement of the complexity of software. Hence, enabling software engineering to assess and manage software complexity. Reducing software costs is one of the major concerns of software engineering which creates an increasing need for new methodologies and techniques to control those costs. Software complexity metrics can help us to do so. In this paper, we would investigate how those metrics can be used to reduce software costs. We would first analyze the most popular complexity metrics and distinguish their properties. Then, we will show how each of those metrics fit within the software life cycle. Finally, we will provide a detailed approach to use the complexity metrics to reduce software costs.

APA, Harvard, Vancouver, ISO, and other styles

33

AMOUI, MEHDI, MAZEIAR SALEHIE, and LADAN TAHVILDARI. "TEMPORAL SOFTWARE CHANGE PREDICTION USING NEURAL NETWORKS." International Journal of Software Engineering and Knowledge Engineering 19, no. 07 (November 2009): 995–1014. http://dx.doi.org/10.1142/s0218194009004489.

Full text

Abstract:

Predicting changes in software entities (e.g. source files) that are more likely to change can help in the efficient allocation of the project resources. A powerful change prediction tool can improve maintenance and evolution tasks in software projects in terms of cost and time factors. The vast majority of research works have focused on determining "where" the most change-prone entities are, and "how" the change will be propagated through a system. This article suggests that knowing "when" changes are likely to happen can also provide another consideration for managers and developers to plan their maintenance activities more efficiently. To address this issue, a Neural Network-based Temporal Change Prediction (NNTCP) framework is proposed. This novel framework indicates "where" the changes are likely to happen (i.e. hot spots), and then adds the time dimension to predict "when" it may occur. In proving this concept, the NNTCP framework is applied in two large-scale open source software projects, Mozilla and Eclipse. The results obtained indicate NNTCP can predict the occurrence of several future revisions with reasonable performance.

APA, Harvard, Vancouver, ISO, and other styles

34

Gyimothy, T., and V. Rajlich. "Guest Editors' Introduction to the Special Issue on the International Conference on Software Maintenance and Evolution." IEEE Transactions on Software Engineering 32, no. 9 (2006): 625–26. http://dx.doi.org/10.1109/tse.2006.89.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Binkley, David, Rainer Koschke, and Spiros Mancoridis. "Guest Editors' Introduction to the Special Section from the International Conference on Software Maintenance and Evolution." IEEE Transactions on Software Engineering 33, no. 12 (December 2007): 797–98. http://dx.doi.org/10.1109/tse.2007.70765.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Aversano, Lerina, Umberto Carpenito, and Martina Iammarino. "An Empirical Study on the Evolution of Design Smells." Information 11, no. 7 (July 4, 2020): 348. http://dx.doi.org/10.3390/info11070348.

Full text

Abstract:

The evolution of software systems often leads to its architectural degradation due to the presence of design problems. In the literature, design smells have been defined as indicators of such problems. In particular, the presence of design smells could indicate the use of constructs that are harmful to system maintenance activities. In this work, an investigation on the nature and presence of design smells has been performed. An empirical study has been conducted considering the complete history of eight software systems, commit by commit. The detection of instances of multiple design smell types has been performed at each commit, and the analysis of the relationships between the detected smells and the maintenance activities, specifically due to refactoring activities, has been investigated. The proposed study evidenced that classes affected by design smells are more subject to change, especially when multiple smells are detected in the same classes. Moreover, it emerged that in some cases these smells are removed, and this occurs involving more smells at the same time. Finally, results indicate that smells removals are not correlated to the refactoring activities.

APA, Harvard, Vancouver, ISO, and other styles

37

Domagała, Adam, Katarzyna Grobler-Dębska, Jarosław Wąs, and Edyta Kucharska. "Post-Implementation ERP Software Development: Upgrade or Reimplementation." Applied Sciences 11, no. 11 (May 27, 2021): 4937. http://dx.doi.org/10.3390/app11114937.

Full text

Abstract:

The paper deals with problems in the post-implementation phase of management Enterprise Resource Planning (ERP) systems. Proper management of the system maintenance stage is a basis for efficient system development in terms of business needs. Based on the research and analysis of collected materials, it turns out that making a decision to upgrade the system is equally crucial. We present revealed mechanisms determining the post-implementation approach to upgrade or reimplement the ERP system. The main aim is to determine the methodology and difference understanding to achieve success in the post-implementation stage. The paper shows that the systemic approach to the maintenance stage of the ERP system affects its further decisions: upgrade or reimplement. It has a direct impact on future maintenance costs and the scope of new business demands. This research is an outcome of industry–academia collaboration and based on several developed implementation systems, achieved upgrade and reimplementation projects. Based on case study analysis, we show that reimplementation means an evolution of the current ERP processes rather than another attempt to “reimplement” an unsuccessful system implementation. On the other hand, upgrades are not only a tool or system actualization but the easiest way to bolster company sustainability and to have the information system up to date. The issues discussed in the article will be used to develop changes in the implementation methodology of ERP systems.

APA, Harvard, Vancouver, ISO, and other styles

38

Koskinen, Jussi. "Seminars on Software Maintenance and Evolution: An Empirical Study of the Background Factors Affecting Student Success." Open Software Engineering Journal 3, no. 1 (June 18, 2009): 39–71. http://dx.doi.org/10.2174/1874107x00903010039.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Koskinen, Jussi. "Seminars on Software Maintenance and Evolution: An Empirical Study of the Background Factors Affecting Student Success." Open Software Engineering Journal 4, no. 1 (June 24, 2013): 39–71. http://dx.doi.org/10.2174/1874107x01003010039.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

XING, ZHENCHANG, and ELENI STROULIA. "UNDERSTANDING THE EVOLUTION AND CO-EVOLUTION OF CLASSES IN OBJECT-ORIENTED SYSTEMS." International Journal of Software Engineering and Knowledge Engineering 16, no. 01 (February 2006): 23–51. http://dx.doi.org/10.1142/s0218194006002707.

Full text

Abstract:

As software systems evolve over a long time, non-trivial and often unintended relationships among system classes arise, which cannot be easily perceived through source-code reading. As a result, the developers' understanding of continuously evolving, large, long-lived systems deteriorates steadily. A most interesting relationship is class co-evolution: because of implicit design dependencies clusters of classes change in "parallel" ways and recognizing such co-evolution is crucial in effectively extending and maintaining the system. In this paper, we propose a data-mining method for recovering "hidden" co-evolutions of system classes. This method relies on our UML-aware structural differencing algorithm, UMLDiff, which, given a sequence of UML class models of an object-oriented software system, produces a sequence of "change records" that describe the design-level changes over its life span. The change records are analyzed from the perspective of each individual system class to extract "class change profiles". Each phase of a class change profile is then discretized and classified into one of two general change types: function extension or refactoring. Finally, the Apriori association-rule mining algorithm is applied to the database of categorical class change profiles, to elicit co-evolution patterns among two or more classes, which may be as yet undocumented and unknown. The recovered knowledge facilitates the overall understanding of system evolution and the planning of future maintenance activities. We report on one real world case study evaluating our approach.

APA, Harvard, Vancouver, ISO, and other styles

41

Dinh, Duy, Julio Cesar Dos Reis, Cédric Pruski, Marcos Da Silveira, and Chantal Reynaud-Delaître. "Identifying relevant concept attributes to support mapping maintenance under ontology evolution." Journal of Web Semantics 29 (December 2014): 53–66. http://dx.doi.org/10.1016/j.websem.2014.05.002.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Wang, Xiaofeng, Shu Guo, Jian Shen, and Yang Liu. "Optimization of preventive maintenance for series manufacturing system by differential evolution algorithm." Journal of Intelligent Manufacturing 31, no. 3 (May 20, 2019): 745–57. http://dx.doi.org/10.1007/s10845-019-01475-y.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Alseadoon, Ibrahim. "Motivations, challenges, and process support for the evolution of existing software to mobile computing platforms." International Journal of ADVANCED AND APPLIED SCIENCES 8, no. 5 (May 2021): 89–106. http://dx.doi.org/10.21833/ijaas.2021.05.011.

Full text

Abstract:

Software maintenance and evolution support changes in the structure and behavior of existing software to change it as per the needs and demands of new requirements. The majority of the existing software systems lack features of mobile computing such as portability, context-awareness, connectivity, and high interactivity. The evolution of the existing software for mobile computing platforms can enable these systems to retain their core data and logic while acquiring new features that are compatible with mobile systems. The objectives of this research are to (i) systematically identify the motivations and challenges of software evolution for mobile computing, and (ii) develop and validate a process model that supports the evolution of existing software to a mobile computing platform. To conduct this research, an empirical software engineering approach has been adopted to investigate existing solutions (30 published studies from 1996 to 2019) and empirically derive a process model that supports software evolution for mobile computing. A case study-based approach is adopted to demonstrate the process-centric evolution of existing software as a mobile-enabled application. Case study-based demonstration highlights that the proposed process (i) supports an incremental evolution and (ii) allows user-decision support to guide the evolution process. Evaluation results highlight computation and energy efficiency along with enhanced usability of a mobile application when executed on resource-constrained mobile devices. The results of this research could help researchers and practitioners to rationalize motivations and challenges to utilize a process-based approach to evolve existing or aging software for mobile computing platforms. Future research is focused on providing patterns and tool support to automate and customize the evolution process.

APA, Harvard, Vancouver, ISO, and other styles

44

Nanthaamornphong, Aziz, Jeffrey Carver, Karla Morris, and Salvatore Filippone. "Extracting UML Class Diagrams from Object-Oriented Fortran: ForUML." Scientific Programming 2015 (2015): 1–15. http://dx.doi.org/10.1155/2015/421816.

Full text

Abstract:

Many scientists who implement computational science and engineering software have adopted the object-oriented (OO) Fortran paradigm. One of the challenges faced by OO Fortran developers is the inability to obtain high level software design descriptions of existing applications. Knowledge of the overall software design is not only valuable in the absence of documentation, it can also serve to assist developers with accomplishing different tasks during the software development process, especially maintenance and refactoring. The software engineering community commonly uses reverse engineering techniques to deal with this challenge. A number of reverse engineering-based tools have been proposed, but few of them can be applied to OO Fortran applications. In this paper, we propose a software tool to extract unified modeling language (UML) class diagrams from Fortran code. The UML class diagram facilitates the developers' ability to examine the entities and their relationships in the software system. The extracted diagrams enhance software maintenance and evolution. The experiments carried out to evaluate the proposed tool show its accuracy and a few of the limitations.

APA, Harvard, Vancouver, ISO, and other styles

45

Syeed, M. M. Mahbubul, Imed Hammouda, and Tarja Systä. "Prediction Models and Techniques for Open Source Software Projects." International Journal of Open Source Software and Processes 5, no. 2 (April 2014): 1–39. http://dx.doi.org/10.4018/ijossp.2014040101.

Full text

Abstract:

Open Source Software (OSS) is currently a widely adopted approach to developing and distributing software. For effective adoption of OSS, fundamental knowledge of project development is needed. This often calls for reliable prediction models to simulate project evolution and to envision project future. These models provide help in supporting preventive maintenance and building quality software. This paper reports on a systematic literature survey aimed at the identification and structuring of research that offer prediction models and techniques in analyzing OSS projects. In this review, we systematically selected and reviewed 52 peer reviewed articles that were published between January, 2000 and March, 2013. The study outcome provides insight in what constitutes the main contributions of the field, identifies gaps and opportunities, and distills several important future research directions.

APA, Harvard, Vancouver, ISO, and other styles

46

Cowling, James Austin, and Wendy K. Ivins. "Assessing the Potential Improvement an Open Systems Development Perspective Could Offer to the Software Evolution Paradigm." International Journal of Information Technologies and Systems Approach 9, no. 2 (July 2016): 68–87. http://dx.doi.org/10.4018/ijitsa.2016070105.

Full text

Abstract:

Emerging stakeholder needs and a changing environment drive increasing demands for the constant adaption of software through maintenance and new capability development. A more evolutionary software engineering approach is sought to improve engineering responsiveness; Open System Development appears to offer a partial contribution but presents many challenges. This exploratory research proposes a new definition of the evolution of complex engineered systems, building on the essential features of ‘openness' described by Cowling et al (2014) and Lehman's (1980) ideas of evolutionary software. Using Checkland's (1999) Soft System Methodology enabled a structured literature review and analysis of the relative contributions of three divergent methodologies to the success of systems outcomes. These methodologies are: Plan-Driven, Agile, and Open Source Software Development. The analysis reveals several opportunities and highlights the critical issue of determining return on investment which needs to be overcome if an open approach is to contribute to evolutionary software engineering.

APA, Harvard, Vancouver, ISO, and other styles

47

Carvalho, Nuno, Alberto Simões, and José Almeida. "DMOSS: Open source software documentation assessment." Computer Science and Information Systems 11, no. 4 (2014): 1197–207. http://dx.doi.org/10.2298/csis131005027c.

Full text

Abstract:

Besides source code, the fundamental source of information about open source software lies in documentation, and other non source code files, like README, INSTALL, or How-To files, commonly available in the software ecosystem. These documents, written in natural language, provide valuable information during the software development stage, but also in future maintenance and evolution tasks. DMOSS3 is a toolkit designed to systematically assess the quality of non source code content found in software packages. The toolkit handles a package as an attribute tree, and performs several tree traverse algorithms through a set of plugins, specialized in retrieving specific metrics from text, gathering information about the software. These metrics are later used to infer knowledge about the software, and composed together to build reports that assess the quality of specific features. This paper discusses the motivations for this work, continues with a description of the toolkit implementation and design goals. This is followed by an example of its usage to process a software package, and the produced report.

APA, Harvard, Vancouver, ISO, and other styles

48

Iglesias, Aitziber, Goiuria Sagardui, and Cristobal Arellano. "Industrial Cyber-Physical System Evolution Detection and Alert Generation." Applied Sciences 9, no. 8 (April 17, 2019): 1586. http://dx.doi.org/10.3390/app9081586.

Full text

Abstract:

Industrial Cyber-Physical System (ICPS) monitoring is increasingly being used to make decisions that impact the operation of the industry. Industrial manufacturing environments such as production lines are dynamic and evolve over time due to new requirements (new customer needs, conformance to standards, maintenance, etc.) or due to the anomalies detected. When an evolution happens (e.g., new devices are introduced), monitoring systems must be aware of it in order to inform the user and to provide updated and reliable information. In this article, CALENDAR is presented, a software module for a monitoring system that addresses ICPS evolutions. The solution is based on a data metamodel that captures the structure of an ICPS in different timestamps. By comparing the data model in two subsequent timestamps, CALENDAR is able to detect and effectively classify the evolution of ICPSs at runtime to finally generate alerts about the detected evolution. In order to evaluate CALENDAR with different ICPS topologies (e.g., different ICPS sizes), a scalability test was performed considering the information captured from the production lines domain.

APA, Harvard, Vancouver, ISO, and other styles

49

Karray, Mohamed-Hedi, Brigitte Chebel-Morello, and Noureddine Zerhouni. "PETRA: Process Evolution using a TRAce-based system on a maintenance platform." Knowledge-Based Systems 68 (September 2014): 21–39. http://dx.doi.org/10.1016/j.knosys.2014.03.010.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Kapur, P. K., Saurabh Panwar, Vivek Kumar, and Ompal Singh. "Entropy-Based Two-Dimensional Software Reliability Growth Modeling for Open-Source Software Incorporating Change-Point." International Journal of Reliability, Quality and Safety Engineering 27, no. 05 (March 2, 2020): 2040009. http://dx.doi.org/10.1142/s0218539320400094.

Full text

Abstract:

This study provides an analytical model to predict the fixing pattern of issues in the open-source software (OSS) packages to assist developers in software development and maintenance. Moreover, the continuous evolution of software due to bugs removal, new features addition or existing features modification results in the source code complexity. The proposed model quantifies the complexity in the source code using the Shannon entropy measure. In addition, the issues fixing growth behavior is viewed as a function of continuation time of the software in the field environment and amount of uncertainty or complexity present in the source code. Therefore, a two-dimensional function called Cobb–Douglas production function is applied to model the intensity function of the issues fixing rate. Furthermore, the rate of fixing the different issue types is considered variable that may alter after certain time points. Thus, this study incorporates the concept of multiple change-points to predict and assess the fixing behavior of issues in the software system. The performance of the proposed model is validated by fitting the proposed model to the actual issues data of three open-source projects. Findings of the data analysis exhibit excellent prediction and estimation capability of the model.

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!