It's all about the answers!

Ask a question

Concerns around DNG 6 for creating project baselines

anoop mc (75010149205) | asked Sep 23 '15, 2:51 a.m.
 Before we move on to DNG 6.0 from current version 501, our project team would like to clarify the 
functionality with DNG 6.0 

Note that the project team plan to use RM inbuilt CM and not any other global configuration 
management system. 

Concerns around DNG6 around creating project baselines

Today the team face problems with project baselines in Version 501, they just donĀ“t work. After we 
migrate to DNG6 will we be using this mechanism as a usual mechanism.

- When the project baselines were working, for us it took about 30 minutes to create one baseline.

- What will happen with the module baselines after the migration to V 6.0?

Accepted answer

permanent link
Ralph Schoon (57.0k23642) | answered Sep 23 '15, 4:28 a.m.
edited Sep 23 '15, 4:31 a.m.
I would highly recommend to set up a test system and to enable configuration management there and play with the concepts. You will require to request a key to do so. Carefully read the whole page and make sure you understand its content.

Enabling it has consequences. Make sure you experiment with it and understand the impact on reporting and the data warehouse and anything else, before you try this in production.

As far as I am aware the old concept of baselines will be totally gone if you enable Global Configuration Management. You will use configurations and baselines on configurations instead of the old baselines. If you want to understand the performance implications, set up your current system in an isolated test environment and prototype with it, to understand the implications and get a feel for what you can do.
anoop mc selected this answer as the correct answer

Ralph Schoon commented Sep 23 '15, 4:30 a.m.

Please also see and note that you can migrate your old baselines to the new concepts.

anoop mc commented Sep 29 '15, 6:30 a.m. | edited Sep 29 '15, 6:44 a.m.

Going through articles, I feel that until we make use of all the SDLC feature using these CLM 6.0 tools it doesnt make sense to enable Global Configuration Management capability in DNG.

In our case the project team use only DNG for Requirements Management as standalone.

Ralph Schoon commented Sep 29 '15, 6:45 a.m. | edited Sep 29 '15, 6:45 a.m.

In this case there are no side effects and the feature could be potentially interesting. Even if you don't use global configuration or only global configurations in RDNG, having the capability to branch, stream and merge requirements could be of interest. This kind of capabilities have been requested for years by a lot of customers.

If you can live with the baselines you have today, I would suggest to wait and evaluate the capabilities in a test system.

If the answer was helpful, please accept it.

One other answer

permanent link
ian green (17814) | answered Sep 30 '15, 2:04 a.m.
Ralph's suggestion to set up a test environment is a good one.  You can use the sandbox to try DNG; but the sandbox cannot be used to see how your module baselines are migrated.

I would add:
  • In 6.0, baselines are created of the entire project (including all modules in that project); it is not possible to create a baseline of only a single module.
  • Baselines can be created in 6.0 without enabling the configuration management feature.  (Enabling configuration management provides additional facilities beyond baselining.)
  • Each of your module baselines will be migrated to a 6.0 baseline, and you will be able to use those baselines as you did prior to upgrade.

Your answer

Register or to post your answer.