Handling of sub categories

[wurstbrot]

The proposed Build and Deployment/Deployment and the activity "Use of User Roles for SCM" are sub-categories of Role Based Access Control and BCDR.

Options

I see the following two options here:

• Allow Sub-Activities marked as such and add a filter to the UI
• Attached details to existing activities

Allow Sub-Activities marked as such and add a filter to the UI

Benefits:

• The generic activity, e.g. "Role based authentication and authorization", is often too generic so that depending on the system implemented, it might be on an other level. Sub-Activities would allow to point this out by having their own level.

Weakness:

• In maturity models, we try to de-duplicate activities

Attached details to existing activities

Put the details as an assessment / comment into the father category.

Weakness/Benefits swapped.

[wurstbrot]

Request for comments @ioggstream @0x41head @clazba @maxwhalezhou

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. :calendar: It will be closed automatically in one week if no further activity occurs.

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity.