View in EDS

When Computers Fly, It Has to Be Right: Using SPARK for Flight Control of Small Unmanned Aerial Vehicles.

Saved in:
Bibliographic Details
Title: When Computers Fly, It Has to Be Right: Using SPARK for Flight Control of Small Unmanned Aerial Vehicles.
Authors: Sward, Ricky E.1 ricky.sward@wavmax.com, Gerken, Mark1 mark.gerken@usafa.af.mil, Casey, Dan1 daniel.casey@ramstein.af.mil
Source: CrossTalk: The Journal of Defense Software Engineering. Sep2006, Vol. 19 Issue 9, p10-14. 5p. 3 Diagrams.
Subjects: SPARK (Computer program language), Computer software, Computer systems, Computer industry, Software failures, System failures
Geographic Terms: United States
Abstract: One approach to software assurance is to use an annotated language such as SPARK. For safety critical software programs such as Unmanned Aerial Vehicle flight control software, the risk of software failure demands high assurance that the software will perform its intended function. Using an example from work being done at the U.S. Air Force Academy, this article describes SPARK and the formal process of proving correctness of software implementations. [ABSTRACT FROM AUTHOR]
Copyright of CrossTalk: The Journal of Defense Software Engineering is the property of USAF Software Technology Support Center and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Database: Engineering Source
FullText Text:
  Availability: 0
Header DbId: egs
DbLabel: Engineering Source
An: 22957402
AccessLevel: 6
PubType: Periodical
PubTypeId: serialPeriodical
PreciseRelevancyScore: 0
IllustrationInfo
Items – Name: Title
  Label: Title
  Group: Ti
  Data: When Computers Fly, It Has to Be Right: Using SPARK for Flight Control of Small Unmanned Aerial Vehicles.
– Name: Author
  Label: Authors
  Group: Au
  Data: <searchLink fieldCode="AR" term="%22Sward%2C+Ricky+E%2E%22">Sward, Ricky E.</searchLink><relatesTo>1</relatesTo><i> ricky.sward@wavmax.com</i><br /><searchLink fieldCode="AR" term="%22Gerken%2C+Mark%22">Gerken, Mark</searchLink><relatesTo>1</relatesTo><i> mark.gerken@usafa.af.mil</i><br /><searchLink fieldCode="AR" term="%22Casey%2C+Dan%22">Casey, Dan</searchLink><relatesTo>1</relatesTo><i> daniel.casey@ramstein.af.mil</i>
– Name: TitleSource
  Label: Source
  Group: Src
  Data: <searchLink fieldCode="JN" term="%22CrossTalk%3A+The+Journal+of+Defense+Software+Engineering%22">CrossTalk: The Journal of Defense Software Engineering</searchLink>. Sep2006, Vol. 19 Issue 9, p10-14. 5p. 3 Diagrams.
– Name: Subject
  Label: Subjects
  Group: Su
  Data: <searchLink fieldCode="DE" term="%22SPARK+%28Computer+program+language%29%22">SPARK (Computer program language)</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+software%22">Computer software</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+systems%22">Computer systems</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+industry%22">Computer industry</searchLink><br /><searchLink fieldCode="DE" term="%22Software+failures%22">Software failures</searchLink><br /><searchLink fieldCode="DE" term="%22System+failures%22">System failures</searchLink>
– Name: SubjectGeographic
  Label: Geographic Terms
  Group: Su
  Data: <searchLink fieldCode="DE" term="%22United+States%22">United States</searchLink>
– Name: Abstract
  Label: Abstract
  Group: Ab
  Data: One approach to software assurance is to use an annotated language such as SPARK. For safety critical software programs such as Unmanned Aerial Vehicle flight control software, the risk of software failure demands high assurance that the software will perform its intended function. Using an example from work being done at the U.S. Air Force Academy, this article describes SPARK and the formal process of proving correctness of software implementations. [ABSTRACT FROM AUTHOR]
– Name: AbstractSuppliedCopyright
  Label:
  Group: Ab
  Data: <i>Copyright of CrossTalk: The Journal of Defense Software Engineering is the property of USAF Software Technology Support Center and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract.</i> (Copyright applies to all Abstracts.)
PLink https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=22957402
RecordInfo BibRecord:
  BibEntity:
    Languages:
      – Code: eng
        Text: English
    PhysicalDescription:
      Pagination:
        PageCount: 5
        StartPage: 10
    Subjects:
      – SubjectFull: SPARK (Computer program language)
        Type: general
      – SubjectFull: Computer software
        Type: general
      – SubjectFull: Computer systems
        Type: general
      – SubjectFull: Computer industry
        Type: general
      – SubjectFull: Software failures
        Type: general
      – SubjectFull: System failures
        Type: general
      – SubjectFull: United States
        Type: general
    Titles:
      – TitleFull: When Computers Fly, It Has to Be Right: Using SPARK for Flight Control of Small Unmanned Aerial Vehicles.
        Type: main
  BibRelationships:
    HasContributorRelationships:
      – PersonEntity:
          Name:
            NameFull: Sward, Ricky E.
      – PersonEntity:
          Name:
            NameFull: Gerken, Mark
      – PersonEntity:
          Name:
            NameFull: Casey, Dan
    IsPartOfRelationships:
      – BibEntity:
          Dates:
            – D: 01
              M: 09
              Text: Sep2006
              Type: published
              Y: 2006
          Identifiers:
            – Type: issn-print
              Value: 21601577
          Numbering:
            – Type: volume
              Value: 19
            – Type: issue
              Value: 9
          Titles:
            – TitleFull: CrossTalk: The Journal of Defense Software Engineering
              Type: main
ResultId 1