Object Oriented Software Engineering   View all facts   Glossary   Help

subject > criterion > principle > design principle > anticipating obsolescence

anticipating obsolescence comparison table

Subject	mean	is an instance of	is a kind of	assume that	accomplish by
design principle			principle
anticipating obsolescence	planning for changes in the technology or environment so the software will continue to run or can be easily changed	design principle		changes will inevitably occur in the technology a software system uses and the environment in which it runs	Avoiding the use of early releases of technology Avoiding the use of software libraries that are specific to particular environments Avoiding the use of undocumented features or little-used features of software libraries Avoiding the use of reusable software or special hardware from smaller companies, or from those that are less likely to provide long-term support Using standard languages and technologies that are supported by multiple vendors

Next design principle: decreasing coupling    Up: design principle    Previous design principle: reusing existing designs and code where possible