Requirements (also catalog requirements) and measures should have assignable priorities. Priorities should be implemented as a separate entity named Priority. This entity will have the following fields:
name: Name of the priority level.
level: Numeric value representing the priority level, higher values indicate higher priorities.
The existing IT-Grundschutz attribute gs_absicherung should be replaced by the new priority levels as follows:
Basic requirements should be assigned the highest priority level (30).
Standard requirements should be assigned a medium priority level (20).
Requirements for increased protection needs should be assigned the lowest
priority level (10).
Please note that the change to the gs_absicherung attribute may affect Issues #80 and #98.
As part of this feature, create the necessary classes and relations in the data model, as well as the required database migrations.
Requirements (also catalog requirements) and measures should have assignable priorities. Priorities should be implemented as a separate entity named
Priority. This entity will have the following fields:name: Name of the priority level.level: Numeric value representing the priority level, higher values indicate higher priorities.The existing IT-Grundschutz attribute
gs_absicherungshould be replaced by the new priority levels as follows:Please note that the change to the
gs_absicherungattribute may affect Issues #80 and #98.As part of this feature, create the necessary classes and relations in the data model, as well as the required database migrations.