Move beyond the limitations of isolated, document-centric databases. Embrace a data-centric, OSLC-powered web platform designed to achieve seamless, real-time traceability across your entire engineering lifecycle—without replicating data.
Initiate Launch SequenceEngineering the Digital Thread requires understanding core platform shifts.
DNG treats every requirement as a discrete, reusable, version-controlled "Artifact" rather than a static line in a document. Welcome to true information reuse.
Master lifecycle states natively. Move from manual baselines in Classic to dynamic CM in DNG utilizing Streams, Baselines, and isolated Change Sets.
Say goodbye to isolated DXL scripts. Leverage industry-standard JavaScript, Python, and RESTful APIs to automate traceability and requirement health scoring.
| DOORS Classic (D9) | DOORS Next (DNG) | Strategic Advantage in DNG |
|---|---|---|
| Object | Artifact | Discrete, atomic units of data reused across modules without "clone and own" errors. |
| Formal Module | Web-based Module | Acts as a structured document referencing base artifacts, providing precise context. |
| Proprietary Linking | OSLC Linking | Real-time, cross-application traceability (the Digital Thread) without data replication. |
| DXL Scripts | JS / Python REST APIs | Industry-standard automation for quality scoring; highly maintainable. |
| Local DB (Thick Client) | Jazz Team Server | Reduces IT burden, browser-accessible anywhere, centralized administration. |
| Manual Baselines | Configuration Management | Parallel development, read-only snapshots, and sandboxed Change Sets. |
Your 4-Week DNG Integration Curriculum
Shifting from Objects to Artifacts and understanding Base vs. Module Artifacts.
KNOWLEDGE CHECK:
"What is the fundamental difference between a Base Artifact and a Module Artifact?"
Answer: A Base Artifact resides in the folder repository as core data, while a Module Artifact is a context-specific reference to it within a document.
Establishing robust OSLC traceability using Link Validity across projects.
KNOWLEDGE CHECK:
"How does OSLC improve traceability compared to traditional linking?"
Answer: OSLC links data across the Jazz platform (e.g., to EWM/ETM) via RESTful services in real-time without copying the underlying data.
Navigating Streams (live state), Baselines (snapshots), and Change Sets.
KNOWLEDGE CHECK:
"Why create a Change Set before modifying a baseline requirement?"
Answer: It provides an isolated mirror environment to propose and approve modifications without disrupting the live Stream.
Transitioning from DXL to modern APIs for health monitoring.
KNOWLEDGE CHECK:
"Which modern languages replace DXL for customizations in DNG?"
Answer: JavaScript for internal widget customizations and Python/REST APIs for external data automation.
Automate quality control and enforce the Digital Thread using modern APIs.
Implement JS regex to scan Primary Text. If words like "should", "could", or "maybe" are detected, update the Quality Score attribute to "Review Required".
Utilize the REST API to query modules. Flag any "System Requirement" artifact that lacks an outbound OSLC link to a Test Case in ETM.
Immediate visibility into project health, traceability, and governance.
Widget 1
Historical volatility vs. stability (30 days)
Widget 2
Real-time % linked to downstream test cases
Widget 3
Dynamic list of artifacts flagged for review
Widget 4
Pending changes requiring formal approval
Widget 5
Quick links to read-only snapshots for governance audits