Trainee UI - Scenarios

Since the scope of the Trainee View is limited to current functionality, the scope relating to Trainee JIRA tickets should be as follows:

TIS-540
TIS-684
TIS-681
TIS-539
TIS-683
TIS-92
TIS-682
TIS-278 << NOT REQUIRED, REMOVED FROM JIRA
NEW STORY REQUIRED - support
NEW STORY REQUIRED - form R, part A

Out of Scope:

TIS-193
TIS-196
TIS-200
TIS-20
TIS-171
TIS-174
TIS-319

Process Name	T-1 New Registration - FURTHER DISCUSSION REQUIRED, maybe make this a sub-story of TIS-629	Comments MVP
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 process. 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	user register a username user sets password user sets security user validates details system shares	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	TIS-629	Wider discussion necessary on whether this is a valid story, before writing a JIRA ticket
Audit Log	TBC

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 email. What about users transitioning from Synapse? What will happen to details there?
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	Traine enters username Trainee enters password System validates details System presents logged in view of system
Alternative Flow	T-17 Forgotten Username T-18 Forgotten Password T-19 Username / Password Error
Rules	Error: Invalid email entered Error: Incorrect password
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	Trainee selects to logout System logs user out System presents logged out view
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?
Actors	Trainee System
Pre-Conditions	Trainee is logged in
Post-Conditions	Summary details in view Navigation menu available
Process Steps	User logs in System presents summary User navigates through view
Alternative Flow	N/A
Rules	Validation rules?
JIRA Reference	TBD
Audit Log	TBD

Process Name	T-5 View & Edit Personal Details	Comments MVP
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	User navigates to Personal Details space System presents personal details in editable view User makes changes to relevant fields System validates changes System saves changes	Relevant Fields: Surname Forenames Known As Maiden Name Title Telephone Mobile Email Address Address 1 Address 2 Address 3 Address 4 Post Code GMC Number GMC Status EEA Resident Permit to Work Settled Visa Issued Details/Number
Alternative Flow	N/A
Rules	View & Edit select fields, see data table
JIRA Reference	TIS-540, TIS-278
Audit Log	TBD

Process Name	T-6 View Programme	Comments MVP (Synapse equivalence?)
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	User navigates to summary view System presents summary information User selects to view detail System presents detail view User selects to leave Programme Detail view System presents summary view	Summary Fields Programme Name Curriculum Start Date End Date Managing Deanery Should user be presented with previous view or summary screen? View will show historical programmes, current and future programmes if applicable IO - this could be deemed as detailed information, rather than summary, but we should discuss it further with Steve & Alex
Alternative Flow	N/A
Rules	View only
JIRA Reference	TIS-684
Audit Log	TBD

Process Name	T-7 View Placement	Comments MVP (Synapse equivalence)
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	User navigates to summary view System presents summary information User selects to view detail System presents detail view User selects to leave Placement Detail view System presents summary view << is this correct?	Start Date End Date Site Grade Specialty Placement type
Alternative Flow	N/A
Rules	View only Detailed view should present historical, current and future placements
JIRA Reference	TIS-681
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	User navigates to summary view System presents summary information User selects to view detail System presents detail view User selects to leave Assessment Detail view System presents summary view	Review (date) Curriculum Assessed Outcome Grade at Time Period From Period To
Alternative Flow	N/A
Rules	View only Detailed view should present historical, current and future assessments
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? Joanne Watson (Unlicensed)
Actors	Trainee
Pre-Conditions	User is logged in
Post-Conditions	System presents relevant detail	What details can be seen?
Process Steps	User navigates to summary view System presents summary information User selects to view detail System presents detail view User selects to leave Course Detail view System presents summary view	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 MVP (Synapse equivalence)
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	User navigates to Personal Details space System presents personal details in editable view User makes changes to relevant fields System validates changes System saves changes User selects to submit Form-R (Part A) Form-R (Part A) is sent to GMC	Should this be a manual trigger or automated whenever personal details are updated? Manual Trigger perhaps more appropriate dependent on design.
Alternative Flow	T-20 No submission of Form R (Part A)	Only relevant if the Part A submission is automated - TO BE DISCUSSED FURTHER
Rules	Autopopulation will be required from personal details and other sections, where appropriate.
JIRA Reference	N/A
Audit Log	TBD

