mg50539000013e2_e.doc

PREPARED BY

The Boeing Company

CS-SW

Mark Kostelic

AUTHORITY

CS SEIT

Becky Gaede

08 Sept 2010

SUBJECT

PSDR/NR

SOFTWARE REQUIREMENTS SPECIFICATION

FOR THE

POSITIONAL TRAINING EMULATOR

OF THE GLOBAL POSITIONING SYSTEM BLOCK IIF

CONTRACT NO. F04701-96-C-0025

ADPL SEQUENCE NO. 025-4

Prepared for:

U.S. AIR FORCE

HEADQUARTERS SPACE & MISSILE SYSTEMS CENTER

LOS ANGELES, CA 90009-2960

Prepared by:

BOEING

SPACE AND INTELLIGENCE SYSTEMS

2201 Seal Beach Blvd

Seal Beach, CA 90740

Distribution D: Distribution authorized to DOD and US DOD contractors only. (Reason: Administrative or Operational Use) (Date of Determination: 28 September 1995). Other requests for this document shall be referred to NAVSTAR Global Positioning System Joint Program Office (SMC/CZ).

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. 2571 et seq.) or Executive Order 12470. Violation of these export control laws is subject to severe criminal penalties. Dissemination of this document is controlled under DOD directive 5230.25 and AFI 61-204. Include this notice with any reproduced part of this document.

DESTRUCTION NOTICE: For classified documents, follow DOD 5220.22M, National Industrial Security Program Operating Manual. For unclassified limited documents, destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

FORM 3935-G-1 REV 1-97 (Word 7.0)

Document Revision & Version History

Action Item PTE-018 from FCA/PCA. Added Missing IIF Training Capabilities for PTE-SRS-3290, PTE-SRS-3292,and PTE-SRS-3293.

Notices

The following terms are trademarks, registered trademarks, or service marks of other companies and organizations. Each term is the property of its respective owner.

Table of Contents 11 Scope

11.1 Identification

11.2 System Overview

11.2.1 PTE Mission

21.2.2 PTE Software Overview

21.3 Document Overview

21.3.1 Document Requirements Terminology and Use

32 Referenced Documents

32.1 Government Documents

32.1.1 Specifications

32.1.2 Standards

32.1.3 Drawings

32.1.4 Other Publications

42.2 Non-government Documents

42.2.1 Reference Documents

42.2.2 Specifications

42.2.3 Standards

52.2.4 Drawings

52.2.5 Other Publications

63 Requirements

63.1 Required States and Modes.

63.2 Software System Requirements.

63.2.1 Hardware

63.2.2 PTE Capability Requirements

103.2.3 Crew Training.

103.2.4 Positional Training

103.2.5 Basic Operator (BOPR) Training

103.2.6 Advanced Training Capabilities (Advanced Operator Training).

113.2.7 PTE MCS External Interface Requirements.

113.3.1 Interface Identification and Diagrams.

113.3.2 Project Unique Identification of Interface.

113.3.3 PTE MCS System External Interface Requirements.

113.4 PTE Internal Interface Requirements.

113.5 PTE Internal Data Requirements.

113.6 Adaptation Requirements.

113.7 Safety Requirements.

123.8 Security and Privacy Requirements.

123.9 PTE Environment Requirements.

123.10 Computer Resource Requirements.

123.10.1 Computer Hardware Requirements.

123.10.2 Computer Hardware Resource Utilization Requirements.

123.10.3 Computer Software Requirements.

123.10.4 Communications Requirements.

123.11 Software Quality Factors.

123.12 Design and Implementation Constraints.

133.13 Personnel Related Requirements.

133.14 Training Related Requirements.

133.15 Logistics Related Requirements.

133.16 Other Requirements.

133.17 Packaging Requirements.

133.18 Precedence and Criticality of Requirements.

144 Qualification Provisions

144.1 Test Program

154.2 Verification Methods

154.2.1 Demonstration.

154.2.2 Test.

154.2.3 Analysis.

154.2.4 Inspection.

165 Requirements Traceability

176 Notes

176.1 Acronyms

196.2 Technical Glossary

List of Appendices

110 APPENDIX A: Requirements Traceability and Verification Cross Reference A-

120 APPENDIX B: Basic Operator (BOPR) Training Capabilities B-

130 APPENDIX C: Vehicle Advanced Training Capabilities C-

140 APPENDIX D: Payload Advanced Training Capabilities D-

