• Home
  • Current congress
  • Public Website
  • My papers
  • root
  • browse
  • IAC-11
  • B6
  • 1
  • paper
  • Human Space Flight Software Evolution

    Paper number

    IAC-11,B6,1,11,x11597

    Author

    Mr. Graham O''Neil, USA Space Operations LLC, United States

    Year

    2011

    Abstract
    For human spaceflight, the emphasis is on safe operation of critical functions.  Differences in space operations between human rated software and other common approaches to spaceflight software for operations are inevitable.  As human spaceflight expands internationally, the challenges of integration and assurance of safe operations become more significant due to differences in language, and culture oriented development processes.  
    
     Both challenges are present from the early life cycle stages to performance of operational support of critical tasks in space.  Over the life cycle, changes in workforce technical skills will occur. Developers will not necessarily be available to support software sustainment during the operations phase of the life cycle.  Yet it is still important to provide capability to perform enhancement and modification to software.  Over enough mission cycles, this may be equivalent to continuous sustainment activity. This paper provides examples of software tool classes to meet the challenges. 
    
    Some tools provide built in guidance and training on their use to ensure all levels of software engineers can use them correctly.  This class of tools includes analysis, test and verification, and code review support. Other tool classes improve operations safety by reducing error insertion, flag dangerous software constructs, or exhaustively execute test cases with permutations on real world crew vehicle interactions. A third set of tools provides improved integration of systems and operations by maintaining system health and capability status as needed for safe sequencing of each mission activity.  
    
    To meet the challenges of international participation, other tools include common templates for constrained input.  These will have directions in several languages to be selected by the user.  The input fields will be verified against history and significant changes highlighted for the trainer, user and other reviewers depending on the mission phase. 
    
    Automated, consistent status reporting of all mission software modules including their 
    pedigree from verification testing is one approach to ensure the proper functioning of on-board software as it evolves over long mission timelines. Integration of new components is based on acceptable performance in standardized Earthbound testbeds or an equivalent space vehicle.  Test suites are generated based on defined requirements.  Test coverage and level of correct behavioral responses will be retained for post test analysis.  
    
    Implementation of these tools and close integration with the operations community will provide high quality software for use in international human spaceflight.
    Abstract document

    IAC-11,B6,1,11,x11597.brief.pdf

    Manuscript document

    (absent)