What and how many superior roles are necessary for an extended system?
There should always be a global service owner who has overall responsibility for all systems. The Service Owner should be responsible for applications at the technical level and within the scope of the service, feedback and training.
Any system that can potentially have more than 200 users should have a team of 2-3 application owners. These individuals should be responsible for the application management of their system, and configuration of the use cases.
What is the maximum number of Entities for a system to be utilized efficiently?
In general, a system should have 1-5 generic Entities that are useful to the majority of users. This should also be the case at the field level per Entity - individual information can be improved at a later stage by visibility and confidentiality restrictions.
The maximum number of Entities should not exceed 15. Before creating an Entity, Application Owners should consider the following aspects:
- Are there any thematic overlaps with other existing Entities? - If so, they may be consolidated.
- Does this Entity require complex access control? – If so, it needs to be considered how to reasonably adjust application permissions.
- How many actual (not potential) users will get value from the Entity? – At least 15 users should be working with a single Entity to justify it.
How many roles are reasonable?
At the beginning, no more than 5 roles should be required. These roles should be the Application Owner along with 4 additional roles to cover the create, read, update, and delete (CRUD) operations.
- Role 1 = CRUD
- Role 2 = CRU
- Role 3 = CR
- Role 4 = R
- Role 5 = Application Owner
More complex access controls can be created using confidentiality, visibility and user context. If an Entity-specific role is required, this role should be justified after explicit validation of its necessity.
Learn more about the ITONICS Guiding Principles in this article.