Abstract
The nature of interfaces is discussed. It is recommended that modern software approaches to interfaces (such as abstract data types) be extended to interfaces of all kinds. These interfaces can and should be developed at the level of abstraction appropriate to the interacting elements, rather than at the level of their lowest common denominator, which is frequently the case. It is proposed that for an interface to exist at any level of abstraction, there must be an operational framework that implements that level of abstraction and within which the interfacing elements interact. Four tasks required for the development of interfaces are described. The traditional classification of interfaces as hardware/software, software/software, and hardware/hardware is found wanting and a new partitioning is suggested—structural or interpretive interfaces, symbolic interfaces, and physical interfaces. Standards and scientific and engineering theories are shown to define levels of abstraction for general interfaces in much the same way that programming languages do for software interfaces. Implications for software engineering and concurrent engineering are explored.
Similar content being viewed by others
References
G.T. Almes, A. P. Black, E. D. Lazowska, and J. D. Noe, “The Eden System: A technical review,”IEEE Trans. Software Eng., Vol. SE-11, No. 1, pp. 43–59, January 1985.
N. Cercone and G. McCalla.The Knowledge Frontier: Essays in the Representation of Knowledge, Springer-Verlag: New York, 1987.
U.S. Department of Defense, DI-E-30131: Interface Control Document. Department of Defense, 1966.
U.S. Department of Defense, DI-E-30141: Interface Specification. Department of Defense, 1973.
U.S. Department of Defense, DI-E-5550: System/System Segment Interface Control Document. Department of Defense, 1981.
U.S. Department of Defense, DI-MCCR-800026A: Interface Requirements Specification. Department of Defense, 1988.
U.S. Department of Defense, DI-MCCR-800027A: Interface Design Document. Department of Defense, 1988.
J.V. Guttag, “Notes on type abstraction,”IEEE Trans. Software Eng., Vol. SE-6, No. 1, pp. 13–23, January 1980.
J.R. Hobbs and R.C. Moore,Formal Theories of the Commonsense World, Ablex Publishing Corp.: Norwood, NJ, 1985.
J. McCarthy, “Networks considered harmful for electronic mail,”CACM, vol. 32, pp. 1389–1390, December 1989.
Merriam- Webster, Inc.,Webster's Ninth New Collegiate Dictionary, Merriam-Webster, Inc.: Springfield, MA, 1987.
G.E. Peterson,Tutorial: Object Oriented Computing, IEEE Computer Society Press: Los Alamitos, CA, 1987.
L. Robinson and K.N. Levitt, “Proof techniques for hierarchically structured programs,”CACM, vol. 20 (3) pp. 271–283, April 1977.
R.H. Thayer and M. Dorfman,System and Software Requirements Engineering, IEEE Computer Society Press: Los Alamitos, CA, 1990.
D.S. Weld and J. de Kleer,Qualitative Reasoning about Physical Systems, Morgan Kaufmann: San Mateo, CA, 1990.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Abbott, R.J. On interfaces. Journal of Systems Integration 1, 143–162 (1991). https://doi.org/10.1007/BF02426921
Received:
Revised:
Issue Date:
DOI: https://doi.org/10.1007/BF02426921