Process Name | T-1 New Registration | Comments |
Description | User has the ability to register to use the TIS system directly | Is this a necessary story? Do trainees have the ability to request Intrepid access? Do we need same/separate login details for new TIS, so migration consideration? Trainees will not be requesting access we will send creds out as part of the onboarding prcoess. We will have to consider how we migrate the current trainees onto TIS. |
Actors | Trainee | |
Pre-Conditions | TBC | |
Post-Conditions | Trainee has access to new TIS system - login / logout capability | |
Process Steps |
| What interaction should this have with Admin UI? What are the back end implications? User able to change their password once logged in for the first time. User name will be email address. Processes to be done by the admins/system not the trainee. |
Alternative Flow | User is registered from <another system> | |
Rules | TBC | Format of username? Email Validation of password? None What security should be implemented? There will be a trainee 'role' applied to all trainee users. |
JIRA Reference | New story TBD | Wider discussion necessary on whether this is a valid story, before writing a JIRA ticket |
Audit Log | TBC |
Process Name | T-2 Trainee Login | Comments |
Description | Trainee has the ability to login using the details they were registered for the service with | Will they be able to use their old details, or have to re-register? They won't need to re register. I imagine we will setup all trainees with a profile in TIS and send out creds via email. |
Actors | Trainee | |
Pre-Conditions | Trainee has been registered on system Trainee has validated their registered details | |
Post-Conditions | Trainee is able to view the space | |
Process Steps |
| |
Alternative Flow | T-17 Forgotten Username T-18 Forgotten Password T-19 Username / Password Error | |
Rules | Error validation? | Invalid email warning? Password reset function. |
JIRA Reference | TBD | |
Audit Log | TBD |
T-3 Trainee Logout | Comments | |
Description | Trainee has the ability to logout of the system | |
Actors | Trainee | |
Pre-Conditions | Trainee has been registered on system Trainee has validated their registered details | |
Post-Conditions | Trainee leaves logged in view of system securely | |
Process Steps |
| |
Alternative Flow | N/A | |
Rules | Error validation? | |
JIRA Reference | TBD | |
Audit Log | TBD |
Process Name | T-4 View Summary | Comments |
Description | Trainee has the ability to view the summary screen | Not sure summary screen is required as information presented is not extensive. |
Actors | Trainee System | |
Pre-Conditions | Trainee is logged in | |
Post-Conditions | Summary details in view Navigation menu available | |
Process Steps |
| |
Alternative Flow | N/A | |
Rules | Validation rules? | |
JIRA Reference | TBD | |
Audit Log | TBD |
Process Name | T-5 View & Edit Personal Details | Comments |
Description | User has the ability to view and update their own details | |
Actors | Trainee | |
Pre-Conditions | Trainee is logged in to their own account | |
Post-Conditions | Trainee can see currently stored details in an editable format Trainee can make and save changes to specified details System updates personal details centrally | |
Process Steps |
| Surname |
Alternative Flow | N/A | |
Rules | Validation rules? | See Trainee UI field definition spreadsheet. |
JIRA Reference | TBD | |
Audit Log | TBD |
Process Name | T-6 View Programme | Comments |
Description | User has the ability to view their Programme details | |
Actors | Trainee | |
Pre-Conditions | User is logged in | Is there a need for detailed Programme view? Not as such, the details of the Programme are the placements and assessments which we have considered. |
Post-Conditions | System presents relevant detail | |
Process Steps |
| What details are shown on summary v detail? Programme Name Should user be presented with previous view or summary screen? View will show historical programmes, current and future programmes if applicable |
Alternative Flow | N/A | |
Rules | Validation rules?
| |
JIRA Reference | TBD | |
Audit Log | TBD |
Process Name | T-7 View Placement | Comments |
Description | User has the ability to view their Placement details | |
Actors | Trainee | |
Pre-Conditions | User is logged in | |
Post-Conditions | System presents relevant detail | |
Process Steps |
| Start Date should present historical, current and future placements |
Alternative Flow | N/A | |
Rules | View only | |
JIRA Reference | TBD | |
Audit Log | TBD |
Process Name | T-8 View Assessment | Comments |
Description | User has the ability to view their Assessment details | |
Actors | Trainee | |
Pre-Conditions | User is logged in | |
Post-Conditions | System presents relevant detail | |
Process Steps |
| Review should present historical, current and future assessments |
Alternative Flow | ||
Rules | View only | |
JIRA Reference | TBD | |
Audit Log | TBD |
Process Name | T-9 View Courses | Comments |
Description | User has the ability to view their Course details | Do we need this as part of the MVP? |
Actors | Trainee | |
Pre-Conditions | User is logged in | |
Post-Conditions | System presents relevant detail | What details can be seen? |
Process Steps |
| Should there be a summary view of courses? |
Alternative Flow | T-19 Book Course | Is this necessary for MVP? |
Rules | View Only | |
JIRA Reference | TBD | |
Audit Log | TBD |
Process Name | T-10 Submit Form-R (Part A) | Comments |
Description | User is able to submit the form that will update their personal details with the GMC | |
Actors | Trainee | |
Pre-Conditions | User is logged in | |
Post-Conditions | User personal details are updated in TIS across all systems User personal details are updated with GMC | |
Process Steps |
| Should this be a manual trigger or automated whenever personal details are updated? Manual Trigger perhaps more appropriate dependent on design. Should this be from Personal Details space, or Assessments, alongside Part B? autopopulation will be required from personal details and other sections. where appropriate. |
Alternative Flow | T-20 No submission of Form R (Part A) | Only relevant if the Part A submission is automated |
Rules | Validation rules? | |
JIRA Reference | TBD | |
Audit Log | TBD |
Process Name | T-11 Submit Form-R (Part B) | Comments |
Description | User is able to submit the form that will update their personal details with the GMC | |
Actors | Trainee GMC | |
Pre-Conditions | User is logged in Form-R submission is imminent | Can this be submitted anytime? No it is usually requested by the local office prior to the ARCP. i think the timescales differ in different local offices. |
Post-Conditions | Form-R (Part B) is submitted | |
Process Steps |
| Where should this be located? Alongside Assessments, or in it's own area? Unsure. May be best to keep both parts together in their own space. |
Alternative Flow | TBD | Are drafts possible? Yes i think the trainee should be able to save the form as they go or autosave as with other areas of the system. |
Rules | Validation Rules? | |
JIRA Reference | TBD | |
Audit Log | TBD |
Process Name | T-12 Submit OOP | Comments |
Description | ||
Actors | ||
Pre-Conditions | ||
Post-Conditions | ||
Process Steps | ||
Alternative Flow | ||
Rules | ||
JIRA Reference | ||
Audit Log |
Process Name | T-13 Submit LTFT | Comments |
Description | ||
Actors | ||
Pre-Conditions | ||
Post-Conditions | ||
Process Steps | ||
Alternative Flow | ||
Rules | ||
JIRA Reference | ||
Audit Log |
Process Name | T-14 Submit LTFT | Comments |
Description | ||
Actors | ||
Pre-Conditions | ||
Post-Conditions | ||
Process Steps | ||
Alternative Flow | ||
Rules | ||
JIRA Reference | ||
Audit Log |
Process Name | T-15 Submit Expenses | Comments |
Description | ||
Actors | ||
Pre-Conditions | ||
Post-Conditions | ||
Process Steps | ||
Alternative Flow | ||
Rules | ||
JIRA Reference | ||
Audit Log |
Process Name | T-16 Access Help & Support | Comments |
Description | ||
Actors | ||
Pre-Conditions | ||
Post-Conditions | ||
Process Steps | ||
Alternative Flow | ||
Rules | ||
JIRA Reference | ||
Audit Log |
Process Name | T-17 Forgotten Username | Comments |
Description | ||
Actors | ||
Pre-Conditions | ||
Post-Conditions | ||
Process Steps | ||
Alternative Flow | ||
Rules | ||
JIRA Reference | ||
Audit Log |
Process Name | T-18 Forgotten Password | Comments |
Description | User has ability to navigate to "Posts" area within the UI from their current location on site | Story not needed |
Actors | Local Admin | |
Pre-Conditions | Logged in HEE Admin | Admin is a permission applied by user |
Post-Conditions | View Posts landing page | |
Process Steps | 1. View navigation 2. Select "Posts" 3. Present landing page | |
Alternative Flow | N/A | |
Rules | - Error: page unavailable | |
JIRA Reference | N/A | |
Audit Log | N/A |
Process Name | T-19 Book Courses | Comments |
Description | User has the ability to book new Courses | Do we need this as part of the MVP? |
Actors | Trainee | |
Pre-Conditions | User is logged in | |
Post-Conditions | System presents relevant detail | What details can be seen? |
Process Steps |
| |
Alternative Flow | T-9 - View Course | ?? |
Rules | Validation Rules? | |
JIRA Reference | TBD | |
Audit log | TBD |
Add Comment