1. January, 20011 Please join us in the Tech Tower Auditorium on Tuesday, January 30th for a WFC3 Post-CDR Celebration 4:30 to 7:30 pm Dinner and adult beverages will be provided WFC3 CDR Party !!!

2. January, 20012 WFC3 and COS Flight and Ground Test Software Agenda: –Ball SI Development Team Organization –what are we doing and how we do it? –where are we and what is left to do? –when will it be done and what are the risks?

3. January, 20013 On-site Contractor Off-site Contractor Ball

4. January, 20014 RIU NSSC-1 MEB Cmds ED Cmds Response SDF Science Data UVIS State Machine Digitized Pixel Data (4x) UVIS Det Clock Drivers Clocks Analog Pixel Data A/D Conv IR Det Clocks Analog Pixel Data IR DEB IR State Machine Clock Drivers 4 FIFOs Digitized Pixel Data (4x) CS Buffer Memory MEB = Main Electronics Box CEB = CCD Electronics Box IR DEB = IR Detector Electronics Box A/D Conv CS FSW WFC3 AP FSW CEB WFC3SI C&DH HST

5. January, 20015 RIU NSSC-1 COS AP FSW MEB CS FSW Cmds ED Cmds Hskp Response NUV DET MCE FSW MCE DCE FSW FUV DET DCE DIB DIB FSW Raw NUV SD Raw FUV SD Processed SD SDF Science Data CS Cmds Response COSSI C&DH HST

6. January, 20016 SW/Ops Test Bench: Non-flight Main Electronics Box CPU, Memory (2) Comm, SES (4) Low Voltage Power Supply Box power relays: hold & operate Facility power (not PDU) Mechanism Simulator Detector (CEB/DEB) Simulator Science Data Simulator In Circuit Emulator sw unit test & debug tool WFC3 SW/Ops Test Bench Bench 1 of 2 in development The test bench shall support 100% path testing of FSW at the unit test level. No manual intervention shall be required during the execution of a full function SMS The executable flight software shall not be modified for operation on the test bench.

7. January, 20017 Ball Science Instrument Documentation

8. January, 20018 Ball Science Instrument Documentation (cont)

9. January, 20019 Software Development Methodology Qualification Test Iterate For Multiple Software Builds Tasks & Functions Tested Units Tested Components Tested Builds SW Requirements Peer Review CSCI Level Peer Review Code & Unit Test Component Test Build Test Software Documentation List: DM-03 SW Management Plan DM-03 FSW Requirements DM-03 FSW Design DM-06 Science Data Format DM-07 FSW Test Plan DM-08 FSW Test Procedure DM-03 FSW Users Manual Testable Requirements Components Component Level Peer Review Software Requirements Detailed Design System Requirements Review CEI OP-01 HW Design System Requirement Analysis System Requirement Analysis Preliminary Design

10. January, 200110 COS Build Plan

11. January, 200111 WFC3 Build Plan

12. January, 200112 UNIT TEST - tests every line of code and full range of conditions (full path testing) for all new software SW INTEGRATION & TEST - verifies functionality of SW in a flight like environment COMPONENT TEST - verifies SW I/F and functions using SITS & SW/Ops Test Bench - independent test team FORMAL QUALIFICATION TEST (FQT) - verifies SW requirements in a flight like environment CSU Unit Test CSC CSUs Component Test CSCI CSCs FQT Flight Image Code Review S/W I&T

13. January, 200113 PC Ground Simulation Flight Simulation DatabaseCCSSci Data PC SUN Flight Simulator Power Distribution Unit Science Instrument SW/Ops Test Bench: non-flight Main Electronics Box Mechanism Simulator Science Data Simulator Detector Simulator Internal power Remote User Workstations: tlm monitoring, and science data analysis & archive Science Instrument Test System (SITS): commanding (realtime & stored) tlm monitoring, eng data analysis & fault isolation

14. January, 200114

15. January, 200115 Risk List Staffing Risks Concern Definition: –Reduced SW and Ops staff from previous HST programs and new personnel with less HST experience. Traditional support group involved in other work and new responsibilities. –COS: there is no SI/SE on-site support here at Ball –Impacts Schedule - performance achieved on past programs can not be counted on. Technical - over-site / review may miss a design mistake resulting in a costly fix later on, or no fix and degraded science Mitigation: –Provide diligent SW/Ops management to achieve maximum results for the current staff. –Make sure program / peer reviews are will attended by all cooperative groups

16. January, 200116 Risk List SITS GSE Concern Definition: –CCS is a new system. No science instrument has ever been completely developed using this system. There are over 900 documented CCS problems, and the SI development groups needs are second behind flight ops. –Impacts: Schedule - users are unfamiliar with how to use this new system. Performance achieved on past programs can not be counted on for WFC3. Flight HW safety - user I/F problems and commanding problems may lead to FSW anomalies not being caught in a timely manner, or unwanted commands being set to the flight hardware. Mitigation: –Schedule user training - done –Conduct weekly telecons with SITS developers to review problems - done –Maintain SITS users guide with problem workarounds - done –Review critical issues with users on a weekly basis - not done

17. January, 200117 Risk List Test Bench Availability Concern Definition: –Schedule problems: WFC3 the test benches do not arrive until most of the way through Build 2 COS - flight electronics testing needs boards from one of the SW/Ops test benches –Impacts: Schedule - unit and component level testing will have to be put off until later Schedule - resource shortages will occur during periods of high equipment usage Mitigation: –WFC3: Build table top MEB to support unit level testing - in work schedule new code development early - done –COS: work with electronics folks to minimize bench down time - in work work two shifts as required when only one bench is available