|
| | | |
Safety, Software Architecture and MIL-STD-1760
Squair, M.J.
Integrating modern aircraft stores, particularly weapons,
creates a complex system of systems challenge. The
traditional approach to such integrations was for each to
be a stand-alone program. For each program a unique
interface would usually be implemented, usually also
with a set of unique problems, such as the missile
'ghosting' problems experienced during the F-16 to
AMRAAM integration (Ward 1993). In response to the
problems of such an approach MIL-STD-1760 an
Interface Standard for Aircraft to Store Electrical
Interconnection System was released by the US DoD to
standardise aircraft/store interfaces. This paper discusses
the advantages and limitations of the architectural
techniques of MIL-STD-1760. A hierarchical method for
integrating the use of the standard into a safety case is
also described. |
Cite as: Squair, M.J. (2006). Safety, Software Architecture and MIL-STD-1760. In Proc. Eleventh Australian Workshop on Safety-Related Programmable Systems (SCS 2006), Melbourne, Australia. CRPIT, 69. Cant, T., Ed. ACS. 93-112. |
(from crpit.com)
(local if available)
|
|