Price: $2,499.00

Length: 3 Days
Print Friendly, PDF & Email

DO-178C Training

As early as 1980 there were considerations in aerospace on how to develop software safely and as accurately as possible. These considerations led to the development of the DO-178C standard in 2012 that is widely respected far beyond software.

The standard defines the software planning, development, verification, quality assurance and configuration management process.

DO-178C was preceded by Document 178B (DO-178B). The update became necessary after concerns developed over the meaning of verification in a model-based development paradigm and considerations for replacing some or all software testing activities with model simulation or formal methods.

Additionally, there had been insistence by FAA designated engineering representatives for better clarification of the definitions and boundaries between the key DO-178B concepts of high-level requirements, low-level requirements and derived requirements. There was also a call for a better definition of the exit/entry criteria between systems requirements and system design as well as that of software requirements and software design.

Today, DO-178C helps to make flying safer.

DO-178C classifies safety in five levels. Each level corresponds to the consequence if the software fails.

  • Level A: Catastrophic
  • Level B: Hazardous
  • Level C: Major
  • Level D: Minor
  • Level E: No Safety Effect

These software safety levels are designated based on risk. And the higher the risk, the more safety objectives need to be met.

DO-178C defines objectives for 10 software life cycle processes, activities that can satisfy those objectives, and descriptions of the evidence required to show that the objectives have been satisfied. Meeting different objectives requires varying levels of effort, as some are harder than others. DO-178C defines objectives for several different processes

While DO-178C is crucial for airborne vehicle safety, all told, it is a complicated and difficult document to satisfy, which is why top shelf training is extremely important.

DO-178C is also costly, more so if not completed correctly the first go around.

For example, DO-178C defines 22 documentation datasets that plan, direct, explain, define, record, or provide evidence of activities. About 85% of the time, a significant portion of the required documentation is reverse engineered from the code, especially when existing nonairborne code is integrated into an airborne application.

As specialists analyze the code, they often find issues that need to be addressed and then interact with the developers to change it. When this happens, parts of the software life cycle process must be repeated. Finding defects earlier in the software development life cycle saves money in terms of hours expended to mitigate the defect.

Static analysis also reduces both budget and schedule risk.

DO-178C Training Course by Tonex

DO-178C Training, by Tonex covers all aspects of Software Considerations in Airborne Systems and Equipment Certification. This is the primary standard for commercial avionics software development supported by FAA and EASA, ED-12C. DO-178C  Training  provides insight to this recommendations for the production of airborne systems and equipment software.

Upon attending DO-178C  Training, the attendees are able to understand the compliance aspects of the DO-178C and comprehend the objectives of DO-178C as the primary means for meeting airworthiness requirements to obtain approval of software used in civil aviation products.

DO-178C training

This 3-day DO-178C training will introduce industry best practices for real-world commercial avionics software development and how to avoid common DO-178C mistakes. DO-178C training courses helps you to minimize any risks and costs related to DO-178C. Our highly qualified instructors will discuss many other related topics such as SAE standards ARP-4761 for Safety and ARP-4754A for Systems Development, safety, systems, systems engineering, software planning, software requirements analysis, and software design, coding, testing including verification, validation and risk-based testing.

Additionally, DO-178C training will introduce tools that focus on the additional activities required due to the changes made in going from DO-178B to DO-178C.

Learning Objectives

Upon attending DO-178C training, the attendees will be able to:

  • Understand basics concepts behind DO-178C
  • Examine software planning and development standards
  • List objectives of DO-178C
  • Compare DO-178C with DO-178B
  • List software requirements, design, code, and testing for avionics
  • Identify basic configuration management and quality assurance
  • Mitigate common DO-178C risks and mistakes
  • Apply industry-best practices
  • List objectives of DO-330 Software Tool Qualification Considerations
  • List objectives of DO-331 Model-Based Development and Verification Supplement to DO-178C and DO-278
  • List objectives of DO-332 Object-Oriented Technology and Related Techniques Supplement to DO-178C and DO-278A
  • List objectives of DO-333 Formal Methods Supplement to DO-178C and DO 278A

Who Should Attend

DO-178C training is designed for Avionics Project and Program Managers, Software Engineers, Testing Professional who need to understand the requirements, objectives and practices of using DO-178C in software development.

