Skip to content

Verification and Validation Management

Verification and Validation supports plans, sets, cases, execution snapshots, defects, requirement mappings, and RVTM reporting.

Primary objective

Ensure each requirement has planned and executable verification evidence, with traceable results and controlled defect handling.

What You Can Do

  • Create and manage verification plans.
  • Manage sets and cases globally and per plan.
  • Import/export verification data and cases.
  • Create execution snapshots and update execution results.
  • Track defects and lifecycle status.
  • Link cases to requirements.
  • Generate and export RVTM.

Typical Workflow

  1. Create a verification plan.
  2. Add sets and cases (manual or import).
  3. Map cases to requirements.
  4. Execute through snapshots and record result updates.
  5. Log and triage defects.
  6. Review RVTM and export evidence.

Verification Workflow Diagram

flowchart TD
    A[Create Verification Plan] --> B[Create or Import Sets and Cases]
    B --> C[Map Cases to Requirements]
    C --> D[Execute via Snapshots]
    D --> E[Update Results]
    E --> F[Log and Track Defects]
    F --> G[Review RVTM and Export]

Key Pages

  • Dashboard, plans, sets, cases, defects.
  • Case import/export (global and plan-scoped).
  • Data import/export and snapshot import.
  • Mapping add/remove, RVTM view/export.
  • Activity and execution-result CRUD endpoints.
Collapsed quality gate

Do not freeze release-related artifacts until unmapped cases, failed results, and unresolved high-severity defects are reviewed.

Practical Tips

  • Keep naming synchronized with requirement module IDs.
  • Use snapshots to preserve point-in-time evidence for audits.
  • Review unmapped cases before release readiness reviews.

Operational habit

Run RVTM checks after every significant case import to catch mapping drift early.