Abstract
As the data model begins to develop, situations will sometimes arise where we find that a class may not describe our possible objects as neatly as we might like. We might find that we have some objects for which some of the attributes do not really apply. For example, if we have a class to record information about all the people associated with a company, we might find that some have hourly pay rates while others have annual salaries. In many respects, much of the information about each of the employees is similar, but there are differences. We may also come across the case where we have started with two separate classes, for example Lecturers and Students, and then begin to realize that there is a great deal of information in common or that they are involved in the same relationships (who has parking permits, say). How do we handle these “same only different” cases in a pragmatic way?
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2012 Clare Churcher
About this chapter
Cite this chapter
Churcher, C. (2012). Generalization and Specialization. In: Beginning Database Design. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4210-9_6
Download citation
DOI: https://doi.org/10.1007/978-1-4302-4210-9_6
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-4209-3
Online ISBN: 978-1-4302-4210-9
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books