1 / 7

Smooth Transition of Ground Segment across Mission Phases

This article discusses the challenges faced by ground segment developers in ensuring a smooth transition between mission phases. It highlights the traditional approach of developing software in isolation and the problems that can occur after launch. It suggests a new approach of iterative software development and user involvement to minimize surprises and ensure compatibility across phases.

ablanco
Download Presentation

Smooth Transition of Ground Segment across Mission Phases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Smooth Transition of Ground Segmentacross Mission Phases Maohai Huang National Astronomical Observatories, China 2006-06-30

  2. Problem for the part of ground segment for P/L users and science data users • In traditional approach: • s/w is developed when instruments are developed • The two group of developers work largely in isolation, linked by documentations that could need frequent and diligently maintained. • Despite best effort in ground testing, bad surprises often happens after launch (the first time the s/w is used in full): • Incorrectly implemented functionality, • Insufficient performance and quality • Incompatible format and specs of Instrument data • User interface,

  3. Mission phases • Instrument Level Test (ILT) • Integrated System Test (IST) • In-orbit Check-out • Routine operation

  4. Software developed in previous phases are used in later phases • Start developing and USING s/w when instruments are developed • New Version of G/S s/w are released periodically in iterative an approach • Instrument testing engineers and calibration scientists are users of the s/w in current release, and testers for later releases • There will be minimal bad surprise when a new mission phase starts, no “big bang” for s/w users of the mission when s/c is lauches – by the time of launch time, the s/w would have already been used and debugged for years

  5. Data in previous phases can be accessed, used, processed, without modification of data or software, in later phases • Instrument configuration data • Instrument calibration data • s/c HK data and metadata • Science data

  6. Smooth transition • Requirement of Herschel ground segment on smooth transition between mission phases (J. Brumfitt)

  7. Some implications • Has high level requirement on G/S implementation • Interface between instrument and software tools are defined early in mission phases • Defined, but controlled evolution allowed, even required • Interface between MOC should be mature (S2K?) • Interactive development approach needed • More interaction between s/w developers and engineers and scientists

More Related