reqmd Stakeholder Goals

5 requirements (5 parents, 0 children)

approved5
Root

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.

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

#
Priority
Critical
Source
Product
Category
Authoring

The requirement management tool shall enable text-first, Git-native authoring of requirement specifications without requiring a GUI.

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.

Upstream (0)
Downstream (2)
SYS-FMT-001Markdown requirement format SYS-CLI-001CLI subcommands

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

#
Priority
Critical
Source
Engineering
Category
Authoring

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

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.

Upstream (0)
Downstream (4)
SYS-FMT-002Built-in attribute system SYS-FMT-004YAML frontmatter support SYS-BAS-001Baseline comparison via git tags SYS-REPIN-001Bulk version-pin update via reqmd repin

STK-GOAL-003: Schema-driven validation

#
Priority
Critical
Source
Quality
Category
Validation

The tool shall validate requirements against a project-defined schema, rejecting malformed or incomplete entries before they reach production reviews.

Rationale:

Manual review alone does not scale. Schema-driven validation catches missing fields, invalid values, and broken trace chains automatically in CI.

Upstream (0)
Downstream (2)
SYS-FMT-003Schema.yaml document configuration SYS-VAL-001Multi-pass validation pipeline

STK-GOAL-004: Multi-format export

#
Priority
High
Source
Product
Category
Export

The tool shall export requirement specifications to standard interchange formats including CSV, HTML, and graph database. The HTML export shall present requirements in a card-based layout with a persistent tree TOC sidebar for navigation.

Rationale:

Tier-1 suppliers and homologation authorities require structured export formats. CSV covers basic exchange; HTML supports human review with trace navigation and a tree sidebar for browsing requirement hierarchies.

Upstream (0)
Downstream (2)
SYS-CLI-001CLI subcommands SYS-HTM-001Standalone HTML export

STK-GOAL-005: V-model traceability

#
Priority
High
Source
Safety
Category
Traceability

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

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.

Upstream (0)
Downstream (3)
SYS-VAL-001Multi-pass validation pipeline SYS-TRC-001Upstream-only trace model SYS-VAL-002Verification result ingestion and outcome-gated checks