LNEXT-SC-REQ-0029 Landsat Next Spacecraft Contract Data Requirements List (CDRL) and Data Item Descriptions (DID) Rev - Draft 5 20251203 2.pdf

LNext SC CDRL & DID DRAFT LNEXT-SC-REQ-0029 Revision -ii

Landsat Next Spacecraft Contract Data Requirements List (CDRL) and Data Item Descriptions (DID)

Signature/Approval Page

Prepared by:

Stephen McKim Date Landsat Next Deputy Mission System Engineer NASA/GSFC, Code 599

Approved by:

Charles Bacon Date Landsat Next Observatory Manager NASA/GSFC, Code 429

Ross Henry Date Landsat Next Project Manager NASA/GSFC, Code 426

Evan Webb Date Landsat Next Mission System Manager NASA/GSFC, Code 599 iii

CM Foreword This document is a Landsat Next Project Configuration Management (CM)-controlled document.

Changes to this document require prior approval of the applicable Configuration Control Board (CCB) Chairperson or designee. Proposed changes shall be submitted to the Landsat Next CM Office (CMO), along with supportive material justifying the proposed change. Changes to this document will be made by complete revision.

Questions or comments concerning this document should be addressed to:

NASA/Goddard Space Flight Center Landsat Next Project Office, Code 426 Attention: Configuration Management Office Greenbelt, Maryland 20771 iv

Change History Log Change History will be provided by CM prior to release v

Table of Contents SIGNATURE/APPROVAL PAGE ................................................................................................ II CM FOREWORD ..........................................................................................................................III CHANGE HISTORY LOG .......................................................................................................... IV

TABLE OF CONTENTS ................................................................................................................ V

LIST OF FIGURES ...................................................................................................................... VI LIST OF TABLES ........................................................................................................................ VI

1.0 INTRODUCTION

2.0 DEFINITION OF DUE DATES/MATRUITY, DEFINITION OF CATEGORIES, AND

MAILING DISTRIBUTION INSTRUCTIONS

2.1 Due Dates - Related Definitions

2.1.1 Due Date

2.2 Maturity

2.3 Category

2.4 Media

3.0 LNEXT CONTRACT DATA REQUIREMENTS LIST

3.1 CDRL Table

3.1.1 Program Management Data

3.1.2 Review Data

3.1.3 Software Data

3.1.4 Integration and Test Data

3.1.5 Systems Engineering Data

3.1.6 Launch Vehicle Data

3.1.7 Simulator Data

3.1.8 Operations Data

3.1.9 Spacecraft Data

3.1.10 Systems Assurance Data

4.0 DESCRIPTION OF REQUIRED DATA

4.1 Program Management Data

4.2 Review Data

4.3 Software Data

4.4 Integration and Test Data

4.5 Systems Engineering Data

4.6 Launch Vehicle Data

4.7 Simulator Data

4.8 Operations Data

4.9 Spacecraft Data

4.10 Systems Assurance Data

vi

List of Figures No table of contents entries found.

List of Tables No table of contents entries found.

1.0 INTRODUCTION

This Contract Data Requirements List (CDRL) document defines the requirements for deliverable documentation to be provided by the Spacecraft (SC) Contractor. Section 2.0 includes definitions and instructions for mailing and/or distribution. The table in Sections 3.1.1 through 3.1.8 present the CDRL item by item, with due dates, and media format. Section 4.0 provides the Description of Required Data (DRD) or Data Item Descriptions (DIDs), a description of each item, which describes the use for the deliverable and the required preparation information; except where specifically indicated to the contrary, the formats and drawing standards used shall be those normally used by the SC Contractor and by its Subcontractors.

2.0 DEFINITION OF DUE DATES/MATRUITY, DEFINITION OF

CATEGORIES, AND MAILING DISTRIBUTION INSTRUCTIONS

2.1 DUE DATES - RELATED DEFINITIONS

The following definitions apply to the DUE DATE column in the tables in Section 3.1.1 through

3.1.8. Unless otherwise specified, deadlines are in calendar days. Submissions can be made before the due date if the Contractor believes that no changes will be made between the submittal date and the due date.

2.1.1 Due Date

DUE DATE: The contract baseline schedule for delivery of SOW CDRL items is shown in the CDRL tables in Sections 3.1.1 through 3.1.8; items in the schedule for delivery are associated with acronyms for the various program reviews that form the contract baseline. Items designated for delivery "As Generated", or "Update As Required (UAR)" shall be provided to the Government within the timeframe specified in the table or as agreed to by the Government.

Monthly: Submitted on monthly basis L: Launch Date DACA: (Calendar) Days After Contract Award NLT: No later than Other entries in the "DUE DATE" column are self-explanatory.

2.2 MATURITY

The following definitions apply to the MATURITY column in the tables in Sections 3.1.1 through 3.1.8.

(1) Initial: The first submission of an item, which will be revised and resubmitted at a later date.

(2) Preliminary: An early submission of an item. To be completed as is practicable at the time of preparation. Preliminary submittals are written with the best available current information and are resubmitted when further information becomes available.

(3) Final: The complete, thorough submission of an item for approval, review, or information that, to the best of the Contractor’s knowledge and intention, will not require further revision or updates. However, this type of submission does not preclude updating if later found to be necessary. Any updates shall require the same "approval/review" process as was required for the original final submissions.

(4) Baseline, Current: The delivery is written with the best up-to-date information available at the time.

(5) Update: The delivery is revised with the best up-to-date information available at the time.

Other entries in the "MATURITY" column are self-explanatory.

2.3 CATEGORY

The following definitions apply to the CATEGORY column in the tables in Sections 3.1.1 through 3.1.8. If separate approval instructions are not specified for separate submission due date/maturity items, then the listed approval instruction applies to all submissions.

A Approval. CDRL items in this category require approval by the GSFC Contracting Officer’s

Representative (COR) or Contracting Officer (CO) prior to use by the Contractor. Receipt by the Government shall occur within the time specified in the "Due Date" column in the tables in Sections 3.1.1 through 3.1.8 of this document.

Requirements for re-submission shall be as specified by the Contracting Officer or Contracting Officer's Representative. In most cases, the Contractor will be required to resubmit the document within 14 calendar days of receiving comments from the Government. If the Contractor has not received a response from GSFC within 45 calendar days of delivery of a CDRL item, the Contractor may proceed as if the document has been approved.

R Review. Documents in this category require delivery to the Government prior to use and within the time period specified in the "Due Date" column in the tables in Sections 3.1.1 through 3.1.8 of this document. They are subject to evaluation by the Government or its designated representatives to determine Contractor effectiveness in meeting Contract objectives. Upon submission, the Contractor may proceed with associated work while the Government reviews the submission.

