Length: 2 Days
DO-278 Training
DO-278 is the Software Integrity Assurance Considerations for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems: (FAA) Software and Hardware Integrity Assurance Standard.
DO-278 is often referred to as the “Software Integrity Assurance” standard.
Sector analysts generally feel that DO-278 is a very strong guideline with its mix of assessable objectives and recommendations.
DO-278 provides guidelines for the assurance of software contained in non-airborne CNS/ATM systems and provides recommendations for the production of that software commensurate with a level of confidence in safety.
DO-278 provides guidelines for the production of software for ground based avionics systems and equipment that performs its intended function with a level of confidence in safety. The guidelines are in the form of:
- Objectives of software life cycle processes
- Description of activities and design considerations for achieving these objectives
- Description of the evidence that indicate that the objectives have been satisfied
DO-278A is the second version of the baseline DO-278 document. It’s a corollary to DO-178C, which is a similar standard for airborne software safety, e.g., software that typically executes onboard aircraft which contributes to flight safety.
DO-278A defines a set of objectives recommended to establish assurance that the developed CNS/ATM software has the integrity needed for use in a safety-related application.
Today, DO-278A is a standalone document. Although it describes many activities, processes, and objectives that are in common with DO-178C, it is no longer necessary to use them side-by-side.
The Assurance Levels in DO-278A are labeled AL1 through AL6 and they are slightly different from those in DO-178C where they are labeled A through E. DO-278A has specific objectives based upon the assurance level (AL) of the software.
Higher AL’s must satisfy more DO-278A objectives than lower levels. After the software criticality level has been determined, you examine DO-278A to determine exactly which objectives must be satisfied for the software.
Planning comes next followed by a Development Process. A concurrent Correctness Process is ongoing throughout both Planning and Development.
Sector analysts recommend applying DO-278A along with ARP4754A and ARP4761.
DO-278 Training Course by Tonex
DO-278 Training, RTCA DO-278 / EUROCAE ED-109 training covers the Guidelines for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems Software Integrity Assurance”. Learn about DO-278 which is a key complement to the DO-178B/DO-178C airborne standard. RTCA DO-278 training course provides a framework to learn about guidelines for the assurance of software contained in non-airborne CNS/ATM systems. DO-278 training teaches the attendees requirements for the software development process, the base set of required documentation and life cycle artifacts.
DO-178B/DO-178C//ED-12, Software Considerations in Airborne Systems and Equipment Certification, provides a set of objectives and guidelines used as assurance for the airborne software.
DO-278 training covers all you need for the application of DO-178B/DO-178C guidance to non-airborne CNS/ATM systems.
Learn about:
- DO-278 guidelines for the production of software for ground based avionics systems and equipment for a level of confidence in safety. The guidelines are in the form of:
- Objectives of software life cycle processes applied to airborne and activities
- Certification for ground based software part of avionics systems to be used in CNS or ATM equipment.
- DO-278 Approval
- Administrative process
- Software system within its operational environment including all of its non-IT (information technology) parts at the FAA
- Target of Evaluation (TOE)
- Operational Environment (OE)
- DO-278 Approval
- Safety assessment
- Proper Assurance Level (AL) needed for approval
- Assurance Level 1 (AL1)
- Assurance Level 2 (AL2)
- Assurance Level 3 (AL3)
- Assurance Level 4 (AL4)
- Assurance Level 5 (AL5)
- Assurance Level 6 (AL6)
- Transitioning to RTCA DO-178C/DO-278A
Course Topics
Software Levels and Coverage
- Flight-Critical Data Integrity Assurance for Ground-Based COTS Components
- DO-278 Approval Process
- Certification and Accreditation
- Software Development Model
- Internal Processes
- Design and Engineering
- Testing
- Verification and Validation
Certification of Safety-Critical Software Under DO-178C and DO-278A
- RTCA DO-278A3: Software Integrity Assurance Considerations for Communication, Navigation,
- Surveillance and Air Traffic Management (CNS/ATM) Systems
- RTCA DO-248C4: Supporting Information for DO-178C and DO-278A
- RTCA DO-3305: Software Tool Qualification Considerations
- RTCA DO-3316: Model-Based Development and Verification Supplement to DO-178C and DO-278A
- RTCA DO-3327: Object-Oriented Technology and Related Techniques Supplement to DO-178C and
- DO-278A
- RTCA DO-3338: Formal Methods Supplement to DO-178C and DO-278A
The Software Levels in DO-278/ED-109
- Transitioning to RTCA DO-178C/DO-278A
- Assurance Levels (AL): AL1, AL2, AL3, AL4, AL5, and AL6
- Software Failure Analysis and Modes
- Failure of the Ground-based System
- Catastrophic Failure Condition
- Hazardous or Severe Failure Condition
- Major Failure Condition
- DO-278 Process and Documentation Requirements
- Guidelines and Plan for Software Aspects of Approval (PSAA)
- Guidelines to Create Software Quality Assurance Plan
- Guidelines to Create Software Configuration Management Plan
- Guidelines to Create Configuration Control Procedures
- Guidelines to Create Software Code Standard
- Guidelines to Create Software Design Standard
- Guidelines to Create Software Requirements Standard
- Guidelines to Create Software Development Plan
- Guidelines to Create Software Verification Plan
- Guidelines to Create Source, Executable Object Code, SCI and SECI
- Guidelines to Create Software Design Document
- Guidelines to Create Software Requirements Document
- Guidelines to Create Software Development Plan
- Guidelines to Create Software Verification Plan
- Guidelines to Create Traceability Requirements
- Guidelines to Create Test Cases and Procedures
- Guidelines to Analyze Verification Results
- Guidelines to Create Quality Assurance Records
- Guidelines to Use Configuration Management Records
- Guidelines to Monitor Problem Reports
- Guidelines to Create Software Accomplishments Summary
DO-278 Training