{"title":"Interface-based design","quality_controlled":0,"status":"public","alternative_title":["NATO Science Series: Mathematics, Physics, and Chemistry"],"intvolume":" 195","publist_id":"85","volume":195,"date_created":"2018-12-11T12:09:49Z","publisher":"Springer","year":"2005","citation":{"ama":"De Alfaro L, Henzinger TA. Interface-based design. In: Vol 195. Springer; 2005:83-104. doi:10.1007/1-4020-3532-2_3","ista":"De Alfaro L, Henzinger TA. 2005. Interface-based design. Engineering Theories of Software Intensive Systems, NATO Science Series: Mathematics, Physics, and Chemistry, vol. 195, 83–104.","chicago":"De Alfaro, Luca, and Thomas A Henzinger. “Interface-Based Design,” 195:83–104. Springer, 2005. https://doi.org/10.1007/1-4020-3532-2_3.","apa":"De Alfaro, L., & Henzinger, T. A. (2005). Interface-based design (Vol. 195, pp. 83–104). Presented at the Engineering Theories of Software Intensive Systems, Springer. https://doi.org/10.1007/1-4020-3532-2_3","short":"L. De Alfaro, T.A. Henzinger, in:, Springer, 2005, pp. 83–104.","mla":"De Alfaro, Luca, and Thomas A. Henzinger. Interface-Based Design. Vol. 195, Springer, 2005, pp. 83–104, doi:10.1007/1-4020-3532-2_3.","ieee":"L. De Alfaro and T. A. Henzinger, “Interface-based design,” presented at the Engineering Theories of Software Intensive Systems, 2005, vol. 195, pp. 83–104."},"date_published":"2005-07-15T00:00:00Z","publication_status":"published","conference":{"name":"Engineering Theories of Software Intensive Systems"},"extern":1,"_id":"4624","abstract":[{"lang":"eng","text":"Surveying results from [5] and [6], we motivate and introduce the theory behind formalizing rich interfaces for software and hardware components. Rich interfaces specify the protocol aspects of component interaction. Their formalization, called interface automata, permits a compiler to check the compatibility of component interaction protocols. Interface automata support incremental design and independent implementability. Incremental design means that the compatibility checking of interfaces can proceed for partial system descriptions, without knowing the interfaces of all components. Independent implementability means that compatible interfaces can be refined separately, while still maintaining compatibility."}],"type":"conference","page":"83 - 104","doi":"10.1007/1-4020-3532-2_3","author":[{"full_name":"de Alfaro, Luca","last_name":"De Alfaro","first_name":"Luca"},{"orcid":"0000−0002−2985−7724","full_name":"Thomas Henzinger","id":"40876CD8-F248-11E8-B48F-1D18A9856A87","last_name":"Henzinger","first_name":"Thomas A"}],"day":"15","month":"07","date_updated":"2021-01-12T08:00:36Z"}