I Information. Data in this category shall be delivered to the Government within the time period specified in the “Due Date” column in the tables in Sections 3.1.1 through 3.1.8 for the purpose of determining current program status, progress, and future planning requirements. The Government may request changes on deliverables where errors or omissions are noted.

2.4 MEDIA

All data items shall be delivered in electronic format to a mutually defined web portal that allows external Government and Contractor access unless otherwise noted in the tables in Sections 3.1.1 through 3.1.10.

The CO shall be notified of electronic submission of the deliverable via email.

Electronic deliverables shall be delivered in the following formats unless otherwise approved by the Government:

Text Documents: Portable Document Format (PDF) (searchable) or Microsoft (MS) Word Presentations: PDF (searchable) or MS PowerPoint Spreadsheets: MS Excel Database: Delimited American Standard Code for Information Interchange (ASCII) files accompanied with database schema document defining tables and entries Schedules: PDF (searchable) and MS Project Schematics and Drawings: High-Resolution PDF to be readable

Photographs: Joint Photographic Experts Group (JPEG) or current industry standard Video: Any readily available open standard (e.g., Audio Video Interleave (AVI), Movie Picture Experts Group (MPEG))

3.0 LNEXT CONTRACT DATA REQUIREMENTS LIST

3.1 CDRL TABLE

The tables in Sections 3.1.1 through 3.1.10 comprise the Spacecraft Contract Data Requirements List.

The tables contain the following CDRLs:

Program Management (PM) Reviews (RE) Flight Software (SW) Integration and Test (IT) System Engineering (SE) Launch Vehicle (LV) Simulators (SIM) Spacecraft (SC) Systems Assurance (SA) Operations (OPS)

3.1.1 Program Management Data

CDRL Number CDRL Title Category Due Date and Maturity SOW Reference

LNext-PM-01 Monthly Project Status Reviews

LNext-PM-01: I LNext-PM-01:Monthly, materials -5 days before meeting

LNext-PM-02 Program Security Plan and Inputs to Project Protection Plan

LNext-PM-02-01: R LNext-PM-02-02: I LNext-PM-02-03: I LNext-PM-02-04: I LNext-PM-02-05: I LNext-PM-02-06: I LNext-PM-02-07: I

LNext-PM-02-01:Program Security Plan, DACA +30 days, Final LNext-PM-02-02:PPP Inputs, MSRR -15 days, Preliminary LNext-PM-02-03:PPP Inputs, MPDR -15 days, Updates LNext-PM-02-04:PPP Inputs, MCDR -15 days, Updates LNext-PM-02-05:PPP Inputs, MSIR -15 days, Updates LNext-PM-02-06:PPP Inputs, FRR -15 days, Updates LNext-PM-02-07:PPP Inputs, OAR -15 days, Final

LNext-PM-03 Contractor’s Review Plan LNext-PM-03-01: I LNext-PM-03-02: I

LNext-PM-03-01:DACA +30 days, Draft LNext-PM-03-02:SC SRR -14 days, Final

LNext-PM-04 Security Requirements for Unclassified IT Resources

LNext-PM-04: A LNext-PM-04:DACA +30 days, Final

3.1.2 Review Data

CDRL Number CDRL Title Category Due Date and Maturity SOW Reference LNext-RE-01 Contractor’s Review

Materials LNext-RE-01-01: I LNext-RE-01-02: I

LNext-RE-01-01:Review -7 days, Preliminary LNext-RE-01-02:Review +7 days, As-Presented version.

LNext-RE-02 Inputs to Mission Level Reviews

LNext-RE-02-01: I LNext-RE-02-02: I LNext-RE-02-03: I LNext-RE-02-04: I LNext-RE-02-05: I LNext-RE-02-06: I LNext-RE-02-07: I LNext-RE-02-08: I

LNext-RE-02-01:SC SRR -14 days, Final LNext-RE-02-02:MPDR -14 days, Final LNext-RE-02-03:MCDR -14 days, Final LNext-RE-02-04:MSIR -14 days, Final LNext-RE-02-05:ORR -14 days, Final LNext-RE-02-06:FRR -14 days, Final LNext-RE-02-07:Final LNext-RE-02-08:PLAR -14 days, Final

LNext-RE-03 Test Readiness Review LNext-RE-03-01: I LNext-RE-03-02: I

LNext-RE-03-01:SC CPT Prior to Test Start, Final LNext-RE-03-02:All Observatory Tests Prior to Start, Final

LNext-RE-04 On-Orbit Acceptance Review (OAR)

LNext-RE-04: R LNext-RE-04:OAR -14 days, Final

3.1.3 Software Data

CDRL Number CDRL Title Category Due Date and Maturity SOW Reference LNext-SW-01 Software Management and

Development Plan (SMDP) LNext-SW-01-01: R LNext-SW-01-02: I LNext-SW-01-03: I LNext-SW-01-04: I

LNext-SW-01-01:DACA +30 days, Initial LNext-SW-01-02:SC SRR -30 days, Baseline LNext-SW-01-03:SC PDR -30 days, Update LNext-SW-01-04:SC CDR -30 days, Update

LNext-SW-02 Software Architectural and Detailed Design Description

(SDD)

LNext-SW-02-01: R LNext-SW-02-02: I LNext-SW-02-03: I

LNext-SW-02-01:SC PDR -30 days, Baseline LNext-SW-02-02:SC CDR -30 days, Update LNext-SW-02-03:OIRR -30 days, Update

LNext-SW-03 Software Version Description Document

LNext-SW-03: R LNext-SW-03:With each Software/patch release, Final

LNext-SW-04 Software Requirements Specification

LNext-SW-04-01: A LNext-SW-04-02: R

LNext-SW-04-01:SC PDR -30 days, Initial LNext-SW-04-02:SC CDR -30 days, Baseline

LNext-SW-05 Software Test Plan LNext-SW-05-01: R LNext-SW-05-02: R LNext-SW-05-03: I

LNext-SW-05-01:SC PDR -30 days, Initial LNext-SW-05-02:SC CDR -30 days, Baseline LNext-SW-05-03:OIRR, Update

LNext-SW-06 Software Test Reports (STR) LNext-SW-06: R LNext-SW-06:OIRR -30 days, Final

3.1.4 Integration and Test Data

CDRL Number CDRL Title Category Due Date and Maturity SOW

Reference LNext-IT-01 Observatory Integration and Test

Plan LNext-IT-01-01: I LNext-IT-01-02: R LNext-IT-01-03: A

