Prompt for the ProgrammplanApp

Please create a React-JS application for the ProgrammplanModule. The application  has to offer the following views for the user interface: 
    1. ProgrammplanView 
    2. SignalphaseView 
    3. UeberwegView 
    4. UmgangsbezeichnungView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The ProgrammplanView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Endzeit   type: STRING 
    - name: Kreuzung   type: Kreuzung 
    - name: Name   type: STRING 
    - name: Startzeit   type: STRING 
    - name: Steuerstrategie   type: Steuerstrategie 
    - name: Tagtyp   type: STRING 
    - name: Zykluszeit   type: LONG 
The data source for the [Kreuzung] select control should be loaded from the relative URL: 
    "/KreuzungService/kreuzung"   (HTTP-GET) 
The data source for the [Steuerstrategie] select control should be loaded from the relative URL: 
    "/KreuzungService/steuerstrategie"   (HTTP-GET) 
An existing Programmplan entity should be loaded from the relative URL: 
    "/ProgrammplanService/programmplan/{id}"   (HTTP-GET) 
If a new Programmplan entity has been created, the new entity should be posted to the relative URL: 
    "/ProgrammplanService/programmplan"   (HTTP-POST) 
If an existing Programmplan entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProgrammplanService/programmplan/{id}"   (HTTP-PUT) 
If an existing Programmplan entity has to be deleted, the following relative URL should be called: 
    "/ProgrammplanService/programmplan/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Signalphase columns: 
    - column: Gelb 
    - column: Reihenfolge 
    - column: IstRaeumzeit 
    - column: Beschreibung 
    - column: Programmplan 
    - column: IstGeschuetztesAbbiegen 
    - column: MaxGruen 
    - column: Rot 
    - column: Signalgruppe 
    - column: MinGruen 
The table should have the title "Signalphases" und the data must be loaded from the server with the following relative URL: 
    "/ProgrammplanService/signalphase/programmplan/{id}"

2. The SignalphaseView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Gelb   type: LONG 
    - name: IstGeschuetztesAbbiegen   type: BOOL 
    - name: IstRaeumzeit   type: BOOL 
    - name: MaxGruen   type: LONG 
    - name: MinGruen   type: LONG 
    - name: Programmplan   type: Programmplan 
    - name: Reihenfolge   type: LONG 
    - name: Rot   type: LONG 
    - name: Signalgruppe   type: Signalgruppe 
The data source for the [Programmplan] select control should be loaded from the relative URL: 
    "/ProgrammplanService/programmplan"   (HTTP-GET) 
The data source for the [Signalgruppe] select control should be loaded from the relative URL: 
    "/VerkehrsartService/signalgruppe"   (HTTP-GET) 
An existing Signalphase entity should be loaded from the relative URL: 
    "/ProgrammplanService/signalphase/{id}"   (HTTP-GET) 
If a new Signalphase entity has been created, the new entity should be posted to the relative URL: 
    "/ProgrammplanService/signalphase"   (HTTP-POST) 
If an existing Signalphase entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProgrammplanService/signalphase/{id}"   (HTTP-PUT) 
If an existing Signalphase entity has to be deleted, the following relative URL should be called: 
    "/ProgrammplanService/signalphase/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following PhasenAspekt columns: 
    - column: SignalAspekt 
    - column: Signalphase 
    - column: StartOffset 
    - column: EndOffset 
The table should have the title "PhasenAspekts" und the data must be loaded from the server with the following relative URL: 
    "/SignalFarbeService/phasenaspekt/signalphase/{id}"

3. The UeberwegView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: HatZebrastreifen   type: BOOL 
    - name: IstEbenerdig   type: BOOL 
    - name: IstSignalisiert   type: BOOL 
    - name: Kreuzung   type: Kreuzung 
    - name: Typ   type: STRING 
The data source for the [Kreuzung] select control should be loaded from the relative URL: 
    "/KreuzungService/kreuzung"   (HTTP-GET) 
An existing Ueberweg entity should be loaded from the relative URL: 
    "/ProgrammplanService/ueberweg/{id}"   (HTTP-GET) 
If a new Ueberweg entity has been created, the new entity should be posted to the relative URL: 
    "/ProgrammplanService/ueberweg"   (HTTP-POST) 
If an existing Ueberweg entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProgrammplanService/ueberweg/{id}"   (HTTP-PUT) 
If an existing Ueberweg entity has to be deleted, the following relative URL should be called: 
    "/ProgrammplanService/ueberweg/{id}"   (HTTP-DELETE)

4. The UmgangsbezeichnungView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Land   type: Land 
    - name: Name   type: STRING 
    - name: SignalSystem   type: SignalSystem 
    - name: Sprache   type: STRING 
The data source for the [SignalSystem] select control should be loaded from the relative URL: 
    "/SignalSystemService/signalsystem"   (HTTP-GET) 
The data source for the [Land] select control should be loaded from the relative URL: 
    "/LandService/land"   (HTTP-GET) 
An existing Umgangsbezeichnung entity should be loaded from the relative URL: 
    "/ProgrammplanService/umgangsbezeichnung/{id}"   (HTTP-GET) 
If a new Umgangsbezeichnung entity has been created, the new entity should be posted to the relative URL: 
    "/ProgrammplanService/umgangsbezeichnung"   (HTTP-POST) 
If an existing Umgangsbezeichnung entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProgrammplanService/umgangsbezeichnung/{id}"   (HTTP-PUT) 
If an existing Umgangsbezeichnung entity has to be deleted, the following relative URL should be called: 
    "/ProgrammplanService/umgangsbezeichnung/{id}"   (HTTP-DELETE)