# MOVE BEYOND Requirements

## High Level Requirements

### General Project Goals

| # | Id | Name | Text | Source | Author | Rationale | Payload-related | Verify Method | Allocated To |
|----:|:--------|:----------------------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------|:------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:----------------|:-----------------------------------------|
| 1 | GEN-1 | Project Mission | The project shall provide development of satellite platform which serves as baseline for the next satellites built at the TUM Chair of Astronautics | SCR | Karolina Latserus | To make the base of knowledge for future projects | No | Demonstration | MB Project |
| 2 | GEN-1.1 | MOVE BEYOND CubeSat assignment | The MOVE BEYOND CubeSat shall be designed to perform one of the MOVE BEYOND Missions | SCR | Karolina Latserus | | Yes | Inspection | MB CubeSat,Sino German Satellite Program |
| 3 | GEN-1.2 | MOVE BEYOND CubeSat Platform assignments | The MOVE BEYOND CubeSat Platform design shall provide Level-0 functionality | | Karolina Latserus | Development of MOVE BEYOND Platform CubeSat is a solution to fasten the implementation of basic CubeSat technologies and functions which are relevant for any mission. Adapting the Platform CubeSat to the certain payload will take less time that development the payload-oriented CubeSat from the beginning. | No | Test | MB CubeSat Platform |
| 4 | GEN-2 | Project Educational Goal | The project shall provide hands-on education of student in spacecraft design, qualification, testing and operation | SCR | Karolina Latserus | | No | Demonstration | MB Project |
| 5 | GEN-3 | MOVE BEYOND CubeSat orbit altitude | The MOVE BEYOND CubeSat shall operate in the orbits with altitude range from 400 km to 600 km | Launch providers | Karolina Latserus | CubeSat launch regulations | Yes | Analysis | MB CubeSat |
| 6 | GEN-4 | MOVE BEYOND CubeSat lifetime | The MOVE BEYOND CubeSat on-orbit lifetime shall be not less than 6 months | Florian Schummer | Karolina Latserus | | Yes | Analysis | MB CubeSat |
| 7 | GEN-5 | MOVE BEYOND CubeSat operating temperature range | The MOVE BEYOND CubeSat shall operate in the temperature range [TBD] | | Karolina Latserus | Temperature of environment for related altitude range | Yes | Analysis | MB CubeSat |
| 8 | GEN-6 | MOVE BEYOND CubeSat Platform flexibility | The MOVE BEYOND CubeSat Platform shall be flexible to host variety of payloads from MOVE BEYOND missions | SCR | Karolina Latserus | To make a technology baseline which can be adapted to certain mission and save time for its preparation | Yes | Analysis | MB CubeSat Platform |
| 9 | GEN-7 | MOVE BEYOND CubeSat Platform preliminary dimensions | All the 0-level functionality design decisions of MOVE BEYOND CubeSat Platform shall fit the 1U CubeSat specification size | SCR | Karolina Latserus | To have possibility to host large payloads and fit the CubeSat specifications | No | Inspection | MB CubeSat Platform |

---
### Team Established Project Goals

