Introduction¶
Bringing Engineering-as-Code to the Sphinx framework.
Combine Docs-as-Code with Application Lifecycle Management, to track requirements, specifications, test cases, and other engineering objects in your documentation.
An extension for the Python based Sphinx documentation framework, enabling you to define, link, and analyse engineering objects within your documentation, specific to your project, such as features, requirements, specifications, test cases, …
Allows you to define the exact way of using and configuring need objects, to create documentation valid with ISO 26262, DO-178B/C or any other safety standard.
Extensive configuration options allow you to adapt the extension to your specific needs, and the built-in API allows other extensions to extend sphinx-needs for specific solutions.
Integration with external sources
Import and export mechanisms facilitate external synchronization with other tools, such as JIRA, GitHub, or spreadsheets, allowing for embedding tickets, requirements and other information into your documentation.
Dynamic functions allow you to handle complex data chains between needs, to load and set changeable data automatically during the documentation generation phase.
Allows for the creation of specific objects for architecture elements, which can be reused and recombined in different flow diagrams and higher architecture elements, using PlantUML.
See more from useblocks to enhance your sphinx-needs experience:
Provides an oversight of the useblocks ecosystem, and its goal to bring Engineering-as-Code to the software development process.