LNext-IT-01-01:SC CDR -15 days, Preliminary LNext-IT-01-02:OIIRR -30 days, Final LNext-IT-01-03:Obs PER -45 days, EMI/EMC, Dynamics, Thermal Vacuum Specific Plan, Final

LNext-IT-02 Observatory Integration and Test Procedures

LNext-IT-02-01: R LNext-IT-02-02: R

LNext-IT-02-01:Test -60 days, Preliminary LNext-IT-02-02:Test -30 days, Final

LNext-IT-03 Observatory and Simulator Test Data Sets

LNext-IT-03-01: R LNext-IT-03-02: I

LNext-IT-03-01:Test completion +2 days, Preliminary LNext-IT-03-02:Test completion +15 days, Final

LNext-IT-04 Observatory Test Results LNext-IT-04-01: R LNext-IT-04-02: I

LNext-IT-04-01:Test completion +2 days, Preliminary LNext-IT-04-02:Test completion +15 days, Final

LNext-IT-05 Spacecraft Comprehensive Performance Test Plan

LNext-IT-05-01: R LNext-IT-05-01:SC CPT -90 days, Final

LNext-IT-06 EMI/EMC Control Plan LNext-IT-06-01: I LNext-IT-06-02: I

LNext-IT-06-01:SC PDR -30 days, Initial LNext-IT-06-02:Obs PER -60 days, Final

3.1.5 Systems Engineering Data

CDRL Number CDRL Title Category Due Date and Maturity SOW

Reference LNext-SE-01 Engineering Change

Proposals (ECPs), Deviations and Waivers

LNext-SE-01-01: A LNext-SE-01-02: I

LNext-SE-01-01:Class I changes, As generated LNext-SE-01-02:Class II changes, As generated

LNext-SE-02 Micro Meteoroid and Orbital Debris Assessment and End of Mission Plan Inputs

LNext-SE-02-01: I LNext-SE-02-02: I LNext-SE-02-03: I LNext-SE-02-04: I LNext-SE-02-05: I

LNext-SE-02-01:MPDR -45 days, Preliminary ODAR LNext-SE-02-02:MCDR -45 days, Preliminary ODAR LNext-SE-02-03:MSIR, ORSAT Model Inputs, Preliminary LNext-SE-02-04:MPER, ORSAT Model Inputs, Final LNext-SE-02-05:SMSR -60 days, Final ODAR/EOMP

LNext-SE-03 Requirements Verification & Validation (V&V) Plan

LNext-SE-03-01: R LNext-SE-03-02: A LNext-SE-03-03: A

LNext-SE-03-01:SC PDR -10 days, Preliminary LNext-SE-03-02:SC CDR -10 days, Final LNext-SE-03-03:OIIRR -15 days, Update

LNext-SE-04 Requirements Verification Matrix and Verification Artifacts

LNext-SE-04-01: R LNext-SE-04-02: A LNext-SE-04-03: A LNext-SE-04-04: A

LNext-SE-04-01:SC PDR -30 days, Initial LNext-SE-04-02:SC CDR -30 days, Final LNext-SE-04-03:SC Bus CPT +30 days, Updates LNext-SE-04-04:As required, Updates

LNext-SE-05 Fault Management Description Document

LNext-SE-05-01: I LNext-SE-05-02: R LNext-SE-05-03: I

LNext-SE-05-01:SC PDR -14 days, Preliminary LNext-SE-05-02:SC CDR -14 days, Baseline LNext-SE-05-03:FM Test -60 days, Final

LNext-SE-06 DOORS Compatible Database LNext-SE-06-01: I LNext-SE-06-02: I

LNext-SE-06-01:SC SRR -60 days, Preliminary LNext-SE-06-02:Monthly, Updates

LNext-SE-07 Observatory Ground Support Equipment Plan

LNext-SE-07-01: I LNext-SE-07-02: I LNext-SE-07-03: I LNext-SE-07-04: I

LNext-SE-07-01:MPDR -30 days, Preliminary LNext-SE-07-02:MCDR -30 days, Baseline LNext-SE-07-03:Obs PER -30 days, Updates LNext-SE-07-04:PSR -30 days, Final

LNext-SE-08 Observatory & Simulator Acceptance Data Packages

LNext-SE-08-01: A LNext-SE-08-02: A LNext-SE-08-03: A LNext-SE-08-04: A LNext-SE-08-05: A LNext-SE-08-06: A

LNext-SE-08-01:Observatory Data, PSR -60 days LNext-SE-08-02:MOC Site Acceptance Test +15 days, Observatory Operations Simulator LNext-SE-08-03:RF Suitcase Acceptance Test +15 days, RF Suitcase LNext-SE-08-04:CTSS MOC Site Acceptance Test +15 days, CTSS

LNext-SE-08-05:SoftSim MOC Site Acceptance Test +15 days, SoftSim LNext-SE-08-06:LVIS Acceptance Test +15 days, LVIS

LNext-SE-09 Engineering Drawings and Drawing Tree

LNext-SE-09-01: I LNext-SE-09-02: I

LNext-SE-09-01:SC PDR -30 days, Drawing Tree LNext-SE-09-02:SC CDR -30 days, Baseline

CDRL Number CDRL Title Category Due Date and Maturity SOW Reference

LNext-SE-09-03: R LNext-SE-09-04: R

LNext-SE-09-03:As Generated +15 days, As Built, Updates LNext-SE-09-04:Launch -30 days, Final

LNext-SE-10 Dynamics Model Validation Plan and Report

LNext-SE-10-01: I LNext-SE-10-02: R LNext-SE-10-03: I LNext-SE-10-04: R

LNext-SE-10-01:SC PDR -30 days, Initial Plan LNext-SE-10-02:SC CDR -30 days, Final Plan LNext-SE-10-03:SC CDR +30 days, Initial Report LNext-SE-10-04:Post Test CPT +30 days, Final Report

LNext-SE-11 Spacecraft Bus End Item Data Package

LNext-SE-11-01: I LNext-SE-11-02: A

LNext-SE-11-01:SC Bus CPT -30 days, Initial LNext-SE-11-02:SC Bus CPT +30 days, Final

3.1.6 Launch Vehicle Data

CDRL Number CDRL Title Category Due Date and Maturity SOW Reference LNext-LV-01 Launch Site Ground Operations

Plan LNext-LV-01-01: R LNext-LV-01-02: R LNext-LV-01-03: R

LNext-LV-01-01:SC CDR -45 days, Preliminary LNext-LV-01-02:OIRR -15 days, Updates LNext-LV-01-03:PSR -120 days, Final