150 APPENDIX E: Crew Advanced Training Capabilities E-

160 APPENDIX F: NAVWAR Training Capabilities.

F-

170 APPENDIX G: IIF Basic Operator Training Capabilities.

G-

180 APPENDIX H: IIF Vehicle Advanced Training Capabilities.

H-

190 APPENDIX I IIF Payload Advanced Training Capabilities.

J-1

List of Tables 4Table 1: Requirements Documentation

1Table A-1: Requirements Verification Matrix A-

5Table A-2: Requirements Traceability Matrix A-

1Table B-1: Basic Operator (BOPR) Training Capabilities B-

1Table C-1: Vehicle Advanced Training Capabilities C-

1Table D-1: Payload Advanced Training Capabilities D-

1Table E-1: Crew Advanced Training Capabilities E-

1Table F-1: NAVWAR Training Capabilities F-

1Table G-1: IIF Basic Operator Training Capabilities G-

1Table H-1: IIF Vehicle Advanced Training Capabilities H-

1Table I-1: IIF Payload Advanced Training Capabilities I-

List of Figures

2Figure 1-1. System Diagram

1 Scope

1.1 Identification

This Software Requirements Specification (SRS), MG50539000013E2, specifies the requirements and qualification provisions for the Positional Training Emulator (PTE) computer software. It includes the requirements and qualification provisions for the three components of PTE: the Global Positioning System (GPS) Operational Control System (OCS) Architecture Evolution Program (AEP), the GPS Satellite Training and Rehearsal Simulator (STARSIM) version of the GPS System Simulator, and Instructor Control (IC).

1.2 System Overview

1.2.1 PTE Mission

The mission of the PTE is to provide a realistic training environment for the 50th Operation Support Squadron (OSS) that supports crew training and positional training for the Global Positioning System (GPS) Operational Control System (OCS) operators.

PTE provides a GPS training emulator for the 50th (OSS). It provides the operators of the GPS ground system with realistic Basic Operator Training (BOPR) and Advanced Operator Training that includes Vehicle Advanced, Payload Advanced, Crew Advanced and Navigation Warfare (NAVWAR) training.

PTE is a tailored combination of the Global Positioning System (GPS) Operational Control System (OCS) Architecture Evolution Program (AEP), the GPS Satellite Training and Rehearsal (STAR) Simulator (SIM), and the Instructor Control (IC). See Figure 1-1.

Figure 1-1. System Diagram

1.2.2 PTE Software Overview

1.3 Document Overview

The purpose of this Software Requirements Specification (SRS) is to specify the requirements and qualification provisions of the PTE. The remaining paragraphs of this specification contain a list of referenced documents, the computer software requirements, the qualification provisions, requirements traceability linking the requirements specified in this SRS with the requirements specified in SS-PTE-615, and Appendix A, which includes a Verification Cross Reference Matrix (VCRM). This document is unclassified. Distribution and destruction of this document should follow the instructions specified on the title page of this document.

1.3.1 Document Requirements Terminology and Use

This specification and its supporting/subordinate specifications utilize the following requirements terminology:

a. A 'shall' identifies a requirement (or any portion thereof) that is being designed, built and unless otherwise stated, tested. Each 'shall' is uniquely numbered for identification and traceability.

b. A 'must' identifies a requirement that is not being designed, built or tested, but is a system design constraint or provision that is being provided to the designer by the government (upon which the designer is dependent). 'Musts' are not numbered, and thus there is no provision for unique identification or traceability.

c. The conventional usage of 'wills' for government furnished equipment/property (GFE/GFP) etc., is now handled as described above (now using 'musts'), except in the cases where the portion of the system being designed is not dependent upon the GFE/GFP (which is identified by the use of 'will'). 'Wills' are not numbered, and thus there is no provision for unique identification or traceability.

2 Referenced Documents

2.1 Government Documents

Interim Department of Defense (DoD) Certification and Accreditation (C&A) Process Guidance, SUBJECT: DoD Information Assurance Certification and Accreditation Process (DIACAP), Undated (distributed July 2006)

DoD Directive 8500.1, SUBJECT: Information Assurance (IA), October 24, 2002

DoD Instruction 8500.2, SUBJECT: Information Assurance (IA) Implementation, February 6, 2003

2.1.1 Specifications

2.1.1.1 Federal

2.1.1.2 Military

None.

2.1.1.3 Other Government Documents

None.

2.1.2 Standards

