Software that translates a high-level request into the low-level commands required to perform the operation. The most common abstraction layer is the programming interface (API) between an application and the operating system. High-level calls are made to the operating system, which executes the necessary instructions to perform the task.
The domain names and URLs on the Internet are another common abstraction layer, enabling an alphabetic name such as computerlanguage.com to be converted into the numeric IP address of the Web server (see Internet domain name).
Multiple Layers of Abstraction
Today's applications are often programmed in multiple layers of abstraction. For example, a program can be written by selecting menu options and dragging icons around the screen. These movements may be translated into a high-level language that is translated into a low-level language, which is translated into machine language. The farther away from the machine language of the computer that an operation is programmed, the more instructions are executed to perform the task.
Combine this with the interaction of the operating system, which itself may be executing 10 times as many instructions as necessary, and you understand why even on a fast computer, a user may be able to press the keyboard keys faster than the program can accept the input. Considering modern personal computers execute upwards of two billion instructions per second, compared to the first PCs that executed one million, the extra machine cycles are absorbed layer to layer, each one telling the next one what to do. See level of abstraction.
Download Computer Desktop Encyclopedia to your PC, iPhone or Android.
An abstraction layer (or abstraction level, or a layer of abstraction) is a way of hiding the implementation details of a particular set of functionality. Software models that use layers of abstraction include the OSI 7-layer model for computer network protocols, the OpenGL graphics drawing library, and the byte stream input/output (I/O) model originated by Unix and adopted by MSDOS, Linux, and most other modern operating systems.
In the Unix operating system, most types of input and output operations are considered to be streams of bytes being read from a device or being written to a device. This stream of bytes model is used for file I/O, socket I/O, and terminal I/O in order to provide device independence. In order to read and write to a device at the application level, the program calls a function to open the device which may be a real device such as a terminal or a virtual device such as a network port or a file in a file system. The device's physical characteristics are mediated by the operating system which in turn presents an abstract interface that allows the programmer to read and write bytes from/to the device. The operating system then performs the actual transformation needed to read and write the stream of bytes to the device.
Most graphics libraries such as OpGL provide an abstract graphical device model as an interface. The library is responsible for translating the commands provided by the programmer into the specific device commands needed to draw the graphical elements and objects. The specific device commands for a plotter are different from the device commands for a CRT monitor but the graphics library hides the implementation and device dependent details by providing an abstract interface which provides a set of primitives that are generally useful for drawing graphical objects.
In computer science, an abstraction level is a generalization of a model or algorithm, away from any specific implementation. These generalizations arise from broad similarities that are best encapsulated by models that express similarities present in various specific implementations. The simplification provided by a good abstraction layer allows for easy reuse by distilling a useful concept or metaphor so that situations where it may be accurately applied can be quickly recognized.
A good abstraction will generalize that which can be made abstract; while allowing specificity where the abstraction breaks down and its successful application requires customization to each unique requirement or problem.
Frequently abstraction layers can be composed into a hierarchy of abstraction levels. The ISO-OSI networking model comprises seven abstraction layers. Each layer of the OSI ISO networking model encapsulates and addresses a different part of the needs of much digital communications, thereby reducing the complexity of the associated engineering solutions.
A famous aphorism of David Wheeler goes: All problems in computer science can be solved by another level of indirection;[2] this is often deliberately mis-quoted with "abstraction" substituted for "indirection". Kevlin Henney's corollary to this is, "...except for the problem of too many layers of indirection."
In computer architecture, a computer system is usually represented as consisting of five abstraction levels: hardware (see hardware abstraction), firmware, assembler, operating system and processes.[1]
This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)