TY - GEN
T1 - Archface
T2 - 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010
AU - Ubayashi, Naoyasu
AU - Nomura, Jun
AU - Tamai, Tetsuo
PY - 2010/7/23
Y1 - 2010/7/23
N2 - This paper proposes Archface, an interface mechanism for bridging the gap between architectural design and its implementation. Archface, which encapsulates design essence based on the component-and-connector architecture, is not only an ADL (Architecture Description Language) but also a programming-level interface. Archface is effective for software evolution because traceability between design and its implementation can be realized by enforcing architectural constraints on program implementation, and this traceability is bidirectional. In Archface, a component exposes program points such as method call/execution and a connector defines how to coordinate exposed program points. A collaborative architecture consisting of components can be encapsulated into a group of interfaces and separated from implementation, because dynamic program points representing control flow can be specified in the interfaces. We can characterize the notion of Archface with the phrase "predicate coordination," in which program points are exposed by a predicate and coordinated by a trait-based connector.
AB - This paper proposes Archface, an interface mechanism for bridging the gap between architectural design and its implementation. Archface, which encapsulates design essence based on the component-and-connector architecture, is not only an ADL (Architecture Description Language) but also a programming-level interface. Archface is effective for software evolution because traceability between design and its implementation can be realized by enforcing architectural constraints on program implementation, and this traceability is bidirectional. In Archface, a component exposes program points such as method call/execution and a connector defines how to coordinate exposed program points. A collaborative architecture consisting of components can be encapsulated into a group of interfaces and separated from implementation, because dynamic program points representing control flow can be specified in the interfaces. We can characterize the notion of Archface with the phrase "predicate coordination," in which program points are exposed by a predicate and coordinated by a trait-based connector.
UR - http://www.scopus.com/inward/record.url?scp=77954714022&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=77954714022&partnerID=8YFLogxK
U2 - 10.1145/1806799.1806815
DO - 10.1145/1806799.1806815
M3 - Conference contribution
AN - SCOPUS:77954714022
SN - 9781605587196
T3 - Proceedings - International Conference on Software Engineering
SP - 75
EP - 84
BT - ICSE 2010 - Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering
Y2 - 1 May 2010 through 8 May 2010
ER -