It's all about the answers!

Ask a question

DNG: Setup in DNG from DOORS Classic


vinitha dsouza (147223136) | asked Aug 30 '17, 1:42 a.m.

Hello Experts,

We are currently Using Doors Classic 9.x version.
After watching many tutorials, i am still confused how to Migrate and understanding DNG Terminology.

In some tutorials where Door Classic comparision to DNG is given, i have got some hints. Would like to know your inputs on this.

Is Database in Doors equivalent of One Project Area?
Because we have one Database Used and have many projects => Folders=> Modules.
- We used to do baseline the Specific modules and Permissions are set at Projects level.

If Database is one Project area,when i use DNG i am only allowed to create baseline on Project Area level.
How can i get same behaviour which we used to do in Doors?

Thanks



Accepted answer


permanent link
Adrian Haw (2991242) | answered Aug 30 '17, 5:10 a.m.
edited Aug 30 '17, 5:10 a.m.

It's impossible to explain everything here but specifically to your questions.....

Is Database in Doors equivalent of One Project Area?
==> No. A DOORS 9 database can contain many projects as can a DOORS NG database. When starting out in DOORS NG think of a project in DOORS 9 equalling a project in DOORS NG (it's more complicated than that but start at the beginning).

If Database is one Project area,when i use DNG i am only allowed to create baseline on Project Area level.
How can i get same behaviour which we used to do in Doors?
==> You cannot specifically baseline a module in DOORS NG. A DOORS NG project contains at least 1 Component but can contain more. Each Component has at least 1 version (In DOORS NG this is called a Stream) but can have more. Each Component can have 1 or more modules. A Component Stream can be baselined which means everything contained in that Component Stream is baselined as a unit.
Taking the concepts a bit further... how you set up your Projects, Components and Streams has a major impact on things like establishing traceability in DOORS NG. In DOORS 9 creating traceability was relatively easy - all projects only have 1 version, projects can contain other projects and linking objects in modules within and across projects was easy as the database was in a version sense 'flat'. In DOORS NG this is not the case because now Project Components have versions (streams) to link between artifacts in different projects requires you to select which version (Stream) of the project component(s) contain artifacts (DOORS NG name for objects) you will be creating links between - you do this by adding in project component versions to a DOORS NG Global Configuration. Note that Global Configurations also contain at least 1 Component but can have many and each Global Configuration Component has at least 1 version (Stream) but can have many. Note: Global Configurations can contain other Global Configurations but Projects cannot contain other Projects.

My advice is to arrange consultancy because you will sure spend a lot of time (money) trying to figure this out for yourself using youtube and these forums.


vinitha dsouza selected this answer as the correct answer

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.