Sphinx-Needs¶
Sphinx makes it easy to create intelligent and beautiful documentation.
|
Analysis¶
ID |
Title |
Type |
|---|---|---|
Sphinx-Needs needs.json file |
artifact |
|
Do not use dynamic functions |
restriction |
|
Programmatic errors in rst/md files result in ignored Traceability objects |
fault |
|
Constraint check fails silently |
fault |
|
Constraint check runs with incomplete data |
fault |
|
Constraint check runs with invalid data |
fault |
|
Constraint not checked during build |
fault |
|
Constraint check runs with wrong data |
fault |
|
Content contains syntax errors |
fault |
|
Invalid meta-data in rst/md files leads to ignored Traceability objects |
fault |
|
Dead link false positive |
fault |
|
Dead link not detected |
fault |
|
Duplicate ID is not detected |
fault |
|
Dynamic functions return invalid meta-data |
fault |
|
Function returns invalid value |
fault |
|
Function gets not executed |
fault |
|
Function returns no value |
fault |
|
Dynamic functions return wrong meta-data |
fault |
|
Function returns wrong calculated values |
fault |
|
Exported needs.json file is corrupted |
fault |
|
Exporting needs.json fails silently |
fault |
|
Exported needs.json file is not valid |
fault |
|
Bulk modification failes silently |
fault |
|
Bulk modification of needs is not completed |
fault |
|
Bulk modification of needs is not valid |
fault |
|
ID already exists |
fault |
|
ID format is invalid |
fault |
|
ID generation failed |
fault |
|
ID length is invalid |
fault |
|
Importing needs is not accessible |
fault |
|
Importing needs is not completed |
fault |
|
Importing needs is not valid |
fault |
|
Invalid link type used in a need |
fault |
|
Link target value violates link schema |
fault |
|
Invalid field used in a need |
fault |
|
Field value does not match declared schema |
fault |
|
Invalid status used in a need |
fault |
|
Traceability objects content corrupted |
fault |
|
Traceability objects meta-data corrupted |
fault |
|
Corrupted external needs.json file |
fault |
|
Invalid or incorrect filters used for external needs.json |
fault |
|
Exported link conditions differ from runtime evaluation |
fault |
|
Link conditions missing in needs.json |
fault |
|
Traceability objects links corrupted |
fault |
|
Objects missing in needs.json |
fault |
|
Missing external needs.json file |
fault |
|
Meta-data missing |
fault |
|
Wrong meta-data is used |
fault |
|
Layout leads to incorrect information |
fault |
|
Layout leads to incorrect rendering |
fault |
|
Layout leads to missing information |
fault |
|
Condition evaluates to the wrong result |
fault |
|
Condition hides a safety-relevant link |
fault |
|
Condition opt-in missing |
fault |
|
Condition expression parse error |
fault |
|
Link target not found |
fault |
|
Link target is not valid |
fault |
|
External needs corrupted |
fault |
|
Links missing |
fault |
|
Back-links are not set |
fault |
|
External needs not found |
fault |
|
Internal target link is not found |
fault |
|
Manual ID already exists |
fault |
|
Manual ID format is invalid |
fault |
|
Manual ID length is invalid |
fault |
|
Sphinx-Needs data not valid |
fault |
|
Sphinx-Needs data is not process-compliant |
fault |
|
Field value is not allowed |
fault |
|
Permalink generation fails silently |
fault |
|
Permalink links to non-existing need |
fault |
|
Permalink is not valid |
fault |
|
Permalink links to wrong need |
fault |
|
Schema validation silently disabled |
fault |
|
Schema definition itself is invalid |
fault |
|
Network validation misses indirect links |
fault |
|
Schema violation not surfaced in build |
fault |
|
Schema ``select`` does not match the intended needs |
fault |
|
Schema violation wrongly suppressed via severity |
fault |
|
Authentication issues with needsservice |
fault |
|
External service unreachable by needsservice |
fault |
|
needsservice unable to process data from external service |
fault |
|
Syntax errors in rst/md files cause Traceability objects to be ignored |
fault |
|
Template file is not a valid Jinja2 template |
fault |
|
Template file not found |
fault |
|
Template file contains syntax errors |
fault |
|
Template file is not a valid Jinja2 template |
fault |
|
Template file not found |
fault |
|
Template file contains syntax errors |
fault |
|
Enum constraint not enforced |
fault |
|
Range constraint not enforced |
fault |
|
Schema type mismatch not detected |
fault |
|
Link cardinality not enforced |
fault |
|
Typed link accepts wrong target type |
fault |
|
Display Traceability objects content in Sphinx-Needs |
feature |
|
Generate object representation in Sphinx-Needs |
feature |
|
Apply dynamic functions for meta-data computation |
feature |
|
Export needs.json file using Sphinx-Needs |
feature |
|
Link conditions exported to needs.json |
feature |
|
Establish links between Traceability objects in Sphinx-Needs |
feature |
|
Conditional link evaluation (NeedLink, parse_conditions) |
feature |
|
Read Traceability objects in Sphinx-Needs |
feature |
|
Declarative schema validation of needs |
feature |
|
Assign meta-data to Traceability objects in Sphinx-Needs |
feature |
|
Enhance Need content using templates in Sphinx-Needs |
feature |
|
Extend page content with templates in Sphinx-Needs |
feature |
|
Typed need fields with JSON-Schema validation |
feature |
|
Typed link schemas (cardinality and targeting) |
feature |
|
Automatic ID generation |
feature |
|
Configuration via conf.py or an external TOML file |
feature |
|
Customizable layouts for need presentation |
feature |
|
Customizable link types |
feature |
|
Customizable need fields |
feature |
|
Definable need types |
feature |
|
Create a bar chart based on need statistics (needbar) |
feature |
|
Modify existing needs in bulk (needextend) |
feature |
|
Render a PlantUML flow diagram of needs (needflow) |
feature |
|
Import needs from an external JSON file (needimport) |
feature |
|
Create a pie chart based on need statistics (needpie) |
feature |
|
Display needs in a filterable table (needtable) |
feature |
|
Legacy constraint checking (needs_constraints) |
feature |
|
JSON builder to export all need data |
feature |
|
Permalink generation to specific need objects |
feature |
|
Bidirectional link tracking |
feature |
|
Dead link detection and warnings |
feature |
|
Direct linking between needs using IDs |
feature |
|
Manual ID assignment |
feature |
|
In-content need parts for granular references |
feature |
|
Need status enforcement |
feature |
|
Tagging support |
feature |
|
Unique ID enforcement and checks |
feature |
|
Clean full build |
restriction |
|
Export link conditions in needs.json |
restriction |
|
Declare cardinality on safety-relevant link types |
restriction |
|
Use severity "violation" for safety-relevant schema rules |
restriction |
|
Type every extra field via needs.fields schema |
restriction |
|
Use declarative schema validation instead of needs_constraints |
restriction |
|
Warning to Error |
restriction |
|
Sphinx-Needs |
tool |
✅ Compliance statistics
Features without faults: 9 / 37
Faults without a mitigation: 75 / 91
Restrictions without fault: 1 / 8
Checks without fault: 0 / 0