Skip to content

Verification Management#

Verification is the process by which requirements are validated against real-world behavior, ensuring that the system conforms to the specified needs. In SysGit, each Verification artifact is a formal object that ties a Requirement to an engineering activity used to confirm compliance—whether through inspection, test, analysis, or demonstration.

Verification Table#

The Verification Table offers a dedicated, streamlined view for managing all verification artifacts associated with your current project. This table presents a row for each Verification and includes the following columns:

  • ID: A unique identifier for the verification artifact.
  • Name: A short title or description of the verification activity.
  • Objective: Describes the purpose and procedure of the verification effort.
  • Verifies: Links to the associated Requirement(s) being verified. Clicking the link opens the corresponding Requirement in context.
  • Method: The method of verification used (e.g., Test, Analyze, Inspect, Demo).
  • Results: Optionally links to the result artifact, such as a report, document, or data capture.
  • Risk Level: A color-coded indicator (Low, Medium, High) that allows engineers to quickly identify high-risk verification efforts.

This view allows Systems Engineers and QA stakeholders to assess the verification coverage and identify critical areas of the system that may require deeper scrutiny or additional testing. Each row is interactively linked with the Requirements and can be filtered or exported for reporting purposes.

By keeping this table up to date, engineering teams can easily demonstrate compliance to stakeholders and customers, and provide the necessary documentation trail for system certification.

Verification Methods#

Test#

[Content to be added - when to use test method, examples]

Analyze#

[Content to be added - when to use analyze method, examples]

Inspect#

[Content to be added - when to use inspect method, examples]

Demonstrate#

[Content to be added - when to use demo method, examples]

Managing Verification Results#

Linking to External Artifacts#

[Content to be added - how to link test results, reports, etc.]

Status Tracking#

[Content to be added - tracking verification status]

Pass/Fail Criteria#

[Content to be added - defining and evaluating criteria]

Verification Best Practices#

[Content to be added - consolidation strategies, avoiding duplication, etc.]

See Also#