Advances in Software Maintenance Management: Technologies and Solutions (original) (raw)
Related papers
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. Abstract: The process for managing and executing software maintenance activities is described. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities outside of IEEE that have expressed an interest in participating in the development of the standard. Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services r...
2002
This article is an overview of software maintance, its relevance, the problems, and the available solutions. The focus is on the structure of the maintenance activity, including general models of the maintenance process, existing standards, and management practices and tools. The article also includes a discussion of related areas that support software maintenance, and particularly reverse engineering, reengineering, and legacy systems.
Practical Software Maintenance
Journal of Software Maintenance: Research and Practice, 2000
Tom Pigoski's Practical Software Maintenance serves as documentation of the author's years of experience as a software maintenance practitioner. I recently had the opportunity to use portions of this book in a special topics course on late life cycle issues in the Information Systems Department at the University of Maryland Baltimore County. Pigoski's book is not meant as a textbook; its intended audience is software maintenance practitioners in industry. However, as Pigoski notes, no other book exists currently that is geared towards teaching maintenance. So I chose this one to support my course and that is the perspective from which I review it here. My overall experience with the book is that, while it offers unique and valuable insights, it often couches them in ways that are not well comprehended by students with little practical experience, and it lacks some features that would be useful in a classroom setting. First, some facts and figures. The full title of the book is Practical Software Maintenance: Best Practices for Managing Your Software Investment. The main text of the book is nearly 350 pages, divided into 21 chapters, as summarized and detailed in Table I. The book also includes a table of contents (6 pages), a glossary containing 63 definitions (7 pages), an unannotated bibliography with 184 entries (12 pages), a subject index (14 pages), and one page each of preface, acknowledgments, and author biography. Tables, figures, and icons (such as 'Tom's Tips') are used liberally throughout the text. In addition, 28 sidebars called 'Practical Experiences,' ranging from a short paragraph to several pages in length, are sprinkled throughout most of the chapters and give detailed examples from the author's own experience in real software maintenance organizations. Each chapter ends with a few review questions. The introductory chapter is very brief. It presents the author's background, upon which the material in the book is based. Also, a strong statement is made about how maintenance should fit into the overall life cycle. The author proposes, correctly I believe, that maintenance activities must start before delivery, during development, '.. . coincident with the decision to develop a system.. . '. This turns out to be a recurring theme throughout the book. Finally, some terminology is presented. The 'Overview of Software Maintenance' chapter introduces a rather eclectic collection of concepts in software maintenance. Various definitions of maintenance are presented, as well as the basic life cycle models (waterfall, incremental, etc.). There is a discussion of why maintenance is and always will
Software Maintenance: Concepts and Practice
2003
The purpose of this book is to explore the key issues underpinning software change and to discuss how these issues impact on the implementation of changes to software systems. The motivation for the book came from the need for texts dealing directly with challenges that software engineers face when modifying complex software systems. The extent of this challenge can be seen in the cost of modifying software. This cost can reach 70% of the total life-cycle cost [4, 36, 176]. Software maintenance is recognised as a key area in software engineering [9, 163]. Despite this, many mainstream software engineering courses are biased towards the development of new software systems at the expense of issues surrounding changes to these systems after they become operational [70].
Software Maintenance: Challenges and Issues and Models for Reducing the Maintenance Cost
International Journal of Advanced Research in Computer Science, 2017
Software maintenance is a very tedious and vital job in software development life cycle (SDLC). In today’s ever growing technological market outsourcing is done for best product delivery as well high efficiency. The outsourcing companies usually deliver a completed model to the company or user and further evolution or changes are done according to the requests made, these evolution or changes comes under Software Maintenance. Software maintenance is basically the modification done to assure a quality product after it is sent to the company or user who ordered it. This paper discovers the current models and strategies taken up by most of the leading companies for software maintenance and handling. It also explores the common challenges faced and its mitigation strategies. The preventive strategies are then discussed to help reduce for the issues faced by companies so as to overcome the overhead cost after delivering the product. The model/framework and strategies will explain the wor...
MANTEMA: a software maintenance methodology based on the ISO/IEC 12207 standard
Proceedings 4th IEEE International Software Engineering Standards Symposium and Forum (ISESS'99). 'Best Software Practices for the Internet Age', 1999
The maintenance of information systems is one of the greatest problems in the software life cycle: It is the most conflictive, costliest, less planificable; and the process requiring the most resources. In spite of this reality, most organizations do not possess methodologies for software maintenance. These facts, key to the imperative need of controlling the maintenance process, have carried us to propose a maintenance methodology. In this paper an adjustment of the ISO/IEC 12207 standard for the processes of the ltfe cycle maintenance is presented. This methodology is being used by Atos ODS, one of the most important European consultants on software outsourcing and maintenance.
Software maintenance in the telecommunication area-status and perspectives
Proceedings. EUROMICRO '90 Workshop on Real Time, 1990
ABSTRACT The standard classification of software maintenance into the corrective, adaptive, and perfective categories is reviewed and extended for telecommunications applications. General issues that confront telecommunication software maintenance are explored, and implications for the basic functions of the operating systems, the support tools, and the operating companies' needs are considered. Considerations on in-house maintenance are given, and software requirements from the maintenance viewpoint are analyzed. As a practical example, the Italian situation is illustrated and discussed
A Review on Software Maintenance Issues and How to Reduce Maintenance Efforts
Software Maintenance and evolution are identifying by their huge cost and slow speed of implementation. Survey showed that around 60% of the maintenance effort was on the total cost of software. But after delivering the software to the client, the maintenance work begins. This paper suggests some issues and problems faced by software maintenance process. There are some issues of software maintenance i.e.: database size, system age, maintenance budget, system size, staff size or restructuring for change. This paper presents several ways to reduce cost and efforts involved in software maintenance. Software maintenance costs can be reduced significantly if the software architecture is well defined, clearly documented, and creates an environment that promotes design consistency through the use of guidelines and testing quality. Keywords Software maintenance, issues and problems in software maintenance, cost and challenges in maintenance, maintenance cost reduction.
Software Maintenance Like Maintenance in Other Engineering Disciplines
Proceedings of the 22Nd ACM SIGSOFT International Symposium on Foundations of Software Engineering, 2014
Software maintenance exhibits many differences regarding how other engineering disciplines carry out maintenance on their artifacts. Such dissimilarity is caused due to the fact that it is easy to get a copy from the original artifact to be used in maintenance, and also because the flat dimension of the software text facilitates access to the components by simply using a text editor. Other engineering disciplines resort to different artifact 'versions' (obtained by dissassembling) where the introduction of modifications (previous comprehension) is easier. After which the artifact is reassembled. In software engineering this approach can be simulated by combining program transformation techniques, search-based software engineering technology and design attributes.