1. Contents
Introduction
History of DO-178B
Features of DO-178B
Drawbacks of DO-178B
DO-178C
Conclusion
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

2. Introduction
Avonics Software . . . . . .
Avionics software is embedded software with legally mandated
safety and reliability concerns used in avionics.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

3. Introduction
Avonics Software . . . . . .
Avionics software is embedded software with legally mandated
safety and reliability concerns used in avionics.
To assure safety and reliability some representative standards
like MIL-STD-2167 for military systems,RCTA DO-178B for
civil aircraft are introduced.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

4. History of DO-178B
It was realized that the usual approach to seek the safety and
reliability will not work for Safety critical systems.
There was a great need for finding design errors which came
out in the form of first DO- 178 certification document.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

5. History of DO-178B
DO-178
The software applications were divided into three categories:
critical, essential, and nonessential.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

6. History of DO-178B
DO-178
The software applications were divided into three categories:
critical, essential, and nonessential.
DO-178 also established the relationship between the software
certification process and the other relevant Federal Aviation
Regulations.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

7. History of DO-178B
DO-178A
Software development processes were described in a more
systematic and structured manner.
The verification process included distinctions in effort required
by software level.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

8. History of DO-178B
DO-178B
The purpose was to provide detailed guidelines for the production
of software for airborne systems. The goals were the following:
Develop objectives for the life cycle processes.
Provide a description of the activities and design
considerations for achieving those objectives
Provide a description of the evidence indicating the objectives
have been satisfied.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

9. Features of DO-178B
The Table shows the software level per failure condition and the
amount of DO-178B objectives associated to each.
SW Failure Description Objec- With
Level Condition tives Indep
A Catastropic Conditions which would prevent 66 25
continued safe flight and landing.
B Hazardous Software that could cause or contribute 65 14
to the failure of the system resulting in
a hazardous or severe failure condition
C Major Conditions which would significantly 57 2
reduce aircraft safety, crew ability to
work under adverse operation.
D Minor Conditions which would not significantly 28 2
reduce aircraft safety, slight increase in
crew workload.
E No Effect Conditions which do not affect the 0 0
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

10. Features of DO-178B
The important sections of DO-178B document :
Software Planning Process
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

11. Features of DO-178B
The important sections of DO-178B document :
Software Planning Process
Software Development Process
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

12. Features of DO-178B
The important sections of DO-178B document :
Software Planning Process
Software Development Process
Software Verification Process
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

13. Features of DO-178B
The important sections of DO-178B document :
Software Planning Process
Software Development Process
Software Verification Process
Software Configuration Management
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

14. Features of DO-178B
Software Planning Process
Plan for Software Aspects of Certification.
Software Development Plan.
Software Verification Plan.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

15. Software Development Process
Software requirements,software design,software coding and
integration.
Adherence to a set of software coding standards.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

16. Software Verification Process
To detect and report errors.
Reviews, Analyses and Development of test cases.
Structural Coverage Analysis.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

17. Software Configuration Management
Task of tracking and controlling the changes in the software.
How problem reports are dealt with?
How the development process are recorded?
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

18. Drawbacks of DO-178B
No clarification of the definitions and boundaries between the
key concepts of High Level Requirements, Low Level
Requirements and Derived Requirements.
It does not consider new development methodologies like
MBT.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

19. DO-178C
Provides clearer language and terminology.
Provides more consistency.
Use of formal methods.
Use of Object Oriented Programming.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards

20. Conclusion
The DO-178B solely focuses on design assurance where the
required assurance is defined on the basis of the criticality.
DO-178C which is partially approved,clarified most of the
unclear topics of DO-178B and includes few latest
technologies.
Formal methods are addressed to complement testing but not
to replace.
Kuladeep-COE11B026 Sushma-COE11B010 Avionics Software Standards