DO-178C Part 5 - Configuration Management and Quality Assurance

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. 

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. 

1. Keeping Everything Versioned and Controlled
IBM ELM provides a shared environment where all lifecycle data is stored and tracked. Teams can:
● Keep full version history for requirements, design, code, and tests
● Capture baselines at important milestones
● Compare changes between versions
● See exactly who made changes and why
This makes it much easier to understand how the system evolves over time.  

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 affected artifacts
● Require approvals before anything is applied
● Keep a complete record of what happened
This keeps changes visible, justified, and properly managed. 

3. Keeping Baselines Consistent Across the Project
IBM ELM makes it possible to align baselines across different artifact types, so everything stays in sync.
● Requirements, design, code, and tests can be captured together
● Each baseline reflects a stable system snapshot
● Previous states can be revisited when needed
This is especially important when demonstrating compliance at key milestones.

1. Keeping Oversight Independent
DO-178C requires QA to stay independent from development.
IBM ELM supports this by:
● Defining roles and responsibilities clearly
● Enforcing approvals from the right people
● Separating development and QA activities in workflows
This helps ensure QA decisions aren’t influenced by development pressure.  

2. Keeping an Eye on Process Compliance
QA teams need visibility into how things are progressing.
IBM ELM provides dashboards and reports that help them:
● Follow lifecycle progress
● Spot missing approvals or incomplete work
● Check if processes are being followed
● Review traceability coverage
This makes it easier to catch issues early rather than at the end. 

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 automatically
● Keeping records of changes, approvals, and reviews
● Generating reports when needed
Instead of scrambling for evidence later, teams build it as they go.

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 supports structured reviews for:
● Requirements
● Design
● Code
● Test artifacts
Teams can:
● Assign reviewers
● Track feedback
● Record approvals
● Keep a history of decisions
This keeps the review process clear and consistent.

2. Keeping Evidence of Reviews
All review activity is recorded within the system, including:
● Comments and feedback
● Approval decisions
● Changes made after reviews
● Resolution of issues
This creates solid evidence that verification has been carried out properly.

3. Connecting Reviews to the Rest of the Lifecycle
Reviews don’t sit on their own — they feed back into the project.
IBM ELM links review outcomes to:
● Requirement updates
● Design changes
● Code updates
● Test adjustments
This ensures feedback is actually applied and tracked. 

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. 

Softacus supports aerospace teams in setting up IBM ELM so configuration management, QA, and reviews work smoothly together.
This typically includes:
● Setting up configuration and baseline management
● Designing workflows for change control and approvals
● Linking all lifecycle artifacts for full traceability
● Supporting QA activities and audit preparation
● Providing guidance so teams use the tools effectively
With the right setup, teams can stay organized, maintain control, and approach certification with confidence.

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.