2.1.2.1 Federal

None.

2.1.2.2 Military

None.

2.1.2.3 Other Government Documents

Interim Department of Defense (DoD) Certification and Accreditation (C&A) Process Guidance, SUBJECT: DoD Information Assurance Certification and Accreditation Process (DIACAP), Undated (distributed July 2006)

DoD Directive 8500.1, SUBJECT: Information Assurance (IA), October 24, 2002 DoD Instruction 8500.2, SUBJECT: Information Assurance (IA) Implementation, February 6, 2003

2.1.3 Drawings

None.

2.1.4 Other Publications

2.1.4.1 Manuals

None.

2.1.4.2 Regulations

None.

2.1.4.3 Handbooks

None.

2.1.4.4 Bulletins

None.

2.2 Non-government Documents

2.2.1 Reference Documents

Table 1: Requirements Documentation

MG50539000013E5

Rev NEW Interface Design Document for the Positional Training Emulator of the Global Positioning System Block IIF

MG50533001033E2

Rev A Software Requirements Specification for the System Simulator CSCI of the Global Positioning System Block IIF-Rel 3

SS-PTE-615

Rev B Prime Item Development Specification for the Positional Training Emulator of the Global Positioning System Block IIF

MG50532004033E5 Rev A

Software Design Document for the Telemetry, Tracking and Command CSCI of the Global Positioning System Block IIF-V5.5

MG50532004033E2 Rev D

Software Requirements Specification for the Telemetry, Tracking and Command CSCI of the Global Positioning System Block IIF-V5.5

2.2.2 Specifications

None.

2.2.3 Standards

X Window System

Version 11, Release 6 X Window System

2.2.4 Drawings

2.2.5 Other Publications

3 Requirements

3.1 Required States and Modes.

· Support the independent execution of a script for each student

· Perform sequential execution of directives

· Delay directive execution a specified interval of simulation time after completion of the previous directive

· Delay directive execution a specified interval of simulation time since the start of the scenario

· Include in the script a pause for script execution

· Allow a script to invoke another script

· Permit the instructor to pause script execution

· Permit the instructor to step through the execution of a script

· Permit the instructor to go to any directive in the script to resume script execution from that directive

· Permit the instructor to select, specify, and execute a directive during a training scenario

3.2 Software System Requirements.

3.2.1 Hardware

3.2.2 PTE Capability Requirements

3.2.2.1 Scenario Execution.

3.2.2.2 Initial Conditions and Time Synchronization.

3.2.2.3 Pause/Resume Time Operations.

3.2.2.4 Fast/Slow Time Operations

3.2.2.5 Save/Restore Operations.

3.2.2.6 Logging of Student Activities.

3.2.2.7 Initial Condition Management

3.2.2.7.1 Initial Condition Data Management.

3.2.2.7.2 Initial Condition Data Synchronization.

3.2.3 Crew Training.

3.2.4 Positional Training

3.2.5 Basic Operator (BOPR) Training

3.2.6 Advanced Training Capabilities (Advanced Operator Training).

3.2.7 PTE MCS External Interface Requirements.

N/A

3.3.1 Interface Identification and Diagrams.

3.3.2 Project Unique Identification of Interface.

This section has been tailored out.

3.3.3 PTE MCS System External Interface Requirements.

N/A

3.4 PTE Internal Interface Requirements.

All internal interfaces of the PTE have been left to design.

3.5 PTE Internal Data Requirements.

All decisions about the internal data of the PTE have been left to design.

3.6 Adaptation Requirements.

This section is not applicable to this SRS.

3.7 Safety Requirements.

This section is not applicable to this SRS.

3.8 Security and Privacy Requirements.

• Interim Department of Defense (DoD) Certification and Accreditation (C&A) Process Guidance, SUBJECT: DoD Information Assurance Certification and Accreditation Process (DIACAP), Undated (distributed July 2006)

• DoD Directive 8500.1, SUBJECT: Information Assurance (IA), October 24, 2002

• DoD Instruction 8500.2, SUBJECT: Information Assurance (IA) Implementation, February 6, 2003

3.9 PTE Environment Requirements.

The PTE operates in the environment provided by the Services Computer Software Configuration Item (CSCI) of the OCS.

3.10 Computer Resource Requirements.

3.10.1 Computer Hardware Requirements.

This section is not applicable to this SRS.

3.10.2 Computer Hardware Resource Utilization Requirements.

