Search results
Results from the WOW.Com Content Network
The flexible nature of DO-178C's processes and entry/exit criteria make it difficult to implement the first time, because these aspects are abstract and there is no "base set" of activities from which to work. The intention of DO-178C was not to be prescriptive. There are many possible and acceptable ways for a real project to define these aspects.
The Advisory Circular AC 20-115( ), Airborne Software Development Assurance Using EUROCAE ED-12( ) and RTCA DO-178( ) (previously Airborne Software Assurance), recognizes [1] the RTCA published standard DO-178 as defining a suitable means for demonstrating compliance for the use of software within aircraft systems.
Many of RTCA documents begin with the letters DO which stands for DOcument. RTCA develops Minimum Operating Performance Standards for aviation-based technology (typically avionics) but has developed standards for such far-ranging topics as Airport Security, Counter UAS Detection standards, and Aircraft Cockpit and Cabin Cleaning standards.
Software was still considered to be assessed and controlled by other means; that is, by RTCA/DO-178A or later revision, via Advisory Circular AC 20-115A. [ 19 ] In 2002, work was done on Revision B, but it was not formally released; the result is the Rulemaking Advisory Committee-recommended revision B- Arsenal Draft (2002).
Various standards suggest different levels, e.g. Software Levels A-E in DO-178C, [4] SIL (Safety Integrity Level) 1-4 in IEC 61508, [1] ASIL (Automotive Safety Integrity Level) A-D in ISO 26262. [2] The assignment is typically done in the context of an overarching system, where the worst case consequences of software failures are investigated.
The search engine that helps you find exactly what you're looking for. Find the most relevant information, video, images, and answers from all across the Web.
CAST-15, Merging High-Level and Low-Level Requirements is a Certification Authorities Software Team (CAST) Position Paper. It is an FAA publication that "does not constitute official policy or guidance from any of the authorities", but is provided to applicants for software and hardware certification for educational and informational purposes only.
Some advisory circulars are only a few pages long and do little more than reference a recommended standard; for example, AC 20-152 referencing DO-254. [8] Others, like AC 20-115 C/D, are considerably longer; in this case including guidance on how to transition from DO-178 revision B to C [ 9 ] while AC 20-152A adds several new objectives to an ...