Rules for Writing Safety Critical Code (2006)

Re:Rules for Writing Safety Critical Code (2006) by ti32x on Friday November 04, 2016 @07:20AM (#12871706)

I have heard that Polarion is an ok requirements management tool for software, but it is expensive.

DOORS is good for tracking and tracing requirements, but from what I can see doesn't do code parsing. This may have changed. However, my opinion of IBM software is irreparably broken so I don't have a huge amount of trust in it.

We use Reqtify to glue requirement documents to code. It also sucks, but I think it's still powerful. You just need to set up some regexes which can recognize your requirement identifier style and you're good to go.

Whoever comes up with a solution to glue DOORS requirements to Jira issues to code seamlessly is going to be fairly rich.

[ Parent | on HN ]

Re:Rules for Writing Safety Critical Code (2006) by rubidium on Friday November 04, 2016 @10:15AM (#12872689)

I've done a bit a research on this. Company uses DOORS and hates it. We've evaluated JAMA and Polarion (both expensive) and both are better than DOORS. JAMA has a nice JIRA integration. Polarion can be integrated it seems but untested.

[ Parent | on HN ]