This section has been tailored out.

3.10.3 Computer Software Requirements.

The PTE uses the services of the computer software provided by the Services CSCI of the OCS.

3.10.4 Communications Requirements.

The PTE uses the computer communication services of the OCS Services CSCI.

3.11 Software Quality Factors.

This section has been tailored out.

3.12 Design and Implementation Constraints.

The PTE Design is accomplished by reuse of the real AEP Command and Control system in conjunction with the existing Simulator (GPSS). The PTE Simulator component reuses GPSS satellite and ground antenna models. By default, this technical solution provides the look and behavior of the operational AEP system. The GPSS Space Segment, GA, MS, and ARTS model requirements have been previously qualified and accepted.

GPSW and 50th Space Wing accept the fact that there will be some compromise in PTE usability as a result of their selection of the AEP-Centric Option, November 2006 (as presented by Boeing in the last of the AEP PTE Solution briefings). The trade-off with the AEP-Centric solution option is better fidelity and lower technical risk, versus a potential compromise in usability (unlimited student independence whereby each student trains in their own GPS universe.

3.13 Personnel Related Requirements.

This section has been tailored out.

3.14 Training Related Requirements.

This section has been tailored out.

3.15 Logistics Related Requirements.

This section is not applicable to this SRS.

3.16 Other Requirements.

This section is not applicable to this SRS.

3.17 Packaging Requirements.

This section is not applicable to this SRS.

3.18 Precedence and Criticality of Requirements.

This section is not applicable to this SRS.

4 Qualification Provisions

PTE verification demonstrations of the capabilities are performed with Air Force participation.

The Air Force performance worksheet training scenarios are used as test procedures. The verification method for requirements in this document (Table B-1) will be verified through demonstration.

Exception: Test procedures or scripts shall be used to demonstrate the set of Training Features.

Verification Sheets (VS) are generated prior to each capability demonstration, which concisely describes how each capability is demonstrated. The VS is signed before and after each demonstration to document the agreement between the Air Force and Boeing. Signed VS are impounded by Quality Assurance (QA).

All demonstrations will be conducted at the Boeing GPS Center, witnessed by the 50th OSS, GPSW, and Boeing QA.

The following are accomplished for rapid prototype test and verification activities:

· Develop and exercise training scenarios as the system develops

· Obtain Air Force concurrence throughout the process (not just at the end)

· Air Force participation in development and exercise of training scenarios

· Reconcile system functionality with capabilities list

· The Air Force will rate the training tasks performance based on pass/fail

· Boeing QA will witness demonstrations

· Discrepancies will be noted during demonstrations

· If necessary, software will be updated between individual capability demonstrations to achieve a passing rating.

4.1 Test Program

The contractor's test program will qualify each requirement in Table A-1, Requirements Traceability and Verification Cross Reference, by the specified method.

4.2 Verification Methods

4.2.1 Demonstration.

The demonstration method is the operation of the system, or a part of the system that relies on observable functional operation not requiring the use of instrumentation, special test equipment, or subsequent analysis.

4.2.2 Test.

The test method is the operation of the system, or a part of the system, using instrumentation or other special test equipment to collect data for later analysis.

4.2.3 Analysis.

The analysis method is the analytical processing of accumulated data obtained from studies, calculations, analysis, modeling and/or other qualification methods. Examples are reduction, interpolation, or extrapolation of test results.

4.2.4 Inspection.

The inspection method is the visual examination of system components, documentation, etc.

5 Requirements Traceability

See Appendix A 6 Notes

6.1 Acronyms

6.2 Technical Glossary

10 APPENDIX A: Requirements Traceability and Verification Cross Reference Table A-1: Requirements Verification Matrix

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

Table A-2: Requirements Traceability Matrix

20 APPENDIX B: Basic Operator (BOPR) Training Capabilities Table B-1: Basic Operator (BOPR) Training Capabilities

2.6 Perform Nominal Vehicle Commanding

(A-Side) Contractor developed

30 APPENDIX C: Vehicle Advanced Training Capabilities

Table C-1: Vehicle Advanced Training Capabilities

2.11 Perform Nominal Electrical Power Subsystem Commanding

40 APPENDIX D: Payload Advanced Training Capabilities Table D-1: Payload Advanced Training Capabilities

3.1 Perform Payload Display Checks

3.16 Perform L-Band Anomaly

Navigation Data Errors

L-Band Lock Problems

L-Band Monitor Actions