Enclosure 2 RTO-ELV Requirements.pdf

RTO ELV Requirements Document

Table of Contents

Table of Contents

Section 1. Overview

1.1 Purpose

1.2 Scope

1.3 Objectives

1.4 Applicability

Section 2. Summary of Range Services Requirements

2.1 Detailed Requirements Matrices

2.2 Associated Operations Requirements

Section 1. Overview

1.1 Purpose

The purpose of this document is to define the requirements for the ELV launch mission; to take place from Pad-0A located at Wallops Flight Facility (WFF).

1.2 Scope

The scope of this document is to identify mission requirements. These requirements cover staffing, resources, and schedules. Detailed test procedures and usage operations plans, along with vehicle or mission specific details (beside those necessary for providing range support) are out of the scope of this document; they are addressed in associated documents

1.3 Objectives

The objectives of this document are to list all requirements allocated to the Range, assign each a trackable identification, identify the source or traceability of the requirement, identify the type of requirement, and identify how the requirements will be verified.

The source of requirements is broken into the following categories

Source Description

Explicit Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.

Derived Requirement that is not explicitly stated in the set of stakeholder requirements and is inferred or derived from a stakeholder requirement. The requirement may also be developed during the design activities as a result of the design team, not the stakeholder.

As a result, the derived requirement may not directly trace to a stakeholder requirement, but it will not conflict with a stakeholder requirement or a constraint.

The types of requirements are broken into the following categories

Type Description

Mandatory Requirement specified by the customer and those listed in the PRD and/or other requirements documents must be met.

Desired Desired capability to improve utility of system; does not need to be met for project success.

The types of verification methods are broken into the following categories:

Type Description

Test (T) Verification by test consists of operations of all or part of the subsystem under controlled conditions to determine that qualitative design or performance requirements have been met. It includes the collection and subsequent examination of quantitative data. Test may rely on the use of instrumentation and special test equipment to measure the parameter(s) that characterize the requirement.

Demonstration (D) Verification by demonstration consists of operations of all or part of the subsystem under controlled conditions to determine that qualitative design or performance requirements have been met. Demonstration relies on observation/recording of functional operation not requiring the use of elaborate instrumentation, special test equipment, or quantitative evaluation of data.

Analysis (A) Verification by evaluation of data by generally accepted analytical techniques to determine that the item will meet specified requirements. Analytical techniques may include systems engineering analysis, statics, analog modeling, similarity, and computer simulation.

Inspection (I) Verification of compliance by the examination of documentation or direct examination of an attribute (dimension, weight, physical characteristics, computer program code, etc.).

1.4 Applicability

This requirements document applies to contractors responsible for range instrumentation, engineering and operations support

If a conflict is discovered between this requirement document and any other approved mission documentation, the conflict shall be immediately identified to the NASA Project Manager for resolution