Easiest way to have multiple persons work same database ?

What's the easiest way to obtain something like a check-in / check-out for a
given database ?

I've seen this for a copied database from a company - a window pops up, in
which you can check-in the necessary files.

Since I started this database on my local computer, there must be a way to
do this with cadence utilities ...

Does anyone know how ?

We need this to prevent people from editing the same verilogA/AMS models at
the same time ...


Regards,

Stefan

 

What you're looking for is version control. Cadence comes with
VersionSync, which will let you do that for small groups. If you're
looking for something professional, consider Synchronicity (or
Perforce/ICManage).

 

I should point out that VersionSync is End Of Lifed - so whilst it is still
included with IC5141, it has not been supported for (roughly) two years, and is
not in any subsequent release.

There are three commercial DM solutions out there - DesignSyncDFII (from Enovia
MatrixOne), IC Manage (from IC Manage) and SOS (from ClioSoft) - which work with
DFII.

Regards,

Andrew.

 

I should also add that I've been using subversion, and it works rather
well. There's no integration with Cadence (you have to do everything
from the command-line). This forces your users to understand how
subversion works--but that understanding has its advantages.

 

actually there's a 4th commercially available DDM tool called VersIC
by MethodICs. This supports multiple backend repositories including
Subversion and Perforce.

www.methodics-eda.com for more details.

 

By paying Cadence VCAD to implement it for you.

Cadence understood that having multiple persons working on the same
project is something that the cadence toolchain does not support very
well. Their database has been too proprietary. That's why they
introduced the OpenAccess database, to make it possible that all
vendors, no matter who, should be able to exchange data in an open and
well documented way. With OA it should be possible to even write your
own little applications to interact directly with the database. This
sounds like the Brave New World, and it also is. Just like the book,
OA is a parody on the future. Did you know that you could earn more
money on keeping a piece of software obscure and sell expensive
support, than to introduce new and better features? A user will pay
only once for a proper software (unless the sw use FlexLM to increase
the CBR of your company), for support you pay every time.

 

Also, for those in the original discussion, I wanted to mention that
this is the same project we were discussing a year ago on
comp.cad.cadence (although it's considerably grown in scope since then).

http://tinyurl.com/33npj3