14
14 Michael S. McCorquodale University of Michigan Bottom-Up Design Methodology The Problems No opportunity for architectural studies Time-consuming design iteration Cross-domain verification at top level only Time-consuming system level simulation, if it is even possible MotivationMicrosystemsBottom-UpMicrocontrollerFrameworkTop-DownGaps & Solns.Conclusions

23
23 Michael S. McCorquodale University of Michigan Conclusions Microsystem design methodologies are in their infancy Current methodologies have originated from the disparate nature of the technology The proposed top-down methodology leverages advances in mixed-signal design automation The proposed methodology is efficient and offers superior verification as compared to current methodologies Gaps in tool suites exist and must be addressed for future microsystems developments Tool suites are disparate and can be built into a single framework MotivationMicrosystemsBottom-UpMicrocontrollerFrameworkTop-DownGaps & Solns.Conclusions