-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doorstep and ISO 26262 / EN 61508 #509
Comments
We are using doorstop in this context. It's usefull to maintain traceability. But it's necessary to know the limitations of the tool. One of the limitations that I miss the most is: |
Maybe Doorstop will develop in the direction of easy and simple usability, without bothering too much about the peculiar needs of FUSA concerned env, while the similar StrictDoc will evolve more into a FUSA tool? As far as I can see, StrictDoc solves exactly these limitations you mention here |
In the past I had to use several tools w.r.t. requirement engineering. One pain point overlooked quite often is interoperability with other tools. Usually requirements of a single compontent need to get into the context of some bigger system. This means the tool you use has to support at least the export of requirements in commonly agreed on requirement interoperability standards which will differ dependent on the domain I guess. @stefanoco Thanks for letting us know about StrictDoc. |
I do have a proposal for solving the "multi-parent" problem. I'm coming from a medical device software development environment and have similar requirements as mentioned above. We are using Caliber for most of the requirements and the idea is derived from how we define traces there. It depends on what exactly you need to achieve, but please read on and comment on the proposal Context:
If the assumptions are above are valid, then a possible implementation sketch can look like this
The implementation should be quite easy. we would need a hard-coded or flexible way to configure attributes on document level (maybe a new feature like |
example implementation is now avail according to the feature description above |
@stefanoco I've implemented a suggestion in pr #569 , maybe you you review the proposal to see whether this would fit your needs. |
Sure @ckolumbus I'm doing now thanks! |
In addition to these more technical issues, a concern we are having in adopting Doorstop is the implementation of the ReqIF interchange format, the standard interchange used by Doors and others. In our case, we need a ReqIF output or adapter to plug into our MBSE tool, Capella. Has the use of ReqIF for an export format been investigated? Are there non-obvious technical challenges, or could we make a prototype and send it in as a pull request? |
Also relates to #309
I'm willing to start a discussion about using doorstop in the context of Functional Safety concerned developments according to mentioned norms. Any experience about this?
The text was updated successfully, but these errors were encountered: