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.

January, 2001 1

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

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 !!!

WFC3 CDR Party !!!

January, 2001 2

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?

January, 2001 3

C O S & W FC -3 Software and Operations S taff

Ira B e ckerS ta ff C on su lta n t

S o ftw a re Q AS te ve N issen

Ju s tin A hre nsC o nfig u ra tion M a n ag e m e nt

A lliso n E llio tt(C O S )

R o b e rt G ille tt(C O S )

B ria n R e hm(W F C 3 )

G S F C(W F C 3 )

Ja n e t P itts(W F C 3 )

L in da K ra u ze(C O S )

G a vin P a yne

Je ff P u g lia no(C O S )

T B D(W F C 3 )

F lig h t S o ftw a re

Je ff P u g lia no

D in a D e m a ra

G S E S o ftw a re

S o ftw a reC h ris D o ra to

T o dd B a rto(W F C 3 )

H u g h M u rp hy(W F C 3 )

S te ve P itts(C O S )

G a ry W ilb e rg er

T e s tD e n ise M ille r

R a n dy S teve ns

A d a m T ho d eyS IT S

L in da R e m s tad(C O S )

T o dd B a rto(W F C 3 )

D e ve lo p m e nt

M ike D ra u g e lis(W F C 3 D B )

T im S ch o e ne w e is(W F C -3 )

C h ris B lue(C O S D B )

S u e R o ss(C O S )

E n g in e ering

O p s S ys . E n g ine e ringT im (W F C 3 ) & S u e (C O S )

S co tt M cA rth ur

R o g er G he squ ie re

C h ris B lue

T e s t B e n ch es & F ac ilit iesT B D

IP T L e adG ra n t B lue

On-site Contractor

Off-site Contractor

Ball

January, 2001 4

RIU

NSSC-1

MEB

Cmds

ED

Cmds

Cmds

Response

Response

SDFScience 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

IRState 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

January, 2001 5

RIU

NSSC-1

COS AP FSW

MEB

CS FSW

Cmds

ED

Cmds

Cmds

Hskp

Response

NUV DET

MCE FSW

MCE

DCE FSW

FUV DET

DCE

DIB

DIB FSW

Raw NUV SD

Raw FUV SD

Processed SD

SDFScience Data

CS

CmdsResponse

COSSI C&DH

HST

January, 2001 6

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.

January, 2001 7

SI: COS Task: Documentation

DRDNo.

CDRL Title Author SubmittalType

Milestone Due Date toCM

DM-01 SI Cmds List S. Downey Initial FSW Prelim Design 10/15/99DM-01 SI Cmds List C. Blue Update As needed 2/28/01DM-01 SI Cmds List C. Blue Final SI delivery to GSFC 2/7/02DM-02 Engineering Data List C. Blue Initial FSW Component Test 2/28/01DM-02 Engineering Data List C. Blue Update As needed -DM-02 Engineering Data List C. Blue Final SI delivery to GSFC 2/7/02DM-03 SW Management Plan C. Dorato Final FSW Req. Review 5/1/99DM-03 FSW Req. Document C. Dorato Final FSW Req. Review 5/1/99DM-03 FSW Req. Document C. Dorato Update As needed 1/15/01DM-03 FSW Design Document C. Dorato Initial FSW Prelim. Design 9/10/99DM-03 FSW Design Document C. Dorato Final FSW Detailed Design 1/15/01DM-03 FSW User Manual C. Dorato Initial SI delivery to GSFC 2/7/02DM-03 FSW User Manual C. Dorato Update As needed -DM-03 FSW User Manual C. Dorato Final SW Maint. to Code 582 3/5/03DM-03 Unit Development Folders C. Dorato Final SW Maint. to Code 582 3/5/03DM-04 GSE SW C. Dorato Final GSE delivery to GSFC 2/7/02

Ball Science Instrument Documentation

January, 2001 8

Ball Science Instrument Documentation (cont)

DM-05 Cmd Definition S. Ross Initial FSW Detailed Design 10/31/00DM-05 Cmd Definition S. Ross Update As needed 1/12/01DM-05 Cmd Definition S. Ross Final SI delivery to GSFC 2/7/02

DM-06 Science Data Format R. Brewster Initial FSW Detailed Design 3/31/00DM-06 Science Data Format L. Krauze Update As needed 1/19/01DM-06 Science Data Format L. Krauze Final SI delivery to GSFC 2/7/02

DM-07 FSW Test Plan D. Miller Initial FSW Detailed Design 3/31/00DM-07 FSW Test Plan D. Miller Update As needed -

DM-08 FSW Test Procedure D. Miller Initial 45 days before start of FQT 7/30/01DM-08 FSW Test Procedure D. Miller Final FQT as run 11/1/01

DM-14 Tlm Calibration List C. Blue Initial FSW Component Test 2/31/01DM-14 Tlm Calibration List C. Blue Update As needed -DM-14 Tlm Calibration List C. Blue Final SI delivery to GSFC 2/7/02OP-04 CARD & OLD S. Ross Initial System functional test 8/15/01OP-04 CARD & OLD S. Ross Update As needed -OP-04 CARD & OLD S. Ross Final SI delivery to GSFC 2/7/02

January, 2001 9

Software Development Methodology

Qualification TestQualification Test

Iterate For MultipleSoftware Builds

Tasks &Functions

TestedUnits

TestedComponents

TestedBuilds

SW Requirements Peer Review

CSCI Level Peer Review

Code & Unit TestCode & Unit Test

Component TestComponent Test

Build TestBuild Test

Software Documentation List:DM-03 SW Management PlanDM-03 FSW RequirementsDM-03 FSW DesignDM-06 Science Data FormatDM-07 FSW Test PlanDM-08 FSW Test ProcedureDM-03 FSW Users Manual

TestableRequirements

Components Component Level Peer Review

Software RequirementsSoftware Requirements

Detailed DesignDetailed Design

System Requirements Review

CEIOP-01HW Design

System RequirementAnalysis

System RequirementAnalysis

Preliminary DesignPreliminary Design

January, 2001 10

COS Build Plan

January, 2001 11

WFC3 Build Plan

January, 2001 12

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

UnitTest

CSC

CSUs

Component Test

CSCI

CSCs

FQT

FlightImage

CodeReview

S/W I&T

January, 2001 13

PC PC PC

Ground Simulation Flight Simulation

Database CCS Sci Data

PC 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

January, 2001 14

January, 2001 15

Risk ListStaffing 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

January, 2001 16

Risk ListSITS 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

January, 2001 17

Risk ListTest 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