On January 11,, we, the Federal Aviation Administration (FAA), published Advisory Circular (AC) B recognizing RTCA/DOB, Software. FAA Underestimated Complexity of Proving the Integrity Requirement SAE ARP /, RTCA DOB; Consists of Audits/Reviews of. [5] FAA AC B, RTCA DOB – FAA policy which invokes RTCA [6] RTCA DOB/EUROCAE EDB, Software Considerations in Airborne Systems.

Author: Toshura Vugore
Country: Yemen
Language: English (Spanish)
Genre: Science
Published (Last): 8 July 2011
Pages: 453
PDF File Size: 17.16 Mb
ePub File Size: 6.88 Mb
ISBN: 643-8-39575-658-6
Downloads: 27876
Price: Free* [*Free Regsitration Required]
Uploader: Vular

Thanks for creating this blog, this will help all level of avionics engineers. Views Read Edit View history. 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.

Typically used software development process:. These high level requirements include Functional, performance, interface and safety-related requirements. Hi Mahadev, thanks for the feedback. The FAA approved AC C [4] on 19 Julmaking DOC a recognized “acceptable means, but not the only means, for showing compliance with the applicable airworthiness regulations for the software aspects of airborne systems and equipment certification.

The structure of the document remains largely the same from B to C. Thanks for visiting the Website!!!!! The system safety assessments combined with methods such as SAE ARP A determine the after mitigation DAL and may allow reduction of the DOB software level objectives to be satisfied if redundancy, design safety features and other architectural forms of hazard mitigation are taa requirements driven by the safety analyses.

Software Life Cycle process is. Archived from the original on 19 July By using this site, you agree to the Terms of Use and Privacy Policy. It is the software safety raa that drive the system safety assessments that determine co178b DAL that drives the appropriate level of rigor in DOB. We derive these requirements by delving into the details of the user requirement. Guidelines always help to make things in correct direction.


Hi Nagendra, Thanks for visiting the Website!!!!! Hi Sai, Thanks for posting!! 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.

This process performs reviews and audits to show compliance with DOB. Derived Low Level requirements are identified separately.

DO178B Interview Questions

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. Hi Venkat, Thanks for visiting the site!! Derived requirements are lesser than user requirements.

This process handles problem reports, changes and related activities. A derived requirement is something that we infer or derive from a user requirement. The intention of DOB was not to be prescriptive. Software can automate, assist or otherwise handle or help in the DOB processes.

These activities are defined by the project planners as part of the Planning process. Please go through the required information in this website only. Your email address will not be published.

Although technically a guideline, it was a de facto standard for developing avionics software systems until it was replaced in by DOC. This page was last edited on 4 Decemberat Overall, DOC keeps most of the DOB text, which has raised concerns fsa issues with DOB, such as the ambiguity about the concept of low-level requirements, may not be fully resolved.

Furthermore, processes and their concrete activities must have well defined entry and exit criteria, according to DOB, and a do178bb must show that it is respecting those criteria as it performs the activities in the process.

The software level is determined after system safety assessment and the safety impact of software is known. For objectives that must be satisfied with independence, the person verifying the item such as a requirement or faaa code may not be the person who authored the item and this separation must be clearly documented.


DOB Interview Questions | AeroSpace

In the same report, they also note that DOC seems well-poised to address this issue. What are changes are made in DOC? Removal of the errors is an activity of the software development processes.

Thanks for making things in one place. DOB alone is not intended to guarantee software safety aspects. DOC alone is not intended to guarantee software safety aspects. The additional clarification fills a gap that a software developer may encounter when interpreting the document.

Archived from the original on 11 September It really only needs to be retained.

FAA lists DOB as a means of compliance that is acceptable to the regulators of software in fax avionics community. Even the use of the requirement after the implemented features have been deployed and used should be traceable. Please list those type of questions also. In-Flight Entertainment System of any commercial aircraft in service. European Organization for Civil Aviation Equipment. Tools used to verify the code simulators, test execution tool, coverage tools, reporting tools, etc.

Retrieved from ” https: The software faq process uses the outputs of the system life cycle process to develop the software high-level requirements.

A traceability analysis is then used to ensure that each requirement is fulfilled by the source code, that each requirement is tested, that each line of source code has a purpose is connected to a requirementand so forth.