② Build your first requirements trace
Goal
Using combo agent, within ~1 hour produce a trace matrix for one domain (suggested: body control):
- Import ≥50 requirements
- Build Stakeholder → Feature → Component trace
- Output a compliance-oriented report (ASPICE 4.0)
Prerequisites
- DOORS Next credentials (or a ReqIF file), or
- Bundled sample ReqIF (~80 body-control requirements)
Steps
Step 1 — DOORS credentials (~5 minutes)
Dashboard → Integrations → DOORS Next → add:
- Project URI
- Username + password or OAuth token
Step 2 — Create requirements session (~1 minute)
Create a Combo named Body control traceability v1.
Step 3 — Import requirements (~10 minutes)
Or:
The system:
- Parses hierarchy
- Extracts attributes
- Displays the requirement inventory in-session
Step 4 — Establish trace (~20 minutes)
The system:
- Detects existing trace links
- Proposes semantic matches for missing links
- Outputs candidate pairs with confidence
You approve or fix candidates.
Step 5 — Compliance check (~10 minutes)
Outputs:
- Gap list (missing upstream stakeholder)
- Orphan list (missing downstream component)
- Compliance scorecard
Step 6 — Export (~5 minutes)
Or:
Acceptance checklist
- Requirement inventory present (≥50 items)
- Trace coverage ≥95%
- ASPICE compliance report generated
- Links written back to DOORS or HTML exported
Next steps
FAQ
Q: DOORS is slow? A: Session caches a requirements snapshot—no need to refetch every time.
Q: Low-confidence matches? A: Marked “needs human confirmation”; nothing auto-commits without approval.