Relevant bibliographies by topics / Software maintenance and evolution

Academic literature on the topic '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:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources 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.

Journal articles on the topic "Software maintenance and evolution"

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
More sources

Dissertations / Theses on the topic "Software maintenance and evolution"

1

Akhlaq, Usman, and Muhammad Usman Yousaf. "Impact of Software Comprehension in Software Maintenance and Evolution." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2176.

Full text
Abstract:
The need of change is essential for a software system to reside longer in the market. Change implementation is only done through the maintenance and successful software maintenance gives birth to a new software release that is a refined form of the previous one. This phenomenon is known as the evolution of the software. To transfer software from lower to upper or better form, maintainers have to get familiar with the particular aspects of software i.e. source code and documentation. Due to the poor quality of documentation maintainers often have to rely on source code. So, thorough understanding of source code is necessary for effective change implementation. This study explores the code comprehension problems discussed in the literature and prioritizes them according to their severity level given by maintenance personnel in the industry. Along with prioritizing the problems, study also presents the maintenance personnel suggested methodologies for improving code comprehension. Consideration of these suggestions in development might help in shortening the maintenance and evolution time.
Usman Akhlaq Mirpur, Azad Kashmir, Pakistan Muhammad Usman Yousaf Bhimber, Azad Kashmir, Pakistan
APA, Harvard, Vancouver, ISO, and other styles
2

Keller, Benjamin J. "An algebraic model of software evolution." Thesis, This resource online, 1990. http://scholar.lib.vt.edu/theses/available/etd-03122009-040841/.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gethers, Malcom Bernard II. "Information Integration for Software Maintenance and Evolution." W&M ScholarWorks, 2012. https://scholarworks.wm.edu/etd/1539720326.

Full text
Abstract:
Software maintenance and evolution is a particularly complex phenomenon in the case of long-lived, large-scale systems. It is not uncommon for such systems to progress through years of development history, a number of developers, and a multitude of software artifacts including millions of lines of code. Therefore, realizing even the slightest change may not always be straightforward. Clearly, changes are the central force driving software evolution. Therefore, it is not surprising that a significant effort has been (and should be) devoted in the software engineering community to systematically understanding, estimating, and managing changes to software artifacts. This effort includes the three core change related tasks of (1) expert developer recommendations - identifying who are the most experienced developers to implement needed changes, (2) traceability link recovery recovering dependencies (traceability links) between different types of software artifacts, and (3) software change impact analysis - which other software entities should be changed given a starting point.;This dissertation defines a framework for an integrated approach to support three core software maintenance and evolution tasks: expert developer recommendation, traceability link recovery, and software change impact analysis. The framework is centered on the use of conceptual and evolutionary relationships latent in structured and unstructured software artifacts. Information Retrieval (IR) and Mining Software Repositories (MSR) based techniques are used for analyzing and deriving these relationships. All the three tasks are supported under the framework by providing systematic combinations of MSR and IR analyses on single and multiple versions of a software system. Our approach to the integration of information is what sets it apart from previously reported relevant solutions in the literature. Evaluation on a number of open source systems suggests that such combinations do offer improvements over individual approaches.
APA, Harvard, Vancouver, ISO, and other styles
4

Chow, Kingsum. "Supporting library interface changes in open system software evolution /." Thesis, Connect to this title online; UW restricted, 1996. http://hdl.handle.net/1773/6999.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Murphy, Gail C. "Lightweight structural summarization as an aid to software evolution /." Thesis, Connect to this title online; UW restricted, 1996. http://hdl.handle.net/1773/6976.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Alhindawi, Nouh. "Supporting source code comprehension during software evolution and maintenance." Thesis, Kent State University, 2014. http://pqdtopen.proquest.com/#viewpdf?dispub=3618939.

Full text
Abstract:

