Interfaces, Hardware

An interface defines the communication boundary between two entities, such as a piece of software, a hardware device, or a user. It generally refers to an abstraction that an entity provides of itself to the outside. more...

Home
Brass
DJ Gear & Lighting
Electronic
Equipment
Guitar
Harmonica
Instruction Books, CDs,...
Keyboard, Piano
Other Instruments
Percussion
Pro Audio
Cables
Computer Recording
Interfaces, Hardware
Loops, Samples
Other
Software
Sound Cards
Microphones
Mixers
Monitors & Speakers
Multi-Track Recorders
Other Pro Audio
Parts, Accessories
Power Amplifiers
Rack Gear
Vintage, Pre-1980
Sheet Music, Song Books
String
Wholesale Lots
Woodwind

This separates the methods of external communication from internal operation, and allows it to be internally modified without affecting the way outside entities interact with it, as well as provide multiple abstractions of itself. It may also provide a means of translation between entities which do not speak the same language, such as between a human and a computer. Because interfaces are a form of indirection, some additional overhead is incurred versus direct communication.

The interface between a human and a computer is called a user interface. Interfaces between hardware components are physical interfaces. This article deals with software interfaces which exist between separate software components and provide a programmatic mechanism by which these components can communicate.

Interfaces in practice

A piece of software is provided access to computer resources (such as memory, CPU, storage, etc.) by its underlying computer system; the availability of these resources to other software can have major ramifications -- sometimes disastrous ones -- for its functionality and stability. A key principle of component-based design is to prohibit access to all resources by default, allowing access only through well-defined entry points, i.e. interfaces (See Information hiding).

The types of access that interfaces provide between software components can include: constants, data types, types of procedures, exception specifications and method signatures. In some instances, it may be useful to define variables as part of the interface. It often also specifies the functionality of those procedures and methods, either by comments or (in some experimental languages) by formal logical assertions.

The interface of a software module A is deliberately kept separate from the implementation of that module. The latter contains the actual code of the procedures and methods described in the interface, as well as other "private" variables, procedures, etc.. Any other software module B (which can be referred to as a client to A) that interacts with A is forced to do so only through the interface. One practical advantage of this arrangement is that replacing the implementation of A by another one that meets the same specifications of the interface should not cause B to fail — as long its use of A complies with the specifications of the interface (See also Liskov substitution principle).

Uses of interfaces

The concept of interface is the cornerstone of modular programming, a forerunner and a standard ingredient of object-oriented programming. In object-oriented programming, an object's interface consists of a set of methods that the object must respond to. Note that the object does not make its instance variables a part of its interface - these are typically accessed by means of accessor methods.

Read more at Wikipedia.org