Since the scope of the Trainee View is limited to current functionality, the scope relating to Trainee JIRA tickets should be as follows:
...
Process Name | T-2 Trainee Login FURTHER DISCUSSION REQUIRED | Comments MVP |
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? I expect all trainees will require new login credentials but they will not have to interact with us They won 't need to re register. I imagine we will setup all trainees with a profile in TIS and send out creds via emailregister' as we will send out logins as and when we migrate trainees to TIS. What about users transitioning from Synapse? What will happen to details there? The process will be the same as they are transitioning from one system to another. |
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 |
| |
JIRA Reference | N/A | |
Audit Log | TBD |
...
T-3 Trainee Logout | Comments MVP | |
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 | N/A | |
JIRA Reference | N/A | |
Audit Log | TBD |
...
Process Name | T-4 View Summary | Comments |
Description | Trainee has the ability to view the summary screen | AP - Not sure summary screen is required as information presented is not extensive. IO - will there be anything to display?MVP? Could be a judgement call from steve? I don't think we need it but i suppose that depends on the design. If we have historical and future information presented the summary could contain current details of placement, programme, assessment etc. |
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-12 Submit OOP | Comments | ||
Description | User is able to submit their OOP request digitally from end to end | |||
Actors | Trainee | |||
Pre-Conditions | Logged in | Any others? | ||
Post-Conditions | OOP form submitted | Where is the result sent? | Process Steps | User navigates to Administrator will need to receive the form in order for it the details to be checked and the application either accepted or denied by the designated authority (Dean or deputy) |
Process Steps |
| |||
Alternative Flow | Save draft | Is this necessary? Yes | ||
Rules | TBD | |||
JIRA Reference | TBD | |||
Audit Log | TBD |
...
Process Name | T-13 Submit LTFT | Comments |
Description | User is able to submit their LTFT request digitally from end to end | |
Actors | Trainee | |
Pre-Conditions | Logged in | |
Post-Conditions | LTFT request sent | Where is the result sent? Administrator will need to receive the form in order for it the details to be checked and the application either accepted or denied by the designated authority (Dean or deputy) |
Process Steps |
| |
Alternative Flow | N/A | |
Rules | TBD | |
JIRA Reference | TBD | |
Audit Log | TBD |
...