14.22 Risk Assessment
This section documents the number of changes to specific areas of the imc Learning Suite; along with a risk assessment. These changes include both enhancements and fixes to resolve known software errors. This risk assessment is general and does not assess a risk for a certain use case or scenario because this varies for each customer individually. Each change was checked according to the certified processes (ISO 9001:2008) of our development and QA department – at least two times before delivery. It is nevertheless recommended for customers to perform own testing of customer specific scenarios or use cases where changes could impact key scenarios.
Modifications in Version 14.22
Functional area | Risk of changes | |||
High*) | Medium | Low | Minimal risk | |
Accessibility | ||||
API | 1 | |||
Architecture | ||||
Attendance tracking | ||||
AVETMISS | ||||
Bookshelf | ||||
Catalogues | 1 | |||
Certifications | ||||
Clients / Multi-tenant | ||||
Compliance Workflows | ||||
Configuration | 1 | |||
Courses | 1 | 3 | ||
Channels | 1 | 3 | ||
Dashboards and Panels | ||||
Data privacy | 0 | |||
Documentation | ||||
e-Payment gateways | ||||
Easy Course Creation | ||||
Emails & Notifications & iCal | 3 | |||
Enrolment processes | 1 | 1 | ||
Equivalences | 1 | |||
Feedbacks | ||||
Gamification | ||||
Integration and interfaces (3rd party) | 3 | 2 | ||
Language handling | ||||
Learner area | ||||
Learning App Windows | ||||
Learning paths | ||||
LTI | 1 | |||
Media | ||||
Miscellaneous | ||||
Mobile Apps | 1 | |||
Multi-language support | ||||
Navigation | ||||
On-the-job Training | ||||
Recommendation engine | ||||
Reporting | 1 | 3 | ||
Resource Management | ||||
SCORM / AICC | 1 | |||
Skill Management | 1 | |||
Supervisor functions | ||||
System Validation | 1 | |||
System wide | 1 | 1 | ||
Tests | ||||
Time Zones | ||||
Tutor functions | ||||
Users / Groups | ||||
UX / Design | 2 | |||
Virtual Classroom | 1 | |||
Wording | 1 | |||
xAPI WBT | 1 | |||
Total issues: | 3 | 6 | 27 | 2 |
High risk change notes:
Sanitizer bypass on System Texts:
The sanitizer bypass is flagged as high risk due to the ability to enter HTML code. In order to edit System Texts a user would require access rights to the System texts function and clearances to wording bundles; this is normally only granted to System Administrators.Meta tag refactoring:
There is a risk that some functionally obsolete meta tag could be removed if assigned to learning objects.Large contenful paint:
Lazy loading introduced for pages changes the loading sequence and will change display of content in some screens.