- Full Description
Software has become omnipresent and vital in our information-based society, so all software producers should assume responsibility for its reliability. While 'reliable' originally assumed implementations that were effective and mainly error-free, additional issues like adaptability and maintainability have gained equal importance recently. For example, the 2004 ACM/IEEE Software Engineering Curriculum Guidelines list software evolution as one of ten key areas of software engineering education. Mens and Demeyer, both international authorities in the field of software evolution, together with the invited contributors, focus on novel trends in software evolution research and its relations with other emerging disciplines such as model-driven software engineering, service-oriented software development, and aspect-oriented software development. They do not restrict themselves to the evolution of source code but also address the evolution of other, equally important software artifacts such as databases and database schemas, design models, software architectures, and process management. The contributing authors provide broad overviews of related work, and they also contribute to a comprehensive glossary, a list of acronyms, and a list of books, journals, websites, standards and conferences that together represent the community’s body of knowledge. Combining all these features, this book is the indispensable source for researchers and professionals looking for an introduction and comprehensive overview of the state of the art. In addition, it is an ideal basis for an advanced course on software evolution.
- Table of Contents
Table of Contents
- From the contents Introduction and Roadmap: History and Challenges of Software Evolution (Tom Mens).
- Part I: Understanding and Analysing Software Evolution.
- Part II: Reengineering of Legacy Systems.
- Part III: Novel Trends in Software Evolution.
- Glossary of Terms.
- List of Acronyms.
If you think that you've found an error in this book, please let us know by emailing to email@example.com . You will find any confirmed erratum below, so you can check if your concern has already been addressed. No errata are currently published