An incremental approach to software systems re-engineering
Journal of Software Maintenance: Research and Practice
Modeling software evolution by evolving interoperation graphs
Annals of Software Engineering
Software Maintenance Management
Software Maintenance Management
Legacy Systems: Coping with Success
IEEE Software
ACM Transactions on Computer Systems (TOCS)
Rules and Tools for Software Evolution Planning and Management
Annals of Software Engineering
Software Evolution and Software Evolution Processes
Annals of Software Engineering
Evolution in software and related areas
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Role of concepts in software evolution
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Achieving ultra rapid evolution using service-based software
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Software Cultures and Evolution
Computer
On Architectural Stability and Evolution
Ada-Europe '02 Proceedings of the 7th Ada-Europe International Conference on Reliable Software Technologies
Behavioural modelling of long-lived evolution processes: some issues and an example
Journal of Software Maintenance: Research and Practice - Special issue: Separation of concerns for software evolution
An Approach to Modelling Long-Term Growth Trends in Software Systems
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
An Architectural Model for Service-Based Software with Ultra Rapid Evolution
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
RIPPLES: Tool for Change in Legacy Software
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Analogy of Incremental Program Development and Constructivist Learning
ICCI '03 Proceedings of the 2nd IEEE International Conference on Cognitive Informatics
Understanding Service-Oriented Software
IEEE Software
Incremental Change in Object-Oriented Programming
IEEE Software
Changing the paradigm of software engineering
Communications of the ACM - Music information retrieval
Subjective evaluation of software evolvability using code smells: An empirical study
Empirical Software Engineering
Adapting the "staged model for software evolution" to free/libre/open source software
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
The UID Approach --the Balance between Hard and Soft Methodologies
Proceedings of the 2005 conference on Software Engineering: Evolution and Emerging Technologies
Change profiles of a reused class framework vs. two of its applications
Information and Software Technology
The Linux kernel as a case study in software evolution
Journal of Systems and Software
A longitudinal study of development and maintenance
Information and Software Technology
Rapid Application Lifecycle Management: a new Approach with Tool Support
Proceedings of the 2010 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the 9th SoMeT_10
Perpetual development: A model of the Linux kernel life cycle
Journal of Systems and Software
Model-driven software migration into service-oriented architectures
Computer Science - Research and Development
ACM Computing Surveys (CSUR)
Hi-index | 4.10 |
Software engineers have traditionally considered any work after initial delivery as simply software maintenance. Some researchers have divided this work into various tasks, including making changes to functionality (perfective), changing the environment (adaptive), correcting errors (corrective), and making improvements to avoid future problems (preventive). However, many have considered maintenance basically uniform over time. Because software development has changed considerably since its early days, the authors believe this approach no longer suffices. They describe a new view of the software life cycle in which maintenance is actually a series of distinct stages, each with different activities, tools, and business consequences. While the industry still considers postdelivery work as simply software maintenance, the authors claim that the process actually falls into stages. They think both business and engineering can benefit from understanding these stages and their transitions.