Interface, a dispersed architecture

C.A. Vissers

Research output: Contribution to journalArticleAcademic

5 Citations (Scopus)
32 Downloads (Pure)

Abstract

Past and current specification techniques use timing diagrams and written text to describe the phenomenology of an interface. This paper treats an interface as the architecture of a number of processes, which are dispersed over the related system parts and the message path. This approach yields a precise definition of an interface. With this definition as starting point, the inherent structure of an interface is developed. A horizontal and vertical partitioning strategy, based on one functional entity per partition and described by a state description, is used to specify the structure. This method allows unambiguous specification, interpretation, and implementation, and allows a much easier judgement of the quality of an interface. The method has been applied to a number of widely used interfaces.
Original languageUndefined
Pages (from-to)98-104
JournalSIGARCH Computer Architecture News
Volume4
Issue number4
DOIs
Publication statusPublished - 1976

Keywords

  • IR-101679

Cite this

Vissers, C.A. / Interface, a dispersed architecture. In: SIGARCH Computer Architecture News. 1976 ; Vol. 4, No. 4. pp. 98-104.
@article{4e7b9975e2444e1fb15176ee77cf5f66,
title = "Interface, a dispersed architecture",
abstract = "Past and current specification techniques use timing diagrams and written text to describe the phenomenology of an interface. This paper treats an interface as the architecture of a number of processes, which are dispersed over the related system parts and the message path. This approach yields a precise definition of an interface. With this definition as starting point, the inherent structure of an interface is developed. A horizontal and vertical partitioning strategy, based on one functional entity per partition and described by a state description, is used to specify the structure. This method allows unambiguous specification, interpretation, and implementation, and allows a much easier judgement of the quality of an interface. The method has been applied to a number of widely used interfaces.",
keywords = "IR-101679",
author = "C.A. Vissers",
note = "Proceeding ISCA '76 Proceedings of the 3rd annual symposium on Computer architecture",
year = "1976",
doi = "10.1145/633617.803557",
language = "Undefined",
volume = "4",
pages = "98--104",
journal = "SIGARCH Computer Architecture News",
issn = "0163-5964",
publisher = "Association for Computing Machinery (ACM)",
number = "4",

}

Interface, a dispersed architecture. / Vissers, C.A.

In: SIGARCH Computer Architecture News, Vol. 4, No. 4, 1976, p. 98-104.

Research output: Contribution to journalArticleAcademic

TY - JOUR

T1 - Interface, a dispersed architecture

AU - Vissers, C.A.

N1 - Proceeding ISCA '76 Proceedings of the 3rd annual symposium on Computer architecture

PY - 1976

Y1 - 1976

N2 - Past and current specification techniques use timing diagrams and written text to describe the phenomenology of an interface. This paper treats an interface as the architecture of a number of processes, which are dispersed over the related system parts and the message path. This approach yields a precise definition of an interface. With this definition as starting point, the inherent structure of an interface is developed. A horizontal and vertical partitioning strategy, based on one functional entity per partition and described by a state description, is used to specify the structure. This method allows unambiguous specification, interpretation, and implementation, and allows a much easier judgement of the quality of an interface. The method has been applied to a number of widely used interfaces.

AB - Past and current specification techniques use timing diagrams and written text to describe the phenomenology of an interface. This paper treats an interface as the architecture of a number of processes, which are dispersed over the related system parts and the message path. This approach yields a precise definition of an interface. With this definition as starting point, the inherent structure of an interface is developed. A horizontal and vertical partitioning strategy, based on one functional entity per partition and described by a state description, is used to specify the structure. This method allows unambiguous specification, interpretation, and implementation, and allows a much easier judgement of the quality of an interface. The method has been applied to a number of widely used interfaces.

KW - IR-101679

U2 - 10.1145/633617.803557

DO - 10.1145/633617.803557

M3 - Article

VL - 4

SP - 98

EP - 104

JO - SIGARCH Computer Architecture News

JF - SIGARCH Computer Architecture News

SN - 0163-5964

IS - 4

ER -