The new approach for modeling the Security Control (and its specialization) is based on Requirements. The profile changes are described in the following table:
| Before migration | After migration | Comment | ||
|---|---|---|---|---|
| Name | Type | Name | Type | |
| Security Control | Activity | Security Control | Class | Aditionally, Security Process is created to overtake the information, that cannot be stored in Security Control [Class]. |
| Security Control Family | Comment | Security Control Family | Class | The Criterion from SecurityControlFamily [comment] is moved to the Text of the SecurityControlFamily [class, requirement]. Information about the Annotated Element is moved to ToDo. |
| Enhanced Security Control | Activity | Enhanced Security Control | Class | Aditionally, Security Process is created to overtake the information, that cannot be stored in Security Control [Class]. |
| Security Control Action | Call Behavior Action | Security Process Action | Call Behavior Action | |
| - | - | Security Process | Activity | Security Process is a new element dedicated for modeling security behaviors. |
