Expose verification evidence and environment attributes in requirements inspection

Aperta
#25 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react, typescript

Direzione di ricerca

Start with the requirements table and verification matrix implementation, then inspect the linked model files at the reported revision to see how verify links, inherited objectives, and pointer attributes are represented. The report describes an unverified observation from a specific hosted build, so first establish current behavior and record the engine/build identity. Done means the team has defined attribute selection and display, pointer-versus-result semantics, and CSV behavior, with supported links covered without changing saved drafts or the last valid model.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Source and status

WP26 feedback report — Feature F-2; suggestion 2. Session dated 2026-11-10, using the hosted editor as served that day; deployed commit was not identified. The report does not establish current develop or current deployment behavior.

Reported by Zargham in WP26; not independently reproduced by maintainers.

Problem

Tables show declared verify links but not the verifying usage’s evidence, record, test or environment pointer attributes. A typed verification usage without a locally repeated objective reportedly contributed no visible link.

Reproduction / requested workflow

  1. Open the stakeholder model’s Requirements table and verification matrix.
  2. Find requirements verified by evidence usages carrying pointer attributes.
  3. Compare usages with inherited versus locally declared objectives.

Acceptance / investigation criteria

  • Define how users select/view authored verification attributes and their usage context.
  • Show evidence/environment pointers for supported verify links, including inherited objectives where semantically valid.
  • Distinguish pointers and declared links from retrieved evidence or executed results.
  • Consider short names/identifiers, effective documentation and constraint expressions from suggestion 2 without inventing identifiers or interpreting arbitrary doc text as structured evidence.
  • Keep CSV semantics explicit.

Evidence

Model files at the reported revision.

Preserve unapplied drafts and the last valid model. Record exact engine/build identity and distinguish a reported observation from a newly reproduced result.

Lingua principale
TypeScript
Stelle
2
Fork
0
Merge medio
13h 40m
PR unite (30g)
17

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Open-MBEE/sysml_view_editor

Tutte le issue di Open-MBEE/sysml_view_editor

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.