Clarify Completeness of Requirements Decomposition

Aperta
  • Qualcosa non va?
#852 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
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
documentation

Direzione di ricerca

Start by reading the process description sections on Feature Requirements, Component Requirements, traceability, and Feature Integration Tests to understand what assurance the current process already defines. Then identify whether the existing activities and reviews establish complete decomposition while preserving intent. Done means the process team clarifies what is sufficient and documents any additional expectations needed, without prescribing unnecessary overhead.

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

Descrizione

Context

Feature Requirements are decomposed into Component Requirements. While traceability establishes the relationships between requirements, it does not necessarily demonstrate that the lower-level requirements collectively cover the original requirement completely.

Feature Integration Tests do not necessarily close this gap, as they typically focus on feature-level behavior rather than verifying every detail of the original requirements. Therefore, successful Feature Integration Tests cannot be relied upon to establish the completeness of requirements decomposition.

Open Question

How do we ensure that the decomposition of higher-level requirements into lower-level requirements is complete, without losing or unintentionally changing the original intent?

Is this already sufficiently addressed by our existing process, or do we need additional expectations regarding completeness?

Request to the Process Team

Please evaluate and clarify:

  • Whether and how completeness of requirements decomposition needs to be addressed in our process.
  • Whether existing activities and reviews already provide sufficient assurance.
  • If additional expectations are necessary, what exactly needs to be established, documented, or reviewed.

The intention is not to prescribe a particular solution or introduce additional process overhead by default, but to clarify what is actually necessary and ensure our process addresses it appropriately.

Lingua principale
HTML
Stelle
6
Fork
25
Merge medio
14h 47m
PR unite (30g)
35

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

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 eclipse-score/process_description

Tutte le issue di eclipse-score/process_description

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.