| # | Id | Name | Text | Source | Author | Functionality Level | Rationale | Development Status | Payload-related | Verify Method | Allocated To |
|----:|:-----|:------------------------------------------------|:------------------------------------------------------------------------------------------------|:---------|:------------------|:----------------------|:-------------------------------------------------------------------------------------------------------------|:---------------------|:------------------|:----------------|:-----------------------------------------------------------|
| 1 | TE-1 | CubeSat on-the-run reconfigurability | The system hardware shall be reconfigurable from the ground while CubeSat is being on the orbit | SCR | Karolina Latserus | | To be able to change microcontrollers firmware | UNDER DEVELOPMENT | No | Test | ADCS,CDH,COM Satellite,DOSIS Satellite,EPS,Mission Control |
| 2 | TE-2 | Communication between subsystems | The system shall enable transferring data from one CubeSat subsystem to another | SCR | Karolina Latserus | | To support internal communication between subsystens without a need to make it via Ground station | UNDER DEVELOPMENT | No | Test | ADCS,CDH,COM Satellite,DOSIS Satellite,EPS |
| 3 | TE-3 | Reaction on data transmitted between subsystems | The CDH system shall listen to data transmitted over CubeSat subsystems and react on them | SCR | Karolina Latserus | | To make the satellite more autonomous and solve internal operational problems without Ground Station command | UNDER DEVELOPMENT | No | Test | CDH,HORST,CDH Team |
| 4 | TE-4 | EPS subsystem modularity | The power supplying components of the EPS system shall be designed in a modular way | SCR | Karolina Latserus | | To be flexible to host payloads which require more power | UNDER DEVELOPMENT | Yes | Analysis | EPS,EPS Team |
| 5 | TE-5 | S-Band uplink | The COM system shall support the S-Band uplink | SCR | Karolina Latserus | | To increase the data transmittion possibility and make redundancy for COM system | UNDER DEVELOPMENT | Yes | Test | COM Team,COM Satellite,COM Ground Station |
| 6 | TE-6 | GPS module development | The CubeSat shall have its GPS module | SCR | Karolina Latserus | | To estimate the CubeSat attitude and provide this information to payload if needed | UNDER DEVELOPMENT | Yes | Demonstration | COM Satellite,COM Team |
| 7 | TE-7 | X-Band uplink | The COM system shall support the X-Band uplink | SCR | Karolina Latserus | | To increase the data transmittion possibility and make redundancy for COM system | DELAYED | Yes | Test | COM Satellite,COM Ground Station,COM Team |
| 8 | TE-8 | Development of reaction wheels | The system shall be able to be equipped with reaction wheels | SCR | Karolina Latserus | | To increase the pointing accuracy | DELAYED | Yes | Demonstration | ADCS,ADCS Team |

## Subsystems Requirements

### ADCS Requirements

| id | Name | Text | Source | Author | Functionality Level | Development Status | Rationale | Payload-related | Verify Method | Allocated To |
|:-------------|:------------------------|:--------------------------------------------------------------------------------------------------------------------------------|:----------------------------------|:-----------------|:----------------------|:-------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------------|:--------------|:--------------------|
| ADCS-1 | Detumbling | The ADCS shall provide the ability to bring the satellite's angular verlocity from up to 200deg/s down to no more than 20deg/s. | Ivan Karageorgiev, David Messmann | Florian Strasser | Level 0 Functionality | UNDER DEVELOPMENT | The ADCS shall be able to slow down the tumbling satellite to achieve a state from which further attitude control mechanisms can be performed. | No | Test | ADCS ADCS_Detumbling|
| ADCS-2 | Attitude Determination | The ADCS shall provide coarse determination of the satellite's attitude with at least 20 degrees accuracy. | Ivan Karageorgiev, SCR | Florian Strasser | Level 0 Functionality | UNDER DEVELOPMENT | It is critical for the ADCS to know the coarse attitude of the satellite in terms of a reliable power incomce and communication. | No | Analysis | ADCS |
| ADCS-3 | Attitude Control | The ADCS shall provide coarse control of the satellite's attitude with at least 20 degrees accuracy. | SCR | Florian Strasser | Level 0 Functionality | UNDER DEVELOPMENT | The ADCS shall provide means of altering its attitude actively in order to ensure a reliable power income, communication and therefore a robust functional state of the system. | No | Analysis | ADCS |
| ADCS-4 | ADCS Communication | The ADCS shall use the provided bus for communication with other subsystems and the payloads. | SCR, TE-2 | Florian Strasser | Level 0 Functionality | UNDER DEVELOPMENT | Since other subystems can be dependent on the attitude of the satellite, a way of communication between the ADCS and other subsystems as well as the payload has to be established. | No | Test | ADCS |
| ADCS-5 | ADCS Reconfigurability | The ADCS shall be reconfigurable from the ground. | David Messmann, TE-1 | Florian Strasser | Level 0 Functionality | UNDER DEVELOPMENT | The ADCS shall be changable even after deployment of the satellite in orbit. | No | Test | ADCS |
| ADCS-6 | ADCS Parameterizability | The ADCS shall be parameterizable. | David Messmann, GEN-8 | Florian Strasser | Level 0 Functionality | UNDER DEVELOPMENT | The ADCS has to be set up in a way that it is flexible and scalable in order to be able to adapt to a variety of payloads. | No | Test | ADCS |
| ADCS-7 | Pointing Accuracy | The ADCS shall provide pointing of the satellite to any desired point with a maximum deviation of 2 degrees. | SCR, Patrick Schnierle | Florian Strasser | Level 2 Functionality | DELAYED | Some payloads require accurate pointing abilities of the satellite which the ADCS has to be able to fulfill accordingly. | Yes | Analysis | ADCS |

