reqmd reqmd Stakeholder Goals

reqmd Stakeholder Goals

approved 7Root

7 requirements

Stakeholder goals define the high-level business and technical objectives that the reqmd tool must satisfy. As the top V-model layer, they have no upstream traces.

Category
Priority
Source

STK-GOAL-001 Text-first Git-native authoring

#

The requirement management tool shall enable text-first, Git-native authoring of requirement specifications without requiring a GUI. New projects shall be able to start from a working scaffold (schema plus example document) without hand-writing schema boilerplate.

Details
Priority
Critical
Source
Product
Category
Authoring
Rationale:

Engineers work in IDEs and version control daily. A plain-text format that diffs cleanly and reviews in standard pull requests minimizes tool-switching friction. A scaffolded starting point removes the blank-page cost of adopting a schema-driven format.

Traced from (3)
SYS-CLI-001CLI subcommands SYS-FMT-001Markdown requirement format SYS-INI-001Project scaffolding with presets

STK-GOAL-002 Human-readable machine-parsable specs

#

Requirement documents shall be human-readable in any Markdown renderer and simultaneously machine-parsable into structured attributes.

Details
Priority
Critical
Source
Engineering
Category
Authoring
Rationale:

Non-technical stakeholders review requirements in rendered form (GitHub, GitLab, docs sites). Automated tooling needs structured data for validation and export. Both modes must coexist in the same file.

Traced from (6)
SYS-BAS-001Baseline comparison via git tags SYS-FMT-002Built-in attribute system SYS-FMT-004YAML frontmatter support SYS-IMP-001Source-code requirement extraction SYS-IMP-002External requirement import via an exchange format SYS-REPIN-001Bulk version-pin update via reqmd repin

STK-GOAL-003 Schema-driven validation

#

The tool shall validate requirements against a project-defined schema, rejecting malformed or incomplete entries before they reach production reviews. Validation shall be scopable to a filtered subset of the tree without losing trace resolution.

Details
Priority
Critical
Source
Quality
Category
Validation
Rationale:

Manual review alone does not scale. Schema-driven validation catches missing fields, invalid values, and broken trace chains automatically in CI. Scoping keeps incremental CI affordable on large trees.

Traced from (7)
SYS-CHK-003Disjoint-attribute consistency check SYS-CON-001Content tree — nothing dropped SYS-FIL-001Generic attribute filtering SYS-FMT-003Schema.yaml document configuration SYS-STS-001Requirement status lifecycle SYS-SUP-001Check suppression SYS-VAL-001Multi-pass validation pipeline

STK-GOAL-004 Multi-format export for review and analytics

#

The tool shall export requirement specifications to standard interchange formats: CSV for suppliers, standalone HTML for human review, flat NDJSON tables for reporting platforms and data warehouses, and a graph database for structural queries.

Details
Priority
High
Source
Product
Category
Export
Rationale:

Tier-1 suppliers and homologation authorities require structured export formats. CSV covers basic exchange; HTML supports human trace navigation; NDJSON feeds analytics and dashboards without a bespoke integration; the graph export serves cross-cutting dependency and impact queries.

Traced from (4)
SYS-CLI-001CLI subcommands SYS-EXP-001NDJSON tables for reporting platforms SYS-GRA-001Graph database export SYS-HTM-001Standalone HTML export

STK-GOAL-005 V-model traceability

#

The tool shall support V-model traceability patterns conformant with ASPICE and ISO 26262, including upstream-only trace declarations, disposition tracking, version pins, and automatic parent-child hierarchy linking from heading levels.

Details
Priority
High
Source
Safety
Category
Traceability
Rationale:

Functional safety standards mandate bidirectional traceability from stakeholder needs through system requirements, software requirements, and test specifications. Heading-level hierarchy lets authors decompose requirements naturally while the tool auto-links child-to-parent traces.

Traced from (9)
SYS-CON-001Content tree — nothing dropped SYS-FIL-001Generic attribute filtering SYS-FMT-005Level-typed trace coverage SYS-IMP-001Source-code requirement extraction SYS-IMP-002External requirement import via an exchange format SYS-STS-001Requirement status lifecycle SYS-TRC-001Upstream-only trace model SYS-VAL-001Multi-pass validation pipeline SYS-VAL-002Verification result ingestion and outcome-gated checks

STK-GOAL-006 Verification results close the V-model

#

The tool shall consume verification and validation results produced by automated tests and manual reviews, and shall enforce that every approved verification measure carries a current, passing result.

Details
Priority
High
Source
Quality
Category
Verification
Rationale:

A trace to a test specification proves that verification was planned, not that it passed. ASPICE requires recording and evaluating verification results. Loading results per invocation (CTRF reports and review documents) keeps run-to-run churn out of git while still failing CI on a failing or missing verdict.

STK-GOAL-007 Interoperable requirement ingestion

#

The tool shall ingest requirements that originate outside authored Markdown — source-code symbols with documented trace markers, and records exported from ALM systems such as DOORS or codeBeamer — into the same ID space and document format as hand-authored requirements.

Details
Priority
High
Source
Engineering
Category
Interoperability
Rationale:

Real projects do not start with an empty repository. Imported items must validate, trace, export, and diff exactly like authored ones, or the tool only covers half the specification. A single versioned exchange format keeps every importer small and keeps the Markdown/YAML syntax rules in one implementation.