The table below is a collection of requirements, considerations, must have's and must not's, process, features and functionality gathered from workshops with Senior/Regional Business Managers and Local Administrators for the 'Trainee Application'.
...
| Feature | Element | Interaction | Comments | Actions |
|---|---|---|---|---|
| All features | Syncing all data | No duplications | If the application does not sync with other systems I will not use it | We need to make sure that any features in the application do not require duplication of effort to update other systems with the same data. The application should automatically update any other systems with the same data tables. |
| Personal details | Contact details | Sync all systems with this data | The ability to sync all my contact details. My multiple emails for work into one central place for contacting me | Investigate how this might work. Who owns these different contact emails. We may need the user to submit all and we update in TIS? |
| Personal details | Personal details and training grade | Incorrect information | The ability to review and then update this to be correct | If we do not allow the users the ability to edit this area due to ESR we may need to find a way to log a 'notification' that is sent to the Admin to let them know this is incorrect |
| Programme membership | CCT Date calculator | Interactive | We need to look at exactly what they need this to do. Does this have more opportunity to calculate other things for the user? Is this off the shelf plug-in, or is this tied into other features and has other dependencies? | We would need to look at the tech for this. Is this something we build or is this off the shelf? |
| High-level details | Read-only/links? | Who's who. Organizational structure. Who is the 'Dean' for the Trust I am working with? Who are the senior people or people who I may need to know and how do I contact them? | A way of showing the hierarchy of an establishment so that the Trainee feels they know the right people before they begin. Helps with support | |
| Training | Contracts | No contracts for training | Think this is frustration and causes lots of issues with benefits | |
| Placements | Rotations | Read-only | Rotation dates and trusts (These must be correct) | We would need to check how this would pull into the application? |
| Rotations | Interaction/notification | Leave request for future placements | How would this feedback to the Administrator? Is this a form or a request for a form? | |
| Rotations | Read-only/links | A frustration is that they have no way of knowing about job opportunities (eg. Fellowships) | We should investigate this further if they want to see the opportunities. Maybe a lost with links? | |
| Placements | Read-only | A list of future placements and rotations | The ability to view upcoming rotations and placements scheduled for the trainee. This gives them the ability to flag up anything that is wrong or they need to change | |
| Assessments | ARCP | Read-only/links? | ARCP Checklist (Tickbox culture) | We should check exactly what data needs to be on this list? Does anything cause issues with data protection? |
| ARCP | Read-only/Interaction | These may tie into the 'Calendar' so that the Trainee is able to plan and schedule around these dates: RCOA e-portfolio style checklist was mentioned, think of a traffic light style checklist of essential documents for ARCP | Think around how this may work in a Checklist that they follow and ticks off as they complete different actions around ARCP. Think about how this may also tie in with a calendar and how the Admins feed these dates into this feature through TIS? | |
| Forms | ||||
| Notifications | ||||
| Calendar | ||||
| On/Off-boarding | ||||
| Support | ||||
| Other ideas |
...