Abstract
During the process of developing software the architecture and its underlying objects are victims of small things like technically ‘impure’ objects1 or (implementation and other) concessions that undermine the maintainability and extensibility by introducing a series of context-dependent decisions.
By “technically ‘impure’ objects” we mean objects that when exposed to all of the paradigm’s implications show some kind of problem. But these problems are usually not considered an issue due to other practical issues.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
References
“Metaphysics”-Arisoteles
“Design Patterns: Elements of Reusable Object-Oriented Software”-Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides. Addison-Wesley, 1995.
“Designing Object-Oriented Software”-Rebecca Wirffs-Brock, Brian Wilkerson, Lauren Wiener. Prentice Hall, 1990.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1998 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Alvarez, X., Dombiak, G., Zak, F., Prieto, M. (1998). Ensuring Object Survival in a Desert. In: Demeyer, S., Bosch, J. (eds) Object-Oriented Technology: ECOOP’98 Workshop Reader. ECOOP 1998. Lecture Notes in Computer Science, vol 1543. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-49255-0_15
Download citation
DOI: https://doi.org/10.1007/3-540-49255-0_15
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-65460-5
Online ISBN: 978-3-540-49255-9
eBook Packages: Springer Book Archive