The report is available in the deliverables folder for more details on the scenarios and the architecture.
- Docker
- Maven 4.0.0
- Spring 3.1.3
- Java 17
- JDK 19
git clone [email protected]:pns-si5-al-course/soa-marsy-marsy-23-24-team-a.git
cd soa-marsy-marsy-23-24-team-a
git checkout tags/FINAL
./prepare.sh
./run.sh
-
Mission successful
- Poll to weather and rocket department services
- Rocket launch
- Speed variation through Max Q
- Stage splitting and returning to Earth
- Payload dropped and monitored
- Robot dropped and monitored
- Moon sample analysis
-
Mission failed: severe anomaly
- Rocket damaged, sabotaged by Elune Mars
- Rocket destroyed by the mission commander, to avoid potential ground damage
-
Mission failed: critical anomaly
- Rocket damaged, sabotaged by Palpatooine
- Rocket self-destructed, to avoid potential ground damage
The three scenarios will automatically be run in sequence using the run.sh script
-
weather-service: make sure the weather is safe across sites
- Reply GO or NO-GO to the mission-service when it asks for the weather status before launching the rocket
-
logs-service: Records all mission logs
- Receive all logs from all services linked to the mission, then save them
- Allows access to the log history of each rocket for different missions
-
mission-service: overlook the whole mission
- Inform the log-service and the telemtry-service that the mission is about to start
- Ask for the fueling of the both rocket stages
- Ask for the payload loading
- Ask the weather-service and the rocket-department-service for a GO or NO-GO to launch the rocket
- Send a GO or NO-GO to rocket-department-service based on responses from weather-service and rocket-department-service
- Inform payload-service and executive-service when the mission begins
- Request telemetry-service to be notified if the rocket has a severe anomaly
- Gives the order to destroy the rocket in case of severe anomaly
- End the mission if the rocket has destroyed itself because of a severe anomaly
-
rocket-department-service: manage the rocket and its systems
- Reply GO or NO-GO to the mission-service when it asks for the rocket status before the launch
- Start the countdown to launch the rocket after receiving the GO answer from the mission-service
- Request the telemetry-service to be notified of certain events during the mission
- Stage the rocket mid-flight when there is no more fuel in the first stage
- Slow down the rocket when passing through the Max Q zone to avoid damage to the hardware and payload
- Slow down the rocket when it reaches the orbital altitude
-
telemetry-service: handle the data communications between the flight hardware and the ground
- Receive event notification requests from other services
- Receive, monitor and save data from rocket-hardware-mock-service, stage-hardware-mock-service, payload-hardware-mock-service and robot-hardware-mock-service
- Informs, using Kafka, mission-service, executive-service, payload-service, rocket-department-service, robot-departement-service and scientific-department-service of certain events
- Send, using Kafka, data on ground samples taken by the robot
-
payload-service: responsible for the customer’s cargo and the efficient trajectory or orbit insertion
- Ask the telemetry-service to be informed when the rocket reaches the correct height to drop the payload
- Drop the payload into the correct orbit
- Receive and save data from payload-hardware-mock-service via telemetry-service
- Verify that the altitude of the payload was still correct after it was dropped
-
executive-service: direct and drive strategically the company’s business and objectives
- Request the telemetry service to be informed of the successful return of the rocket's first stage to Earth
-
logs-service: Records all mission logs
- Receive all logs from all services linked to the mission, then save them
- Allows access to the log history of each rocket for different missions
-
robot-department-service: responsible for managing the robot and its release on the moon
- Asks the telemetry-service to be informed when the rocket reaches the correct height to deploy the robot
- Asks the rocket-hardware-mock-service to release the robot then launches the robot landing procedure by asking the telemetry-service to be informed when it lands on the moon
- Ask the scientific-department-service for the coordinates where to carry out soil analyses
- Starts self-piloting of the robot at said coordinates
- At the desired location, asks the robot-hardware-mock-service to carry out soil analyzes then transmits these analyzes to the scientific-department-service
-
webcaster-service: Is notified of the different stages of the mission then broadcasts them live on the web
- Is informed when key milestones of the mission are reached
- Broadcast this information live
-
scientific-department-service: analyzes the data from the samples taken by the robot
- When requested, send contact details where to carry out soil analyzes
- Receives data from the telemetry-service on the soil collected by the robot
-
rocket-hardware-mock-service: fictional representation of the rocket hardware
- Start sending data to the telemetry service after the start of the mission
- Send data on the altitude, the speed, the fuel of each stage, the status, and acceleration every half second
- Release the first stage of the rocket
- Drop the cargo from the rocket
- Drop the robot on the Moon
- If a critical anomaly is detected, the rocket informs the *mission-service that it will self-destruct due to this anomaly, then proceeds with the self-destruction.
-
stage-hardware-mock-service: fictional representation of the stages hardware
- Start sending data of a specific stage to the telemetry service after the stage has been detached
- Send data on the altitude, the speed, the fuel, and acceleration every second
-
payload-hardware-mock-service: fictional representation of the payload hardware
- Start sending data to the telemetry-service after being dropped
- Send data on the current position of the payload to telemetry-service every second
-
robot-hardware-mock-service: fictional representation of the robot hardware
- Starts sending data to the telemetry-service after being released from the rocket
- Sends data about the robot's current position to the telemetry-service every second
- Waits for the order to move towards a specific point to use its autopilot
- Take soil samples for analysis
-
database-telemetry:
- Save the rocket data received by the rocket-hardware-mock-service
- Save the stage data received by the stage-hardware-mock-service
- Save robot data received by the robot-hardware-mock-service
- Save notification requests received by other services
- Save rocket names received by mission-service
-
database-telemetry-slave:
- Read-only database-telemetry slave
-
database-payload:
- Save the payload data received by the payload-hardware-mock-service
-
database-logs:
- Records rocket names received by mission-service
- Records data from all logs of services linked to the mission, all except webcaster-service
| Services | Port |
|---|---|
| weather-service | 3000 |
| mission-service | 3001 |
| rocket-department-service | 3002 |
| telemetry-service | 3003 |
| payload-service | 3004 |
| rocket-hardware-mock-service | 3005 |
| database-telemetry | 3006 |
| database-payload | 3007 |
| executive-service | 3008 |
| payload-hardware-mock-service | 3009 |
| stage-hardware-mock-service | 3010 |
| logs-service | 3011 |
| database-logs | 3012 |
| webcaster-service | 3013 |
| robot-department-service | 3014 |
| robot-hardware-mock-service | 3015 |
| scientific-department-service | 3016 |
| telemetry-reader-service | 3017 |
| telemetry-slave | 3018 |
| Members | Points |
|---|---|
| Antoine BUQUET | 100 |
| Benoit GAUDET | 100 |
| Ayoub IMAMI | 100 |
| Mourad KARRAKCHOU | 100 |