Here're my 2 cents.Originally posted in cdnusers.org by email@example.com
There's probably no right or wrong answer here. What you choose to DM depends a lot on your flow, and that's a function of how the tools in your flow behave. If your flow insists that netlists be generated every time right before they are used, DM the netlist might actually cause problems (think of AMS's netlists in cellviews and TMPDIR usage). On the other hand, not DM'ing netlists can leave you in a situation where the more recently generated netlists do not match an older version of schematic you just checked out, and if the tools in your flow just check for time stamp, you can very well be working on netlists which don't match your design.
DM and archiving are related, but are really different. As our moderators said in their interviews, DM is so important for multi-site designs. If you look at DM as something that is active and current, versus archiving which is static, you will consider the management of secondary or generated files as important. The fact that you can generate these secondary files does not mean that your flow will always generate them as needed.
Product Engineering, Central Architecture and Technology