This dissertation addresses the problems of program comprehension to support the evolution of large-scale software systems. The research concerns how software engineers locate features and concepts along with categorizing changes within very large bodies of source code along with their versioned histories. More specifically, advanced Information Retrieval (IR) and Natural Language Processing (NLP) are utilized and enhanced to support various software engineering tasks. This research is not aimed at directly improving IR or NLP approaches; rather it is aimed at understanding how additional information can be leveraged to improve the final results. The work advances the field by investigating approaches to augment and re-document source code with different types of abstract behavior information. The hypothesis is that enriching the source code corpus with meaningful descriptive information, and integrating this orthogonal information (semantic and structural) that is extracted from source code, will improve the results of the IR methods for indexing and querying information. Moreover, adding this new information to a corpus is a form of supervision. That is, apriori knowledge is often used to direct and supervise machine-learning and IR approaches.

The main contributions of this dissertation involve improving on the results of previous work in feature location and source code querying. The dissertation demonstrates that the addition of statically derived information from source code (e.g., method stereotypes) can improve the results of IR methods applied to the problem of feature location. Further contributions include showing the effects of eliminating certain textual information (comments and function calls) from being included when performing source code indexing for feature/concept location. Moreover, the dissertation demonstrates an IR-based method of natural language topic extraction that assists developers in gaining an overview of past maintenance activities based on software repository commits.

The ultimate goal of this work is to reduce the costs, effort, and time of software maintenance by improving the results of previous work in feature location and source code querying, and by supporting a new platform for enhancing program comprehension and facilitating software engineering research.

APA, Harvard, Vancouver, ISO, and other styles
7

Alhindawi, Nouh Talal. "Supporting Source Code Comprehension During Software Evolution and Maintenance." Kent State University / OhioLINK, 2013. http://rave.ohiolink.edu/etdc/view?acc_num=kent1374790792.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Decker, Michael John. "srcDiff: Syntactic Differencing to Support Software Maintenance and Evolution." Kent State University / OhioLINK, 2017. http://rave.ohiolink.edu/etdc/view?acc_num=kent150074391000591.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Dam, Khanh Hoa, and s3007289@student rmit edu au. "Supporting Software Evolution in Agent Systems." RMIT University. Computer Science and Information Technology, 2009. http://adt.lib.rmit.edu.au/adt/public/adt-VIT20090319.143847.

Full text
Abstract:
Software maintenance and evolution is arguably a lengthy and expensive phase in the life cycle of a software system. A critical issue at this phase is change propagation: given a set of primary changes that have been made to software, what additional secondary changes are needed to maintain consistency between software artefacts? Although many approaches have been proposed, automated change propagation is still a significant technical challenge in software maintenance and evolution. Our objective is to provide tool support for assisting designers in propagating changes during the process of maintaining and evolving models. We propose a novel, agent-oriented, approach that works by repairing violations of desired consistency rules in a design model. Such consistency constraints are specified using the Object Constraint Language (OCL) and the Unified Modelling Language (UML) metamodel, which form the key inputs to our change propagation framework. The underlying change propagation mechanism of our framework is based on the well-known Belief-Desire-Intention (BDI) agent architecture. Our approach represents change options for repairing inconsistencies using event-triggered plans, as is done in BDI agent platforms. This naturally reflects the cascading nature of change propagation, where each change (primary or secondary) can require further changes to be made. We also propose a new method for generating repair plans from OCL consistency constraints. Furthermore, a given inconsistency will typically have a number of repair plans that could be used to restore consistency, and we propose a mechanism for semi-automatically selecting between alternative repair plans. This mechanism, which is based on a notion of cost, takes into account cascades (where fixing the violation of a constraint breaks another constraint), and synergies between constraints (where fixing the violation of a constraint also fixes another violated constraint). Finally, we report on an evaluation of the approach, covering both effectiveness and efficiency.
APA, Harvard, Vancouver, ISO, and other styles
10

Timsina, Achyuta, and Shree Dimna Prajapati. "Mobile Applications Evolution." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2579.

