Skip to content

doorstop-dev/doorstop

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Jan 12, 2025
5e94842 · Jan 12, 2025
Jan 12, 2025
Jan 12, 2025
Oct 4, 2024
Jan 11, 2025
Jan 12, 2025
Jan 13, 2024
Mar 21, 2024
Oct 7, 2024
Jul 11, 2019
Sep 30, 2024
Feb 12, 2024
Jan 15, 2021
Apr 15, 2015
Jan 13, 2024
Apr 15, 2015
Nov 14, 2014
Feb 17, 2018
Oct 4, 2024
Oct 7, 2024
Sep 18, 2018
Jan 12, 2025
Jan 12, 2025
Jan 11, 2025
Jan 25, 2024
Mar 11, 2017
Jul 11, 2019
Feb 27, 2017
Oct 7, 2024
Apr 12, 2017
Apr 9, 2024
Oct 16, 2024
Jan 12, 2025
Jan 12, 2025
Jan 11, 2025
Mar 18, 2022

Repository files navigation

Linux Tests macOS Tests Windows Tests
Coverage Status Scrutinizer Code Quality PyPI Version
Gitter Google Best Practices

Overview

Doorstop is a requirements management tool that facilitates the storage of textual requirements alongside source code in version control.

When a project leverages this tool, each linkable item (requirement, test case, etc.) is stored as a YAML file in a designated directory. The items in each directory form a document. The relationship between documents forms a tree hierarchy. Doorstop provides mechanisms for modifying this tree, validating item traceability, and publishing documents in several formats.

Doorstop is under active development and we welcome contributions. The project is licensed as LGPLv3. To report a problem or a security vulnerability please raise an issue. Additional references:

Setup

Requirements

  • Python 3.9+
  • A version control system for requirements storage

Installation

Install Doorstop with pip:

$ pip install doorstop

or add it to your Poetry project:

$ poetry add doorstop

After installation, Doorstop is available on the command-line:

$ doorstop --help

And the package is available under the name 'doorstop':

$ python
>>> import doorstop
>>> doorstop.__version__

Usage

Switch to an existing version control working directory, or create one:

$ git init .

Create documents

Create a new parent requirements document:

$ doorstop create SRD ./reqs/srd

Add a few items to that document:

$ doorstop add SRD
$ doorstop add SRD
$ doorstop add SRD

Link items

Create a child document to link to the parent:

$ doorstop create HLTC ./tests/hl --parent SRD
$ doorstop add HLTC

Link items between documents:

$ doorstop link HLTC001 SRD002

Publish reports

Run integrity checks on the document tree:

$ doorstop

Publish the documents as HTML:

$ doorstop publish all ./public