abstract class

abstract class

(programming)
In object-oriented programming, a class designed only as a parent from which sub-classes may be derived, but which is not itself suitable for instantiation. Often used to "abstract out" incomplete sets of features which may then be shared by a group of sibling sub-classes which add different variations of the missing pieces.

abstract class

Also called an "abstract superclass," in object technology, it is a class created as a master structure. No objects of an abstract class are created, rather subclasses of the abstract class are defined with their own variations, and the subclasses are used to create the actual objects.
References in periodicals archive ?
Now all save option classes of fixed page formats (HtmlFixedSaveOptions, ImageSaveOptions, PdfSaveOptions, PsSaveOptions, SvgSaveOptions, SwfSaveOptions, XamlFixedSaveOptions and XpsSaveOptions) are inherited from the new public abstract class FixedPageSaveOptions.
A mestizo might "disappear" because different labels could attach to him or her and because mestizos were an abstract class, not a social group.
To implement a content provider in Android, we need to create a class that extends from abstract class Content Provider and implement its 6 required methods - query(), insert(), update(), delete() getType(), onCreate().
It must be mentioned from the beginning that the input/output operations with XML files represented using this abstract class are making use of the DOM technology [van der Vlist 02].
Therefore, since the representation of the raw image of some type is an obligatory attribute of StillImage an abstract class RawImageRep is defined and associated with the StillImage class through a mandatory association.
1, task is represented as an abstract class 'Task', which derives two abstract subclasses: ElementaryTask and CompisiteTask.
a formal, abstract class, distinct from the concrete viral objects that replicate and cause disease and that are written in Roman characters.
An abstract class is one that exists for other classes to inherit from.
Speaking in terms of object-oriented analysis and design, the OBOA model defines an abstract class K_element for representing an abstract knowledge element, no matter how complex the element is or what its purpose is.
Surely, this is going to affront many system modelers and most implementers: why waste the name Rectangle for an abstract class which cannot have instances, and why introduce an additional class oddly named OtherRectangle which will create most of the instances of Rectangle?
The problem is that C++ provides only one type abstraction mechanism, the class, and that implementations must explicitly state their adherence to an abstract type by inheriting from the abstract class defining the type.
Simply being identified as victims of poverty in an abstract class analysis that sidesteps these complexities doesn't do it.