LNext-LV-02 Launch Site Test Procedures LNext-LV-02-01: R LNext-LV-02-02: A

LNext-LV-02-01:PSR -90 days, Preliminary LNext-LV-02-02:Obs shipment -30 days, Final

LNext-LV-03 Launch Commit Criteria LNext-LV-03-01: I LNext-LV-03-02: I LNext-LV-03-03: I

LNext-LV-03-01:MOR -90 days, Preliminary LNext-LV-03-02:ORR -30 days, Update LNext-LV-03-03:FOR -30 days, Final

3.1.7 Simulator Data

CDRL Number CDRL Title Category Due Date and Maturity SOW Reference LNext-SIM-01 Simulator Verification and

Acceptance Test Plan LNext-SIM-01-01:

R LNext-SIM-01-02:

R

LNext-SIM-01-01:SC PDR -15 days, Preliminary LNext-SIM-01-02:Simulator Integration Start -60 days, Final

LNext-SIM-02 Simulator Acceptance Test Procedures and As-Run Procedure Artifacts

LNext-SIM-02-01:

I LNext-SIM-02-02:

I LNext-SIM-02-03:

R

LNext-SIM-02-01:Simulator Acceptance Test Start -45 days, Preliminary Test Procedures LNext-SIM-02-02:Simulator Acceptance Test Start -14 days, Final Test Procedures LNext-SIM-02-03:Sim Acceptance Test Completion +10 days, Test As-Run Procedures & Artifacts

LNext-SIM-03 Simulator's User's Guide and Training Materials

LNext-SIM-03-01:

R LNext-SIM-03-02:

I LNext-SIM-03-03:

I LNext-SIM-03-04:

I LNext-SIM-03-05:

I

LNext-SIM-03-01:User Guide, Simulator Deliveries -45 days, Preliminary LNext-SIM-03-02:User Guide, With Simulator Delivery, Final LNext-SIM-03-03:Training Materials, Training Date, Final LNext-SIM-03-04:

LNext-SIM-03-05:

LNext-SIM-04 Simulator Development Plan LNext-SIM-04-01:

I LNext-SIM-04-02:

R

LNext-SIM-04-01:DACA +60 days, Preliminary LNext-SIM-04-02:SC SRR -15 days, Final

3.1.8 Operations Data

CDRL Number CDRL Title Category Due Date and Maturity SOW

Reference LNext-OPS-01 Flight Operations Team (FOT)

Training Materials LNext-OPS-01-01: R LNext-OPS-01-02: I LNext-OPS-01-03: I

LNext-OPS-01-01:Training Session #1 -60 days, Final LNext-OPS-01-02:Training Session #2 -30 days, Updates LNext-OPS-01-03:Training Materials, At OAR, Updates

LNext-OPS-02 On-Orbit Commissioning and Operations Support Plan

LNext-OPS-02-01: I LNext-OPS-02-02: I LNext-OPS-02-03: R LNext-OPS-02-04: I

LNext-OPS-02-01:SC CDR +15 days, Preliminary LNext-OPS-02-02:First Scheduled MRT -180 days, Update LNext-OPS-02-03:Obs CPT +30 days, Update LNext-OPS-02-04:PSR -90 days, Final

LNext-OPS-03 Space to Operations Interface Documentation

LNext-OPS-03-01: I LNext-OPS-03-02: I LNext-OPS-03-03: R LNext-OPS-03-04: I

LNext-OPS-03-01:SC PDR, Preliminary LNext-OPS-03-02:SC CDR, Update LNext-OPS-03-03:OIRR, Final LNext-OPS-03-04:Update

LNext-OPS-04 Inputs to On-Orbit Operations and Contingency Procedures

LNext-OPS-04-01: R LNext-OPS-04-02: R LNext-OPS-04-03: A LNext-OPS-04-04: R

LNext-OPS-04-01:Test or Simulation Event -180 days LNext-OPS-04-02:SC CDR +30 days, Preliminary LNext-OPS-04-03:PSR -30 days, Launch Baseline LNext-OPS-04-04:OAR, Final

LNext-OPS-05 Spacecraft User's Manual LNext-OPS-05-01: I LNext-OPS-05-02: R LNext-OPS-05-03: I LNext-OPS-05-04: I LNext-OPS-05-05: R

LNext-OPS-05-01:SC CDR -15 days, Preliminary LNext-OPS-05-02:SC Bus CPT +60 days, Updates LNext-OPS-05-03:First Mission Sim -90 days, Update LNext-OPS-05-04:PSR -30 days, Final Pre-launch version LNext-OPS-05-05:OAR, Final

LNext-OPS-06 Observatory Command and Telemetry Handbook & Database (per Observatory)

LNext-OPS-06-01: R LNext-OPS-06-02: I LNext-OPS-06-03: I LNext-OPS-06-04: I LNext-OPS-06-05: R LNext-OPS-06-06: I

LNext-OPS-06-01:MCDR -90 days, Preliminary LNext-OPS-06-02:MCDR +90 days, Update LNext-OPS-06-03:Start of Obs I&T -15 days, Update LNext-OPS-06-04:Obs CPT -30 days, Update LNext-OPS-06-05:Obs CPT +30 days, Final LNext-OPS-06-06:Approx. every 3 months until final On- Orbit acceptance, Updates

LNext-OPS-07 Observatory Constraints, Restrictions, and Warnings Document

LNext-OPS-07-01: R LNext-OPS-07-02: I LNext-OPS-07-03: R LNext-OPS-07-04: I

LNext-OPS-07-01:MCDR, Preliminary LNext-OPS-07-02:OIRR, Updates LNext-OPS-07-03:PSR -15 days, Final Pre-Launch Version LNext-OPS-07-04:OAR, Final

LNext-OPS-08 Operationally Delivered Tools Documentation and Training

LNext-OPS-08: I LNext-OPS-08:In conjunction with tool delivery and updates, As Generated

3.1.9 Spacecraft Data

LNEXT-SC-

REQ-0029 Draft Rev -

CDRL Title Category Due Date and Maturity SOW Reference

LNext-SC-01 Observatory Thermal Models and Analysis

LNext-SC-01-01: I LNext-SC-01-02: R LNext-SC-01-03: I LNext-SC-01-04: I LNext-SC-01-05: R LNext-SC-01-06: R LNext-SC-01-07: I

LNext-SC-01-01:MPDR -30 days, Preliminary LNext-SC-01-02:MCDR -30 days, Update LNext-SC-01-03:Observatory TB/TV -30 days, Update (Test Model) LNext-SC-01-04:Observatory TB/TV +60 days, Final (Correlated) LNext-SC-01-05:Reduced Launch Model, LRD-24 Months or as specified by Launch Services Provider, Preliminary LNext-SC-01-06:Reduced Launch Model, LRD-18 Months or as specified by Launch Services Provider, Updated LNext-SC-01-07:As generated, Updates

