Prompt for the ShipRoleApp

Please create a React-JS application for the ShipRoleModule. The application  has to offer the following views for the user interface: 
    1. RocketEngineView 
    2. ShipRoleView 
    3. StageEngineView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The RocketEngineView must contain the following fields: 
    - name: Company   type: Company 
    - name: CycleType   type: STRING 
    - name: Name   type: STRING 
    - name: Notes   type: STRING 
    - name: SpecificImpulseVacSec   type: STRING 
    - name: ThrustKn   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing RocketEngine entity should be loaded from the relative URL: 
    "/ShipRoleService/rocketengine/{id}"   (HTTP-GET) 
If a new RocketEngine entity has been created, the new entity should be posted to the relative URL: 
    "/ShipRoleService/rocketengine"   (HTTP-POST) 
If an existing RocketEngine entity has been updated, the modified entity should be sent to the relative URL: 
    "/ShipRoleService/rocketengine/{id}"   (HTTP-PUT) 
If an existing RocketEngine entity has to be deleted, the following relative URL should be called: 
    "/ShipRoleService/rocketengine/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following StageEngine columns: 
    - column: RocketEngine 
    - column: EngineCount 
    - column: RocketStage 
    - column: Role 
The table should have the title "StageEngines" und the data must be loaded from the server with the following relative URL: 
    "/ShipRoleService/stageengine/rocketengine/{id}"

2. The ShipRoleView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing ShipRole entity should be loaded from the relative URL: 
    "/ShipRoleService/shiprole/{id}"   (HTTP-GET) 
If a new ShipRole entity has been created, the new entity should be posted to the relative URL: 
    "/ShipRoleService/shiprole"   (HTTP-POST) 
If an existing ShipRole entity has been updated, the modified entity should be sent to the relative URL: 
    "/ShipRoleService/shiprole/{id}"   (HTTP-PUT) 
If an existing ShipRole entity has to be deleted, the following relative URL should be called: 
    "/ShipRoleService/shiprole/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ShipAssignment columns: 
    - column: ShipRole 
    - column: Notes 
    - column: Mission 
    - column: Ship 
The table should have the title "ShipAssignments" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/shipassignment/shiprole/{id}"

3. The StageEngineView must contain the following fields: 
    - name: EngineCount   type: INT 
    - name: RocketEngine   type: RocketEngine 
    - name: RocketStage   type: RocketStage 
    - name: Role   type: STRING 
The data source for the [RocketStage] select control should be loaded from the relative URL: 
    "/LaunchVehicleService/rocketstage"   (HTTP-GET) 
The data source for the [RocketEngine] select control should be loaded from the relative URL: 
    "/ShipRoleService/rocketengine"   (HTTP-GET) 
An existing StageEngine entity should be loaded from the relative URL: 
    "/ShipRoleService/stageengine/{id}"   (HTTP-GET) 
If a new StageEngine entity has been created, the new entity should be posted to the relative URL: 
    "/ShipRoleService/stageengine"   (HTTP-POST) 
If an existing StageEngine entity has been updated, the modified entity should be sent to the relative URL: 
    "/ShipRoleService/stageengine/{id}"   (HTTP-PUT) 
If an existing StageEngine entity has to be deleted, the following relative URL should be called: 
    "/ShipRoleService/stageengine/{id}"   (HTTP-DELETE)