---
### CDH Requirements

| # | Name | Text | Source | Author | Functionality Level | Development Status | Rationale | Payload-related | Verify Method | Allocated To |
|----:|:-----------------|:---------------------------------------------------------------------------------------------------------------|:-------------|:----------------|:----------------------|:---------------------|:--------------|:------------------|:----------------|:---------------|
| 1 | Process Commands | The CDH subsystem shall process on board commands. | Niklas Johne | Hannes Baeuerle | | UNDER DEVELOPMENT | on board? | No | Demonstration | |
| 2 | Execute Commands | The CDH subsystem shall execute on board commands. | Niklas Johne | Hannes Baeuerle | | UNDER DEVELOPMENT | on board? | No | Demonstration | |
| 3 | Process Data | The CDH subsystem shall process on board data. | Niklas Johne | Hannes Baeuerle | | UNDER DEVELOPMENT | | No | Demonstration | |
| 4 | | The CDH subsystem shall decide autonomously whether processed data is relevant for the beacon or housekeeping. | Niklas Johne | Hannes Baeuerle | | UNDER DEVELOPMENT | | No | Demonstration | |
| 5 | Download Data | The CDH subsystem shall download on board produced data. | Niklas Johne | Hannes Baeuerle | | UNDER DEVELOPMENT | | No | Demonstration | |
| 6 | | The CDH subsystem shall download data in the beacon automatically every 60 seconds. | Niklas Johne | Hannes Baeuerle | | UNDER DEVELOPMENT | | No | Demonstration | |
| 7 | | The CDH subsystem shall download housekeeping data on request. | Niklas Johne | Hannes Baeuerle | | UNDER DEVELOPMENT | | No | Demonstration | |
| 8 | Store Data | The CDH subsystem shall be able to store data. | Niklas Johne | Hannes Baeuerle | | UNDER DEVELOPMENT | Write!? | No | Demonstration | |
| 9 | Storage Access | The CDH subsystem shall have access to stored data. | Niklas Johne | Hannes Baeuerle | | UNDER DEVELOPMENT | Read storage? | No | Demonstration | |

---
### COM Requirements