Course Agenda

Introduction Do-178C

  • DO-178B vs. DO-178C
  • DO-178Certification Process
  • DO-178C Project Planning and Management
  • DO-178C Master Plan
  • DO-178C Need Analysis and Requirements
  • Software Life Cycle Processes
  • Software Life Cycle Definition
  • Transition Criteria Between Processes
  • Software Development Plan
  • Software Life Cycle Environment Planning
  • Software Development Standards
  • Review of the Software Planning Process Software Considerations in System Life Cycle Processes

System Considerations in Software Life Cycle Processes

  • Software Plan Development and Certification
  • Software Development, Design, Coding and Testing Techniques
  • DO-178C Criticality levels
  • Software Design, Testing, Verification and Validation Processes
  • Software Planning Process Objectives
  • Software Planning Process Activities
  • Software Plans
  • Plan for Software Aspects of Certification (PSAC)
  • Software Quality Assurance Planning (SQAP)
  • Software Configuration Management Planning (SCMP)
  • Software Development Planning (SDP)
  • Requirements, Design, Code, and Integration
  • Software Verification Planning (SVP)
  • Reviews, Tests, and Analysis
  • Programmable hardware plan development and certification
  • Software and programmable hardware verification and validation
  • Recommended Templates and recommendations
  • Hardware Design Life Cycle
  • Tool Qualification
  • Cost Estimation and Metrics
  • Software Aspects of Certification
  • Compliance Determination

Software Development Processes

  • Software Requirements Process
  • Software Design Process
  • Software Coding Process
  • Integration Process
  • Software Development Process Traceability

Software Verification Processes

  • Purpose of Software Verification
  • Overview of Software Verification Process Activities
  • Software Reviews and Analyses
  • Software Testing
  • Requirements-Based Testing Methods
  • Test Coverage Analysis
  • Software Verification Process Traceability
  • Verification of Parameter Data Items

Software Configuration Management (CM) Processes

  • Software Configuration Management Process Objectives
  • Software Configuration Management Process Activities
  • Data Control Categories
  • Software Load Control
  • Software Life Cycle Environment Control

Software Quality Assurance (QA) Processes

  • Software Quality Assurance Process Objectives
  • Software Quality Assurance Process Activities
  • Software Conformity Review

Software Life Cycle Data

  • Plan for Software Aspects of Certification
  • Software Development Plan
  • Software Verification Plan
  • Software Configuration Management Plan
  • Software Quality Assurance Plan
  • Software Requirements Standards
  • Software Design Standards
  • Software Code Standards
  • Software Requirements Data

Additional Considerations

  • Use of Previously Developed Software
  • Alternative Methods
  • Software Reliability Models
  • Product Service History

DO-330 Tool Qualification and DO-331 Modeling

  • DO-330- Tool qualification for DO-178C
  • DO-331 Software Modeling for DO-178C; Model-Based Development and Verification (MD&V)
  • DO-332 Object-Oriented (OO) Technology
  • DO-333 Formal Methods (FM)
  • Object Oriented Technology and DO-178C’s DO-332
  • Formal Methods and DO-178C’s DO-333

Working with Tonex DO-178C Templates

  • Plan for Software Aspects of Certification (PSAC)
  • Plan for Software Aspects of Approval (PSAA)
  • Software Development Plan (SDP)
  • Software Verification Plan (SVP)
  • Software Configuration Management Plan (SCMP)
  • Software Quality Assurance Plan (SQAP)
  • Software Requirements Standards (SRS)
  • Software Design Standards (SDS)
  • Software Code Standards (scs)
  • Software Requirements Document (SRD)
  • Software Design Description (SDD)
  • Software Verification Cases and Procedures (SVCP)
  • Structural Coverage Analysis Results (SCAR)
  • Software Environment Configuration Index (SLECI)
  • Software Configuration Index (SCI)
  • Software Accomplishment Summary (SAS)

New Templates: DO-178C Supplements

  • Tool Qualification Templates (DO-330)
  • Model Based Development Templates (DO-331)
  • OO Technology Templates (DO-332)
  • Formal Methods Templates (DO-333)

DO-178C Training

Request More Information

Please enter contact information followed by your questions, comments and/or request(s):
  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.