Rules and Tools for Software Evolution Planning and Management
Annals of Software Engineering
Software Evolution and Software Evolution Processes
Annals of Software Engineering
Evolution in software and related areas
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
An approach to a theory of software evolution
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Understanding open source developers' evolution using TransFlow
CRIWG'09 Proceedings of the 15th international conference on Groupware: design, implementation, and use
Rapid Application Lifecycle Management: a new Approach with Tool Support
Proceedings of the 2010 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the 9th SoMeT_10
Hi-index | 0.01 |
M. Lehman's (Proc. IEEE, vol.68, no.9, p.1060-76, 1980) notion of programs can be used to describe a system in terms of the way it relates to the environment in which it operates. Unlike programs handled in the abstract, the real world contains uncertainties and concepts we do not understand completely. The more dependent a system is on the real world for its requirements, the more likely it is to change. Systems are described as S-systems (formally defined by and derivable from a Specification), P-systems (based on a Practical abstraction of the problem) and E-systems (Embedded in the real world and changing as the world does), characterized by the way the software interacts with its environment and by the degree to which the environment and underlying problem can change. Using these ideas, we can design our systems to be flexible, and plan our maintenance releases and new versions so that we understand and control our software, rather than merely react when problems arise