Table of Contents
Naming Convention
OPCON Stages Examples
OPC-LAUNCH
OPC-ORBIT_INSERT
OPC-STANDBY
OPC-RENDEZVOUS
OPC-PROXIMITY_OPS
OPC-DOCKING
OPC-PROP_TRANSFER
OPC-UNDOCKING
OPC-RETURN
OPC-DISPOSAL
Requirements
IOR-<LEVEL>-<CATEGORY>-NNN
LEVEL
- STKR = Stakeholder Requirement
- MISR = Mission Requirement
- SYSR = System Requirement
- DERR = Derived Requirement
- VERI = Verification Requirement
- HSWR – High Level Software Requirement
- LSWR – Low Level Software Requirement
CATEGORY
Discipline grouping
- OPEC = Operational Coverage
- FUNC = Functional Capability
- PERF = Performance
- SAFT = Safety
- COMM = Communications
- NAVI = Navigation
- PROP = Propulsion
- INTF = Interface
- OPRS = Operations
- REGU = Regulatory
SUB-CATEGORY
Is not part of the Requirements ID but SUB-CATEGORY is an optional attribute inside a requirement.
NNN
Three-digit number identified. Need not be sequential
Examples
IOR-MISR-OPEC-001: IOR-Mission Requirement-Operational Coverage-001
IOR-MISR-FUNC-004: IOR-Mission Requirement-Functional Capability-004
IOR-SYSR-PROP-012: IOR-System Requirement-Propulsion-012
IOR-SYSR-COMM-003: IOR-System Requirement-Communications-003
IOR-VERI-OPEC-001: IOR-Verification Requirement-Operational Coverage-001
ARCADIA Model Naming Convention (Very Important)
Model objects should be readable, not coded.
Use: <Type> – <System> – <Function>
Examples
- Operational Capability:LEO Servicing
- Operational Activity:Perform Rendezvous
- System Function:Transfer Propellant
- Logical Function:Regulate Propellant Flow
- Component:Service Vehicle
- Interface:SV-to-Depot Mechanical Interface
- Exchange:State Vector Data
- Component:Service Vehicle
- Component:Orbital Depot
- Component:Ground Segment