DOORS Next Generation has been out in the field and in serious use for some time, and we know that many long-time DOORS users have been looking to extend it in the same way as they can with DOORS. The scripting capabilities in DNG are not as full as those provided through DXL, but they are being developed with each release. We already have a number of examples published on jazz.net. I am sure that many of you will have had ideas as well. I encourage you to add yours to the existing catalog.

If anybody is looking for ideas, a recent piece of work I was involved with came up with the following list of candidates:

• Set attribute value on import based on keyword. E.g., if text has "shall", set Priority to "High".
• Module comparison. The Use Case is a document is exported for review by people without access to DNG, they send back a new version that contains changes. The recipient wants to see the changes. In some ways, this is similar to round trip, but where the historical version is retained rather than updated. This is similar to the DOORS 9 module comparison
• Parent-child linking. This maintains traceability as required by many standards.  For DOORS, we always recommended that such links not be created (as they make traceability analysis more difficult), but that the requirements should be written in such a way that they are not needed. This can always be done, but often requires some thought. Note that this linking should not (generally) be done between requirements and headings, only where one requirement is a child of another.
• Allow viewing and editing of traceability as a matrix
• Make permissions visible

I'm sure that there are many other ideas out there!