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.
Execution of the function provides immediate feedback to the user Execution of the function provides some feedback to the user Execution of the function provides no feedback to the user Execution of the function requires more than one step by the user Function is executed as part of a broader operation Function is executed in two or more phases or as part of two or more operations Function behaves differently under different conditions Function cannot be executed under certain conditions There is more than one way of performing the function Date checked (by test centre): Provide additional explanation of observations given above (test centre to complete): Requirement R11.4.1 Requirement: Requirement R11.4.2 R11.4.2 Whenever an MCRS exports entities, under R11.4.1 or R11.4.3, the MCRS must not, by default, export residual entities unless the authorised user specifically includes them.However, where the user so chooses, the MCRS must export all entities, including both active and residual. For example, if the user exports an aggregation, only the active records in the aggregation would normally be included in the export.However, the MCRS must also provide the user with an option to export the aggregation and include both its active and residual entities.
Ability to specify the view where the application will open or have the application always open at the most recent view; Keep track of the user’s location in the application using a breadcrumb trail or equivalent; Allow users to browse back to previous screens and views, see N101.5.8; and Provide an ability to create personal saved searches and saved report definitions, see R10.4.23 and R10.4.27. In what ways can the GUI be personalised to suit individual and can these settings be saved as a user’s personal default? Answer this non-functional requirement (in 200 to 400 words): Requirement N101.5.5 Non-Functional Requirement (this requirement is not tested): Requirement N101.5.6 N101.5.6 alerts and notifications may also be configurable. Does the GUI make use of audio alerts and notifications, and can audio alerts, notifications, and volume settings be individually adjusted and personalised under N101.5.5? Answer this non-functional requirement (in 200 to 400 words):
Provide additional explanation of observations given above (test centre to complete): Requirement R301.4.3 Requirement: Requirement R301.4.4 R301.4.4 Where there is more than one component in a record, the MCRS must generate a unique Presentation Order for each component. The Presentation Order provides a simple way of logically ordering the components of a record, when there is more than one, so they may be listed in a relevant way.The Presentation Order of each component must be unique; meaning no two components of the same record may have the same Presentation Order. For example, when capturing the contents of a web page as a series of components, the main HTML script may be listed first in presentation order, before the other components (CSS, JavaScript, images, etc.).Similarly, multipart datafiles may have an intrinsic order, an email message may be presented before its attachments, and so on. MoReq2010® does not give specific guidance on the presentation order of components within a record for different content types. If the solution has a GUI then attach a screenshot showing how the function is performed: Answer this functional requirement (in 100 to 250 words): Requirement R301.4.4