Advertisement

Technical Obsolescence Management Strategies for Safety-Related Software for Airborne Systems

  • Simos GerasimouEmail author
  • Dimitris Kolovos
  • Richard Paige
  • Michael Standish
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 10748)

Abstract

Complex software systems deployed in safety-critical and business-critical application domains (e.g., avionics, defence, healthcare) are meant to provide service for decades. Although many of these systems withstand technological evolution and infrequently undergo substantial changes, they will likely face software obsolescence problems during their lifetime. Resolving these obsolescence problems is an expensive, time-consuming and labour intensive process. This project investigates technical obsolescence problems in safety-related software for airborne systems, examines the applicability of obsolescence management strategies and explores methods to automate the resolution of software obsolescence.

References

  1. 1.
    IEC 62402:2007: Obsolescence management. Application guide (2007)Google Scholar
  2. 2.
    JSPP 886, Volume 7, Part 8.13: Obsolescence management (2007)Google Scholar
  3. 3.
    Management of the Typhoon Project: House of Commons Committee of Public Accounts. Thirtieth Report of Session 2010–12 (2011)Google Scholar
  4. 4.
    Balaban, I., Tip, F., Fuhrer, R.: Refactoring support for class library migration. In: OOPSLA 2005, pp. 265–279 (2005)Google Scholar
  5. 5.
    Bartels, B., Ermel, U., Pecht, M., Sandborn, P.: Strategies to the Prediction, Mitigation and Management of Product Obsolescence. Wiley, Hoboken (2012)CrossRefGoogle Scholar
  6. 6.
    Bartolomei, T.T., Czarnecki, K., Lämmel, R.: Swing to SWT and back: patterns for API migration by wrapping. In: ICSM 2010, pp. 1–10 (2010)Google Scholar
  7. 7.
    Cossette, B.E., Walker, R.J.: Seeking the ground truth: a retroactive study on the evolution and migration of software libraries. In: FSE 2012, pp. 1–11 (2012)Google Scholar
  8. 8.
    Dagenais, B., Robillard, M.P.: Recommending adaptive changes for framework evolution. ACM Trans. Softw. Eng. Methodol. 20(4), 19:1–19:35 (2011)CrossRefGoogle Scholar
  9. 9.
    Dig, D., Johnson, R.: The role of refactorings in API evolution. In: ICSM 2005, pp. 389–398 (2005)Google Scholar
  10. 10.
    Dig, D., Johnson, R.: How do APIs evolve? A story of refactoring: research articles. J. Softw. Maint. Evol. 18(2), 83–107 (2006)CrossRefGoogle Scholar
  11. 11.
    Henkel, J., Diwan, A.: Catchup!: Capturing and replaying refactorings to support API evolution. In: ICSE 2005, pp. 274–283 (2005)Google Scholar
  12. 12.
    Kolovos, D., Rose, L., Paige, R., Garcıa-Domınguez, A.: The epsilon book. Structure 178, 1–10 (2010)Google Scholar
  13. 13.
    Lämmel, R., Pek, E., Starek, J.: Large-scale, AST-based API-usage analysis of open-source Java projects. In: SAC 2011, pp. 1317–1324 (2011)Google Scholar
  14. 14.
    Nguyen, A.T., Nguyen, H.A., Nguyen, T.T., Nguyen, T.N.: Statistical learning approach for mining API usage mappings for code migration. In: ASE 2014, pp. 457–468 (2014)Google Scholar
  15. 15.
    Nguyen, H.A., Nguyen, T.T., Wilson Jr., G., Nguyen, A.T., Kim, M., Nguyen, T.N.: A graph-based approach to API usage adaptation. In: OOPSLA 2010, pp. 302–321 (2010)Google Scholar
  16. 16.
    Nita, M., Notkin, D.: Using twinning to adapt programs to alternative APIs. In: ICSE 2010, pp. 205–214 (2010)Google Scholar
  17. 17.
    Robillard, M.P., Bodden, E., Kawrykow, D., Mezini, M., Ratchford, T.: Automated API property inference techniques. IEEE TSE 39(5), 613–637 (2013)Google Scholar
  18. 18.
    Romero Rojo, F.J., Roy, R., Shehab, E.: Obsolescence management for long-life contracts state of the art and future trends. Int. J. Adv. Manuf. Technol. 49(9), 1235–1250 (2010)CrossRefGoogle Scholar
  19. 19.
    Sandborn, P., Myers, J.: Designing engineering systems for sustainability. In: Misra, K.B. (ed.) Handbook of Performability Engineering, pp. 81–103. Springer, London (2008).  https://doi.org/10.1007/978-1-84800-131-2_7 CrossRefGoogle Scholar
  20. 20.
    Singh, P., Sandborn, P.: Obsolescence driven design refresh planning for sustainment-dominated systems. Eng. Econ. 51(2), 115–139 (2006)CrossRefGoogle Scholar
  21. 21.
    University of York: Response to “Investigation into Technical Obsolescence Management Strategies for Safety-Related Software for Airborne Systems”, July 2016Google Scholar
  22. 22.
    Xing, Z., Stroulia, E.: API-evolution support with Diff-CatchUp. IEEE TSE 33(12), 818–836 (2007)Google Scholar
  23. 23.
    Zhong, H., Thummalapenta, S., Xie, T., Zhang, L., Wang, Q.: Mining API mapping for language migration. In: ICSE 2010, pp. 195–204 (2010)Google Scholar

Copyright information

© Springer International Publishing AG 2018

Authors and Affiliations

  • Simos Gerasimou
    • 1
    Email author
  • Dimitris Kolovos
    • 1
  • Richard Paige
    • 1
  • Michael Standish
    • 2
  1. 1.Department of Computer ScienceUniversity of YorkYorkUK
  2. 2.Defence Science and Technology LaboratoryMinistry of DefenceLondonUK

Personalised recommendations