LNext-SC-02 Mass Properties Report LNext-SC-02-01: R LNext-SC-02-02: I LNext-SC-02-03: I LNext-SC-02-04: R

LNext-SC-02-01:MPDR, Preliminary LNext-SC-02-02:MCDR, Updates LNext-SC-02-03:PER and as Required by Launch Service Provider, Updates LNext-SC-02-04:PSR, Final

LNext-SC-03 Observatory Mechanical Models and Analyses

LNext-SC-03-01: I LNext-SC-03-02: R LNext-SC-03-03: I

LNext-SC-03-01:Completion of CLA cycle, FEA Models, Updates LNext-SC-03-02:Obs PER -15 days, Analysis Report, Initial LNext-SC-03-03:PSR -180 days, FEA Models & Analyses, Final

LNext-SC-04 Attitude Control and Pointing Analyses

LNext-SC-04-01: I LNext-SC-04-02: R LNext-SC-04-03: I

LNext-SC-04-01:MPDR -30 days, Initial LNext-SC-04-02:MCDR -14 days, Update LNext-SC-04-03:Final FEM Delivery -30 days, Final

LNext-SC-05 Observatory Level Structural, Thermal, Optical Precision (STOP) analysis

LNext-SC-05-01: I LNext-SC-05-02: I LNext-SC-05-03: I

LNext-SC-05-01:MPDR -30 days, Initial LNext-SC-05-02:MCDR -30 days, Update LNext-SC-05-03:PSR -180 days, Final

LNext-SC-06 Observatory Flight Dynamics and Orbital Maintenance Analysis

LNext-SC-06-01: I LNext-SC-06-02: I LNext-SC-06-03: I

LNext-SC-06-01:MPDR -14 days, Preliminary LNext-SC-06-02:MCDR -14 days, Update LNext-SC-06-03:Obs PER, Final

LNext-SC-07 RF Link Analysis and BER Analysis

LNext-SC-07-01: I LNext-SC-07-02: R LNext-SC-07-03: I

LNext-SC-07-01:MPDR -60 days, Preliminary LNext-SC-07-02:MCDR -60 days, Final LNext-SC-07-03:RF Compat +60 days, Updates

LNext-SC-08 Observatory Power System Performance Analysis/Energy Balance

LNext-SC-08-01: I LNext-SC-08-02: I

LNext-SC-08-01:MPDR -14 days, Preliminary LNext-SC-08-02:MCDR -14 days, Final

LNEXT-SC-

REQ-0029 Draft Rev -

CDRL Title Category Due Date and Maturity SOW Reference

LNext-SC-09 C&DH and Electrical Subsystem Performance Analysis

LNext-SC-09-01: I LNext-SC-09-02: I

LNext-SC-09-01:SC PDR -30 days, Preliminary LNext-SC-09-02:SC CDR -30 days, Final

LNext-SC-10 Battery Handling Plan LNext-SC-10-01: I LNext-SC-10-02: R LNext-SC-10-03: I

LNext-SC-10-01:SC PDR -30 days, Preliminary LNext-SC-10-02:PSR -45 days, Final LNext-SC-10-03:As generated, Updates

LNext-SC-11 Observatory Storage, Transportation and Handling Plan

LNext-SC-11-01: R LNext-SC-11-02: R LNext-SC-11-03: I

LNext-SC-11-01:OIRR -60 days, Initial LNext-SC-11-02:PSR -90 days, Final LNext-SC-11-03:As generated, Updates

LNext-SC-12 Observatory Contamination Analyses

LNext-SC-12-01: I LNext-SC-12-02: I LNext-SC-12-03: I LNext-SC-12-04: I LNext-SC-12-05: I LNext-SC-12-06: I LNext-SC-12-07: I LNext-SC-12-08: I

LNext-SC-12-01:SC SRR -30 days, Preliminary derivation of contamination requirements from performance allowances & Launch Induced particle redistribution LNext-SC-12-02:MPDR -30 days, Preliminary On-orbit outgassing and mass transport, thruster plume impingement/heating LNext-SC-12-03:MPDR +60 days, Final derivation of contamination requirements from performance allowances LNext-SC-12-04:MCDR +60 days, Final On-orbit outgassing and mass transport and thruster plume impingement/heating LNext-SC-12-05:MCDR +30 days, Update Launch Induced particle redistribution LNext-SC-12-06:MPSR -45 days, Final Launch Induced particle redistribution LNext-SC-12-07:Launch -660 days, Preliminary Venting analysis LNext-SC-12-08:Launch -420 days, Final Venting analysis

LNext-SC-13 Observatory Charging Analysis Model

LNext-SC-13-01: I LNext-SC-13-02: I LNext-SC-13-03: R

LNext-SC-13-01:SC PDR -30 days, Preliminary LNext-SC-13-02:SC CDR -30 days, Updates LNext-SC-13-03:OIRR -45 days, Final

3.1.10 Systems Assurance Data

CDRL Number CDRL Title Category Due Date and Maturity SOW Reference LNext-SA-01 Supplier List LNext-SA-01: I LNext-SA-01:SC CDR -30 days, Final LNext-SA-02 Safety Requirements Compliance

Checklist LNext-SA-02-01: R LNext-SA-02-02: R

LNext-SA-02-01:SC SRR -30 days, Preliminary LNext-SA-02-02:SC PDR -30 days, Final

LNext-SA-03 Safety Data Package LNext-SA-03: A LNext-SA-03:CDR -60 days, Baseline LNext-SA-04 Hazard Verification Tracking Log LNext-SA-04: A LNext-SA-04:PSR -120 days, Initial LNext-SA-05 FMECA & CIL LNext-SA-05-01: R

LNext-SA-05-02: R LNext-SA-05-03: I

LNext-SA-05-01:SC PDR -30 days, Preliminary LNext-SA-05-02:SC CDR -30 days, Baseline LNext-SA-05-03:Each Milestone review up to LRR -30 days, Update

LNext-SA-06 Software Assurance Plan LNext-SA-06-01: I LNext-SA-06-02: R LNext-SA-06-03: I

LNext-SA-06-01:SC SRR -30 days, Preliminary LNext-SA-06-02:SC PDR -15 days, Final LNext-SA-06-03:SC CDR -30 days, Update

LNext-SA-07 Master EEE Parts List LNext-SA-07-01: I LNext-SA-07-02: I

