2005 National Software and Complex Electronic Hardware Standardization Conference
Abstracts
Wednesday
Thursday
FAA Software, CEH Activities, and Research - The 5-Year Plan Barbara Lingberg
This presentation provides an overview of the Aircraft Certification Software and Complex Electronic Hardware Program Management Plan for fiscal years FY06 – FY10. Also, included is an overview of the Software and Digital Systems (SDSS) Research, Engineering, and Development (RE&D) Program.
Overview of NASA's Certification-Relevant Research....................... Kelly Hayhurst
Proposals abound for exciting new technologies that will solve existing aviation problems and facilitate our transition into a modern National Airspace System (NAS). Keeping pace with these new technologies, especially advances in automation, poses considerable challenges for certification practices. This presentation will cover NASA’s certification-relevant research, focusing on current planning efforts aimed at identifying research challenges for certification to allow safe and efficient integration of highly automated systems into the NAS.
DO-254 Policy and Guidance Status and Overview John Lewis
This presentation will provide a status of the schedule and the plan for development of the FAA’s policy and guidance for Complex Electronic Hardware (CEH) using RTCA/DO-254, “Design Assurance Guidance for Airborne Electronic Hardware” as well as provide an overview of the FAA’s strategy to address CEH. It will also provide some information on the FAA’s Advisory Circular (AC) 20-152 and draft policy memo for RTCA/DO-254.
DER Delegation for DO-254 Ken Filippelli
This presentation will discuss how DERs can be authorized to approve data related to Complex Electronic Hardware.
DER Special Delegation for CEH and SW TSO Tom Phan
This topic explains criteria for DER in obtaining special delegations in the areas of Complex Hardware and TSO software.
Draft IMA AC John Lewis
This presentation will provide a status of the schedule and the plan for development of the FAA’s Advisory Circular for Integrated Modular Avionics (IMA).
Draft Databus AC John Lewis
This presentation will provide a status of the schedule and the plan for development of the FAA’s Advisory Circular for aviation databuses.
Database Process AC and Order Brad Miller
This presentation is about the advisory circular (AC) 20-153, which provides guidance material on how to evaluate whether data processes comply with the requirements of RTCA/DO-200A. This AC provides guidance for organizations within the aeronautical data chain to follow in order to obtain a Letter of Acceptance (LOA) from the FAA that acknowledges their compliance regarding aeronautical data processing.
DER Considerations from a Legal Perspective Jason Dickstein
Mr. Dickstein’s presentation addresses a number of business issues that face DERs, including scope of civil liability for DER work, techniques for mitigating liability, and a discussion of business entity and tax structure for consultant DERs.
Role of a Software DER Tom Roth
Tom will be talking about all the various perspectives that apply to the many different ways that software DERs need to consider when they perform their tasks. The roles have been outlined in Supplement 2 to the Software Job Aid, but these roles are performed by the perspectives of the individual DER. For example is the company DER the supervisor of the work being reviewed or is he/she from an independent organization within the company. Also, who employed the services of the consultant DER. These different perspectives have the potential to affect the resultant approvals if these perspectives are not properly addressed and considered.
Wednesday Research Activities and Results
HUMS and COTS Verification....................... Yann-Hang Lee
With powerful information management and communication tools, flight data and maintenance records can be easily collected, analyzed, and disseminated for use by a HUMS (Health and Usage Monitoring System) application. This presents an opportunity for cost and efficiency optimization. The opportunity can be realized only when the integrity of the collected flight critical data can be assured.
Processing systems in such HUMS applications are likely to use Commercial-Off-The-Shelf (COTS) components for maintaining critical data. In our project DTFA03-01-C-00047, titled “Flight Critical Data Integrity Assurance for Ground Based COTS Components”, certain objectives were evaluated for ground based COTS components to assure flight critical data integrity. However, due to the nature of COTS components, it is not always possible to meet the required objectives. In case these objectives are not met by the COTS components using a normal system design process, mitigating actions can be considered to increase the reliability, trustworthiness and failsafe properties of the HUMS systems. As defined in HUMS AC29-2, a mitigating action may be viewed as an autonomous and continuing compensating factor that may modify the level of qualification associated with certification of a HUMS application.
This talk will focus in the investigation results on a variety of issues that arise from the use of COTS components in HUMS systems and the approaches needed to ensure the integrity of the data. We will first show a “big picture” view at the use of COTS in HUMS systems, the advantages and challenges posed by the use of COTS components. Then, the issues in applying the current available guidance relating to COTS and ground-based systems will be discussed.
Semiconductor Wearout....................... Lloyd Condra & Gary Horan
Aerospace electronic systems designers must use state-of-the-art commercial-off-the-shelf (COTS) microcircuits to meet performance goals of future systems. A major barrier to this is continuing, profound changes in the global electronics supply chain. This report describes some of those changes, reports results of aerospace industry work to understand and respond to them, and outlines some proposed solutions that will enable us to design future systems that are more capable, affordable, and supportable.
Changes in the electronic supply chain are both (1) structural, i.e., the way products are designed, marketed, produced, and supported, and (2) technological; i.e., new capabilities and limitations in performance, reliability, and supportability. They present both challenges and opportunities for aerospace system design.
The aerospace industry has responded in a variety of ways, e.g., part level approaches such as Diminishing Manufacturing Sources (DMS) initiatives; and system design and architecture approaches such as modular design and open architecture. A complicating factor is the dynamic nature of the problem itself as the electronics supply chain continues to change. In this paper we describe the nature of the problem, resulting from cooperative efforts with aerospace and semiconductor manufacturers, DoD, FAA, universities, and industry consortia. We then outline solutions at the part; assembly, and system levels to mitigate, but not entirely solve, the supply chain challenges.
Development Tools....................... Andrew Kornecki
Software development tools have the potential to reduce software development costs and improve the quality of the software development process. If properly designed and used, software tools can eliminate or reduce the human errors that are introduced in software design and code. The objectives of this research has been to document current status of development tool qualification, identify development tool suites on the market, help in developing/modifying guidelines for assessing software tools for use by FAA and applicants, and determine types of data for reuse in tool qualification.
A number of software tool manufacturers claim their tool will meet DO-178B criteria. However, there is no clear assessment criteria established that both the FAA and industry could use as reference. The purpose of this research has been to assess the safety, quality, economic, efficiency benefits, and advantages/disadvantages of software tool suites used to develop aviation software.
Component Integration....................... Jim Krodel & George Romanski
This study investigates aspects of integrating components, including real-time operating systems (RTOS) software in aviation Integrated Modular Avionics (IMA) systems. Because of the complexity and perhaps unknown integrity of some off-the-shelf components, there are a number of concerns regarding their use in aircraft systems as they may potentially affect aircraft safety. Previous FAA sponsored research in this area identified that COTS RTOSs are a potential focus area for COTS in aviation software applications. This follow-on work provides an in-depth study into the considerations of integrating components in IMA aviation systems and provides a research paper and handbook to assist in understanding some of the concerns. This report specifically studies the integration issues of developing IMA systems, with a particular focus on the roles, activities, tools and development concerns.
Structural Coverage Challenges....................... John Chilenski
This will be a brainstorming session to discuss structural coverage challenges and collect issues requiring further "attention" from the FAA/NASA.
Verification Tools....................... Vdot Santhanam
The FAA and NASA/Langley sponsored Boeing to commission a study of the qualification criteria applicable to tools that automate aspects of software verification per DO-178B, especially as they pertain to structural coverage. This presentation will summarize the findings of that study and the recommendations it makes to bring uniformity among the tools in regards to the interpretation of DO-178B requirements and to the process of qualifying automated coverage verification tools.
Ethernet....................... Yann-Hang Lee, Elliott Rachlin, & Philip Scandura
Ethernet has been seen as potentially attractive in avionics systems, due to its high bandwidth, low wire counts, and low cost. It has been used in the Boeing 777 to transmit non-flight-critical data, and in the Boeing 767ER within a flight-critical display system, and is now chosen as the communication mechanism among safety-critical flight instruments in Airbus 380 and Boeing 787. However, there are many safety concerns when Ethernet is applied to flight-critical systems where deterministic operations are required.
In this talk, safety and certification issues of Ethernet-based aviation databuses are summarized. Topics to be discussed include: emergence of Ethernet as a possible next generation aviation databus technology, and the solutions to help facilitate deterministic operations, the certification criteria for Ethernet-based aviation databuses, and the FAA position paper CAST-16 “Databus Evaluation Criteria”. Also discussed is the development of the Handbook for Ethernet databus design and certification considerations. The Handbook gives design requirements for the use of Ethernet-based networks in the avionics environment, and identifies the relevant issues and concerns regarding the determinism of the system and the certification considerations. Its objective is to facilitate the process by which an Ethernet-based databus may be certified as part of an overall aircraft certification process.
The material to be presented is part of the work done for the research project titled “Safety and Certification Approaches for Ethernet-based Aviation Databuses”, began in October 2001 and completed December 2004. This project was carried out jointly by Arizona State University, Tempe, AZ, and Honeywell Laboratories, Phoenix, AZ, and was funded by the Federal Aviation Administration (FAA).
Why You Should Read Accident Reports....................... Michael Holloway
Very few people except accident investigators and lawyers read accident reports. This is a shame. Engineers in particular can benefit greatly from careful reading of relevant accident reports. Three important benefits include (1) improved ability to separate myths from reality, (2) increased understanding of the consequences of unlikely events, and (3) greater recognition of the importance of refusing to compromise on system safety.
Wednesday FAA Policy & Guidance
Reuse - Order 8110.49 and AC 20-148....................... John Lewis
This presentation will provide an overview of the FAA’s policy and guidance on software reuse based on Order 8110.49, Software Approval Guidelines, and Advisory Circular 20-148, Reusable Software Components.
Tool Qualification....................... Varun Khanna
This presentation provides an overview of Chapter 9 of Software Order 8110.49. It clarifies the guidance in DO-178B on Software Tool Qualification, provides guidelines to DERs and ACO engineers, and identifies the differences between development and verification tools.
Software in Legacy Systems....................... Jorge Castillo
The purpose of this presentation is to provide an overview on the application of the guidance found in FAA Order 8110.49, Chapter 10 regarding the approval of software changes in Legacy systems.
Level D Previously Developed Software....................... Jorge Castillo
The purpose of this presentation is to provide an overview on the application of the guidance found in FAA Order 8110.49, Chapter 8 regarding the application of RTCA/DO-178B Level D criteria to Previously Developed Software such as COTS.
Software Review Process & Level of FAA Involvement....................... Brenda Ocker
This presentation summarizes the software review process. Four types of software reviews are identified and correlated to the software life cycle processes. The procedures for preparing for a software review, conducting a software review, and documenting the results are discussed. The procedure for determining the Level of FAA Involvement (LOFI) in the software review process is also discussed.
OO Verification Research Results....................... John Chienski
Boeing is under contract to the FAA to investigate object-oriented technology verification. Results to date for the research into data coupling and control coupling verification in object-oriented software will be presented.
Using the OOTiA Handbook ....................... Jeff Knickerbocker
This presentation provides a quick overview of the OOTiA Handbook and outlines considerations a company might use as they pursue successful approvals of OOTiA based development efforts.
OO Experiences....................... Jeff Knickerbocker & John Chilenski
This presentation provides a compilation of the results obtained from a survey associated with ongoing OOTiA work. The results provide a snap-shop of current practices within industry, some of the frustrations associated with OOTiA work, and what industry is considering in terms of continuing software development using OO techniques.
Elemental Analysis....................... Jeff Maddalon This talk describes a case study of the SPIDER project to apply the advanced verification methods provided in the RTCA document DO-254. The "Elemental Analysis" verification method is the focus of this talk. This talk describes how the various aspects of Elemental Analysis are being applied to the SPIDER project.
Programmable Logic Devices and DO-254 – This is What We Find in This Stuff....................... Richard Katz
This presentation will cover aspects of RTCA/DO-254, "Design Assurance Guidance for Airborne Electronic Hardware." Portions of DO-254 will be covered in detail and discussed and put into context for high-reliability digital design applications with a series of case studies. Examples showing faults and areas of concern will span the range from high-level design to low-level implementation to the tools that are now relied on for design implementation.
Best Practices in CEH Development....................... Terry Leier &Wayne Haug
AC 20-152 now available! The product of approximately 10 years of FAA-Industry consensus efforts, this advisory circular provides guidance for the applicability of DO‑254 in addressing design assurance for complex electronic hardware. This presentation provides a general perspective of one avionics manufacturer’s participation, transition, current state and anticipated future migration in CEH assurance.
DO-254 Tutorial....................... Tom & Uma Ferrell
RTCA DO-254/ED-80 (Design Assurance Guidance for Airborne Electronic Hardware) was released in April 2000 and is designed to fill the gap for developmental assurance for complex electronic hardware including programmable logic devices (PLDs) and application specific integrated circuits (ASICs). Since its release, the document has generated considerable interest in the topic of hardware design assurance and more than a little bit of controversy. This tutorial is intended to provide an overview of DO-254. Note: this material is intended as a high-level introduction and is intended for people new to the subject of complex electronic hardware design assurance.
Reusable Software Component (RSC) Reality Show....................... Mike DeWalt & Varun Khanna
A summary of the salient issues surrounding approval of an RSC, based on actual regulatory and RSC developer projects. The presentation covers a project from the viewpoint of the regulator and from the viewpoint of the RSC developer. Some tools are provided to simplify collection of data for submittal and approval.
COTS Integrated Circuits....................... Peter Skaves
The purpose of COTS Integrated Circuits Legends & Myths presentation is to provide an overview of the avionics design assurance process and considerations for the use of these devices in airplane applications. Presentation topics include integrated circuit failure contributions, redundancy and fault handling techniques and the use of Built-In-Test Equipment (BITE) of software.
COTS Graphical Processors....................... Gregg Bartley
COTS Graphical Processors (CGP) were designed for use in graphics-intensive video games. Because of the power and flexibility of these devices, they are starting to be used in airborne avionics display systems. The use of these devices present many certification challenges, as they were not developed to a design assurance process such as RTCA/DO-254 and do not have a reliable service history on which to base certification credit.
Model-Based Development – Coming soon to a Theatre Near You....................... Mike DeWalt
Model-Based Development (MBD) has recently appeared in a number of certification projects. This presentation deals with approval of MBD under DO-178B and with use of typical MBD tools in the current environment.
Conformity/TIA Experiences....................... Jeff Knickerbocker
This presentation provides an overview of challenges associated with “conformity” for FAA tests (FAA tests are tests requiring FAA approval – e.g., qual test, HIRF & Lightning, flight test and so on) that are part of a type certification (TC) process. Recent examples and regulatory guidance material are utilized to provide consideration on how a company might successfully comply with “conformity” requirements associated with software in a TC program.
Data and Control Coupling....................... Will Struck
This presentation provides definitions, references and an overview of past subject-related activities, presentations and documents, including DO-178B, DO-248B, CAST Position Paper P-19, and the Reno Software Conference “brainstorming” session. It discusses some challenges for the adequacy of completion criteria for the integration and verification of the integrated system (requirements-based testing, normal range and robustness, data coupling analysis (DCA) and control coupling analysis), and proposes some questions relative to the impact on DCA/CCA of integrated modular avionics (IMA) systems, distributed systems, object oriented technology (OOT) and model-based development (MBD). The guidance of DO-178B was developed from a single LRU perspective. Should the guidance and criteria needed for flight-critical applications be more prescriptive depending on the proposed system architecture?
Introduction to the Military Certification Office....................... Ruth Hirt
This presentation will be a brief introduction to FAA Military Certification Office and its scope of operations.
Leaning Military Aviation Software Acquisitions....................... Joan L. Stredler & Rohit P. Sheth
As the trend goes toward “leaning” our way of doing business, the opportunity arises for the United States Military to redefine their aviation software acquisition practices. This presentation will explore the paradigms that separate the current military aviation software acquisition practices and commercial aviation software acquisition practices. These paradigms will be expressed in terms of issues of responsibility, accountability and authority. The Military’s hierarchal approach with many layers of oversight responsibility adds cost that is not inherent in the FAA’s delegated authority approach. The attitude toward the definition and procurement philosophy relative to Commercial-off-the-shelf also creates a big disparity between methods. The military ‘s approach in this instance creates a quality risk. Several other more subtle differences will be noted and discussed.
For those Military programs that have already moved toward the FAA’s approach, some immediate benefits have been derived. The first relates to the adoption of the DO-178B Gap analysis process. The second involves the developing of a project plan as distinct from, and in addition to, an overall corporate level Software Development Plan. And third, the adoption of the FAA’s Change Impact Analysis process has gained huge acceptance by the supplier community as a well recognized value-added process.
This presentation will propose some changes that could significantly reduce cost (and potentially schedule) and/or improve quality and with safety as a prime concern. In the software arena the Military’s desire to move to commercialization has meant that the FAA standard DO-178B has been put on contract for many new programs. This standard is very beneficial in that it was distributed once and has 10 years of history, training and clarification behind it. These factors were never true of Military Software standards. If the true advantage of these differences is to be realized then the Military should consider using the subject matter experts that the FAA has trained to be the determiners of compliance.
Military Certification: A Practitioner’s View....................... Peggy Wright
The use of FAA standards in the certification of military aircraft is becoming increasingly more common due to several factors. Contributing to this trend are the need to fly military aircraft in international airspace and the desire to reduce the cost of initial certification and continued airworthiness through the use of common design assurance processes. The impact of software design assurance in aircraft certification is distributed throughout the entire project lifecycle. This presentation first describes the author's views of that impact based on her observations as a Designated Alteration Station Software Authorized Representative (AR) in the military division of Boeing. Positive and negative aspects of FAA impact on the various military project phases are identified and conclusions made as to the areas of greatest concern.
Formal Methods: What’s in it for Me?....................... Darren Cofer
The growing complexity and the safety-critical requirements of the embedded software in avionics systems present many challenges to current test-based verification technology. The use of formal verification methods can increase design assurance and reduce development and testing costs by finding design errors early in the development cycle. This talk summarizes our work modeling two avionics software components in an effort to analytically establish correctness of important aspects of their designs. Our findings support the use of formal methods to verify key properties of safety-critical systems that would be difficult or impossible to establish otherwise.
Certification of Adaptive Flight Control Software....................... Michael Richard
NASA is sponsoring a research study at Boeing to investigate various aspects of Intelligent Flight Control Systems (IFCS) using a modified F-15 test platform. A part of that study is devoted to understanding the challenges of getting adaptive software certified under civil airworthiness certification guidelines such as DO-178B. That study focuses on two primary aspects of compliance with DO-178B: (a) compliance with requirements for life cycle processes and artifacts as they relate to adaptive software, and (b) compliance with software verification criteria, such as MC/DC coverage, as they apply to the software that implements adaptive algorithms. This session will present Boeing's preliminary findings relative to these two aspects.
The Software Safety Dartboard....................... Elisabeth Strunk & William Greenwell
Avionics software currently exhibits very low failure rates, but in many cases, software safety assurance is not as rigorously engineered as one would desire. It is more like a dartboard, where many skilled and careful people are throwing the darts to achieve current safety levels. We present several points in the software life cycle where current engineering research can assist developers in achieving their safety and assurance goals--hitting the target for which they aim.
What’s Eating Your Lunch? Industry Feedback on Research Needs....................... John Knight & Kelly Hayhurst
Even though numerous advances have been made in software engineering, dramatic growth in the pervasiveness and complexity of software continues to present significant challenges, especially for safety-critical systems. To help plan an effective and beneficial research program, we would like to hear about problems currently encountered or expected in the development, verification, and certification of aviation applications. This session will solicit input directly from the FAA and industry on what should be done to help the aviation software industry achieve the ability to routinely and cost-effectively develop and deploy dependably safe software systems. This session will also solicit input on developing more effective ways for researchers in government, industry and academia to interact.
Thursday FAA Policy & Guidance FAA Policy & Guidance
Change Impact Analysis....................... Brenda Ocker
This presentation summarizes the Software Change Impact Analysis (CIA) procedure. The focus of the CIA is to determine the impact of the change on the system and assure that safety is not adversely affected. The items that should be addressed in a CIA are identified, and the process for performing a CIA is discussed.
Compliance 101....................... Gerald Pilj
Software certification is not the business of following DO-178B, but the business of following federal law; DO-178B has been accepted as a way to accomplish that. This presentation is a back to basics look at how to comply with the law and how that general concept gets applied to software, using DO-178B. The presentation will provide an understanding of:
Regulations and the legal system,
Determining what a specific regulation really means,
Responsibilities of the FAA and the applicant,
How to know you have shown compliance.
The presentation will conclude with a discussion of “the ideal certification program”.
IMA Trends and Challenges....................... Eric Retko
The presentation outlines some of the enabling technologies that are moving IMA forward, and some of the real world issues encountered in developing and certifying IMA systems, and provides insight and a forum for an open discussion on what is needed from industry and the certification authorities to support future IMA advancements.
ARINC 653 and DER Interests....................... George Romanski
ARINC 653 provides a programming model for software to be run in a partitioned system. A short description of the programming model will be provided. A more detailed description of the challenges of certifying an application using an ARINC 653 platform will follow.
The presentation will cover how to take credit for "target" based objectives, when the target is virtual. It will also discuss how to separate out the configuration responsibilities, and the integration problems, especially when ARINC 653 based systems support many hosted functions from different companies.
The current state of the specification will be summarized together with the planned updates.
Industry Perspective on IMA....................... Norm Ovens
This presentation is an industry perspective of an active Avionics systems engineer over a 5-year period. It discusses the system design process and the strong influences that have shaped system implementations, such as; customer/market requirements, certification, product line. The presentation concludes with the author’s perspective regarding potential benefits of RTCA SC-200 and the current certification plans made for active Rockwell Collins projects.
Differences/Similarities in DO-178B Compliance in an IMA System vs. Federated Product ... Marty Gasiorowski
DO-178B was generated before the advent of Integrated Modular Avionics systems. As a result, there are aspects of IMA that are not addressed well by DO-178B. On the other hand, there are aspects of DO-178B compliance for IMA systems that are unchanged from traditional federated systems. This presentation will discuss the differences and similarities, and clear up some common misconceptions about IMA systems.
Model-Based Development....................... Steve Miller
Informal requirements stated in a natural language often suffer from ambiguity, inconsistency, and incompleteness. For these reasons, the trend over the last decade has been towards alternate approaches for specifying requirements such as use cases and requirement modeling languages. However, the growing popularity of model-based development and the increasing power of formal verification tools make yet another approach possible. In this approach, informal shall statements are rewritten as formal properties over a model and shown to hold on that model. Informal shall statements can thus be viewed as a first step in capturing requirements as system properties. This presentation discusses how this is being explored at Rockwell Collins under NASA Langley's Aviation Safety & Security Program.
Engineering Ethics............. Tom & Uma Ferrell
DERs are not supposed to interpret rules and regulations, but rather they are to find compliance with the rules. However, design assurance for software and complex electronic hardware always requires some amount of engineering judgment. This talk explores some of the instances where such judgments require ethical decision-making. The talk suggests that, now more than ever, DERs should be driven by a code of ethics.
Non-covered Code....................... Steve Ward
The Non-covered Code presentation looks at practical issues involved in resolving Structural Coverage Analysis (SCA) findings. The presentation reviews DO-178B SCA resolution definitions and discusses what DERs need to be concerned about in assuring developers are in compliance with them. Additionally, concerns about dead and deactivated code issues are discussed and practical approaches on DER review to assure needed analyses have been completed.
Non-TSO Function in Policy Carol Martineau
Currently, Paragraph 17d(3) of Order 8150.1B allows the incorporation of a non-TSO function in a TSO article, but stipulates that the safety and performance of its intended function be evaluated under the appropriate airworthiness certification procedures during installation. However, the design data that defines the non-TSO function, nevertheless, is still contained in the design data package that is granted TSO authorization. In addition, the installer generally does not have the equipment or expertise available to the TSO manufacturer to accomplish a thorough equipment performance evaluation, especially when the performance must be determined by laboratory simulation or under stressed conditions. The guidance in notice 8150.NTF brings greater scrutiny to integrated non-TSO functions by providing guidance to the ACO for the consistent article-level evaluation of a non-TSO function at the time of TSO authorization.
RTCA/SC-200....................... Cary Spitzer
This briefing will provide the status of RTCA SC-200 and its work, in cooperation with EUROCAE WG-60, on the preparation of the document "Integrated Modular Avionics (IMA) Design Guidelines and Certification Considerations" to be published this fall. It will provide guidance similar to that found in DO-178 and DO-254. The document is in final preparation and the last plenary meeting of SC-200/WG-60 is scheduled for the end of August.
RTCA/SC-205....................... Jim Krodel
RTCA, Inc. has tasked Special Committee SC205 to consider revising DO-178B due to technology changes since its publication in 1992. Specifically the committee will modify DO-178B/ED-12B, DO-248B/ED-94B, consolidate software development guidance and guidelines and develop supplements to document technology-specific or method-specific guidance and guidelines. This presentation will review the committee’s activities and approach to modifying DO-178B and related documents.
Home - NASA Office of Logic Design
Last Revised:
July 29, 2005
Web Grunt:
Richard Katz
