Hwfl training requirements
0 likes233 views
The document outlines functional requirements for a content management system to house online training modules. It must allow for multiple content templates, with each module containing an intro and rich media content. Registered users will receive weekly emails with links to new modules and their progress will be tracked. The system must integrate with payment and allow administrators to manage users, groups, and modules as well as generate reports on user engagement.
Hwfl training requirements
- 1. Functional requirements Content management system that has several templates for housing training content Each module will consist of a single landing page of rich media content (video, image, animation, pdf viewer) and a short introductory write up Registered users will receive an email every week with a link to a new training module Users will have to log in to see the content The system will track users that have logged in to view the training content Two templates required to start. Additional templates will be added as time passes Templates / Site must be responsive for mobile devices
- 2. Media Content (images, video, animation, slide viewer) Intro Complete Branding Template #1
- 3. Media content Intro Media content Or embeddable form (jotform) Submit Branding Template #2
- 4. Registration requirements Users can sign up online as individuals Paypal integration required Administrator can bulk upload users via .csv file Administrator can add a group Administrator can add sub-groups Signup fields include: First Name Last Name Title Email address Business / Group Name Sub Group Name User can set password Users will receive a thank you note upon online signup along with the date they will receive their first module (all users will receive a streamlined message when bulk uploaded) Administrator can designate a user as a Group Manager
- 5. Reporting requirements How many users viewed the content (# and %) How many users by group / sub group (# and %) Who viewed by user (First & Last) Who did not view by name (First & Last) Every week a designated group manager will get a report emailed to them that shows results from previous week How many users by group / sub group (# and %) Who viewed by name (First & Last) Who did not view by name (First & Last)
- 6. Communication requirements Email once a week with link to module Ideally this process is automated (Mailchimp API?) Emails are pre-scheduled according to start date When they sign up user first receives module 1, regardless of when user signs up For example: if user 1 signs up today (Oct 22) she receives a link to module 1 on the first Monday of the following month (Nov) If user 2 signs up Nov 1st, hell receive module 1 on Dec 1st. User 1 will receive module 2 on Dec 1st.
- 7. Access control requirements User has a user name (email address) / password User can edit / change password User can get password reminder email if password is forgotten Users are associated with a Group / Organization and potentially a sub-group User has one week to view each module, after which time that module will become inactive for the user User can log into a module only twice before they can no longer log in
- 8. Administrator requirements Administrator can log in Administrator can see all modules Administrator can reorder existing modules Administrator can edit existing modules Administrator can create a new module using a simple CMS tool Administrator can bulk upload new users using a CSV file Administrator can delete users Administrator can bulk delete users Administrator can delete groups of users & subgroups Administrator can see basic reports (see reporting requirements) Administrator can export report data to send to users