Document/Purpose Defines the operational environment of the IOR mission, identifies external actors, and describes how the system interacts with them. Reference: https://arcadia-method.org/operational-analysis.html Traceability (Upstream /Downstream) Documents Upstream: Business / Mission Analysis Downstream: Operational Analysis, OPCON Stages, Stakeholder Needs Status DRAFT… 

Document/Purpose Defines the mission-level requirements the IOR system must satisfy to achieve the mission objectives. Reference: https://www.linkedin.com/pulse/mission-system-requirements-whats-difference-why-does-alan-fromberg-felkc/ Traceability (Upstream /Downstream) Documents Upstream: Stakeholder Requirements Downstream: CONOPS, System Requirements Status DRAFT Baseline Version/Date | Current Version Not yet established | v0.1 Last… 

Document/Purpose Identifies users and stakeholders and documents their needs/requirements for the IOR mission Reference: Stakeholder Needs and Requirements (glossary) Traceability (Upstream / Downstream) Documents Upstream: Mission Context Downstream: Mission Requirements, CONOPS Status DRAFT Baseline Version/Date | Current Version Not yet… 

1.2.1 Stakeholder (User/Owner/Customer) Requirements 1.2.2 Mission Requirements

  WHY THIS IOR INITIATIVE This initiative enables companies to build their respective parts of an In-Orbit Refueling (IOR) ecosystem by providing system requirements, designs, system-level specifications, interfaces, QA frameworks, and guidelines. The objective is to ensure that independently developed… 

Document/Purpose Identifies the business/mission problem and analyzes the operational context to ensure the system concept addresses real needs. [en.wikipedia.org] Traceability (Upstream /Downstream) Documents  Upstream: None Downstream: Mission Context, Stakeholder Needs, Mission Requirements Status DRAFT Baseline Version/Date | Current Version Not…