Applying DO-254 objectives referencing DO-178C activities Özgür Babur 1/23 AVIATION ELECTRONICS EUROPE 25.03.2015
Applying DO-254 objectives referencing DO-178C activities
Özgür Babur
1/23
AVIATION ELECTRONICS EUROPE25.03.2015
CONTENT
1. Introduction – Who we are?2. Definitions-Motivatation3. Developing a Certifiable System4. Evidence for Compliance5. Similarities in both SW and HW
2/23
4. Evidence for Compliance5. Similarities in both SW and HW
Systems 6. HW Certification Considerations
INTRODUCTION – WHO WE ARE?
STM A.Ş.
In business since 1991
Consultancy Services
3/23
System Engineering Services
Software Engineering Services
Military/Civil Airworthiness Certification Support Services – Since 2004
CERTIFICATION SUPPORT SERVICES
�A wide range of Airworthiness Certificationconsultancy services for both civil/military aviation authorities and aircraft manufacturers
4/23
STM CERTIFICATION
SUPPORT SERVICES
AUTHORITYAUTHORITY MANUFACTURERSMANUFACTURERS
DEFINITIONS & CONCEPT
RTCA DO-178C/EUROCAE ED-12C :
SOFTWARE Considerations in Airborne Systems and EquipmentCertification, December 2011
Former : DO-178B, December 1992
5/23
RTCA DO-254/EUROCAE ED-80:
Design Assurance Guidance For Airborne Electronic HARDWARE, December 2000
Former : NONE
MOTIVATION
In Turkey we have so many avionics equipment development projects:
Avionics Upgrade Projects(C-130, T-38, F-16)
New Aircrafts
6/23
New Aircrafts
Unmanned Air Vehicles(ANKA, Karayel)
Rotary Wing(T-129 Attack, Basic Utility)
Fixed Wing(Regional Jet, Tx/Fx Trainer-Fighter)
MOTIVATION
Turkish manufacturers now have to show compliance to:
CS/FAR 23, 25, 27, 29
CS E-50, STANAG 4671(UAVs)
7/23
CS E-50, STANAG 4671(UAVs)
RTCA DO-178C& RTCA DO-254
Basic rules for all equipment installations
23/25/27/29.1301-1309
E-50 (d,f)
PURPOSE
Key objectives both listed both in DO-254 & DO-178C
Analogy from the older one(DO-178) for showing compliance to DO-254
Industry’s experience on SW design assurance is more
8/23
Industry’s experience on SW design assurance is more than HW design assurance
Avionics box manufacturers should be agile to HW changes
DEVELOPING A CERTIFIABLE SYSTEM
Should have best fitting company processes – Peer Reviews, Quality/Process Assurance for independent monitoring, Strong Configuration Management
Apply the rules for certification goal from the begining
9/23
Apply the rules for certification goal from the begining and apply to the entire lifecycle
NOT to exceed the COST
NOT to exceed the SCHEDULE
DO-178B/C Software DO-254 Hardware
DESIGN ASSURANCE
ALL LEVELS OF SWOS, BSP, DRIVERS, APPLICATIONS
ALL LEVELS OF HARDWARELRU, CIRCUIT CARD, PLD
VERIFICATION LEVEL A AND LEVEL B LEVEL A AND LEVEL B
SIMILARITIES IN BOTH SW AND HW SYSTEMS
10/23
VERIFICATION INDEPENDENCE
LEVEL A AND LEVEL B SPECIFIC IN TABLES A-1 TO 10
LEVEL A AND LEVEL B
TOOL QUALIFICATION
A FULL SET IS REQUIRED FOR ALL DEVELOPMENT AND VERIFICATION TOOLS
DEFINED IN SECTION 11.4.1 OF DO-154
COVERAGE ANALYSIS
SW CODE STRUCTURAL COVERAGE ANALYSIS(SCA) TABLE A-7
ELEMENENTAL ANALYSIS FOR VHDL CODE - PCBEASA CERT MEMO – FAA REPORTS
SIMILARITIES IN BOTH SW AND HW SYSTEMS
DO-178B/C Software DO-254 Hardware
ON TARGET REQUIREMENTBASED TESTING
ON TARGET HARDWARESIMULATION CREDIT MAY BE TAKEN
MAY BE DIFFICULT IN CIRCUIT TESTING SIMULATION CREDIT MAY BE PROBLEMATIC
11/23
INDEPENDENT MONITORING
QUALITY ASSURANCE IN ALL LEVELS{A, B, C, D}
PROCESS ASSURANCE IN LEVELS{A, B}
TEXT RTCA DO-178C/EUROCAE ED-12CPUBLISHED IN DECEMBER 13, 2011 WORKING GROUP SC-167, WG-12
RTCA DO-254/EUROCAE ED-80 PUBLISHED IN APRIL 19, 2000WORKING GROUP SC-205
COMMON OBJECTIVES IN BOTH BOOK TEXTS
DO-178C # of Objectives for DAL A (TOTAL 71)
Planning => 7
Development => 7
12/23
Verification of Development => 29
Testing => 5
Verification of Testing => 9
CM, QA & Liason => 14
COMMON OBJECTIVES IN BOTH BOOK TEXTS
DO-254 # of Objectives for DAL A (TOTAL 35)
Planning => 4
Design => 17
13/23
Validation and Verification => 7
CM & PA => 6
Advanced Verification => 1
COMMON OBJECTIVES IN BOTH BOOK TEXTS
178C 254 Common
Planning 7 4 4
Design 7 17 7
14/23
V&V 43 8 8
Integral 14 6 6
Result 25
A BASIC COMMON INFRASTUCTURE IF YOU DEVELOP BOTH HW AND SW
You have to have a common;
Templates for Planning Documents
PSAC vs. PHAC
15/23
SVP vs. HVVP
SQAP vs. HPAP etc.(Development Plan, CM Plan)
Requirements Capture Methodology(Inputs to Outputs as a Transfer Function)
A BASIC COMMON INFRASTUCTURE IF YOU DEVELOP BOTH HW AND SW
You have to have a common;
Testing Approach(Partition Based, Pin Level)
Similar Standards for source code and HDL generation
16/23
generation
Source Code and HDL Coverage Analysis Methods
Configuration Management
Quality/Process Assurance Mechanisms
ALTERNATIVE MEANS FOR MODIFIABLE SW SYSTEMS AND OBJECT ORIENTED TECH.
For RTCA DO-178C
Why use OO technology?
To be modifieable
17/23
FOR RTCA DO-254
To be modified cost effectively
Is there such Technology?
Model Based Development
For RTCA DO-178B
CAST Paper #8:
Use of the C++ Programming Language
ALTERNATIVE MEANS FOR MODIFIABLE SW SYSTEMS AND OBJECT ORIENTED TECH.
18/23
For RTCA DO-178C
RTCA DO-332 OO Technology and Related Techniques
For RTCA DO-178C
RTCA DO-331 Model Based Development and Verification Supplement
For RTCA DO-254
MODEL BASED DEVELOPMENT FOR SW AND HDL
19/23
For RTCA DO-254
Modelling Standards to generate Specification/Desing Model should be defined
DO-254 does not fit such a paradigm(Ask DO-331)
Pay attention to have a common evidence infrastructrefor compliance for both HW and SW;
Pay attention on key objectives/activities/outcomes
Planning
CONCLUSIONS
20/23
Planning
Tool Qualification
Peer Reviews
Independent Verification
BUT ALSO REMEMBER...
To distinguish for the technologies specific for the Hardware and the Software....
CONCLUSIONS
21/23
THANKS FOR LISTENING!
�Özgür BABUR – Electronic Hardware Certification Group Leader
� STM(Savunma Teknolojileri Mühendislik ve Ticaret) A.Ş.
22/23
A.Ş.
ANKARA TEKNOLOJİ GELİŞTİRME BÖLGESİ,
BİLKENT CYBERPARK, E BLOK 5.CADDE NO: 6/A
06800, ANKARA, TURKIYE
t : 0 312 266 35 50 f : 0 312 266 35 51
www.stm.com.tr
© STM 2015
23/23
Bu doküman ve içerdiği tüm bilgiler STM AŞ’nin fikri mülkiyetidir. Bu
dokümanın dağıtımı veya sunumu ile bu haklar ortadan kalkmış olmaz.
STM AŞ’nin yazılı izni olmadan bu dokümanın ve içerdiği bilgilerin üçüncü
kişilere aktarımı, çoğaltımı ve dağıtımı yapılamaz. Bu doküman ve içeriği
hazırlanma amacının dışında kullanılamaz.
© STM 2015All Rights Reserved
This document and all information contained herein is the sole property
of STM AŞ. No intellectual property rights are granted by the delivery of
this document or disclosure of its content. This document shall not be
reproduced or disclosed to a third party without the express written
consent of STM AŞ. This document and its content shall not be used for
any other purpose other than for which it is supplied.