1. GLAST LAT Project4.1.7 Dec 15’03 V 1 FSW Organization Chart FSW Lead J. J. Russell Project Manager (IPM) L. Klaisner Electronics & FSW Manager G. Haller Configuration Manager A. P. Waite S/C Interface D. Wood Calibration J. Swain LAT Configuration J. Swain Software Architectures A. P. Waite Thermal Control M. Monirzad FSW Independent Test-Team Lead M. Huffer Test Executive S. Maldonado Front End Simulators O. Saxton Cmd & Telem Database B. Davis Boot/RAD750 Processor R. Caperoon Test Team Rama, Shanu (tbd) Mission Project Office FSW Management E. Andrews Algorithms J. J. Russell Tools K. Lo Driver Development C. Brune On-line, Test- Scripts R. Claus, S. Tuvi I&T Manager E. Bloom Documentation R. Morin FSW Management Support T. Schalk C&DH A.P. Waite

2. GLAST LAT Project4.1.7 Dec 15’03 V 2 Software planning (TS me ) Current activity (working on a roadmap) –Reviewing processes, issues, status –Evaluating re-baseline schedule (work in progress) –Establish metrics Insertion of Demos and mini demos as milestones monthly activity –Understand FS & mini tower status wrt FSW usage –Add people

3. GLAST LAT Project4.1.7 Dec 15’03 V 3 Software planning (TS me ) Major drivers –EM2 (may) Build Integrates with Multiple Towers –ISIS (may) Em2 base + more formal docs; testing; support –Start of FU hardware integration (I&T) july –FU Dec 2004 –FU acceptance Testing Feb 2005 – FU delivered to I&T for Instrument System Testing Establish a CCB for FSW to control potential feature creep (FSW Peer Review (2?)) Navigate the extensive documentation and identify holes QLR response

4. GLAST LAT Project4.1.7 Dec 15’03 V 4 QLR response / “plan” Requirements –Completeness… control… traceability… tests Mike DeKlotz CCB in place well before ISIS Schedule –Reflect real work load (eg hardware testing) –Reflect real priorities for FU elements –Margins ? –With integrated milestones / demos –Expect updates to PMCS during Jan Metrics –Useful to project –and- team –Resource usage Testing (support & planning) CCB and Reviews (including Jan EM2 peer review) staffing

5. GLAST LAT Project4.1.7 Dec 15’03 V 5 Organization Status Manpower issues –M. Monirzad ? –Test script writers –ISIS owner ? (remember this is more formal) –New people have a schedule impact both ways Technical status –primary and secondary boot code (pulled next page from QLR) –Code management tools (CMT CMX CVS) upgrades –Housekeeping design progress –Cmd and event server developments –LCB driver testing –Web access to existing docs

6. GLAST LAT Project4.1.7 Dec 15’03 V 6 Accomplished since CDR (5) Primary boot of RAD750 (from “internal” RAD750 SUROM) –Integrated polled 1553 driver Secondary boot of RAD750 (from “external” SIB EEPROM) SIB EEPROM formatted, file system laid out Performed successful communication test with the Spacecraft Instrument Interface Simulator (SIIS) provided by Spectrum Astro Other tasks such as VxWorks upgrade, etc.

7. GLAST LAT Project4.1.7 Dec 15’03 V 7 Command & Telemetry Database Three Pieces –Utility to capture & edit the information (python) –The information itself (xml files) –Software to respond to telecommand / generate telemetry (data stmts) Utility –Prototyped a version allowing entry into a ‘neutral’ database Will export in a variety of formats –ITOS –Autogen FSW code tables –Autogen documentation (web and full doc) Test output in ITOS format sent to NRL to try on the SIIS Information –Two extensives documents defining Telecommands/Telemetry for File System / Memory Dumps / Task Status / Memory Usage Critical Housekeeping information Software –Critical Housekeeping gathering/reporting in design phase To Do –Move utility from prototype to production quality code –Implement critical housekeeping code

8. GLAST LAT Project4.1.7 Dec 15’03 V 8 Near term activities (jan) testing of EM1 Build –TRK/CAL/DAQ configuration –Event Filtering Demonstration of flight crate boot Demonstrate software control of GASU –Configuration –Control and readout Table driven cmd server prototype EM2 event server prototype Housekeeping design & toy version of code

9. GLAST LAT Project4.1.7 Dec 15’03 V 9 Additional Tasks in next 3 Months Design Internal LAT Software Communication Protocols –Communication task-to-task and CPU-to-CPU Framework (mode control) –What commands can be sent in various modes EM1 packages have been tested, but no formalized reports –EM1 packages were extensively tested before delivery to I&T Detailed Unit testing of EM2 packages (uses EM1 packages) Design Software watchdog Support test-bed effort with software

10. GLAST LAT Project4.1.7 Dec 15’03 V 10 More short term tasks –Incorporate GASU/PDU/EPU code to complete software for test- bed –SIB thermal control/main power switch driver (minor, just register writes) –Service level software for EBM/AEM to be tested with hardware –Service level software for inter-task communication –Finish/test health/housekeeping code –Applications level software scheduled for EM2/FU –Testing

11. GLAST LAT Project4.1.7 Dec 15’03 V 11 PMCS next 2 months…

12. GLAST LAT Project4.1.7 Dec 15’03 V 12 PMCS next 2 months…