fuzzed
fuzzed copied to clipboard
troeger
The Open Reliability Editor (ORE) for dependability modeling and analysis.
Fuzzed doesn't seem to restrict the Name string for elements (e.g., events, fault trees, fuzz trees). There's also unique numeric ID per element, which seems to follow ``namespaceID.elementID`` format. This...
The Python code documentation seems to follow the JsDoc style. It is better to follow Sphinx-compatible default or Google style for the Python code. This will as well help linters...
The mixed fronted and backend code in the project is a pain point, both for the build and the Ansible parts. The backend (daemon) parts should become a separate GitHub...
The idea is to deduct an initial version of the graph. Examples are the OCCI Infrastructure data model (JSON serialization) or the DMTF Cloud Infrastructure Management Interface (CIMI) Model. Our...
http://www.lix.polytechnique.fr/~rauzy/xfta/XFTA-Manual.pdf First analysis by @laena: My impression is that it aims at being much more (too?) generic than we do. From the four layers, the Fuzztrees formats covers only the...
SCRAM provides a ready-to-go analysis engine with a matching license: https://github.com/rakhimov/scram It should be integrated as additional, or even replacement, analysis backend for standard fault tree models and RBDs.
Tastypie is currently fixed to an ancient pre-release, so that our custom *patch_detail* implementation in the frontend API still works. We should either adjust our Tastypie code so that it...
Currently, our project is marked as JavaScript project, because of the large amount of third party code in this language. Since GitHub intentionally does not support repo-specific exclusion lists, we...
