DVM is a database management tool developed in-house at MOSAID. Although similar in function to RCS and CVS (used for textual source code management), DVM is specifically designed for Mentor design data.

Each user in the DVM environment has his own work directory containing a private view of the database and the user's immediate changes, but excludes co-worker's changes. Private Mentor location maps are used to permit common design references to point to one's private view. As such, engineers can work concurrently without interfering with one another. At the time changes are committed to the database, the submitter must provide a log message, which is e-mailed to everyone who may be affected by the change.

The project leader is able to set up access controls and data integrity policies to control the quality of information committed to the database. In the event that unwanted data is committed, it is possible to view the database as it looked at any time in the past, so lost work can be recovered.

DVM consists of both C and AMPLE code. The C code performs all low-level work associated with maintaining the database and managing access. The AMPLE code performs Mentor-specific operations such as verifying references, and providing interactive feedback with the Mentor Common User Interface. The C and AMPLE codes communicate using Unix domain sockets.

This paper describes the basic operation of DVM, the design decisions taken during its development, some advanced Mentor interfacing techniques, and future evolution of the tool.

Bio

David Jones received his Bachelor's degree in computer engineering from the University of Ottawa, and a Master's degree in electrical engineering from the University of Toronto. He currently works as an I.C. design engineer at MOSAID Technologies, semiconductor division, where he has three years' experience designing high-performance merged memory/logic chips.