Full text
Abstract:
Due to improved computing power, connectivity and interaction capability of mobile devices, their popularity and general acceptance in mass population has increased in recent years. Mobile applications are software systems running on mobile hand-held devices such as smart phones and tablets. Due to obvious differences in mobile applications, the evolution studies on them is of high importance. The primary objective is to study and compare the mobile applications evolution with the Lehman's laws of software evolution. Next is to identify and report how the software development team size influences mobile applications evolution. The study is conducted on 9 different open source mobile applications among which 5 were developed by single core developer and 4 were developed by multiple core developers. The selected projects' code repository is cloned into local copy and a number of tools are used on those repositories for extraction of relevant metrics from the artifacts. The Lehman laws are tested graphically, analytically and in some cases statistically. Six of the Lehman's laws are tested for validation in sample mobile applications. Among the six laws, I-Continuing Change is found supportive, III-Self Regulation and VI-Continuing Growth are found partial supportive in mobile applications. The II-Increasing complexity and V-Conservation of Familiarity are inconclusive. The IV-Conservation of Organizational Stability is not supportive in our sample mobile applications. Moreover, mobile applications are developed by a single or a few developers. Small team mobile projects have less time between releases compared to large team projects. The growth pattern of mobile applications is different than that predicted by Lehman laws.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software maintenance and evolution"

1

Tripathy, Priyadarshi, and Kshirasagar Naik. Software Evolution and Maintenance. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2014. http://dx.doi.org/10.1002/9781118964637.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Arthur, Lowell Jay. Software evolution: The software maintenance challenge. New York: Wiley, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Effective Software Maintenance and Evolution. London: Taylor and Francis, 2007.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Varga, Ervin. Unraveling Software Maintenance and Evolution. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Tripathy, Priyadarshi. Software evolution and maintenance: A practitioner's approach. Hoboken, New Jersey: Wiley, 2015.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Emerging technologies for the evolution and maintenance of software models. Hershey, PA: Information Science Reference, 2012.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

International, Conference on Software Maintenance (2001 Florence Italy). Proceedings, IEEE International Conference on Software Maintenance: Systems and software evolution in the era of the Internet : Florence, Italy, 7-9 November, 2001. Los Alamitos, Calif: IEEE Computer Society, 2001.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Westlund, Steve. Software maintenance. St. Louis, MO: Washington University in St. Louis, Center for the Study of Data Processing, 1991.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Mens, Tom, and Serge Demeyer. Software Evolution. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-76440-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

McCall, James A. Software maintenance management. Gaithersburg, MD: U.S. Dept. of Commerce, National Bureau of Standards, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software maintenance and evolution"

1

Coulange, Bernard. "Maintenance and Evolution of Components." In Software Reuse, 193–211. London: Springer London, 1998. http://dx.doi.org/10.1007/978-1-4471-1511-3_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Varga, Ervin. "Architecture and Evolution." In Unraveling Software Maintenance and Evolution, 39–70. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Varga, Ervin. "Introduction." In Unraveling Software Maintenance and Evolution, 3–16. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Varga, Ervin. "Scale of Deployment." In Unraveling Software Maintenance and Evolution, 319–34. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Varga, Ervin. "Context, Rules, and Principles." In Unraveling Software Maintenance and Evolution, 17–29. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Varga, Ervin. "Maintainability and Development." In Unraveling Software Maintenance and Evolution, 31–38. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Varga, Ervin. "Ad Hoc Development." In Unraveling Software Maintenance and Evolution, 73–157. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Varga, Ervin. "Disciplined Development." In Unraveling Software Maintenance and Evolution, 159–244. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Varga, Ervin. "Reengineering and Reverse Engineering." In Unraveling Software Maintenance and Evolution, 247–89. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Varga, Ervin. "Multifaceted Loose Coupling." In Unraveling Software Maintenance and Evolution, 293–97. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-71303-8_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software maintenance and evolution"

1

