DO-178C Part 4 - Software Verification with IBM ELM

In the DO-178C lifecycle, verification is one of those stages that really carries a lot of weight — and it’s often where things get tough. Development is about building the software, but verification is where you actually check that everything works the way it’s supposed to and lines up with the requirements.

But verification under DO-178C goes beyond traditional testing. It’s not just about finding bugs — it’s about proving, with clear and objective evidence, that the software behaves correctly and that every requirement has been fully addressed. This includes reviews, analysis, testing, and for higher criticality levels, structural coverage.

Keeping track of everything manually is a nightmare. IBM ELM makes it way easier to stay on top of it all. By bringing requirements, tests, defects, and results together in one connected environment, it helps teams handle verification in a structured and manageable way.

This article shows how IBM ELM helps teams handle DO-178C software verification and keeps them on top of certification requirements. 

The purpose of verification in DO-178C is simple: make sure the software actually works and does what it’s supposed to. That involves checking that:
● Requirements are accurate, complete, and consistent
● The design properly reflects those requirements
● The code correctly implements the design
● The software behaves as expected during testing
● All verification work is documented and can be reviewed  

To achieve this, teams carry out a range of activities, including:
● Reviewing requirements
● Reviewing design
● Reviewing code
● Creating test cases
● Running tests
● Analyzing results
● Performing structural coverage analysis (for higher DAL levels) 

A key concept in DO-178C is independence. For higher criticality software, verification must be performed by someone other than the original developer to ensure objectivity.
To demonstrate compliance, teams also need to provide:
● Requirements-based test coverage
● Clear links between requirements, tests, and results
● Documented review records
● Evidence of defects and how they were resolved
● Coverage analysis results (such as statement, decision, or MC/DC coverage)
Trying to manage all of this without the right tools — keeping things connected and documented — can easily become one of the hardest parts of a certification project.

1. Requirements-Based Testing with Engineering Test Management (ETM)
DO-178C requires that all testing is driven by requirements. IBM Engineering Test Management helps teams put this into practice by allowing them to:
● Create test plans aligned with verification strategies
● Define test cases directly linked to requirements
● Organize test steps and execution procedures
● Track test progress and results in real time
Each test case is tied back to the requirement it verifies, making it easier to demonstrate full coverage — a key DO-178C expectation.  

2. Connecting Verification Artifacts Across the Lifecycle
Clear connections between artifacts are essential for proving compliance. IBM ELM makes it possible to link:
● Requirements to test cases
● Test cases to execution results
● Defects to failed tests
● Code changes to resolved issues
This keeps everything connected from start to finish — requirements are verified, issues don’t get lost, and fixes are all documented.
Built-in views and reports make it easy to spot missing coverage or gaps early, long before an audit. 

3. Managing Reviews and Verification
Evidence Verification isn’t just about testing — reviews and analysis play a big role too.
IBM ELM supports this by enabling:
● Organized review steps for requirements, design, and code
● Electronic approvals and sign-offs
● Comment tracking and resolution
● Full audit trails of verification activities
This ensures all verification work is properly recorded, controlled, and easy to access when needed.

4. Defect Tracking and Resolution with EWM
Handling defects is a core part of verification.
With IBM Engineering Workflow Management, teams can:
● Log defects directly from failed tests
● Track progress from detection to resolution
● Link defects to requirements, code, and test results
● Maintain a clear history of how issues were handled
This makes sure every issue is documented, addressed, and visible — exactly what DO-178C expects.  

5. Supporting Structural Coverage Analysis
For higher criticality levels (DAL A–C), DO-178C requires structural coverage analysis, including:
● Statement coverage
● Decision coverage
● Modified Condition/Decision Coverage (MC/DC)
While the actual coverage tools are usually external, IBM ELM helps bring everything together by:
● Linking coverage results to requirements and tests
● Tracking coverage status
● Highlighting areas where additional testing is needed
This ensures coverage data becomes part of the overall verification picture, not something separate. 

6. Planning and Monitoring Verification
Verification isn’t a one-time activity — it needs to be planned and continuously monitored.
IBM ELM supports this by:
● Managing verification plans alongside development artifacts
● Providing dashboards to track progress and coverage
● Monitoring overall verification completeness
● Generating reports that make audits and reviews much easier
It shows teams how things are progressing in real time and helps prevent any last-minute stress.

Obstacle 1 — Missing or Incomplete Test Coverage
It’s easy to overlook some requirements or not test them fully.

How IBM ELM helps:
Traceability links and coverage reports ensure every requirement is accounted for, so nothing is overlooked.  

Obstacle 2 — Disconnected Verification Data
Test cases, results, and defect reports often end up scattered across different tools.

How ELM helps:
By keeping everything connected in one environment, teams get better visibility, consistency, and control. 

Obstacle 3 — Stressful Audit Preparation
Getting ready for audits can be time-consuming and nerve-wracking.

How ELM helps: Verification evidence is captured continuously, so audit prep becomes much smoother and far less stressful. 

Obstacle 4 — Maintaining Independence
Keeping development and verification roles properly separate can be tricky.

How ELM helps: Role-based workflows enforce separation and approvals, making independence easy to manage.

Softacus helps aerospace teams use IBM ELM to keep DO-178C verification flowing alongside regular development, instead of leaving it as a separate task you have to scramble through.
Support from Softacus typically includes:
● Setting up IBM ELM so test cases, executions, and verification data are organized and easy to manage
● Linking requirements, tests, defects, and results so nothing gets lost and every step is traceable
● Designing workflows that make reviews and approvals straightforward while keeping development and verification roles properly separated
● Integrating coverage analysis so it aligns with DO-178C objectives
● Automating reports and evidence generation for audits and certification reviews
● Providing training and ongoing guidance to keep teams coordinated and audit-ready
With the right setup and guidance, verification becomes a continuous, transparent process. Teams stay in control, reduce surprises, and can confidently show compliance whenever it’s needed.

Software verification under DO-178C is strict, detailed, and essential for certification. It ensures that software is not only built correctly but proven to meet all requirements.

IBM ELM brings everything together for verification in one organized environment — linking requirements, tests, defects, and results. By making traceability automatic, capturing evidence without extra effort, and supporting smooth verification workflows, it helps teams reduce risk, work more efficiently, and approach certification with confidence.

In the next article, we will explore configuration management and quality assurance, and how IBM ELM supports control, consistency, and compliance across the software lifecycle.