Premium
3.2.1 Issues with Third Party Maintenance of Software Intensive Legacy Systems: A Case Study – Avionic Mission Systems
Author(s) -
Kennedy Damian,
Nesterov Sergey
Publication year - 2008
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2008.tb00810.x
Subject(s) - avionics , legacy system , aerospace , original equipment manufacturer , software , schedule , variety (cybernetics) , systems engineering , software maintenance , avionics software , software system , software development , computer science , engineering , software development process , operating system , aerospace engineering , artificial intelligence
The software maintenance burden in military and industrial applications is well known. A variety of factors influence the evolution of large legacy systems, and system upgrades have always been a challenge in terms of avoiding schedule and cost overruns. This evolution becomes even more of a challenge when it is implemented by an organisation other than the original developers. When maintaining complex legacy systems, third party maintenance organisations are placed under additional constraints. Some of these additional constraints come from the decisions made by the Original Equipment Manufacturer (OEM) on the development processes they use and the Computer Aided Software Engineering (CASE) tools that were used to aid in the system development. This paper will describe and analyse a particular case where this occurred with the maintenance of the AP‐3C Orion fleet for the Australia Defence Force by Tenix Aerospace and Defence.