Hi Anthony,
Each workflow has its pros and cons. There isn't an one-size-fit-all workflow. Adaptivity isn't a solution for all assembly design challenges. Though it is powerful, it has to be used carefully. It is mostly suitable when you have to reference geometry from another component in this particular context. For example, you need to drill a hole in PartA when it is on top of PartB in AssemblyC. This relationship only exists within AssemblyC, not other places. Also because of its adaptive feature, PartA becomes a part specific to AssemblyC. It may not be reused in other assemblies.
If it is planned well, Adaptivity should help facilitate the inter-component dependency. Most of the trouble in adaptivity I have seen for years, besides bugs, is usually related to excessive usage of adaptivity (almost all features are adaptive), cyclic adaptive dependency (PartA -> PartB -> PartC -> PartA), or conflicting adaptive relationship (PartA -> PartB; PartA -> PartC).
Anyway, to efficiently use Adaptive, you will need to be aware of the adaptive relationship at all time and make change carefully. But, that is a tall order for complex assembly design, particularly when there are endless levels, parts are reused or imported, and design keeps changing.
Derive, on the other hand, has been mentioned regularly as an alternative workflow to Adaptive. Conceptually, they are two different concepts for different purposes. Derive, a.k.a Skeletal Modeling, essentially spawns child parts from a parent part (or parent assembly). The idea is that these components share the same common origin geometrically and spatially. Such derivation is not subject to any context. Parent component is almost in total control. Child component can only follow (adding new features are allowed). It is a one-way relationship. You cannot have a derived part driving its source. The good thing is that it provides design stability. The key decision makers can change the parent parts. And, the change propagates to the project members. This has been primary approach for large assembly design.
Many thanks!
Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer