1. Blog posts about StrictDoc
Requirement Traceability with All Substance and No Fuss by BUGSENG.
Text-Based Requirement Management with StrictDoc by Florian Kromer.
F.A.Q. Document
Requirement Traceability with All Substance and No Fuss by BUGSENG.
Text-Based Requirement Management with StrictDoc by Florian Kromer.
The StrictDoc project is a close successor of another project called Doorstop.
Doorstop is a requirements management tool that facilitates the storage of textual requirements alongside source code in version control.
The author of Doorstop has published a paper about Doorstop where the rationale behind text-based requirements management is provided.
The first version of StrictDoc had started as a fork of the Doorstop project. However, after a while, the StrictDoc was started from scratch as a separate project. At this point, StrictDoc and Doorstop do not share any code but StrictDoc still shares with Doorstop their common underlying design principles:
StrictDoc differs from Doorstop in a number of aspects:
The roadmap of StrictDoc contains a work item for supporting the export/import to/from Doorstop format.
Both Sphinx and StrictDoc are both documentation generators but StrictDoc is at a higher level of abstraction: StrictDoc's specialization is requirements and specifications documents. StrictDoc can generate documentation to a number of formats including HTML format as well as the RST format which is a default input format for Sphinx. A two stage generation is therefore possible: StrictDoc generates RST documentation which then can be generated to HTML, PDF, and other formats using Sphinx.
If you are reading this documentation at https://strictdoc.readthedocs.io/en/latest then you are already looking at the example: this documentation stored in strictdoc_02_faq is converted to RST format by StrictDoc which is further converted to the HTML website by readthedocs which uses Sphinx under the hood. The StrictDoc -> RST -> Sphinx -> PDF example is also generated using readthedocs: StrictDoc.
Sphinx-Needs is a text-based requirements management system based on Sphinx. It is implemented as a Sphinx extension which extends the reStructuredText (RST) markup language with an additional syntax for writing requirements documents.
Sphinx-Needs was a great source of inspiration for the second version of StrictDoc which was first implemented as a Sphinx extension and then as a more independent library on top of docutils that Sphinx uses for the underlying RST syntax processing work.
The similarities between Sphinx-Needs and StrictDoc:
The difference between Sphinx-Needs and StrictDoc:
FRET is a framework for the elicitation, specification, formalization and understanding of requirements.
- Users enter system requirements in a specialized natural language.
- FRET helps understanding and review of semantics by utilizing a variety of forms for each requirement: natural language description, formal mathematical logics, and diagrams.
- Requirements can be defined in a hierarchical fashion and can be exported in a variety of forms to be used by analysis tools.
FRET has an impressive list of Publications.
FRET's user interface is built with Electron.
The detailed comparison is coming.