{'fraction_non_alphanumeric': 0.010931351114997814, 'fraction_numerical': 0.0008745080891998251, 'mean_word_length': 5.809523809523809, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
COCOMO II Predicts the Effects of Collaborative Software Development and Sustaining Engineering

This paper explores the use of the COCOMO I1 model to predict results of applying collaborative software development and sustaining engineering to aerospace and government software development projects. Empirical data from the Space Shuttle Telemetry Ground Station upgrade, recently completed using collaborative software development, is compared to model predictions. Extrapolation is done to explore possible benefits of the method to other upgrade or development projects. This new software development method resulted in several positive effects on the ground station upgrade project over the standard method ordinarily employed to develop and upgrade systems. Prior to implementing this new method, the upgrade project had been under development for several years using the standard development method. The standard software development method involves developing custom applications using COTS hardware, operating systems, development tools, drivers and compilers. The new method involved adopting a commercial telemetry ground station software package to provide basic functionality and building additional required capabilities in a collaborative manner with the COTS software. Positive effects recounted in the paper include; a reduction in the initial software development costs, a reduction in the software time to market, improved marketability of the software technology developed, improved product quality, and improved maintainability. Two reasons the method was so successful are explored using the COCOMO I1 model. The first reason explored is that by employing this collaborative method we changed the fundamental skill mix of the software development team. Initially the team was expert in the problem domain and weak in the programming and information technology areas. After changing the development method the skills of the software development team reflected a balanced expert team. The second reason the method was so successful is that the project effectively leveraged existing code and architecture of the commercial product. The paper explores possible application of this development methodology to other government and NASA programs and the probable benefits.