Page:
Functionality required by FRADrive
4
Functionality required by FRADrive
Steffen Jost edited this page 2021-09-14 17:02:27 +02:00
Table of Contents
- A Course may come in different flavors (currently 2, U2W-Schools?) and each has the following steps:
- Enrollment (may require qualification, performed by company-supervisor)
- Lectures for all participants (= U2W-Lecture?)
- Multiple Examinations for 1-3 participants (= U2W-Exercise Class?)
- Automatic re-enrollment for electronic refresher course (separate courses for each flavor?) after a certain time (usually 2 years)
- Course Templates are a must!
- Overview by flavor: which participant has which qualification since when? duration until next refresher?
- Students
- are associated with a company (external) or a department (internal)
- do not manage themselves, but are managed by a company officer
- manager and student may be identical, i.e. self-managed
- multiple manager can be restricted to manage certain sub-groups only
- external are allowed to provide an email address for e-learning passwords
- Overview/Check that rooms bookings do not conflict and satisfy required participants (training cars are not modeled at all, since each examiner has their own training car)
- Overview/Check that tutors have no conflicting lectures/exercises
- Various interfaces to:
- AVS via REST/HTTP.
AVS is ultimate DB for current driving status and knows mail address (but no email) - E-Learning via hourly CSV Files.
We start and remove required e-courses and receive a positive result or nothing - Active Directory for login. Only available for Fraport Employees; knows email address and maybe department.
- Print-center via ???
- AVS via REST/HTTP.
- Copy and edit courses/tutor from last year to current
- Support for billing
- Statistical analysis: which company books how many courses, etc.
Steffen to check with AVN-A
- U2W-Term become Annual Quarters
- U2W-Schools become ???
Steffen has next meeting 13.09.21