Features¶
🔍 Features
ID |
Title |
SI |
Errors |
|---|---|---|---|
C Language Support |
|||
Analyze marked content via CLI interface |
ERR_SCL_CLI_ANALYZE_1; ERR_SCL_CLI_ANALYZE_2; ERR_SCL_CLI_ANALYZE_3 |
||
Discover the filepaths a specified root directory via CLI interface |
|||
Export marked content to other formats via CLI interface |
ERR_SCL_CLI_WRITE_1; ERR_SCL_CLI_WRITE_2; ERR_SCL_CLI_WRITE_3 |
||
Customized comment styles |
|||
C++ Language Support |
|||
Define new traceability objects in source code |
|||
Link code to existing need items |
|||
Python Language Support |
|||
Extract blocks of reStructuredText embedded within comments |
ERR_SCL_RST_EXTRACTION_1; ERR_SCL_RST_EXTRACTION_2; ERR_SCL_RST_EXTRACTION_3 |
Create new Sphinx-Needs directly from a single comment line in your source code. |
Support for defining traceability objects in C source code. |
Support for defining traceability objects in C++ source code. |
Support for defining traceability objects in Python source code. |
Support for different customized comment styles in source code. The comment structure can be defined in the configuration file. |
Link code to existing need items without creating new ones, perfect for tracing implementations to requirements. |
Extract blocks of reStructuredText embedded within comments, allowing you to include rich documentation with associated metadata right next to your code. |
It shall be possible to analyze marked content via the CLI interface. |
It shall be possible to specify a root directory for the CLI interface. All files in and below this directory shall be discovered.
|
It shall be possible to export marked content to other formats via the CLI interface. |