LLMCMSS.01 - LLM CMS Specification Main Part

This page and its child pages contain the specification work and results for the LLM Central management system (LLMCMS).

ATTENTION:  The online-versions of this pages in the LLM-Wiki shall only be read with Firefox (3.5 or newer) browsers! Microsoft Internet Explorer does not render some styles used by the Wiki framework correctly.

Contents:

1. Overview
2. Nature of this specification
3. Functional specification areas
4. Non-functional specification areas
5. Implementation and architectural requirements
6. Optional system features
7. Conventions in this specification
8. Sources and additional information for this Specification
9. Derived Requirements for other parts of the LLM system
10. Parts of this specification

Overview

The LLMCMS is part of the LLM system.

The LLM system, detailed in LLMTOS is the technical system providing the LLM service, also detailed in LLMTOS.

The LLMCMS shall provide all necessary over-all management functionality in the LLM system:

• Administering user account data (Password, user credentials)
• Administration of training data (programs, schedule, results, performance)
• Presentation of reports about training performance
• provide a local user interface for the LLM system user
• provide a remote user interface for local and remote system administration

NOTE: This specification consists of 10 parts. When you are starting to study this specification afresh, the recommended reading sequence is given in the parts section of this part.

LLMCMSS.01.00 Document Control

LLMCMSS.01.02 Nature of this Specification

The specification is intended to be 2 things in one:

1. A requirements specification, containing all the requirements for the LLM-CMS, functional, non-functional, etc.
2. An implementation specification, allowing to be handed over to an implementation software team to be the complete base to implement the software comprising the LLF, LRF, LLM-LUI, the CMS-LUI and the CMS components

By this approach, any traceability issues between requirements and implementation specification should be able to be minimized.

As a result, this approach adds further areas to the specification:

• requirements concerning specific structural elements of the implemented software.
  These may also result from project constraints and already existing components, e.g. the LUI already existing in the eHome system.
• Implementation and modularity hints and rules in every part of the specification

The specification builds on a Reference Architecture (open picture in new window for reference)

LLMCMSS.01.03 Functional Specification Areas

This specification specifies implementation requirements for 5 Components of the reference architecture architecture:

• The LLM-LUI, specified in LLMCMSS.02
• The CMS-LUI, specificied in LLMCMSS.03
• The CMS itself, specified in LLMCMSS.04,  including its RUI, accessing the LLM-Database to manipulate and investigate persistent data and to indirectly control the operative components ILC, PTC and CTC and including notification and workflow processing
• The LLF - LLM system local user interface framework, on which all the components of the LUI are based, specified in LLMCMSS.05
• The LRF - LLM reporting and feedback functional component, specified in LLMCMSS.08

However, there are a set of components in the reference architecture whaich are NOT covered in LLMCMSS as they are not part of the LLM CMS subsystem:

• The CTC and PTC integration. However, there are assumptions about the behaviour of these components that have impact on LLMCMSS.06. Furthermore, the modularity issues to be considered in order to efficiently integrate these components are covered specifically in LLMCMSS.07.02.01.02.

LLMCMSS.01.04 - Non-functional specification areas

The specification also specifies other areas:

1. models and concepts for data management
2. interfaces between components and (if necessary) internal to components
3. volumetrics
4. Performance
5. Availability
6. Safety
7. Security
8. Modularity
9. Multi-Tenancy - NOT COVERED, no requirement 
10. LLMCMSS.06 - Use-Cases: e-Home, Day-Care-Center, Clinical Environment, Home-Care Professional
11. Scalability
12. Accounting - NOT  COVERED, no requirements
13. Evidence Collection & Archiving

LLMCMSS.01.05 - Implementation and Architectural Areas

• LLMCMSS.05 - The LLM LUI Framework (LLF) specification
• LLMCMSS.08 - The LLM Reporting and Feedback functionality (LRF) specification
• LLMCMSS.10 - The LLM system reference architecture
• LLMCMSS.07 - General and Implementation Aspects

LLMCMSS.01.06 - Optional System Features

This section lists optional system features and separates those included in version 1 of the LLM system implementation from those left for later versions.

Motivation for Optionality

This Specification describes part of the first version of the LLM system. The extent to which features can be implemented is determined by the project resources in the LLM project itself: project timeline and available development resources and funding.

Although the LLM project in principle tries to use existing components, there is a development effort necessary to develop the "glue" functionality. Especially the CMS and the LUI framework are part of this "Glue" functionality providing a more seamless look-and-feel and an extended amount of manageability of otherwise separated sub-systems. The LLMTOS describes a rather large number of ideas and concepts assisting in boosting user-friendlyness and lowering usage barriers, be it physiological or psychological.

However, as project timeframe is limited (the core aim of the project, the operational trial phase, has to commence as soon as possible) and so are person-hour-resources for software development and integration. All that said, it appears that not all usability features sketched in LLMTOS will make it into version 1 of the LLM system.

LLMCMSS.01.06.02 - Optional parts not part of LLM System Version 1

For the current version of the LLM system the following parts are considered optional and, as of now, not part of version 1 implementation:

1. Avatar implementation
2. Gesture support for enhanced controllers like Wii-Remote or Multi-Touch
3. Voice Recognition

