Flexible Component Retrieval

  • Satish Venkatesan
  • Karen C. Davis
Part of the Current Issues in Electronic Modeling book series (CIEM, volume 8)


Top-down library-based co-design methodologies have a primary goal of transforming high-level system specifications to implemented or ready-to-implement hardware/software systems. In particular, two phases of this co-design process are data intensive: very high-level synthesis and partitioning. Very high-level (or architecture) synthesis consists of matching component descriptions to specifications. Partitioning consists of identifying subcomponents and assigning those subcomponents to either hardware or software such that design constraints are satisfied. Both phases rely on design space exploration and require a large database of design components to produce satisfactory results. Flexible query processing is required to retrieve and manipulate components that satisfy design criteria and allow tradeoffs between different solutions to be evaluated. In this chapter, we describe the component modeling and retrieval capabilities of a VHDL-based database that supports co-design. Examples of queries issued by both a partitioning tool and an architecture synthesis tool are included.


Query Language Design Space Exploration Hardware Description Language Software Synthesis Electronic Design Automation 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    P. Alexander, P. Baraona, and J. Penix, “Application of Software Synthesis Techniques to Composite Systems,” in Computers in Engineering Symposium of ETCE, Houston, TX, Jan. 1995.Google Scholar
  2. [2]
    P. Baraona and P. Alexander, “VSPEC: A Language for Digital System Specification,” in Proceedings of the AI and Systems Engineering Workshop, pages 19–27, August 1994.Google Scholar
  3. [3]
    P. Baraona, J. Penix, and P. Alexander, “VSPEC: A Declarative Requirements Specification Language for VHDL,” Current Issues in Electronic Modeling, June 1995.Google Scholar
  4. [4]
    E. Bertino et al., “Object-Oriented Query Languages: The Notion and the Issues,” IEEE Transactions on Knowledge and Data Engineering, 4(3):223–237, June 1992.CrossRefGoogle Scholar
  5. [5]
    M. Brown, “VHDL Intermediate Form Standardization: Process, Issues, and Status,” in EURO-VHDL ′92: Proc. of the 2nd European Design Automation Conference, pages 758–762, Brussels, Belgium, 1992.CrossRefGoogle Scholar
  6. [6]
    J. Buck, S. Ha, E.A. Lee, and D.G. Messerschmitt, “Ptolemy: A Framework for Simulating and Prototyping Heterogeneous Systems,” International Journal of Computer Simulation, 4(2):155–182, April 1994.Google Scholar
  7. [7]
    CFI Design Representation Programming Interface: Electrical Connectivity V1.0.0, CAD Framework Initiative, Inc., Austin, TX 78759, 1993.Google Scholar
  8. [8]
    K.C. Davis and L.M.L. Delcambre, “A Denotational Approach to Object Oriented Query Language Definition,” in Workshops in Computing, Springer Verlag, 1992; reprinted from the Proceedings of the 1991 International Workshop on Specifications of Database Systems. Google Scholar
  9. [9]
    EXPRESS Language Reference Manual, Version N14, Part 11, ISO TC 184/S C4/WG5, April 1991.Google Scholar
  10. [10]
    C.A. Giumale, “An Information Model of VHDL,” Technical Report ECIP2/UM/015–1, University of Manchester, May 1993, ESPIRIT ECIP2 European CAD Integration Project, Project 2072.Google Scholar
  11. [11]
    W. Heijenga, U. Jasnoch, and E. Radeke, “DaDaMo — A Conceptual Data Model for Electronic Design Applications,” in EDAC92: European Conference on Design Automation, pages 394–398, Brussels, Belgium, March 1992.CrossRefGoogle Scholar
  12. [12]
    A. Heuer and M.H. Scholl, “Principles of Object-Oriented Query Languages,” in BTW91 — Datenbanksysteme in Buro, Technik und Wissenschaft, pages 178–197, Kaiserslautern, March 1991, German Computer Society, Springer.CrossRefGoogle Scholar
  13. [13]
    IEEE Standard VHDL Language Reference Manual, New York, NY, 1993.Google Scholar
  14. [14]
    A. Kalavade and E.A. Lee, “Hardware-Software Cosynthesis for Digital Systems,” IEEE Design and Test of Computers, 10(3):16–28, September 1993.CrossRefGoogle Scholar
  15. [15]
    W. Kim, J. Banerjee, H.-T. Chou, and J.F. Garza, “Object-oriented Database Support for CAD,” Computer Aided Design, 22(8):469–479, October 1990.CrossRefGoogle Scholar
  16. [16]
    R. Miller and H. Carter, “Hardware/Software Partitioning in COMET,” Proceedings of the COMET Project Review Meeting, 1995, presentation slides.Google Scholar
  17. [17]
    R. Miller, H. Carter, K. Davis, and S. Venkatesan, “Hardware/Software CoSynthesis: Multiple Constraint Satisfaction and Component Retrieval,” in Proceedings of the IEEE 2nd International Conference on Complex Computer Systems, Montreal, Canada, October 1996.Google Scholar
  18. [18]
    T.K. Nayak, A.K. Majumdar, A. Basu, and S. Sarkar, “VLODS: A VLSI Object Oriented Database System,” Information Systems, 16(1):73–96, 1991.CrossRefGoogle Scholar
  19. [19]
    J. Penix, P. Baraona, and P. Alexander, “Classification and Retrieval of Reusable Components Using Semantic Features,” in Proc. of the 10th Knowledge-Based Software Engineering Conference, Boston, November 1995.Google Scholar
  20. [20]
    J. Penix and P. Alexander, “Efficient Specification-Based Component Retrieval,” submitted for publication, 1996.Google Scholar
  21. [21]
    J. Rumbaugh et al., Object-Oriented Modeling and Design, Prentice Hall, Englewood Cliffs, NJ 07632, 1991.Google Scholar
  22. [22]
    E.A. Rundensteiner, “Design Tool Integration Using Object-Oriented Database Views,” in Proceedings of the IEEE/ACM International Conference on CAD-93, pages 104–107, Nov 1993.Google Scholar
  23. [23]
    G.M. Shaw and S.B. Zdonik, “A Query Algebra for Object-Oriented Databases,” in Proceedings of the 6th International Conference on Data Engineering, pages 154–162, Los Angeles, CA, Feb 1990.Google Scholar
  24. [24]
    E. Siepmann and G. Zimmermann, “Object-Oriented Datamodel for the VLSI Design System PLAYOUT,” in Proc. of the 26th ACM/IEEE Design Automation Conference, pages 814–817, Las Vegas, NV, 1989.Google Scholar
  25. [25]
    D.D. Straube and M.T. Ozsu, “Queries and Query Processing in Object Oriented Database Systems,” ACM Trans. on Information Systems, 8(4): 387, 1990.CrossRefGoogle Scholar
  26. [26]
    D.E. Thomas, J.K. Adams, and H. Schmit, “A Model and Methodology for Hardware-Software Codesign,” IEEE Design and Test of Computers, 10(3): 6–15, September 1993.CrossRefGoogle Scholar
  27. [27]
    R. Vemuri, H. Carter, and P. Alexander, “Board and MCM Level Synthesis for Embedded Systems in the COMET Cosynthesis Environment,” in Proceedings of the First Annual RASSP Conference, pages 124–133, Arlington, VA, August 1994.Google Scholar
  28. [28]
    S. Venkatesan, Database Modeling for Electronic Design Automation Environments, PhD thesis, Electrical and Computer Engineering and Computer Science, University of Cincinnati, Cincinnati, OH 45221–0030, January 1996.Google Scholar
  29. [29]
    S. Venkatesan and K.C. Davis, “Odyssey: An Electronic Design Automation Database,” in Proc. of the 2nd International Conference on Applications of Databases, pages 147–157, Santa Clara, CA, December 1995.Google Scholar
  30. [30]
    S. Venkatesan and K.C. Davis, “A Meta-model and Semantic Mapping Methodology for Hardware Design Data Management,” Journal of Integrated Computer-Aided Engineering, special issue on Integrated Product and Process Data Management, 3(1), 1996.Google Scholar
  31. [31]
    F.R. Wagner, “Design Management Requirements for Hardware Description Languages,” in Proc. Of EURO VHDL 95, 1995.Google Scholar

Copyright information

© Springer Science+Business Media Dordrecht 1997

Authors and Affiliations

  • Satish Venkatesan
    • 1
  • Karen C. Davis
    • 2
  1. 1.Intel CorporationSanta ClaraUSA
  2. 2.Database Systems LaboratoryUniversity of CincinnatiCincinnatiUSA

Personalised recommendations