Bennett, Keith H., and Václav T. Rajlich. "Software maintenance and evolution." In the conference. New York, New York, USA: ACM Press, 2000. http://dx.doi.org/10.1145/336512.336534.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Rajlich, Václav. "Software evolution and maintenance." In ICSE '14: 36th International Conference on Software Engineering. New York, NY, USA: ACM, 2014. http://dx.doi.org/10.1145/2593882.2593893.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gallagher, Keith, Mark Fioravanti, and Suzanne Kozaitis. "Teaching Software Maintenance." In 2019 IEEE International Conference on Software Maintenance and Evolution (ICSME). IEEE, 2019. http://dx.doi.org/10.1109/icsme.2019.00054.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Perry. "Dimensions of software evolution." In Proceedings International Conference on Software Maintenance. IEEE Comput. Soc. Press, 1994. http://dx.doi.org/10.1109/icsm.1994.336765.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Yan, Yan, Massimiliano Menarini, and William Griswold. "Mining Software Contracts for Software Evolution." In 2014 IEEE International Conference on Software Maintenance and Evolution (ICSME). IEEE, 2014. http://dx.doi.org/10.1109/icsme.2014.76.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Bakota, Tibor, Rudolf Ferenc, and Tibor Gyimothy. "Clone Smells in Software Evolution." In 2007 IEEE International Conference on Software Maintenance. IEEE, 2007. http://dx.doi.org/10.1109/icsm.2007.4362615.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

"Laws and principles of evolution." In Proceedings International Conference on Software Maintenance. IEEE, 2002. http://dx.doi.org/10.1109/icsm.2002.1167751.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Huang, Shihong. "Frontiers of Web site evolution." In 2008 Frontiers of Software Maintenance (FoSM). IEEE, 2008. http://dx.doi.org/10.1109/fosm.2008.4659251.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Subramanian, S. "CRUISE: using interface hierarchies to support software evolution." In 1988 Conference on Software Maintenance. IEEE, 1988. http://dx.doi.org/10.1109/icsm.1988.10153.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Pang, Candy, and Abram Hindle. "Continuous Maintenance." In 2016 IEEE International Conference on Software Maintenance and Evolution (ICSME). IEEE, 2016. http://dx.doi.org/10.1109/icsme.2016.45.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software maintenance and evolution"

1

Oreizy, Peyman, and Richard N. Taylor. Decentralized Software Evolution. Fort Belvoir, VA: Defense Technical Information Center, September 2003. http://dx.doi.org/10.21236/ada440842.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Osborne, Wilma M. Software maintenance management. Gaithersburg, MD: National Bureau of Standards, 1985. http://dx.doi.org/10.6028/nbs.sp.500-129.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Osborne, Wilma M. Executive guide to software maintenance. Gaithersburg, MD: National Bureau of Standards, 1985. http://dx.doi.org/10.6028/nbs.sp.500-130.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Osborne, Wilma M., and Ron Raigrodski. Annotated bibliogrpahy on software maintenance. Gaithersburg, MD: National Bureau of Standards, 1986. http://dx.doi.org/10.6028/nbs.sp.500-141.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Engle, Charles B., Gary Ford, and Tim Korson. Software Maintenance Exercises for a Software Engineering Project Course. Fort Belvoir, VA: Defense Technical Information Center, February 1989. http://dx.doi.org/10.21236/ada235779.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Sitaraman, Murali, and E. J. Harner. Center of Excellence of Software Evolution. Fort Belvoir, VA: Defense Technical Information Center, October 2001. http://dx.doi.org/10.21236/ada398492.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Lieberherr, Karl. Evolution of Software via Adaptive Programming. Fort Belvoir, VA: Defense Technical Information Center, October 2002. http://dx.doi.org/10.21236/ada408399.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Dampier, David A., and Valdis Berzins. Software Change-Merging in Dynamic Evolution. Fort Belvoir, VA: Defense Technical Information Center, August 1995. http://dx.doi.org/10.21236/ada299317.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Landis, L. D., A. J. Fine, A. L. Gilbert, and P. M. Hyland. Automatic Documentation Methodologies for Software Maintenance. Fort Belvoir, VA: Defense Technical Information Center, January 1989. http://dx.doi.org/10.21236/ada204752.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Schneidewind, Norman F. Software Maintenance: The Need for Standardization. Fort Belvoir, VA: Defense Technical Information Center, February 1989. http://dx.doi.org/10.21236/ada205229.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software maintenance and evolution' for particular source types:
Journal articles Dissertations / Theses Books
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!

To the bibliography