Process Name	T-11 Submit Form-R (Part B)	Comments MVP (Synapse equivalence)
Description	User is able to submit the form that will XYZ
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	User navigates to XXX space System presents form details in editable view User completes relevant fields System validates fields System saves changes User selects to submit Form-R (Part B) Form-R (Part B) is sent to GMC Historical view of submitted Form's updated	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	T-16 Save as draft before submission	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 as per data table
JIRA Reference	TIS-539 & TIS-92
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 XXX space System presents form details in editable view User completes relevant fields System validates fields System saves changes User selects to submit OOP request OOP request is sent to XXX Historical view of submitted Form's updated
Alternative Flow	Save draft	Is this necessary?
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?
Process Steps	User navigates to XXX space System presents form details in editable view User completes relevant fields System validates fields System saves changes User selects to submit LTFT request LTFT is sent to XXX Historical view of submitted Forms updated
Alternative Flow	N/A
Rules	TBD
JIRA Reference	TBD
Audit Log	TBD

Process Name	T-14 Submit Expenses	Comments
Description	User is able to submit their Expenses request digitally from end to end
Actors	Trainee	Any others?
Pre-Conditions	Logged in
Post-Conditions	Expenses form submitted	Where do they receive outcome / follow up?
Process Steps	User navigates to XXX space System presents form details in editable view User completes relevant fields System validates fields System saves changes User selects to submit expenses request Expenses are sent to XXX Historical view of submitted Forms updated
Alternative Flow	N/A
Rules	TBD
JIRA Reference	TBD
Audit Log	TBD

Process Name	T-15 Access Help & Support - TO BE DISCUSSED FURTHER	Comments MVP?
Description	User is able to access technical and administrative support for their journey through the application	The extent to which this occurs is down to scope considerations - how is it done now, what plans are there for future?
Actors	Trainee
Pre-Conditions	TBD
Post-Conditions	TBD
Process Steps	TBD
Alternative Flow	TBD
Rules	TBD
JIRA Reference	TBD
Audit Log	TBD

Process Name	T-16 Save as draft before submission	Comments MVP
Description	User is able to draft and save the form that will XYZ	Confirm purpose of form
Actors	Trainee
Pre-Conditions	Logged in
Post-Conditions	Draft saved and accessible to be completed later
Process Steps	User navigates to XXX space System presents form details in editable view User completes relevant fields System validates fields System saves changes User leaves XXX space without submitting the form System stores draft
Alternative Flow	T-11, T10
Rules	TBD
JIRA Reference	TIS-539 & TIS-92
Audit Log	TBD

Process Name	T-17 Forgotten Username	Comments MVP
Description	User has ability to login after they have forgotten their username	Is there an admin process to support where this does not work?
Actors	Trainee
Pre-Conditions
Post-Conditions
Process Steps		What's the best process here?
Alternative Flow
Rules
JIRA Reference	TBD
Audit Log

Process Name	T-18 Forgotten Password	Comments MVP
Description	User has ability to login after they have forgotten their password	How is this to be achieved? Password reminder v password change? Additional security required?
Actors	Trainee
Pre-Conditions	Username recognised	Is this valid? Or should email be sent regardless - (a) warn that an attempt was made and (b) prompt password reset?
Post-Conditions	View Posts landing page
Process Steps	TBD
Alternative Flow	N/A
Rules	TBD
JIRA Reference	TBD
Audit Log	TBD

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? Joanne Watson (Unlicensed)
Actors	Trainee
Pre-Conditions	User is logged in
Post-Conditions	System presents relevant detail	What details can be seen?
Process Steps	User navigates to summary view System presents summary information User selects to view detail System presents detail view User selects to book Course System presents Booking view
Alternative Flow	T-9 - View Course	??
Rules	Validation Rules?
JIRA Reference	TBD
Audit log	TBD

Trainee UI - Scenarios

0 Comments