Software applications have become crucial to the aerospace industry, providing a wide range of functionalities and capabilities used during the design, manufacturing and support of aircraft. However, as this criticality increases, so too does the risk for business operations when facing a software failure. Hence, there is a need for new methodologies to be developed to support aerospace companies in effectively managing their software portfolios, avoiding the hazards of business disruption and additional costs. This paper aims to provide a definition of operational software maturity, and how this can be used to assess software operational behaviour, as well as a view on the different aspects that drive software maturity within the aerospace industry. The key research question addressed is, how can operational software maturity monitoring assist the aerospace industry in effectively managing large software portfolios? This question has been addressed by conducting an in depth review of current literature, by working closely with aerospace professionals and by running an industry case study within a major aircraft manufacturer. The results are a software maturity model composed of a set of drivers and a prototype tool used for the testing and validation of the research findings. By utilising these methodologies to assess the operational maturity of software applications in aerospace, benefits in maintenance activities and operations disruption avoidance have been observed, supporting business cases for system improvement.
 Caralli, R., Knight, M. and Montgomery, A., “Maturity Models 101: A Primer for Applying Maturity Models to Smart Grid Security, Resilience, and Interoperability”, Software Engineering Institute, 2012.
 Becker, J., Knackstedt, R. and Pöppelbuβ, J., “Developing Maturity Models for IT Management – Aprocedure Model and its Application”. Westfälische Wilhelms Universität Münster European Research Center, Münster, 2009.
 Paulk, M., Curtis, B., Chrissis, M. and Weber, C., “Capability maturity model for software”, 1994 Version 1.1. http://www.sei.cmu.edu/pub/documents/ 93.reports/pdf/tR24.93.pdf. Accessed on 20/04/2017.
 Renken, J.,” Developing an IS/ICT management capability maturity framework.” In: Research conference of the South African Institute for Computer Scientists and Information Technologists (SAICSIT). Stellenbosch, 2004, 53–62.
 Humphrey, W., “Managing the Software Process”, Goodreads, 1989.
 ISO/IEC 25010:2011, “Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – System and software quality models”, 2011.
 ISO/IEC 9126-1, “Software engineering – product quality – Part 1: Quality Model”, first ed.: 2001-06-15.
 McCall, J. and Matsumoto, M., “Software Quality Measurement Manual”, General Electric Company, 1980.
 Lauesen, L., “Quality Factors”, Software Requirements Styles and Techniques, Addison-Wesle y (ed), London, 2002, pp. 220-230.
 de Bruin, T., Rosemann, M., Freeze, R., Kulkarni, U., “Understanding the Main Phases of Developing a Maturity Assessment Model”. In: 16th Australasian Conference on Information Systems (ACIS), 2005, Sydney, Australia.
 Tukey, J., “Exploratory Data Analysis”, Addison-Wesley, 1977.