LNext-SA-07-01:SC PDR -30 days, Initial LNext-SA-07-02:As Generated, Updates

LNext-SA-08 Materials Identification and Usage List & Materials Usage Agreements

LNext-SA-08-01: I LNext-SA-08-02: I LNext-SA-08-03: I

LNext-SA-08-01:SC PDR, Initial LNext-SA-08-02:OIRR, Final LNext-SA-08-03:MUAs, As Generated, Final

LNext-SA-09 Contamination Control Plan LNext-SA-09: I LNext-SA-09:SC PDR -30 days, Final LNext-SA-10 End Item Data Package LNext-SA-10: A LNext-SA-10:PSR -30 days, Final

4.0 DESCRIPTION OF REQUIRED DATA

4.1 PROGRAM MANAGEMENT DATA

CDRL No.: LNext-PM-01 Title: Monthly Project Status Reviews Reference:

Related Documents:

Use:

To evaluate contract status. These reports and meetings will be used to provide an opportunity for face-to-face discussions between the Contractor and the Government regarding project status, plans and issues.

Preparation Information:

The contractor shall prepare and deliver the following:

• Monthly accomplishments

• Technical progress status

• FSW development status and any problem reports

• Requirements verification status

• Technical Performance Metrics summary, status and margins

• Class I changes/waivers status

• Anomaly and/or Material Review Board status and updates, including all non-conformances that effect form, fit and function

• Anomalous facility and hardware cleanliness conditions, if any

• Hardware qualification/acceptance status

• Top Risks and current mitigation status

• Integrated Master Schedule (IMS), its status with critical paths and margins

• Supply chain issues

• GIDEP alerts and disposition

• Upcoming milestones and preparation status

• Contract deliverable status

• Organization breakdown structure to discipline level (for first MPSR only)

• Component procurement status, including status of subcontract awards

• Spare hardware status and any changes to nominal sparing plan

• Special studies progress (as applicable)

CDRL No.: LNext-PM-02 Title: Program Security Plan and Inputs to Project Protection Plan

Reference:

Related Documents:

• NASA Information Security Policy, NPD 2810.1

• Security of Information and Information Systems, NPR 2810.1

• Space System Protection Standard, NASA-STD-1006

• Department of Defense Contract Security Classification Specification, DD 254

• Landsat Next Key Management Plan, LNEXT-MGMT-PLAN-0039

• Landsat Next Project Protection Plan, LNEXT-SYS-PLAN-0027 Use:

The purpose of the Program Security Plan is to address operational security and Physical, Information/Information Technology (IT), Software, Personnel, and Industrial Security aspects of the program.

This also covers inputs to the Project Protection Plan, which describes how the mission is resilient to threats.

Preparation Information:

The contractor shall provide their program security plan that addresses the following:

• Describe the risk-based approach to mitigating vulnerabilities and the artifacts to be delivered to support this process.

• Describe the approach to identify and the types of security events captured by the spacecraft to detect anomalous behavior that may be indicative of compromise or malicious activity in the system.

• Describe the approach to identify in a timely and periodic manner, any cyber incidents.

• Describe the process to implement software updates/upgrades/patches and to check for malware prior to load.

• Describe the use of cryptography in acceptance of all hardware, software and firmware deliveries.

• Describe the comprehensive cybersecurity approach to software development and software assurance across the development lifecycle (e.g. signed code, mature configuration management processes, static/dynamic code analysis, complexity checking, pen testing, threat modeling/testing, regular cross check of BOMs, including the use of Independent Verification & Validation or other 3rd party assessors).

• Describe the approach to participate in the threat and vulnerability assessment process and approach and be responsive to requests for information involving threats, vulnerabilities and developing mitigations / countermeasures for use in the Project Protection Plan.

• Describe the comprehensive approach to cybersecurity that includes the appropriate security controls for both the corporate infrastructure (including protection of sensitive information such as CUI), any development networks and the system(s) that are to be delivered as the spacecraft.

CDRL No.: LNext-PM-03 Title: Contractor’s Review Plan Reference:

Related Documents:

Use:

To provide the project insight and understanding of contractor’s review planning, timing and approach.

Preparation Information:

The contractor shall prepare and deliver their review plan aimed at ensuring systematic evaluations at key project milestones for assessing readiness, identifying risks, and confirming alignment with contract objectives. The plan shall include the purpose, timing, objectives, and success criteria for each review.

CDRL No.: LNext-PM-04 Title: Security Requirements for Unclassified IT Resources

Reference:

Related Documents:

• Security and Privacy Controls for Information Systems and Organizations, NIST SP 800-53

• NASA specific guidance for the implementation of NIST SP 800-53 control families, ITS-HBK-2180 Use:

To ensure that IT security reporting requirements are met for all IT systems utilized during work associated with this contract and necessary training requirements are fulfilled.

Preparation Information:

Distribution: Electronic Submission to the CO, COR, NASA Organization’s Information System Security Officer (ISSO) (i.e., Security Officer). Approval will be provided by the ISSO.

Initial Submission:

IT Security Plan(s): For contractor-owned systems, due at the start of phase-in. Initial submission not required for existing, approved plans for Government-owned and Contractor-managed systems.

Non-Federal System Certification: Prior to any transfer of NASA non-public information to the contractor, the contractor shall provide documentation of the certification of the non-federal system to the security officer of the NASA organization that owns the information (typically the organization responsible for the contract).

Information on Employees in Sensitive Positions/Assignments Report: At the start of phase-in IT Security Point of Contact: At the start of phase-in IT Security Awareness Training: Training required prior to access to NASA information and systems IT Security Role Based Training: Foundational training is provided prior to performance of assigned role. Initial evidence showing completion due at the end of phase-in.

Submission Frequency:

IT security Plan(s): As Required Non-Federal System Certification: Annually Information on Employees in Sensitive Positions/Assignments Report: Annually IT Security Point of Contact: As Required IT Security Awareness Training: Annual on anniversary date of initial training IT Security Role Based Training: Annual on anniversary date of initial training. Evidence of completion due annually.

Format: Unless otherwise directed, the data requested in this DRD shall be delivered to the Government in soft-copy via an electronic transfer mechanism (e.g., electronic mail, flash drive, or file transfer protocol) in a format readable by a Government device utilizing the standards in NASA-STD-2804, “Minimum Interoperability Software Suite.”

Interrelationship: PWS/SOW Section X.X, Applicable Documents:

