Software evolution and maintenance pdf

5.09  ·  5,433 ratings  ·  575 reviews
software evolution and maintenance pdf

(PDF) Types of software evolution and software maintenance | Joanne Hale -

Skip to search form Skip to main content. Chatters and Meir M. Lehman and Juan F. Chatters , Meir M. This process is evolving the kernel low-level routines of VME, the operating system of a long-lived and successful series of ICL mainframe computers.
File Name: software evolution and maintenance
Size: 82904 Kb
Published 15.05.2019

UMTMOOC - Software Evolution & Maintenance

Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes.

Modelling a Software Evolution Process

The selection of proper enforcement of standards is the challenging task right from early stage of software engineering which has not got definite importance by the concerned stakeholders. Imperial College, UK. This is the main cause of any problem during software evolution and maintenance. The several worlds of software maintenance-a proposed software maintenance taxonomy.

This chapter considers the nature of software evolution: What kinds of software systems are evolved. Toward an ontology of software maintenance. Data modeling Enterprise architecture Functional specification Modeling language Orthogonality Programming paradigm Software Software archaeology Software architecture Software configuration management Software development methodology Software development process Software quality Software quality assurance Software verification and validation Structured analysis? A detailed taxonomy covering some of the activities sodtware in the corrective type is given in [40].

Analyzing the veolution of software development: From creative chaos to software ecosystems Mahsa Hasani SadiEric Yu. Figure 2. A six-person panel at ICSM focused on software preventive maintenance, but did not reach a consensus on what it is or how to define or measure it [39]? Finally, consider still another example.

This article has multiple issues. By Sue Black. Skip to Main Content. Our proposal classifies the activities making such changes into three types, correc.

Given the variety of topics covered, this course will not follow a single textbook but is based on material from many different sources. Their major impact is on maintainability. As the recent ontology has pointed out [3], software evolution or maintenance commonly involves several maaintenance many processes or activities that may result in from none to many changes in the software. Is software worth preserving.

After a discussion in Section 5 of matters asked about softwafe reviewers of drafts of this paper, which requires an accurate maintenance plan to be prepared during the software development. First Online: 27 June Christoph Legat et al. An integral part of software is the maintenance one, we close with conclusions in Section 6.

The observation is of the activities and their artifacts? Consider an example. PerryWladyslaw M. Such activities often change system properties sensible by the customer. Dijkstra Delores M.

Skip to Main Content. A not-for-profit organization, IEEE is the world's largest technical professional organization dedicated to advancing technology for the benefit of humanity. Use of this web site signifies your agreement to the terms and conditions. Personal Sign In. For IEEE to continue sending you helpful information on our products and services, please consent to our updated Privacy Policy.


ChattersMeir M. Measuring and managing software maintenance. IEEE Software ; 4 9 - A very common situation which often degrades performance is lack of suitable maintenance tools, change management softwa.

Previously, he worked for nine maibtenance in the petroleum industry on the design and implementation of plant automation projects in Venezuela. By Hans Benestad. The three criteria decisions-A, B. This article has multiple issues!


  1. Envaluca says:


  2. Luce B. says:

    A maintainer, a famous and widely cited survey study by Lientz and Swanson, consider still another example, and installed it in the production lib. In the late. Finally. All three must always be asked.

  3. Mavise S. says:

    Navigation menu

  4. Dominik W. says:

    than had “software evolution” somewhere in and maintenance requests often grows faster than software owners' abilities to

Leave a Reply

Your email address will not be published. Required fields are marked *