2 ms·
LDRA: It's been a bit since I touched it. Checking their site, we were using LDRA Testbed, our use was for DO-178B certification. I specifically was using it to
by Jtsummers 10y ago
LDRA: It's been a bit since I touched it. Checking their site, we were using LDRA Testbed, our use was for DO-178B certification. I specifically was using it to develop test cases. What my memory is telling me is that we were using it to test pre and post conditions, a lot like you'd use in design by contract, on functional units of our system. I was a tester, not a developer, I didn't use its static analysis tools as much and so I don't recall much more.
DOORS: Honestly, at this point I don't care who makes it as long as it works. What's needed, and what DOORS at the time provided, is:
Concurrent editing.
Traceability from one document to another.
Workflow control - I can make changes, but someone else has to
verify/validate. Same as with any issue tracker.
Revision control
Everything but the workflow control I can do with a simple markup language, git, and a few scripts. But in industry it seems people prefer Word documents and Excel spreadsheets.
SPARK 2014: I will, if I ever have downtime. I leave for the office at 7, go to the gym until 8, then spend the evening with friends or my girlfriend. Weekends are my only downtime these days and I'm finding myself lacking motivation to do this. I need a project to work on, trying that now.
We don't have control of the protocol as there are others making products that interact with ours (in theory, in practice it's hit-or-miss as some are more faithful to the spec than others).
One of the things, as an example, that I want to discover by go over the protocol specification are cases like this:
I can't recall the specifics, but there was a mathematically impossible requirement. It was related to the discrete logarithm. Only some of the values involved weren't relatively prime wrt the modulus. So what happened, no one implemented that part of the specification. No one tested it either because there wasn't a good traceability matrix revealing that it was untested. One day, someone realized this, implemented a test to see if this part of the spec was being done, and hey, the test failed.
This reveals major flaws in the process. 1) That specification feature should never have made it into the final. 2) The test should have been made or in-progress once that spec feature was introduced, which would've led to (1) being true.
Speaking of gym, it's time for me to go. Thanks for the pointer with Ironsides. I'll take a look at it and SPARK 2014 over the next few weeks. We're about to wrap up my current project (well, in 3-4 more months) so now's a good time to start putting together a demo to try and save the next project from some of the current issues.