Requirement R4.5.10 Requirement: Requirement R4.5.11 R4.5.11 The MCRS must authorise any active user to perform any function on any entity provided the function to be performed is included in an active role that has been granted to that user or to any active groups to the user belongs, specifically in relation to that entity, including those roles it inherits from its service, parent entity or class (if any). The specific of inheritance used by the model role service are as follows: Root aggregations inherit from the record service and their class; Child aggregations inherit from their parent aggregation and their class; Components use the access control list of the record they belong to (they do not have their own access control lists); Disposal holds inherit from the disposal holding service; Disposal schedules inherit from the disposal scheduling service; Entity inherit from their respective service; Function definitions inherit from the service of their entity type; Groups inherit from the user and group service; Metadata element definitions inherit from the metadata service; Records inherit from their parent aggregation and their class; Roles inherit from the role service; Templates inherit from the metadata service; and inherit from the user and group service. The roles an entity inherits from its service, parent entity or class will be influenced by the setting of the Include Inherited Roles Flag, under R4.5.10. Administrative roles will always be inherited, while non-administrative roles will only be inherited if the Include Inherited Roles Flag is set.
Requirement R4.5.10 Requirement: Requirement R4.5.11 R4.5.11 The MCRS must authorise any active user to perform any function on any entity provided the function to be performed is included in an active role that has been granted to that user or to any active groups to the user belongs, specifically in relation to that entity, including those roles it inherits from its service, parent entity or class (if any). The specific of inheritance used by the model role service are as follows: Root aggregations inherit from the record service and their class; Child aggregations inherit from their parent aggregation and their class; Components use the access control list of the record they belong to (they do not have their own access control lists); Disposal holds inherit from the disposal holding service; Disposal schedules inherit from the disposal scheduling service; Entity inherit from their respective service; Function definitions inherit from the service of their entity type; Groups inherit from the user and group service; Metadata element definitions inherit from the metadata service; Records inherit from their parent aggregation and their class; Roles inherit from the role service; Templates inherit from the metadata service; and inherit from the user and group service. The roles an entity inherits from its service, parent entity or class will be influenced by the setting of the Include Inherited Roles Flag, under R4.5.10. Administrative roles will always be inherited, while non-administrative roles will only be inherited if the Include Inherited Roles Flag is set.
MoReq2010-Test-Framework-Pre-Qualification-Questionnaire.docx