FAR 52.204-21, Basic Safeguarding of Covered Contractor Information Systems FAR 52.204–29, Federal Acquisition Supply Chain Security Act Orders-Representation and Disclosures FISMA 2014, Federal Information Security Modernization Act 2014 NFS 1852.204-76, Security Requirements for Unclassified IT Resources NFS 1852.223-75, Major Breach of Safety or Security NFS 1852.237-72, Access to Sensitive Information NFS 1852.237-73, Release of Sensitive Information NFS 1852.239-73, Review of the Offeror’s Information Technology Systems Supply Chain NFS 1852.239-74, Information Technology System Supply Chain Risk Assessment NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations NIST SP 800-53, Security and Privacy Controls for Information Systems and Organizations NPR 1382.1, NASA Privacy Procedural Requirements NPD 2810.1, Information Security Policy NPR 2810.1, Security of Information and Information Systems NPR 2810.7, Controlled Unclassified Information NPR 7120.7, NASA Information Technology Program and Project Management Requirements OMB Circular A-130, Management of Federal Information Resources

Scope: All contracts that purchase, lease, network to, or otherwise utilize Government-funded IT (as defined by the Clinger-Cohen Act of 1996 and referenced by OMB Circular A-130) must comply with NASA IT Security Requirements.

Contents: The Federal Information Security Modernization Act (FISMA) and Executive Branch policy require external providers that process, store, or transmit federal information or operate information systems on behalf of the federal government to meet the same security and privacy requirements as federal agencies.

Information System Security Plan:

When the contractor is operating a Federal Information System (FIS) on behalf of NASA or is providing a FIS in the execution of this contract, that system must have an Information System Security Plan in accordance with NIST Special Publication (SP) 800-53, “Security and Privacy Controls for Information Systems and Organizations” at the revision number required at the issuance of the contract. This plan and supporting documents shall be entered into the NASA cybersecurity system of record pursuant to Authorization to Operate (ATO) requirements set forth in NASA Policy Directive 2810.1, “NASA Information Security Policy” and NASA Procedural Requirement (NPR) 2810.1, “Security of Information and Information Systems.” The FIS security plan and ATO must be in place before any system may operate in the NASA environment.

NON-FEDERAL SYSTEM SECURITY CERTIFICATION

When the contractor will receive, process, store or transmit NASA non-public information, especially Controlled Unclassified Information (CUI) including Personally Identifiable Information (PII) on a non-federal system (e.g., the contractor’s corporate system) the system must meet the requirements for data protections detailed in NIST Special Publication 800-171, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.”

This documentation may take the form of:

a. A third-party review/audit certifying that the non-federal system meets the requirements of NIST SP 800-171 or equivalent standard of information protection, such as the ISO 27001 standard.

b. A certification from another federal agency such as the DOD Cybersecurity Maturity Model Certification (CMMC) Level 2.

INCIDENT NOTIFICATION

The contractor shall report immediately upon notification any incident involving NASA information on nonfederal (contractor) systems to SOC@nasa.gov.

IT SECURITY POINT OF CONTACT:

The contractor shall identify a point of contact that NASA may reach in its attempt to address IT and cybersecurity issues. The point of contact shall have the authority to ensure the immediate notification of the NASA Security Operations Center of any incident involving NASA information.

IT SECURITY AWARENESS TRAINING:

Contractor employees subject to this contract shall complete the NASA approved IT Security Awareness Training annually. NASA Cybersecurity and Privacy Awareness training is available through the SATERN online system and must be completed prior to access to NASA information and systems. Completion of the training is tracked automatedly by NASA and must recur each year by the anniversary of the initial training as a condition of continued access. Cybersecurity and Privacy training is updated throughout the year as needed, so there is no defined training period.

IT SECURITY ROLE BASED TRAINING:

Contractor employees subject to this contract shall complete NASA’s Foundational IT Security Training in SATERN related to the following role-based functions prior to performing the role:

• IT Security Manager

• Information System Owner (ISO)

• Information Systems Security Officer (ISSO)

• Information System Security Engineer (ISSE) It is highly recommended, but not required, that Contractor employees complete advanced role-based training every other year following completion of the initial training provided by NASA. This training is also provided by NASA but may be fulfilled externally. If fulfilled externally, the Contractor shall provide the “External Role- Based Training Validation Form” to the center CISO. The process for completing this form and receiving credit may be found at: External RBT Validation Form (sharepoint.com).

INFORMATION ON EMPLOYEES IN SENSITIVE POSITION(S)/ASSIGNMENTS REPORT:

The Information on Employees is Sensitive. IT Security (ITS) Positions/Assignments Report shall provide information annually for personnel screening as required by NPR 2810.1(series), and NPR 1600.1 on position risk.

Remarks: None Maintenance:

Information System Security Plan(s) shall be kept up to date as changes to the baseline configuration of the system(s) occur.

4.2 REVIEW DATA

CDRL No.: LNext-RE-01 Title: Contractor’s Review Materials Reference:

Related Documents:

• Engineering Peer Reviews, GPR 8700.6 Use:

To provide review materials for design teams and Government to identify potential engineering design and implementation flaws, gain insight and increase the probability of meeting mission requirements and objectives.

Preparation Information:

The contractor shall provide their review materials to include formal reviews and internal Engineering Peer Reviews. GPR 8700.6 may be used as a guide for Engineering Peer Reviews.

CDRL No.: LNext-RE-02 Title: Inputs to Mission Level Reviews Reference:

Related Documents:

• Criteria for Flight and Flight Support System Lifecycle Reviews, GSFC-STD-1001 Use:

To capture info to support NASA required and led mission level reviews tied to Key Decision Points (KDPs) within the project development lifecycle.

Preparation Information:

The Contractor shall prepare and deliver inputs covering information as applicable on spacecraft subsystems, simulators, Ground Support Equipment (GSE), Observatory, the dispenser and Mission Payload for the following Mission Level Reviews:

• Spacecraft Systems Requirements Review (SC SRR)

• Mission Preliminary Design Review (MPDR)

• Mission Critical Design Review (MCDR)

• Mission Systems Integration Review (MSIR)

• Operations Readiness Review (ORR)

• Flight Readiness Review (FRR)

• Launch Readiness Review (LRR)

• Flight Readiness Review (FRR)

• Post-Launch Acceptance Review (PLAR) Inputs should satisfy the purpose, objectives, and criteria for successful completion of each review as specified in GSFC-STD-1001, Criteria for Flight Project and Flight Support System Lifecycle Reviews for Flight Elements.

CDRL No.: LNext-RE-03 Title: Test Readiness Review Reference:

Related Documents:

Use:

To describe testing to be executed, objectives, expected results and readiness of materials and supporting equipment to execute the test.

Preparation Information:

