Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Avionics software
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Embedded software with legally mandated safety and reliability concerns}} {{multiple issues| {{more citations needed|date=August 2021}} {{original research|date=May 2021}} {{cleanup rewrite|date=May 2021}} }} '''Avionics software''' is [[embedded system|embedded software]] with legally mandated [[aviation safety|safety]] and [[Reliability engineering|reliability]] concerns used in [[avionics]]. The main difference between avionic software and conventional embedded software is that the [[software development model|development process]] is ''required by law'' and is ''optimized for safety.'' It is claimed that the [[Software development process|process]] described below is only slightly slower and more costly (perhaps 15 percent) than the normal ''ad hoc'' processes used for commercial [[Computer software|software]]. Since most software fails because of mistakes, eliminating the mistakes at the earliest possible step is also a relatively inexpensive and reliable way to produce software. In some projects however, mistakes in the specifications may not be detected until deployment. At that point, they can be very expensive to fix. The basic idea of any software development model is that each step of the design process has outputs called "deliverables."<ref>{{Cite web |title=Software models |url=https://www.cs.uct.ac.za/mit_notes/software/htmls/ch02s04.html |access-date=2024-01-28 |website=www.cs.uct.ac.za}}</ref> If the deliverables are tested for correctness and fixed, then normal human mistakes can not easily grow into dangerous or expensive problems. Most manufacturers<ref>{{Cite web |title=What is the Waterfall Model? - Definition and Guide |url=https://www.techtarget.com/searchsoftwarequality/definition/waterfall-model |access-date=2023-12-01 |website=Software Quality |language=en}}</ref> follow the [[waterfall model]] to coordinate the design product,<ref>{{Cite web |title=Software models |url=https://www.cs.uct.ac.za/mit_notes/software/htmls/ch02s04.html |access-date=2024-01-28 |website=www.cs.uct.ac.za}}</ref> but almost all explicitly permit earlier work to be revised. The result is more often closer to a [[spiral model]]. For an overview of embedded software see [[embedded system]] and [[software development model]]s. The rest of this article assumes familiarity with that information, and discusses differences between commercial embedded systems and commercial development models.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)