BaselineCase

Requirement screening for automotive safety teams. Find vague wording, missing metadata, and trace gaps before review.

  1. 1 Upload documents Excel XLSX, CSV/TSV, JSON/JSONL, CycloneDX .cdx.json, HTML/HTM including Sphinx, Markdown/MD, RST, ADOC, DOCX, PDF, TXT, LOG, and mislabeled table/text exports such as .dat.
  2. 2 Review ingested data Confirm artifacts, extracted entities, evidence rows, and identified links.
  3. 3 Review requirement quality See vagueness, atomicity, testability, and metadata completeness findings.
  4. 4 Get assurance insights Prioritize gaps, blockers, and review work before safety sign-off.

Example screening results.

BCU-SW-REQ-1842 High

"The controller shall respond quickly during degraded sensor input."

Finding
Vague timing
Missing
Measured threshold
Reviewer
SW safety requirements
SG-07 -> SWR-211 Blocker

Brake fallback requirement has no linked verification test.

Gap
Missing TC link
Impact
Release evidence incomplete
Next
Add or justify verification
SUP-BRAKE-447 Medium

Supplier batch is missing review-critical fields.

Missing
ASIL, owner, variant
Source
Supplier CSV import
Next
Return for metadata completion

What reviewers see first.

Requirement Outcome Priority
BCU-SW-REQ-1842 Vague timing: "quickly" High
SWR-211 No verification test linked Blocker
SUP-BRAKE-447 ASIL, owner, and variant missing Medium

Screen the baseline before the review starts.

Start for free (no credit card)