BLOG

MY PERSONAL JOURNEY

DO-178B SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEMS AND EQUIPMENT CERTIFICATION PDF

10 déc. Minimum Software Life Cycle Data That Is Submitted tO Certification Authority . 45 .. EUROCAE EDB is identical to RTCA DOB. the production of software for airborne systems and equipment used on aircraft or. Overview. ▫ DOB – Software Considerations in Airborne. Systems and Equipment Certification. ▫ Standard of RTCA Incorporation (in Europe it is ED-. Introduction to DOB – Software Considerations in Airborne Systems and Equipment Certification. 1. Overview of DOB Swamy S M.

Author: Tuzil JoJokus
Country: Peru
Language: English (Spanish)
Genre: Software
Published (Last): 18 March 2005
Pages: 248
PDF File Size: 8.5 Mb
ePub File Size: 19.79 Mb
ISBN: 706-6-70265-742-2
Downloads: 1787
Price: Free* [*Free Regsitration Required]
Uploader: Sajinn

The number of objectives to be satisfied eventually with independence is determined by the software level A-E. This can be difficult the first time a company attempts to develop a civil avionics system under this standard, and has created a niche market for DOB training and consulting.

Processes are intended to support the objectives, according to the software level A through D—Level E was outside the purview of DOB. These software safety tasks and artifacts are integral supporting parts of the process for hazard severity and DAL determination to be documented in system safety assessments SSA. A third party tool can be qualified as a verification tool, but development tools must have been developed following the Do-178h process.

For objectives that must be satisfied with independence, the person verifying the item such as a requirement or source code may not be the person who authored the item and this separation must be clearly documented. Documents maintained by the configuration management process:.

Course outline

Once an activity within a process has been defined, it is generally expected that the project respect that documented activity within its process. Typically used software development process:.

  CATALOG AMORTIZARE MIJLOACE FIXE 2012 PDF

Requirements traceability is concerned with documenting the life of a requirement. Therefore, DOB central theme is design assurance and verification after the prerequisite safety requirements have been established.

Any software that commands, controls, and monitors safety-critical functions should receive the highest DAL – Level A. The interface to the certification authority is also handled by the quality assurance process.

These activities are defined by the project planners as part of the Planning process. Retrieved from ” https: This page was last edited on 4 Decemberat All tools used for DOB development must be part of the certification process. Safety attributes in the design and as implemented as functionality must receive additional mandatory system safety tasks to drive and show objective evidence of meeting explicit safety requirements.

The failure conditions are categorized by their effects on the aircraft, crew, and passengers. Typically IEEE STD Software Safety Plans are allocated and software safety analyses tasks are accomplished in sequential steps requirements analysis, top level design analysis, detailed design analysis, code level analysis, test analysis and change analysis.

It should be possible to trace back to the origin of each requirement and every change made to the requirement should therefore be documented in order to achieve traceability. The FAA applies DOB as the document it uses for guidance to determine if the software will perform reliably in an airborne environment, [1] when specified by the Technical Standard Order TSO for which certification is sought. By using this site, you agree to the Terms of Use and Privacy Policy.

Software can automate, assist or otherwise handle or help in the DOB processes. VDC Research notes that DOB has become “somewhat antiquated” in that it is not adapting well to the needs and preferences of today’s engineers.

  BILLIG LSPLATTA FR PDF

This article needs additional citations for verification. The intention of DOB was not to be prescriptive. Furthermore, processes and their concrete activities must have well defined entry and exit criteria, according to DOB, and a project must show that it is respecting those criteria as it performs the activities in the process.

Analysis of all code and traceability from tests and results to all requirements is typically required depending on software level. June Learn how and when to remove this template message. Tools generating embedded code are qualified as development toolswith the same constraints as the embedded code.

DOC Software Considerations in Airborne Systems and Equipment Certification → Code Coverage

Processes are described as abstract areas of work in DOB, and it is up to the planners of a real project to define and document the specifics of how a process will be carried out.

Tools used to verify the code simulators, test execution tool, coverage tools, reporting tools, etc. Please help improve this article by adding citations to reliable sources. From Wikipedia, the free encyclopedia. It is the software safety analyses that drive the system safety assessments that determine the DAL that drives the appropriate level of rigor in DOB. DOB alone is not intended to guarantee software safety aspects.

The certification authorities require and DOB specifies the correct DAL be established using these comprehensive analyses methods to establish the software level A-E. There are many possible and acceptable ways for a real project to define these aspects.

This process handles problem reports, changes and related activities.