GSFC/NGIMS-FSW-01 Contour/NGIMS Flight Software Management Plan Prepared By: Michael Paulkovich, Lead Software Engineer for NASA/GSFC Code 915 Laboratory for Planetary Atmospheres January 15, 2002 Rev 1.4 Table of Contents 1. INTRODUCTION 3 1.1 Identification 3 1.2 Overview 3 1.3 Applicable Documents 4 2. WORK IMPLEMENTATION PLANNING 4 2.1.1 Requirements, Development and Test Cycle 5 2.2.1 SLOC Estimates 5 2.2.2 Man-Hour Estimates 5 2.2.3 Schedule 5 2.3 Testbed Development 7 2.3.1 IESA Sim Functionality 7 2.3.2 CDS Sim Functionality. 8 2.4 Evolution of Sims 9 2.5 Software Testing 9 2.6 Configuration Management 9 2.7 QA 10 2.8 Documentation 10 ACRONYMS 11 1. INTRODUCTION 1.1 Identification This document describes the management plan for the Neutral Gas & Ion Mass Spectrometer software identified as follows: Program Set Name: NGIMS Flight Software Release: FM Version Number: n/a Release Number: n/a Project: Contour Parent System: Contour Spacecraft This document is a supplement to the general management plan in the Code 915 ISO 9000 Plan for FSW Development, customized for CONTOUR/NGIMS, and includes implementation planning for related ground software. 1.2 Overview Contour/NGIMS is a quadrupole mass spectrometer system for the Contour spacecraft. The controlling microprocessor is a 1750A (Marconi MA31750) running at 8 MHz, with 64KW primary RAM, 64 KW ROM, 128 KW EEPROM, and 32 KW "extra" (I/O-mapped) RAM. The programming languages used are Ada (Tartan compiler system) and 1750 assembly. Contour/NGIMS software resides in the 1750 computer and interfaces to proprietary I/O devices which in turn interface to both the instrument subsystems, and to the Contour S/C CDS (Command and Data System) via 1553 bus. Refer to figure 1-1. Contour/NGIMS software will be developed with some software re-use from Cassini INMS flight software. Anticipated areas of significant change are: TM - modification to packet formats and rates TC - slight modification of TCs CDS - total re-write of S/C interface (old INMS "BIU" and "CDS") Useq - Microsequencer (Useq) formats will change DAC - signal changes DCON, AMux - signal changes, move to Useq interface EEPROM - add access to EEPROM with code reuse from Cassini GCMS Scanning - implement Round Robin and Adaptive Scanning mode. Figure 1-1 NGIMS Interfaces, Flight Configuration 1.3 Applicable Documents TBS 2. WORK IMPLEMENTATION PLANNING This section defines the Work Implementation Plan. Refer also to the Code 915 ISO 9000 Plan for FSW Development. The following sections complete the work implementation planning in that document for CONTOUR/NGIMS. 2.1.1 Requirements, Development and Test Cycle Refer to GSFC/NGIMS-915-FSW, Code 915 FSW Development Procedures. 2.2.1 SLOC Estimates Refer to GSFC/NGIMS-FSW-02, Contour/NGIMS Flight Software Source Lines Of Code Estimates. Summary of SLOC estimates: a) 100% Reuse - TBS b) Reused with modification - TBS c) New code - TBS d) Possible Improvements - package Logical -- TBS package Spacecraft -- TBS 2.2.2 Man-Hour Estimates Refer to GSFC/NGIMS-FSW-03, Contour/NGIMS Flight Software Man-Hour Estimates. Summary of man-hour estimates: 1 person REVIC Schedule TBS 2 persons REVIC Schedule TBS 2.x Software Build Plan 2.x Software reuse plans 2.2.3 Schedule insert "contour schedule.doc" here 2.3 Testbed Development This section describes Testbed Development. Refer also to the Code 915 ISO 9000 Plan for FSW Development. 2.3.1 IESA Sim Functionality The preliminary Instrument Electronics Sub-Assembly (IESA) Sim should be capable of communicating with the NGIMS FC with the following functionality: - Accept operator entry of canned values to be placed in the MicroSeq data block. The data block consists of: Counter1, Counter2 RFMon Mux Data - Read MicroSeq command block periodically for each Integration Period (IP). Although the flight hardware will have an IP of 10 ms, the preliminary IESA Sim may operate slower if necessary. The command block consists of: Vac, Vdc, FreqSel DAC data Valve control Filament on/off control - Provide a step mode wherein each IP is "pulsed" individually by operator keystroke. - Following reading of the command block: output a MicroSeq Data Block: Preliminary Version Secondary Release Counter1, Counter2 2 values set by user Canned or Table lookup as function of amu# RFMon value set by user same Mux Data 1 value set by user Canned or Table lookup as function of Mux ID# - Display status information in alphanumeric format: Command block - Vac, Vdc, FreqSel (hex) DAC data (hex) Valve control (binary) Filament on/off control (binary) Data block information - Counter1, Counter2 (hex) RFMon (hex) Mux Data (hex) Simulator status - valve positions filament switch positions mode (stop/run/step) errors, error counts IP count - Display information in graphical format: Preliminary Version Secondary Release Vac, Vdc n/a plot - Error checking: Invalid Amux address 2.3.2 CDS Sim Functionality. The preliminary CDS Sim should be capable of communicating with the NGIMS FC with the following functionality: - Accept operator entry of mode data for the STM message - Generate and periodically transmit the STM message - Provide a step mode wherein each STM is "pulsed" individually by operator keystroke. - Accept operator entry of TC data and transmit the TC - Read packetized TM periodically. - Read nonpacketized TM periodically. - Display status information in alphanumeric format: STM packetized TM nonpacketized TM TCs transmitted simulator status - mode (stop/run/step) errors, error counts STM counter TM counters TC counter - Display information in graphical format: n/a - Error checking: TM Sequence count error TM header error TBD GSE Functionality (Responsibility of SPRL) Figure 2.2.2-1 NGIMS Interfaces, Testbed Configuration 2.4 Evolution of Sims After preliminary sims have supported initial development, more elaborate simulators are necessary. This include more realistic emulation of hardware, and exact interface protocols and formats. Use of OTS sims may be considered, such as: TBS 2.5 Software Testing Refer to GSFC/NGIMS-915-FSW, "Code 915 FSW Development Procedures," §2.5. 2.6 Configuration Management Refer to GSFC/NGIMS-FSW-51 (Instrument Software Configuration Management Plan). 2.7 QA Quality is assured via the test requirements (§2.5), CM procedures (GSFC/NGIMS-FSW-51, Instrument Software Configuration Management Plan), and procedures in GSFC/915/FSW-01, "Flight Software Development Procedures and Quality Assurance." 2.8 Documentation Refer to GSFC/NGIMS-915-FSW, Code 915 FSW Development Procedures. END Acronyms CDS Command Data System C&UT Code & Unit Test CE Cognizant Engineer CM Configuration Management Co-I Co-Investigator DA Design Analysis DFD Data Flow Diagram DR Design Review; Delivery Report ECP Engineering Change Proposal EM Engineering Model FM Flight Model FS Flight Spare FSW Flight Software H/SIT Hardware/Software Integration Testing IOC Initial Operational Capability IESA Instrument Electronics Sub-Assembly NRCA Non-Conformance Reporting and Corrective Action PI Principle Investigator RA Requirements Analysis RDD Release Description Document S/C Spacecraft SC Stored Command SCP Stored Command Processor SDD Software Design Document SIS Software Interface Specification SMP Software Management Plan SRD Software Requirements Document SRR Solid State Recorder S/S Subsystem STR Software Trouble Report SVVP Software Validation and Verification Plan SW Software TC Telecommand TM Telemetry TR Test Report WOA Work Order Authorization GSFC/FSW-01-SMP Page 4