StrictDoc Requirements coverage

User Guide

F.A.Q.

Development Plan

GOAL-1-TOOL-SUPPORT
1.1. Software support for writing requirements and specifications documents
  • SDOC-HIGH-REQS-MANAGEMENT
    1.1. Requirements management
    • SDOC-DM-MODEL
      3.1. Modeling capability
      • SDOC-FMT-PRIMARY
        4.1. Primary text implementation
GOAL-2-REDUCE-DOCUMENTATION-HAZARDS
1.2. Reduce documentation hazards
GOAL-3-NO-RUNAWAY-DOCUMENTATION
1.3. No (or less) run-away documentation
GOAL-4-CHANGE-MANAGEMENT
1.4. Change management
UI-1-TEXT
2.1. Command-line interface
UI-2-WEB
2.2. Web interface

Backlog

[no UID]
4. Document archetypes

Contributing to StrictDoc

Developer Guide

Requirements

SDOC-HIGH-REQS-MANAGEMENT
1.1. Requirements management
  • SDOC-DM-MODEL
    3.1. Modeling capability
    • SDOC-FMT-PRIMARY
      4.1. Primary text implementation
SDOC-HIGH-DATA-MODEL
1.2. Data model
  • SDOC-DM-MODEL
    3.1. Modeling capability
    • SDOC-FMT-PRIMARY
      4.1. Primary text implementation
  • SDOC-FMT-GRAMMAR
    4.2. Grammar
[no UID]
1.3. Command-line interface
[no UID]
1.6. Platform support
[no UID]
1.6.1. macOS support
[no UID]
1.6.2. Linux support
[no UID]
1.6.3. Windows support
SDOC-HIGH-VALIDATION
1.7. Requirements validation
  • SDOC-VALIDATION-UNIQUE-UID
    6.1. Uniqueness of UID identifiers in a document tree
  • SDOC-VALIDATION-NO-CYCLES
    6.2. No cycles in a document tree
  • SDOC-VALIDATION-VALID-HTML
    6.3. Valid HTML markup
[no UID]
1.8. Requirements text format
[no UID]
1.9. Linking requirements
[no UID]
1.10. Scalability
SDOC-HIGH-REQS-TRACEABILITY
1.11. Traceability
[no UID]
1.12. Visualization
[no UID]
1.13. Open source software
SDOC-IMPL-PARAL
2.1. Parallelization
SDOC-IMPL-INCREMENTAL
2.2. Incremental generation
SDOC-DM-MODEL
3.1. Modeling capability
  • SDOC-FMT-PRIMARY
    4.1. Primary text implementation
[no UID]
3.2. Project
[no UID]
3.2.1. Project title
[no UID]
3.5.1. Statement
[no UID]
3.5.2. UID identifier
[no UID]
3.5.2.1. UID identifier format
[no UID]
3.5.3. Title
[no UID]
3.5.4. References
[no UID]
3.5.5. Comments
[no UID]
3.5.6. Special fields
[no UID]
3.7. Links
[no UID]
3.7.1. Parent links
SDOC-FMT-PRIMARY
4.1. Primary text implementation
SDOC-FMT-GRAMMAR
4.2. Grammar
[no UID]
4.2.1. No indentation
[no UID]
4.3. Type safety
[no UID]
5.1.1. Generated file names
[no UID]
5.2.1. Single document: Normal form
[no UID]
5.2.2. Single document: Tabular form
[no UID]
5.2.3. Single document: 1-level traceability
[no UID]
5.2.4. Single document: Deep traceability
[no UID]
5.2.5. Left panel: Table of contents
[no UID]
5.3.1. Sphinx documentation generator
SDOC-GEN-EXCEL-EXPORT
5.4. Excel Export
[no UID]
5.5. ReqIF import/export
SDOC-VALIDATION-UNIQUE-UID
6.1. Uniqueness of UID identifiers in a document tree
SDOC-VALIDATION-NO-CYCLES
6.2. No cycles in a document tree
SDOC-VALIDATION-VALID-HTML
6.3. Valid HTML markup
[no UID]
7.1. Linking with implementation artifacts
[no UID]
7.1.1. Validation: Broken links from requirements to source files
[no UID]
7.1.2. Validation: Broken links from source files to requirements
[no UID]
7.2. Requirements coverage
[no UID]
7.3. Source coverage
[no UID]
8.1. AJAX updates of multiple web forms

Design Document