F
Freddy Y. C. Mang
Researcher at University of California, Berkeley
Publications - 12
Citations - 997
Freddy Y. C. Mang is an academic researcher from University of California, Berkeley. The author has contributed to research in topics: Component-based software engineering & Model checking. The author has an hindex of 11, co-authored 12 publications receiving 972 citations. Previous affiliations of Freddy Y. C. Mang include Synopsys.
Papers
More filters
Book ChapterDOI
MOCHA: Modularity in Model Checking
Rajeev Alur,Thomas A. Henzinger,Freddy Y. C. Mang,Shaz Qadeer,Sriram K. Rajamani,Serdar Tasiran +5 more
TL;DR: This paper presents a parallel version of the Celada–Seiden cellular automaton that automates the very labor-intensive and therefore time-heavy and therefore expensive and expensive and therefore computationally burdensome process of integrating these two systems.
Book ChapterDOI
Interface Compatibility Checking for Software Modules
TL;DR: A formal methodology and tool for uncovering errors in the interaction of software modules and a tool that has uncovered incompatibilities in TinyOS, a small operating system for sensor nodes in adhoc networks are presented.
Proceedings ArticleDOI
JMOCHA: a model checking tool that exploits design structure
Rajeev Alur,L. de Alfaro,Radu Grosu,Thomas A. Henzinger,M. Kang,Christoph M. Kirsch,Rupak Majumdar,Freddy Y. C. Mang,Bow-Yaw Wang +8 more
TL;DR: The Java MOdel-CHecking Algorithm (jMocha) as mentioned in this paper is a model checker for embedded software that supports the hierarchical modeling framework of reactive modules.
Book ChapterDOI
Synchronous and Bidirectional Component Interfaces
TL;DR: This work presents interface models that describe both the input assumptions of a component, and its output behavior, and presents algorithms for compatibility and refinement checking, and describes efficient symbolic implementations.
Journal Article
Synchronous and bidirectional component interfaces
TL;DR: In this article, the authors present interface models that describe both the input assumptions of a component and its output behavior, and provide a compatibility check for component-based design, enabling us to check that the output behavior of the component satisfies the design specification only when the inputs assumptions of the specification are satisfied.