1 / 2

RFA 19 – Robustness of Operations Software

RFA 19 – Robustness of Operations Software. Specific Request Specify plans and requirements to ensure that software, particularly that “inherited” from I&T, will be of sufficient robustness for operations use. Response Using ITOS for LAT health and safety operations

dex
Download Presentation

RFA 19 – Robustness of Operations Software

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. RFA 19 – Robustness of Operations Software • Specific Request • Specify plans and requirements to ensure that software, particularly that “inherited” from I&T, will be of sufficient robustness for operations use. • Response • Using ITOS for LAT health and safety operations • Plan to use existing automated notification software tools (such as FASAT or SOF RXTE) to help assure reliable 24/7 operation of ISOC • Other software tools • ISOC will use existing software where possible • ISOC will follow a complete verification and validation process, as described in LAT-SS-02513-1 LAT ISOC Verification and Validation Plan • The ISOC Test Plan document (to be released in April 2005) will provide the mapping of all Level III requirements (in LAT-SS-0021-8) to software components • Test procedures will be documented to cover each requirement (either in the Test Plan or in a separate Test Procedures document) • See attached SW development schedule for an outline of ISOC testing • The test procedures will be followed before each release to verify that each requirement is met (including regression tests of previously released features) • A fully functional ISOC system will be available for control of LAT upon its arrival at SpectrumAstro • Schedule includes many months of operational use of software before launch (e.g. during I&T and Mission Simulations)

  2. ISOC Software Development Schedule Phase / Milestone Aug-04 Sep-04 Oct-04 Nov-04 Dec-04 Jan-05 Feb-05 Mar-05 Apr-05 May-05 Jun-05 Jul-05 Aug-05 Sep-05 Oct-05 Nov-05 Dec-05 Jan-06 Feb-06 Mar-06 Apr-06 May-06 Jun-06 Jul-06 Aug-06 Sep-06 Oct-06 Nov-06 Dec-06 Jan-07 Feb-07 Mar-07 ISOC CDR ITOS setup/configuration ISOC Verif. with Test Bed Diagnostic Tool Dev Mission Planning Dev DB/Web/E-logbook Dev Plotting/Trending Dev SW enhancements ISOC Demos ISOC Simulation Testing ISOC SW Releases 1 4 2 3 Ground Readiness Tests 3 4 7 2 6 5 End-to-End Tests 6 5 4 3 1 2 Environmental tests at NRL ISOC testing at NRL ISOC ready to take over LAT operation ISOC used to I/F with LAT (front-door only) Mission Simulations Launch SW Dev Slack Times

More Related