LLMCMSS.03 - LLM CMS LUI functional specification

This part of LLMCMSS provides the functional specification for the local user interface (LUI) for the LLM system central management system (CMS).

LLMCMSS.03.00 Document Control

Item Value
LLMCMSS.03 Document properties
Document LLMCMSS.03
Issue 0.4
History - 0.1 Created due to Reference Architecture V 0.1
History - 0.2 - Updated cross-references to LLF and LRF in Reference Architecture V 0.3
- Details on LUI functions
History - 0.3

- correct numbering in LLMCMSS.03.01.xx
- LLMCMSS.03.02.03 is obsolete due to obsolence of multiple LLM instances
- LLMCMSS.03.01.02 applies only for picture code
- LLMCMSS.03.01.04 only lists schedules on LUI, editing only at CMS RUI
- LLMCMSS.03.01.07 and .08 are OPTIONAL as of LLM V 1
- LLMCMSS.03.09.02 is OPTIONAL as of LLM V 1
- LLMCMSS.03.09.03 is obsolete due to the callback-event-driven notifications
History - 0.4 - LLMCMSS.03.01.9: is now optional, not mandatory for V 1

 

LLMCMSS.03.01 CMS LUI functions

  1. The CMS LUI shall provide all functionality to be performed by the consumer of the LLM service, also referred to as the senior .
  2. Change Authentication secrets: picture code
    1. This optional function shall only be available if the user is entitled to it by their rights
    2. As LUI does not allow for arbitrary text entry, the change function applies only to the picture code and only if a user has configured one.
    3. icture code change shall require the old code and twice the new one
    4. This option shall NOT be available if authentication is done by alternative method like smart-card or sound recognition
  3. Display xTC and other (medical, etc) available performance data and feedback information, prepared by the LRF, detailed in LLMCMSS.08
    1. Display shall be initiated either by notification or deliberate user selection
    2. User selection shall include selecting only reports applicable for the user. Applicability shall be performed by matching user report selection properties against report properties. For LLM V 1.0 there shall be a collection of properties in the user profile that shall be exactly equal to the same subset of report properties.
    3. Notification selected report display shall provide a hyperlink (button) on the notification page invoking exactly one report for display 
  4. Display and Edit xTC and other schedules (repeating) and appointments (one time). Editing is done on CMS RUI
  5. Access to the functions shall be controlled by the security credentials of the user's session
  6. Apart from the UI-functions listed above the user may be presented with other display pages/windows initiated by workflows, schedules and notifications
  7. OPTIONAL: After login, a special "Login-workflow" shall be triggered in the CMS service component that may provide additional notification-triggered activity-prompts
  8. OPTIONAL: Before logout, a "logout-workflow" shall be triggered by a "logout" event in the CMS service component
  9. OPTIONAL: Activity timeouts shall be able to supervise the users activity or in-activity and shall be able to trigger corresponding events in the CMS service component to generate notifications to the user or also to other users or sessions:
    1. timeout responding to notifications
    2. OPTIONAL timeout performing no activity for a certain interval
    3. periodic timeout as long as LUI session exists to check for available information or schedules

LLMCMSS.03.02 CMS LUI Implementation requirements

  1. CMS LUI shall be based on the LLF, detailed in LLMCMSS.05
  2. CMS LUI shall use the CMS service component, detailed in LLMCMSS.04 to perform each activity
  3. CMS LUI shall allow for multiple sessions by multiple users to multiple LLMDB instances on one local terminal
  4. The LLF platform and environmental specifications also apply to the CMS LUI