{"id":13266,"date":"2015-06-26T11:38:42","date_gmt":"2015-06-26T15:38:42","guid":{"rendered":"https:\/\/jazz.net\/blog\/?p=13266"},"modified":"2020-03-09T11:35:52","modified_gmt":"2020-03-09T15:35:52","slug":"whats-new-in-doors-next-generation-6-0","status":"publish","type":"post","link":"https:\/\/jazz.net\/blog\/index.php\/2015\/06\/26\/whats-new-in-doors-next-generation-6-0\/","title":{"rendered":"What’s new in DOORS Next Generation 6.0?"},"content":{"rendered":"

This release could well be introducing the most fundamental function into a requirements management (RM) tool since RM systems began.\u00a0 While we continue our drive with usability and productivity, we are also providing support for requirements configuration management (CM), built from the ground up as part of the native tool, rather than simply integrating an external CM system.<\/p>\n

<\/p>\n

<\/p>\n

Configuration Management<\/h2>\n

DOORS Next Generation 6.0<\/a> is our first release providing native configuration management of requirements, enabling functionality for strategic reuse and Product Line Engineering.<\/p>\n

RM offers the ability to define the scope of a project, program, or deliverable\u2014but unless you have control over change this scope could well consume more of your project costs than you expected.Placing requirements under CM allows for the scope to be controlled, while enabling your teams to work in parallel versions at the same time without the need to make project copies to handle variants.<\/p>\n

<\/p>\n

\"\"<\/a><\/p>\n

<\/p>\n

On a basic level, CM provides a way to manage groups of artifacts and their versions. Versions can be split to support different variants and merged in order to deliver changes of requirements back to accepted releases. With CM, users can efficiently create different streams to help manage parallel versions without the need to make copies of their requirements. Additionally, there is robust linking that is specific to the stream the user is working in. This means that following the link shows users the requirement, test, or design element on the other end of the link that is appropriate for the stream they are working in. The ability to compare across streams and baselines helps users to understand how their versions or variants are different and to correct any mistakes.<\/p>\n

The functionality has been designed expecting only a small number of people to engage directly with parallel versions and CM, while the rest of the engineers continue with their work, mostly as if nothing has changed.<\/p>\n

By default, these new capabilities are turned off and project administrators have to enable them for the server and for each project area where users want to take advantage of them.<\/p>\n

Global Configuration Management<\/h2>\n

For some time we have been discussing the benefits of being able to support use cases such as \u201clink a version of a test case with a version of a requirement\u201d.<\/p>\n

\"\"<\/a>6.0 extends CM with a federated approach to lifecycle information.Strategic reuse for complex systems and software is now possible for requirements (RDNG), design (RDM), test (RQM) and software development (RTC).<\/p>\n