| # | Name | Text | Source | Functionality Level | Development Status | Rationale | Author | Payload-related | Verify Method | Allocated To |
|----:|:-------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|:----------------------|:---------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------|:------------------|:----------------|:---------------------------------|
| 1 | The assignment of COM subsystem | The COM subsystem shall provide a link for communication between satellite and ground station | SCR | 0-level functionality | UNDER DEVELOPMENT | In order to fulfill the mission, communication with OPS and transmission of data needs to be possible. | Janis Milde | No | Test | COM Satellite,COM Ground Station |
| 2 | COM Ground Station assignment | The ground station shall relay data between OPS and COM satellite subsystem on all used frequency bands of the COM satellite subsystem | SCR | 0-level functionality | UNDER DEVELOPMENT | OPS will send and receive comands and data from and to the satellite using ground hardware. | Janis Milde | No | Test | COM Ground Station |
| 3 | COM Satellite subsystem assignment | The COM satellite subsystem shall relay data between COM ground station and the satellite subsystems | SCR | 0-level functionality | UNDER DEVELOPMENT | The data that is received by the COM satellite subsystem must be transfered to the satellite bus and data that is supposed to be transmitted to the ground station shall be received from CDH and transfered to the ground station. | Janis Milde | No | Test | COM Satellite |
| 4 | COM satellite hardware reliability | The COM satellite subsystem should provide a solution for COM hardware redundancy | SCR | 1-level functionality | UNDER DEVELOPMENT | To prevent failiure of the mission when communication hardware fails the reliability of the hardware must be as good as possible while staying in the given constrains. | Janis Milde | No | Inspection | COM Ground Station,COM Satellite |
| 5 | deleted_2019-11-13_with_Martin_Luelf | The COM subsystem shall provide a mechanism to initiate the communication process between ground station and satellite | SCR | 0-level functionality | UNDER DEVELOPMENT | A handshake mechanism is needed to start the communication between satellite and ground station, especially when half duplex is used. | Janis Milde | No | Test | COM Satellite,COM Ground Station |
| 6 | Prevention of unauthorized commanding of the satellite | COM subsystem shall provide a mechanism to prevent unauthorized signals from being relayed to satellite subsystems. | MOVE 2 Lessons Learned | 0-level functionality | UNDER DEVELOPMENT | Because CDH will do data handling, COM satellite subsystem will transfere packages to the satellite bus. Thus authentification should be done first before the comands and data is transfered to the satelite bus. | Janis Milde | No | Analysis | COM Ground Station,COM Satellite |
| 7 | TMTC (telemetry telecommand (UHF) | The COM subsystem shall provide a data link to relay telemetry and commands. | SCR | 0-level functionality | UNDER DEVELOPMENT | To have a reliable data link to relay a low data rate signal that hase a low energy consumption | Janis Milde | No | Analysis | COM Ground Station,COM Satellite |
| 8 | High data rate uplink | The COM subsystem shall provide a high data rate uplink to transfer data from the ground station to the COM satellite subsystem | SCR | 1-level functionality | UNDER DEVELOPMENT | To have a high data rate uplink available to relay big amounts of data in a short period of time to the COM satellite subsystem from the ground station. | Janis Milde | Yes | Analysis | COM Ground Station,COM Satellite |
| 9 | High data rate downlink | The COM subsystem shall provide a high data rate downlink to transfer data from the COM satellite subsystem to the ground station | SCR | 1-level functionality | UNDER DEVELOPMENT | To have a high data rate downlink available to relay big amounts of data in a short period of time from the ground station to the COM satellite subsystem. | Janis Milde | Yes | Analysis | COM Ground Station,COM Satellite |

| # | Name | Text | Source | Functionality Level | Rationale | Payload-related | Verify Method | Allocated To | Author |
|----:|:-----------------------------------|:----------------------------------------------------------------------------------------------------------------------------------|:---------|:----------------------|:-------------------------------------------------------------------------------------------------------------------------|:------------------|:----------------|:---------------------------------|:------------|
| 1 | COM external interface for testing | The COM satellite subsystem shall have external interface for on-ground commands and data transmitting testing | | 0-level functionality | This interface will allow to test functions without the need of an antenna to send data to the COM satellite subsystem. | No | Demonstration | COM Satellite | Janis Milde |
| 2 | COM regulation for design | The COM subsystem shall be designed in compliance with national and international law, regulations and frequency allocation [TBD] | | 0-level functionality | To be leagly allowed to operate the developed hardware. | No | Analysis | COM Satellite,COM Ground Station | Janis Milde |
| 3 | COM software framework | The COM satellite software shall be based on DOSIS framework for internal communications | | 1-level functionality | DOSIS Framework is developed to reduce work for the same functions and mistakes. Thus it shall be used by all subsystems | No | Demonstration | COM Satellite,DOSIS Satellite | Janis Milde |
| 4 | Maximum bit error rate | The link between the satellite and ground station shall maintain the maximum bit error rate of [TBD] bit/bit (= unitless) | | 0-level functionality | A minimum of bit error rate will set a minimum quality level also for test purpuses | No | Test | COM Satellite,COM Ground Station | Janis Milde |

---
### Ground Station Requirements

---
### DOSIS Requirements

| ID | Name | Text | Source | Author | Functionality Level | Development Status | Rationale | Payload-related | Verify Method | Allocated To |
|---------:|:----------------------------|:-------------------------------------------------------------------------------------------------------------------------|:---------|:----------------|:----------------------|:---------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------------------|:----------------|:---------------|
| DOSIS-1 | Decentralized communication | The DOSIS shall ensure a decentralized communication between all subsystems that are connected to the communication bus. | SCR | Hannes Baeuerle | 0-level functionality | UNDER DEVELOPMENT | Assure a lower complexity of the satellite's communication and limit duplicate work. Furthermore, the CDH board is not a single point of failure, as the commanding and configuration of subsystems is possible directly via access to the communication bus. | No | Test | DOSIS |
| DOSIS-2 | Software testability | The DOSIS shall ensure the testability of the satellite's software. | SCR | Hannes Baeuerle | 0-level functionality | UNDER DEVELOPMENT | | No | Test | DOSIS |
| DOSIS-3 | Software debuggability | The DOSIS shall ensure the debuggability of the satellite's software. | SCR | Hannes Baeuerle | 0-level functionality | UNDER DEVELOPMENT | | No | Test | DOSIS |
| DOSIS-4 | Encryption Firmware | TBR | | Hannes Baeuerle | | UNDER DEVELOPMENT | TBR by Hannes Baeuerle | No | | |

---
### EPS Requirements

| ID | Name | Text | Source | Author | Functionality Level | Rationale | Development Status | Payload-related | Verify Method | Reference to Work Package |
|:------:|:--------------------------------- |:-------------------------------------------------------------------------------------------- |:---------------- |:--------------- |:--------------------- |:--------------------------------------------------------------------------- | ------------------:|:--------------- |:------------- |:------------ |
| EPS-1 | EPS energy storing | The EPS shall have an electrical power storage with a capacity of [TBD] Wh. | Store Power | Maximilian Hyba | level-0 functionality | To support flexibility of orbits for the mission and operate in sun eclipse. | UNDER DEVELOPMENT | No | Analysis, Demonstration | Battery Board Development |
| EPS-2 | EPS energy generation | The EPS shall generate electrical power using solar cells in order to have a positive power budget. | Generate Power, Ensure Power Budget Resilience | Maximilian Hyba | level-0 functionality | To provide power in all operation modes in space. | UNDER DEVELOPMENT | No | Test, Analysis | EPS |
| EPS-3 | EPS power supply | The EPS shall supply the required electrical power to every subsystem and payload. | Provide Power to All Subsystems, Distribute Power, Condition Power | Maximilian Hyba | level-0 functionality | To be able to support electronics with different energy supply requirements. | UNDER DEVELOPMENT | No | Demonstration, Test | EPS |
| EPS-4 | EPS consumption measuring | The EPS shall monitor the power consumption of every subsystem and payload. | Ensure Power Budget Resilience, Measure Power Consumption of Subsystems | Maximilian Hyba | level-0 functionality | To check the subsystems and payloads proper working | UNDER DEVELOPMENT | No | Demonstration, Test | EPS |
| EPS-5 | EPS data and commands operation | The EPS shall be able to communicate with every subsystem and payload. | Shut Down Subsystems, Reboot Satellite on Ground Command, Reboot Subsystems | Maximilian Hyba | level-0 functionality | To provide housekeeping data and be operable | UNDER DEVELOPMENT | No | Demonstration | EPS |
| EPS-6 | EPS external power supply | The EPS shall have an external electrical interface. | Provide External Power Supply Interface | Maximilian Hyba | level-0 functionality | To test all electrical related functionalities on ground. | UNDER DEVELOPMENT | No | Demonstration, Inspection | EPS |
| EPS-7 | EPS deployment switches | The EPS shall be able to seperate the battery from the electrical power bus system during launch. | Ensure Separation of Battery and Remaining Circuit | Maximilian Hyba | level-0 functionality | To switch the system off during launch and switch it on after deployment. | UNDER DEVELOPMENT | No | Demonstration | EPS |
| EPS-8/4.1 | EPS faulty components control | The EPS shall detect faulty electrical components. | see 4.1 | Maximilian Hyba | level-0 functionality | To switch off malfunctioning components. | UNDER DEVELOPMENT | No | Test, Demonstration | EPS |
| EPS-9/5 | EPS switches control | The EPS shall be able to switch on/off every subsystem and payload. | | Maximilian Hyba | level-0 functionality | To switch off the malfunctioning components | UNDER DEVELOPMENT | No | Test, Demonstration | EPS |
| EPS-10 | Reboot of other components by EPS | The EPS shall detect the errors in [TBD] operations and provide hard-reset it if needed. | SCR | Maximilian Hyba | level-0 functionality | To detect the errors and react on them | UNDER DEVELOPMENT | No | Test | EPS |

---
### MC Requirements

---
### OPS Requirements

---
### Payload Requirements

---
### STRAIT Requirements

| ID | Name | Text | Source | Functionality Level | Rationale | Development Status | Payload-related | Verify Method | Allocated To |
|---------:|:-------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------|:-----------------------|:-------------------------------------------------------------------------------------------|:---------------------|:------------------|:----------------|:---------------|
| STRAIT-1 | Assignment of STR subsystem | The STR subsystem shall provide the hardware structure for the satellite which ensures integrity of the satellite during launch and in-orbit operations. | SCR | level-0 functionality | To connect all the subsystem into the generic system | UNDER DEVELOPMENT | No | Test | STR |
| STRAIT-2 | Deployment mechanism for solar array | The STR subsystem shall provide the deployment mechanism for solar panels. | SCR | level-0 functionality | If the size of the body-mounted solar array wouldn/t provide enough evergy for the mission | UNDER DEVELOPMENT | No | Demonstration | STR |
| STRAIT-3 | Deployment mechanism for antennas | The STR subsystem shall provide the deployment mechanism for antenna system. | SCR | level-0 functionality | To provide the integrity of the antennas during the launch and expand it after deployment | UNDER DEVELOPMENT | No | Demonstration | STR |
| STRAIT-4 | STR mechanical steadyness | The STR subsystem shall survive g-forces, vibration, shock and sound pressure without any degradation [TBD]. | SCR | level-0 functionality | To face space environment | UNDER DEVELOPMENT | No | Test | STR |
| STRAIT-5 | STR thermal steadyness | The STR subsystem shall survive thermal expansion and thermal cycling without any degradation [TBD]. | SCR | level-0 functionality | To face space environment | UNDER DEVELOPMENT | No | Test | STR |
| STRAIT-6 | STR subsystems PCBs integration | The STR subsystem shall provide the placement for all the internal subsystem PCBs with ability to add/remove any of them without necessity to remove other PCBs. | SCR | level-0 functionality | To support easier testing and integration | UNDER DEVELOPMENT | No | Demonstration | STR |
| STRAIT-7 | Satellite deployment | The satellite's structur and mechanismens shall comply with the CubeSat Design Specifications. | | level-0 functionality | To | UNDER DEVELOPMENT | No | Demonstration | STR |

---
### THM Requirements

---