This is all design and workshop material around the uploader: MVP, Post MVP, and Process
Workshop: MVP, Post MVP, and Process
| MVP | How do we meet this need/ consideration | Post MVP | |
|---|---|---|---|
| FE (Front End) | Secure log in |
| Blank sheet – Validation occurs once uploaded |
View of data sets due + time frames | User Interface - User interaction/table | Pre-formatted sheet – Validation occurs on an excel sheet | |
Ability to upload CSV or XLSX files during submission |
| Online form | |
Only upload current data |
| ||
Agreement with data sharing and use (IG) |
| ||
Interaction only for a user with data from their associated HEI |
| ||
Report on passed/failed validation |
| ||
Upload area – Status of data submitted, a report from the last upload, download template/guidance | User Interface | ||
| FE Validation | Confirm whole numbers | This needs to be clear for the devs to implement | |
Starters must be more than 0 | This needs to be clear for the devs to implement | ||
Makes logical “mathematical” sense (E.g. total number of starting students add up when factoring completions and leavers) | This needs to be clear for the devs to implement | ||
Values in fields agreed from a list of values, data types | This needs to be clear for the devs to implement | ||
| Check current submissions against previous and flag any change to allow HEI to validate | Needs investigating | ||
| Warn if a number of starters are higher than plan | Needs investigating | ||
| BE (Back End) | Uploaded data “passed” stage 1 validation lands in the staging area (How long+ how/when) | This needs to be worked out with the BE and NDW team/specialists | Design reports submissions like HEE admin but for local office only |
Placement activity in weeks (+0.5 partial) | |||
HEE teams have agreed on access to data sets for 2nd validation | |||
Dev access to data in the staging area after initial validation | |||
Reference data is maintained/available for comparison | |||
Data to be amendable and adjustable | |||
Access to the latest data at any time across functions | |||
| Process/Parking | Link to previous submissions at uploader stage | This could be a part of the User Interface | |
| Dropdown list for placement providers | Template? | ||
| Course length in months | Business need to agree on this | ||
| Consistent definitions | Business need to agree on this | ||
| Agreement from end-users on data types, fields and values | Business need to agree on this | ||
| Known email address for each contact | HEE Admins? | ||
| Placement tariff | Were not sure what this is just yet or where it sits? - Flagged as MVP via separate DITAG request, but further info required to understand the amount of work required to build this. | ||
| Testing in Jan with go live in March | DITAG/UX designer to run testing | ||
Automated reminders for outstanding data | System (probably back-end) | ||
Testing with education providers | DITAG/UX designer to run testing | ||
Ability to liaise with ETL dev for onboarding | ? | ||
Verified emails and passwords | Who provides these? | ||
Assurance that the tool is secure | We can do this in the Front end User Interface with acceptance and Policies/Cookies | ||
Information schedule dictates what information is required for | HEE | ||
Caveats to data visible to those users responsible for reporting | HEE | ||
Users notified when new data is available | System | ||
Timely access to agreed info reports | System/HEE | ||
Decisions on what is reported (Finance, quality, RTT) | HEE | ||
Dropdown list for qualification, the course title, pathway and mode | Template: Can you copy and paste if the value is in the drop-down? |
Requirements Master Document with Acceptance Criteria
Wireframes: https://projects.invisionapp.com/freehand/document/vwzjW1cVy
Add Comment