{"date_created":"2018-12-11T12:08:56Z","publist_id":"274","publisher":"ACM","year":"2005","status":"public","quality_controlled":0,"title":"Permissive interfaces","doi":"10.1145/1081706.1081713","page":"31 - 40","author":[{"orcid":"0000−0002−2985−7724","full_name":"Thomas Henzinger","id":"40876CD8-F248-11E8-B48F-1D18A9856A87","last_name":"Henzinger","first_name":"Thomas A"},{"full_name":"Jhala, Ranjit","last_name":"Jhala","first_name":"Ranjit"},{"full_name":"Majumdar, Ritankar S","first_name":"Ritankar","last_name":"Majumdar"}],"day":"01","type":"conference","date_updated":"2021-01-12T07:57:06Z","month":"09","extern":1,"conference":{"name":"FSE: Foundations of Software Engineering"},"publication_status":"published","date_published":"2005-09-01T00:00:00Z","citation":{"short":"T.A. Henzinger, R. Jhala, R. Majumdar, in:, ACM, 2005, pp. 31–40.","chicago":"Henzinger, Thomas A, Ranjit Jhala, and Ritankar Majumdar. “Permissive Interfaces,” 31–40. ACM, 2005. <a href=\"https://doi.org/10.1145/1081706.1081713\">https://doi.org/10.1145/1081706.1081713</a>.","ista":"Henzinger TA, Jhala R, Majumdar R. 2005. Permissive interfaces. FSE: Foundations of Software Engineering, 31–40.","apa":"Henzinger, T. A., Jhala, R., &#38; Majumdar, R. (2005). Permissive interfaces (pp. 31–40). Presented at the FSE: Foundations of Software Engineering, ACM. <a href=\"https://doi.org/10.1145/1081706.1081713\">https://doi.org/10.1145/1081706.1081713</a>","ama":"Henzinger TA, Jhala R, Majumdar R. Permissive interfaces. In: ACM; 2005:31-40. doi:<a href=\"https://doi.org/10.1145/1081706.1081713\">10.1145/1081706.1081713</a>","ieee":"T. A. Henzinger, R. Jhala, and R. Majumdar, “Permissive interfaces,” presented at the FSE: Foundations of Software Engineering, 2005, pp. 31–40.","mla":"Henzinger, Thomas A., et al. <i>Permissive Interfaces</i>. ACM, 2005, pp. 31–40, doi:<a href=\"https://doi.org/10.1145/1081706.1081713\">10.1145/1081706.1081713</a>."},"abstract":[{"lang":"eng","text":"A modular program analysis considers components independently and provides a succinct summary for each component, which is used when checking the rest of the system. Consider a system consisting of a library and a client. A temporal summary, or interface, of the library specifies legal sequences of library calls. The interface is safe if no call sequence violates the library's internal invariants; the interface is permissive if it contains every such sequence. Modular program analysis requires full interfaces, which are both safe and permissive: the client does not cause errors in the library if and only if it makes only sequences of library calls that are allowed by the full interface of the library.Previous interface-based methods have focused on safe interfaces, which may be too restrictive and thus reject good clients. We present an algorithm for automatically synthesizing software interfaces that are both safe and permissive. The algorithm generates interfaces as graphs whose vertices are labeled with predicates over the library's internal state, and whose edges are labeled with library calls. The interface state is refined incrementally until the full interface is constructed. In other words, the algorithm automatically synthesizes a typestate system for the library, against which any client can be checked for compatibility. We present an implementation of the algorithm which is based on the BLAST model checker, and we evaluate some case studies."}],"_id":"4456"}