The Test Readiness Review shall summarize the tests to be conducted and cover areas such as expected test results, requirements compliance, non-conformances and trend data. TRRs shall be held before the final SC CPT and before all Observatory tests.

TRRs shall include at a minimum:

a) Test Identification

b) Status of procedures, GSE, staff, and facilities

c) Hardware and personnel safety considerations and identification of any hazardous operations

d) Effects of previous non-conformance reports

e) Summary of expected requirement(s) to be verified

f) Summary of relevant trended parameters

g) Expected Test Results

CDRL No.: LNext-RE-04 Title: On-Orbit Acceptance Review (OAR) Reference:

Related Documents:

• Criteria for Flight and Flight Support System Lifecycle Reviews, GSFC-STD-1001 Use:

Define the required content for the OAR and determine if the Contractor has satisfied all contract requirements sufficient for the Government to take acceptance of the spacecraft/observatory and related systems.

Preparation Information:

For each Observatory, the Contractor shall present the following at the OAR:

1. A timeline and summary of all events and commissioning activities following liftoff through the completion of on-orbit performance verification.

2. Comparisons if predicted and indicated performance of the Observatory for each event/activity.

3. Summary of all performance discrepancies, their impact on the mission, and their closure status.

4. Description of any in-flight anomalies, actions taken to resolve/recover and current status.

5. Summary of major changes made to FSW, procedures or other on-board configurations since launch.

6. Requirement verification and validation status

7. On-orbit trending data and any recommended changes for trending through End of Life

8. Discussion of open items and deliverable status The OAR may be in presentation format and the contractor may refer to GSFC-STD-1001, Criteria for Flight and Flight Support System Lifecycle Reviews for additional guidance on content.

4.3 SOFTWARE DATA

CDRL No.: LNext-SW-01 Title: Software Management and

Development Plan (SMDP) Reference:

Related Documents:

• NASA Software Engineering Handbook, NASA-HDBK-2203 Use:

The Software Development and Management Plan is used to provide insight into, and is a tool for monitoring, the processes to be followed for software development, the methods to be used, and the approach to be followed for each activity. This plan details the system software, project documentation, project schedules, resources requirements and constraints, and general and detailed software development activities.

Preparation Information:

The Software Development and Management Plan shall include:

A. Description of the system software, project documentation, project schedules, resources requirements and constraints, and software development activities.

B. Description of software engineering environment for development, test, operation and maintenance of the software C. Management of software safety, security and privacy D. Cybersecurity related design and testing activities and policies E. Description of software verification & validation environments, methods, criteria, corrective action and verification F. Discussion of the software life-cycle model, including description of software integration and hardware/software integration processes, software delivery, maintenance, software updates and patching G. Management, development, and testing approach for handling any commercial-off-the-shelf (COTS), Government-off-the-shelf (GOTS), modified-off-the-shelf (MOTS), and reused software. This shall include an analysis of unreachable code for any software associated with space flight operation.

H. Description of software configuration management system I. Plan for and tracking of operational backup software J. Approach for the implementation of modifications to operational software K. Approach for software delivery process, including distribution to facilities and users of the software products and installation of the software in the target environment L. Approach for software delivery process, including distribution to facilities and users of the software products and installation of the software in the target environment (including, but not limited to simulators and ground operations facilities).

CDRL No.: LNext-SW-02 Title: Software Architectural and Detailed Design Description (SDD)

Reference:

Related Documents:

• NASA Software Engineering Handbook, NASA-HDBK-2203 Use:

The Software Design Description is used to understand the design of a Computer Software Configuration Item (CSCI), its architectural design, CSCI-wide design decisions, and the detailed design needed to implement the software.

Preparation Information:

The Software Design Description shall include:

A. CSCI architectural design.

B. CSCI decomposition and interrelationship between components:

1. CSCI components:

a. Description of how the software item satisfies the software requirements, including algorithms, data structures, and functional decomposition.

b. Software item Input/Output (I/O) description.

c. Static/architectural relationship of the software units.

d. Concept of execution, including data flow, control flow, and timing.

e. Requirements, design, and code traceability.

f. CSCI's planned utilization of computer hardware resources.

2. Rationale for software item design decisions/trade decisions including assumptions, limitations, safety and reliability related items/concerns or constraints in design documentation. For consistency, ensure that security and safety are included together throughout the document.

3. Interface design.

CDRL No.: LNext-SW-03 Title: Software Version Description Document

Reference:

Related Documents:

Use:

The software version description document is used to release, track, and control a software version.

Preparation Information:

The software delivery package shall include the following information:

A. Full identification of the system and software (e.g., numbers, titles, abbreviations, version numbers, and release numbers).

B. Source files (include any tables, text files, MatLab files, etc. used during auto-code).

C. Software product files (any files needed to install, build, operate, and maintain the software).

D. Executable software (e.g., batch files, command files, data files, or other software needed to install the software on its target computer).

E. Instructions for building the executable software, including, for example, the instructions and data for compiling and linking.

F. Data integrity checks for the executable object code and source code.

G. Change requests and/or problem reports implemented in the current software version since the last Software Version Description was published.

H. Archive and release data.

I. Software Bill of Materials (SBOM) in machine-readable format, including any open-source software, COTS/GOTS/MOTS, tools used to build and maintain software, etc. The scope of the SBOM shall cover all SW used on the spacecraft, including embedded software in hardware (e.g. Star Trackers, GPS, etc.)

CDRL No.: LNext-SW-04 Title: Software Requirements Specification Reference:

Related Documents:

Use:

The Software Requirements Specification details the software performance, interface, and operational and quality assurance requirements for each computer software configuration items (CSCI).

Preparation Information:

The Software Requirements Specification shall contain:

A. CSCI requirements (including verification method and level):

1. Functional requirements.

2. Required states and modes.

3. External interface requirements.

4. Internal interface requirements.

5. Internal data requirements.

6. Safety requirements.

7. Performance and timing requirements.

8. Security and privacy requirements.

9. Software quality characteristics.

10. Design and implementation constraints.

B. Verification Method (e.g., demonstration, test, analysis, inspection).

C. Bidirectional requirements traceability.

CDRL No.: LNext-SW-05 Title: Software Test Plan Reference:

Related Documents:

Use:

Software Test Plan is used to understand the testing program used to verify software meets requirements.

Preparation Information:

The Software Test Plan shall include:

A. Description of planned tests and types, including Unit Testing, Software integration testing, acceptance testing, long duration error free testing, and regression testing B. Description of test levels ( e.g., component, integration, and system testing), including approach for potential re-test for unique hardware configurations between flight hardware.

C. Description of test conditions D.