I understand the visual usefulness of organizing a DOORS Project with subfolders and a collection of modules (eg, per the V-model of system engineering) ... but is this necessary? Can all requirements for all disciplines and stages of development be captured in a single module, with appropriate chapters/subchapters (that would follow a more complicated folder hierarchy with multiple modules)?
I know DOORS is a complex database, and a single module would become Huge, but given the computing power of most workstations nowadays, I'm not sure performance would really be affected. So, what don't I know about DOORS & req engineering that would advise against a single module approach?
With DNG, this isn't feasible. We have divided out our requirements into modules, and we still have major performance issues with the larger (2000 artifact +) ones. This is despite the fact that DNG is on the highest tier of servers for our company.
From what I understand, DNG's poor performance has less to do with the server/workstation environment on which it's hosted and more to do with its basic Jena architecture.
DNG 6.0.5 has tuning settings to help with loading and viewing large modules. Anyone with large modules should have a plan to get to 6.0.5 as soon as possible just for this reason.
You can read about it here.