However, implementation of Version 1 shall not build up roadblocks or unnecessary difficulties for a later incorporation of these features in later versions of the system. Therefore, implementation must be with such expansion in mind. Designs shall consider hooks and other expansion mechanisms as far as the  knowledge of possible integration of the later-to-be-added features is at the time of design. Reviews must contain checks for this expasion mechanisms while keeping overhead low in order not to waste resources where they should be saved.

LLMCMSS.01.06.03 - Optional part included in LLM System Version 1

However, of all the optional parts there may be a few that are indespensable when it comes to at least providing the least required level of user-friendlyness and adaptation to the needs of the target clientéle. As of the time being, these are:

1. elimination of keyboard typed input for authentication: logging on by contactless ID card.
   However, there are methods existing for authentication by security devices like fingerprint-scanners or other devices. These methods shall be used along with the software support provided in the target operation system(s).
   To further ease acceptance, mobile device methods like NFC/GSM-interoperability shall be checked in conjunction with movement detection also feasable with these devices.

LLMCMSS.01.07 - Conventions in this Specification

1. Where this specification is referenced, it will be called LLMCMSS.
2. As this work is a specification, it is extremely important to cater for traceability. By tracebility, we understand the connections between different requirements and between the different types of requirements. These connections allow to determine if a requirement is caused by another one or is a pre-requiisite for another one. In order to establish these connections, all parts of this specifications are uniquely numbered by a hierarchical naming system. These numbers are prefixed by the ID of the specification itself.
   An example for such a requirements ID is: LLMCMSS.02.01.02 which refers to the 2nd paragraph in the first chapter of the LLM LUI specification, being part 02 of this specification (LLMCMSS).
3. In order to keep requirements-IDs constants, lists in LLMCMSS shall only be appended to. New elements shall never be insterted in the midlle of a list in order for the already existing requirements to keep their numbering. In the same way, requirements rendered obsolete shall never be deleted from a list, but rather marked as "OBSOLETE:" or striked-out (like this).
4. Other referenced documents will be used in a similar, appropriate manner.
5. When it comes to references to an external document (external means not part of the LLMCMSS), only a specific issue of the respective document will be referenced. If it is impossible to rely on a consistent version numbering and administration in the external document, a snapshot of the external document will be taken and kept as a copy with LLMCMSS.

LLMCMSS.01.08 - Sources and additional information for this Specification

[LLMTOS] D3.1 LLM technical and operational specifications Issue v1.9 at the files section of Work Package 3 of the LLM site. There are tracebility issues in connection with this document as it may change in the future. To have at least one stable reference point, issue 1.9 will be tried to be marked up and linked with requirements items in the LLMCMSS. To assist this case, the document will be referenced here as LLMTOS (trace/link Work to be continued).

LLMCMSS.01.09 - Derived Requirements for other Parts of the LLM System

At numerous places in this specification, the specified functionality requires pre-requisites or certain functionality from other parts of the LLM system. At the time of writing for this specification, it is not known if the referred other parts of the LLM system are able to fulfil these requirements. One exemption from this is the LLM-DB, because its functionality for the time being is well defined by the LLM web-service reference. Anyway, the requirements to other system parts will be marked with "ENVREQ:" to denote a requirement of the LLM CMS against its environment. At review of this specification the ENVREQs will have to be checked and appropriate work packages scheduled to implement tham if not yet existing.

Specifically mentioned here shall be parts LLMCMSS.05 and LLMCMSS.09 . These two parts are, by definition, ENVREQs in their totality as they define requirements for external components.

LLMCMSS.01.10 - Parts of this specification

This specification consists of 10 parts. These parts, together with the documents referenced in the sources section above, comprise everything necessary for implementing LLMCMS. No other information source shall be necessary.

LLMCMSS.01.10.01 - Listing of parts

1. LLMCMSS.01 - this part and top level of the hierarchy
2. LLMCMSS.02 - the LLM LUI specification
3. LLMCMSS.03 - the CMS LUI specification
4. LLMCMSS.04 - the CMS service specification
5. LLMCMSS.05 - the LLF - LLM LUI Framework - specification
6. LLMCMSS.06 - LLM CMS Use Cases
7. LLMCMSS.07 - LLM CMS Aspects and Implementation Issues
   This part is concerned with Topics like Performance, Security, Safety, Modularity, Implementation and other orthogonal aspects
8. LLMCMSS.08 - LLM  reporting and user feedback data and flow models and implementation concepts
   This part specifies the function to flexibly and expandaby generate human readable and comprehensible reports and feedback information from performance and logging data throughout the LLM system or even from external systems. The common denominator is that the input information has to be stored in the LLM-database before and the result is generated in HTML form.
9. LLMCMSS.09 - CMS requirements in LLM-Database
   This part summarizes everything the CMS subsystem specified in this specification requires to be provided by the LLM-database component.
10. LLMCMSS.10 - LLM CMS Reference Architecture

LLMCMSS.01.10.02 - Recommended Reading Sequence

If you are starting studying this section from scratch, the recommended sequence of reading is:

• 01 - Main Part
• 06 - Use Cases
• 10 - Architecture
• 02 - LLM LUI specification
• 03 - CMS LUI specification
• 04 - CMS service specification
• 05 - LLF specification
• 08 - LRF specification
• 09 - LLM-DB requirements
• 07 - Aspects and Implementation