As you move further along the DO-178C lifecycle, three areas start to carry more weight: configuration management, quality assurance, and reviewing outputs.

Building and testing the software is only one part of the process. Keeping everything controlled, consistent, and aligned with standards is what really keeps the project together — and makes it possible to show it meets DO-178C.

Without this level of control, even well-developed software can run into problems during certification — not because it doesn’t work, but because something is missing, inconsistent, or not properly documented.

IBM Engineering Lifecycle Management (ELM) helps address this by keeping configuration control, quality oversight, and review activities connected within a single environment instead of spread across disconnected tools.

Table of Contents

Understanding Configuration Management and Quality Assurance in DO-178C

DO-178C expects all lifecycle data to be handled in a controlled and traceable way. That means it needs to be:
● Clearly identified and versioned
● Protected from unauthorized changes
● Linked across the lifecycle
● Stored in stable baselines
● Ready to be reviewed during audits

Configuration Management helps teams keep all artifacts — requirements, design, code, and tests — tidy, up-to-date, and aligned throughout development

Software Quality Assurance provides an outside perspective, making sure that processes are applied consistently and that compliance is always maintained, no matter what happens in development.

Another key requirement is verifying outputs. Every artifact needs to be reviewed to confirm it’s correct, complete, and aligned with expectations.

Together, these activities ensure the lifecycle isn’t just carried out — it’s controlled, visible, and provable.

How IBM ELM Supports Configuration Management

1. Keeping Everything Versioned and Controlled
IBM ELM provides a shared environment where lifecycle data can be stored, tracked, and controlled. Teams can maintain version history across requirements, design artifacts, code, and tests, capture baselines at important milestones, compare changes between versions, and see who made each change and why.

This makes it much easier to understand how the system evolves over time and to prove that important lifecycle artifacts were controlled throughout development.

2. Handling Changes Without Losing Control
Changes are inevitable — controlling them is what matters. With IBM Engineering Workflow Management (EWM), teams can raise and manage change requests, link each change to the affected artifacts, require approvals before changes are applied, and keep a complete record of what happened.

This keeps changes visible, justified, and properly managed. For DO-178C projects, it also helps show that modifications were not made informally or without review.

3. Keeping Baselines Consistent Across the Project
IBM ELM makes it possible to align baselines across different artifact types so the project remains synchronized. Requirements, design, code, and tests can be captured together as part of a stable system snapshot, and previous states can be revisited when needed.

This is especially important at compliance milestones. Teams need to show not only what the system looks like now, but also which approved versions of requirements, design, code, and tests were valid at a specific point in the certification process.

How IBM ELM Supports Quality Assurance (SQA)

1. Keeping Oversight Independent
DO-178C expects quality assurance to remain independent from development. IBM ELM supports this by making roles and responsibilities clear, enforcing approvals from the right people, and separating development and QA activities within defined workflows.

This helps protect QA decisions from development pressure and gives teams a clearer record of who reviewed, approved, or rejected specific lifecycle activities.

2. Monitoring Process Compliance
QA teams need visibility into how the project is progressing, not just at the end but throughout the lifecycle. IBM ELM provides dashboards and reports that help teams follow lifecycle progress, identify missing approvals or incomplete work, check whether defined processes are being followed, and review traceability coverage.

This makes it easier to catch process gaps early, before they become audit findings or certification risks.

3. Staying Ready for Audits
Audit preparation is often one of the most stressful parts of certification. IBM ELM helps reduce that pressure by capturing lifecycle data as the work happens, including changes, approvals, reviews, and related evidence.

Instead of searching for documentation at the end of the project, teams build audit-ready evidence throughout the lifecycle. This makes certification preparation more predictable and gives QA teams stronger confidence in the evidence they present.

Verifying Outputs Through Reviews

Reviews are a core part of DO-178C verification. Every artifact needs to be checked to confirm it is correct, complete, and consistent.

1. Keeping Reviews Organized

IBM ELM helps teams manage structured reviews for requirements, design, code, and test artifacts. Reviewers can be assigned directly in the system, feedback can be tracked, approvals can be recorded, and decisions can remain visible over time.

This keeps the review process clear, consistent, and easier to manage across teams.

2. Keeping Evidence of Reviews
All review activity can be recorded within IBM ELM, including comments, feedback, approval decisions, changes made after review, and the resolution of identified issues.

This creates stronger evidence that verification activities were performed in a controlled way. For DO-178C projects, that evidence is important because teams need to show not only that reviews happened, but also what was reviewed, who approved it, what changed, and how issues were resolved.

3. Connecting Reviews to the Rest of the Lifecycle
Reviews should not sit outside the engineering process. In IBM ELM, review outcomes can be linked to requirement updates, design changes, code updates, and test adjustments.

This ensures that feedback is not only captured, but also applied and tracked through the lifecycle. It gives teams a clearer view of how review decisions affected the project and helps keep verification evidence connected for audits and certification reviews.

Common Obstacles — and How ELM Helps

Obstacle 1 — Uncontrolled Changes
Changes happen without proper tracking or approval.

How ELM helps:
Workflows make sure every change is recorded, reviewed, and approved.

Obstacle 2 — Misaligned Baselines
Different artifacts don’t match the same system state.

How ELM helps:
Baseline management keeps everything aligned and consistent.

Obstacle 3 — Missing Review
Records Review activities aren’t properly documented.

How ELM helps:
Review workflows capture and store all verification evidence.

Obstacle 4 — Audit Pressure
Preparing for audits becomes stressful and time-consuming.

How ELM helps:
Data is captured continuously, making audits much easier to handle.

How Softacus Can Help

Softacus supports aerospace teams in configuring IBM ELM so configuration management, quality assurance, and reviews work together as part of one controlled DO-178C lifecycle process.

This can include setting up configuration and baseline management, designing workflows for change control and approvals, connecting lifecycle artifacts for traceability, supporting QA activities, and preparing teams for audits and certification reviews. Softacus can also provide guidance and training so teams use IBM ELM consistently in their daily work.

With the right setup, teams can stay organized, maintain stronger process control, and approach DO-178C certification activities with greater confidence.

Conclusion

Configuration management, QA, and output verification make sure the software isn’t just working—they make sure it’s properly tracked, consistent, and compliant with all DO-178C rules.

IBM ELM brings everything under one roof, making it easier to control changes, ensure quality, and monitor verification tasks.

By keeping everything connected and visible, it helps teams reduce risk, stay efficient, and be ready for certification when it matters most.