Requirements Management in IBM DOORS Next Generation
Run requirements in IBM DOORS Next (DNG) the way a modern program expects: artifacts and modules, typed OSLC links, configurations and global config, and a traceability matrix that holds up through a review.
IBM DOORS Next (often called DNG) is where a growing number of programs now keep their requirements — a browser-based, OSLC-linked successor to DOORS Classic with configurations, global configuration management, and a very different mental model. This guidebook walks you through it the way a requirements lead would: artifact by artifact, link by link, configuration by configuration, with the discipline that keeps a baseline defensible.
Every guide is built around the artifact you'll actually hand to a reviewer: a clean module, a typed link that traces, a coverage matrix that closes — not a tour of the web UI. If you've worked DOORS Classic, the final guide covers the move; if you're starting fresh in DNG, you can read straight through.
New to DOORS Next
You've been given a DNG project and a login and told to "manage the requirements." Start here.
Coming from DOORS Classic
You know modules and link sets, but configurations, change sets, and OSLC are new territory. This maps the old habits onto the new tool.
Anyone owning the RTM
You're responsible for traceability in DNG and need it to survive a review, not just exist.
- §Move through artifacts, folders, modules, types and attributes without guessing
- §Create typed, directed OSLC links that actually trace — and read one link from both ends
- §Build views, filters and the Query Builder to find and shape exactly the artifacts you need
- §Work configurations: streams, baselines, change sets, and global configuration management
- §Stand up and defend a Requirements Traceability Matrix, and run reviews, reports and the Cameo integration