NTRS - NASA Technical Reports Server

Back to Results
Leveraging Existing Mission Tools in a Re-Usable, Component-Based Software EnvironmentEmerging methods in component-based software development offer significant advantages but may seem incompatible with existing mission operations applications. In this paper we relate our positive experiences integrating existing mission applications into component-based tools we are delivering to three missions. In most operations environments, a number of software applications have been integrated together to form the mission operations software. In contrast, with component-based software development chunks of related functionality and data structures, referred to as components, can be individually delivered, integrated and re-used. With the advent of powerful tools for managing component-based development, complex software systems can potentially see significant benefits in ease of integration, testability and reusability from these techniques. These benefits motivate us to ask how component-based development techniques can be relevant in a mission operations environment, where there is significant investment in software tools that are not component-based and may not be written in languages for which component-based tools even exist. Trusted and complex software tools for sequencing, validation, navigation, and other vital functions cannot simply be re-written or abandoned in order to gain the advantages offered by emerging component-based software techniques. Thus some middle ground must be found. We have faced exactly this issue, and have found several solutions. Ensemble is an open platform for development, integration, and deployment of mission operations software that we are developing. Ensemble itself is an extension of an open source, component-based software development platform called Eclipse. Due to the advantages of component-based development, we have been able to vary rapidly develop mission operations tools for three surface missions by mixing and matching from a common set of mission operation components. We have also had to determine how to integrate existing mission applications for sequence development, sequence validation, and high level activity planning, and other functions into a component-based environment. For each of these, we used a somewhat different technique based upon the structure and usage of the existing application.
Document ID
Document Type
Conference Paper
Greene, Kevin (QSS Group, Inc. Moffett Field, CA, United States)
Grenander, Sven (Jet Propulsion Lab., California Inst. of Tech. Pasadena, CA, United States)
Kurien, James (NASA Ames Research Center Moffett Field, CA, United States)
z,s;fshir. z[orttr (Jet Propulsion Lab., California Inst. of Tech. Pasadena, CA, United States)
z,scer;;. Dvpyy (Jet Propulsion Lab., California Inst. of Tech. Pasadena, CA, United States)
O'Reilly, Taifun (Jet Propulsion Lab., California Inst. of Tech. Pasadena, CA, United States)
Date Acquired
August 23, 2013
Publication Date
January 1, 2006
Subject Category
Computer Programming and Software
Meeting Information
AIAA Space Ops. 2006(Rome)
Distribution Limits