منابع مشابه
Unanticipated Software Evolution
1 Dept. of Computer Science III, University of Bonn, Germany, [email protected] http://www.cs.uni-bonn.de/∼gk/ 2 Software Engineering Lab, University of Twente, Enschede, The Netherlands, [email protected] http://wwwhome.cs.utwente.nl/∼noppen/ 3 Programming Technology Lab, Vrije Universiteit Brussel, Belgium, [email protected] http://prog.vub.ac.be/∼tommens/ 4 University of Limerick, Castle...
متن کاملPitfalls in Unanticipated Dynamic Software Evolution
The authors of this paper have all developed a framework that allows runtime adaptation of software systems. Based on our experiences, we wish to summarize common pitfalls concerning dynamic software evolution. Systems for dynamic adaptation typically follow a certain process which is used as a starting point in this paper. The problems that occur in the different steps of this evolution proces...
متن کاملManaging Unanticipated Evolution of Software Architectures
Few existing approaches towards architectural evolution deal with unanticipated evolution. This is an important restriction, since a lot of architectural changes are very di cult to anticipate. The reuse contract formalism has been designed speci cally to deal with unanticipated software evolution, and has already proven its practical use in di erent domains. We claim that the reuse contract ap...
متن کاملWS 9. The First International Workshop on Unanticipated Software Evolution
This workshop was dedicated to research towards better support for unantic-ipated software evolution (USE) in development tools, programming languages, component models and related runtime infrastructures. The report gives an overview of the submitted papers and summarizes the essence of discussions during plenary sessions and in working groups.
متن کاملDiscovering Unanticipated Software Output Modes
Software risk management is particularly important when the target environment of the software is a safetycritical system. Adequate development standards and methods for building software functionally that is “close to correct” exist. But unfortunately, we often fail to imagine particular classes of system hazards that the software’s behavior could induce, because quite simply, we cannot forese...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: Journal of Software Maintenance and Evolution: Research and Practice
سال: 2005
ISSN: 1532-060X,1532-0618
DOI: 10.1002/smr.318