Are you looking for read ebook online? Search for your book and save it on your Kindle device, PC, phones or tablets. Download Tutorial on Software Maintenance PDF full book. Access full book title Tutorial on Software Maintenance by Girish Parikh. Download full books in PDF and EPUB format.
Author: Girish Parikh Publisher: ISBN: Category : Computers Languages : en Pages : 386
Book Description
Software maintenance, the work done on a software system after it becomes operational, consumes at least half of all technical and management resources expended in the software area. This volume supplies an overview of software maintenance : what it is, how to do it, how to manage it, and trends in current research. The thirty-one papers included are frequently requested from their authors, from hard-to-find sources, cover the foundations of current thinking on this topic, and extend the frontiers of research.
Author: Girish Parikh Publisher: ISBN: Category : Computers Languages : en Pages : 386
Book Description
Software maintenance, the work done on a software system after it becomes operational, consumes at least half of all technical and management resources expended in the software area. This volume supplies an overview of software maintenance : what it is, how to do it, how to manage it, and trends in current research. The thirty-one papers included are frequently requested from their authors, from hard-to-find sources, cover the foundations of current thinking on this topic, and extend the frontiers of research.
Author: Girish Parikh Publisher: Wiley-Interscience ISBN: Category : Computers Languages : en Pages : 456
Book Description
Containing technical and managerial tips, techniques, guidelines, sources and case studies, here is a total guide to effective and economical software management. Using a question- answer format throughout, it addresses just about every issue and topic software managers and technicians face on the job, including the latest maintenance technologies such as structured and software tool-based technologies, common terminology, program rewriting, the role of the user in maintenance, maintaining vendor packages, and the future of software management and technology.
Author: Phaneendra Nath Vellanky Publisher: Universal-Publishers ISBN: 1581129807 Category : Languages : en Pages : 591
Book Description
Computer systems play an important role in our society. Software drives those systems. Massive investments of time and resources are made in developing and implementing these systems. Maintenance is inevitable. It is hard and costly. Considerable resources are required to keep the systems active and dependable. We cannot maintain software unless maintainability characters are built into the products and processes. There is an urgent need to reinforce software development practices based on quality and reliability principles. Though maintenance is a mini development lifecycle, it has its own problems. Maintenance issues need corresponding tools and techniques to address them. Software professionals are key players in maintenance. While development is an art and science, maintenance is a craft. We need to develop maintenance personnel to master this craft. Technology impact is very high in systems world today. We can no longer conduct business in the way we did before. That calls for reengineering systems and software. Even reengineered software needs maintenance, soon after its implementation. We have to take business knowledge, procedures, and data into the newly reengineered world. Software maintenance people can play an important role in this migration process. Software technology is moving into global and distributed networking environments. Client/server systems and object-orientation are on their way. Massively parallel processing systems and networking resources are changing database services into corporate data warehouses. Software engineering environments, rapid application development tools are changing the way we used to develop and maintain software. Software maintenance is moving from code maintenance to design maintenance, even onto specification maintenance. Modifications today are made at specification level, regenating the software components, testing and integrating them with the system. Eventually software maintenance has to manage the evolution and evolutionary characteristics of software systems. Software professionals have to maintain not only the software, but the momentum of change in systems and software. In this study, we observe various issues, tools and techniques, and the emerging trends in software technology with particular reference to maintenance. We are not searching for specific solutions. We are identifying issues and finding ways to manage them, live with them, and control their negative impact.
Author: Alain April Publisher: John Wiley & Sons ISBN: 0470258020 Category : Computers Languages : en Pages : 336
Book Description
This book explores the domain of software maintenance management and provides road maps for improving software maintenance organizations. It describes full maintenance maturity models organized by levels 1, 2, and 3, which allow for benchmarking and continuous improvement paths. Goals for each key practice area are also provided, and the model presented is fully aligned with the architecture and framework of software development maturity models of CMMI and ISO 15504. It is complete with case studies, figures, tables, and graphs.
Author: Norman F. Schneidewind Publisher: John Wiley & Sons ISBN: 0738156779 Category : Computers Languages : en Pages : 54
Book Description
Computer systems, whether hardware or software, are subject to failure. Precisely, what is a failure? It is defined as: The inability of a system or system component to perform a required function within specified limits. Afailure may be produced when a fault is encountered and a loss of the expected service to the user results [IEEE/AIAA P1633]. This brings us to the question of what is a fault? A fault is defect in the hardware or computer code that can be the cause of one or more failures. Software-based systems have become the dominant player in the computer systems world. Since it is imperative that computer systems operate reliably, considering the criticality of software, particularly in safety critical systems, the IEEE and AIAA commissioned the development of the Recommended Practice on Software Reliability. This tutorial serves as a companion document with the purpose of elaborating on key software reliability process practices in more detail than can be specified in the Recommended Practice. However, since other subjects like maintainability and availability are also covered, the tutorial can be used as a stand-alone document. While the focus of the Recommended Practice is software reliability, software and hardware do not operate in a vacuum. Therefore, both software and hardware are addressed in this tutorial in an integrated fashion. The narrative of the tutorial is augmented with illustrative solved problems. The recommended practice [IEEE P1633] is a composite of models and tools and describes the "what and how" of software reliability engineering. It is important for an organization to have a disciplined process if it is to produce high reliability software. This process uses a life cycle approach to software reliability that takes into account the risk to reliability due to requirements changes. A requirements change may induce ambiguity and uncertainty in the development process that cause errors in implementing the changes. Subsequently, these errors may propagate through later phases of development and maintenance. In view of the life cycle ramifications of the software reliability process, maintenance is included in this tutorial. Furthermore, because reliability and maintainability determine availability, the latter is also included.
Author: Girish Parikh
Author: Girish Parikh
Author: Girish Parikh
Author: Symposium On Foundations Of Computer Science
Author: Girish Parikh
Author: Keith Gallagher
Author: Phaneendra Nath Vellanky
Author: Alain April
Author: Norman F. Schneidewind
Author: David H. Longstreet
Author: Wilma M. Osborne