Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add generic module verification and inspection needs to metamodel

Abierto
#611 2 comentarios 0 reacciones 1 asignado Ver en GitHub

@FScholPer ya está trabajando en esto.

Desde el 22/6/2026.

  • #612 de @FScholPer — cerrado sin fusionar

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Summary

Add metamodel support for module-level verification reporting and formal inspection evidence in a way that is generic, scalable, and aligned with S-CORE verification/review concepts.

Background

Current metamodel support is strong for requirement/test traceability (testcase -> fully_verifies/partially_verifies), but module-level verification reporting and checklist-based inspection evidence are not modeled as first-class, flexible needs.

The process expects Module Verification Reports to aggregate heterogeneous evidence (tests, analyses, inspections, coverage, logs/results, qualification evidence), and inspections may use different checklist families (requirements, architecture, implementation, etc.).

Scope

Introduce and integrate:

  • mod_ver_report as a module-level verification aggregation need.
  • mod_insp as a formal inspection evidence need.
  • Extra link types to support broad evidence linkage (evidence) and inspection scope (inspects).
  • Generic linking behavior so reports/inspections can reference many relevant need types (not only a narrow fixed subset).

Requirements

  • Keep existing direct testcase-to-requirement verification links unchanged.
  • Allow mod_ver_report to aggregate evidence for:
    • requirement coverage
    • architecture/detailed design verification
    • DFA/safety/security analysis evidence
    • test results and retained logs
    • static analysis and structural coverage evidence
    • component qualification verification evidence
  • Allow mod_insp to reference multiple checklist/evidence artifact flavors (req/arc/impl/custom).
  • Keep compatibility with existing status patterns and avoid global schema churn.

Acceptance Criteria

  • Metamodel contains mod_ver_report and mod_insp definitions with required metadata and links.
  • mod_ver_report can link to heterogeneous evidence using generic relations (e.g. contains, evidence, covers).
  • mod_insp can link to arbitrary inspected artifacts and checklist evidence.
  • needs_extra_links includes required link types for evidence and inspection.
  • No metamodel parsing/lint errors.

Follow-ups (optional but recommended)

  • Add graph checks for ASIL-specific verification evidence completeness.
  • Add doc examples showing how to populate mod_ver_report and mod_insp with real module artifacts.
  • Align templates/how-to pages with the new needs.

** Co-created by github copilot

Lenguaje dominante
Python
Estrellas
11
Forks
33
Merge medio
22 h 43 min
PR fusionados (30 d)
65

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eclipse-score/docs-as-code

Todos los issues de eclipse-score/docs-as-code

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.