You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
do you plan to add to sphinx-needs new features which could support safety analysis such as FMEA or FTA in docs as code approach?
Maybe we can create the list of the failure modes for every software component similarly as requirements and then we can have a similar fuctionality such as needflow to visualise?
In case of FMEA, we create the componentes, then assign functions to this components, and create failure modes for each function, but curently we cannot visualize the dependencies between them in the form of Fauilure Nets or Function Nets.
It would be very powerful tool when we can manage complete safety development lifecycle in a single text based tool.
The text was updated successfully, but these errors were encountered:
Hey,
I'm not familiar with the terms FMEA/FTA, but I guess we and other have already done it by performing an ISO 26262 toolchain classification and qualification for a docs-as-code toolchain (containing Sphinx, Sphinx-Needs and other extensions).
Unfortunately, the documentation is not Open-Source, but at least I could release a demo-project, how to do it.
Hi,
do you plan to add to sphinx-needs new features which could support safety analysis such as FMEA or FTA in docs as code approach?
Maybe we can create the list of the failure modes for every software component similarly as requirements and then we can have a similar fuctionality such as needflow to visualise?
In case of FMEA, we create the componentes, then assign functions to this components, and create failure modes for each function, but curently we cannot visualize the dependencies between them in the form of Fauilure Nets or Function Nets.
It would be very powerful tool when we can manage complete safety development lifecycle in a single text based tool.
The text was updated successfully, but these errors were encountered: