The USMC changed the definition of “Troops in Contact“, a critical feature of the Software Safety design for the TLDHS. Removing all the places this data was referenced throughout the software would take many 100s of man-hours. It could also comprise the software, and thus would require extensive testing.
NSWC Crane needed a Software Safety Analysis on a detonation device and a subsequent presentation to both the Navy’s System Software Safety Technical Review Panel (SSSTRP) and the equivalent Army Safety board.
We were tasked to provide Safety Support for the Marine Corps GBOSS project. The Logistics team was required to insure that our product had a Mean-Time-Between-Failure (MTBF) below a certain threshold. They used statistics to show that we would need to conduct 1000s of hours of testing. Since this was a complex and expensive system, this approach was going to require extending the schedule and adding $100,000s to the project cost.
One of our clients asked for a 30-minute e-Learning course, which they needed done right away and would have cost on the order of $50,000 to develop. Instead of just saying “Yes, sir – we can do that!” we took the time to explore the “Why’s” of the project.
We were invited to help develop a new Technical Information Report (TIR) for the Association for the Advancement of Medical Instrumentation (AAMI), a standards organization. This report, TIR 32:2004, discussed Medical Device Software Risk Management.
We directed a medical device manufacturer away from low-impact software testing activities to those with a high return on their efforts.
Although not in our original scope, we decided to take a detailed look at the Real-Time Operating System (RTOS) they were depending on. We discovered many potential issues with the RTOS, and steered them to a safer utilization.
Previous project experience includes project management, design, development, testing, and/or analysis of software. The following table lists many of the projects we’ve had an impact on … read more