Skip to end of metadata
  • Created by Former user , last modified on 21 Jul 2017
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »


Process NameT-1 New RegistrationComments
DescriptionUser has the ability to register to use the TIS system directlyIs 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?
ActorsTrainee 
Pre-ConditionsTBC
Post-ConditionsTrainee has access to new TIS system - login / logout capability 
Process Steps
  1. user register a username
  2. user sets password
  3. user sets securiity
  4. user validates details
  5. system shares
What interaction should this have with Admin UI? What are the back end implications? 
Alternative FlowUser is registered from <another system> 
RulesTBC

Format of username?

Validation of password?

What security should be implemented?

JIRA ReferenceNew story TBDWider discussion necessary on whether this is a valid story, before writing a JIRA ticket
Audit LogTBC 


Process NameT-2 Trainee LoginComments
DescriptionTrainee has the ability to login using the details they were registered for the service withWill they be able to use their old details, or have to re-register?
ActorsTrainee 
Pre-Conditions

Trainee has been registered on system

Trainee has validated their registered details


Post-ConditionsTrainee is able to view the space 
Process Steps
  1. Traine enters username
  2. Trainee enters password
  3. System validates details
  4. System presents logged in view of system
 
Alternative Flow

T-17 Forgotten Username

T-18 Forgotten Password

T-19 Username / Password Error

 
RulesError validation?
JIRA ReferenceTBD 
Audit LogTBD 



T-3 Trainee LogoutComments
DescriptionTrainee has the ability to logout of the system
ActorsTrainee 
Pre-Conditions

Trainee has been registered on system

Trainee has validated their registered details


Post-ConditionsTrainee leaves logged in view of system securely 
Process Steps
  1. Trainee selects to logout
  2. System logs user out
  3. System presents logged out view
 
Alternative FlowN/A 
RulesError validation? 
JIRA ReferenceTBD 
Audit LogTBD 


Process NameT-4 View SummaryComments
DescriptionTrainee has the ability to view the summary screen
Actors

Trainee

System

 
Pre-ConditionsTrainee is logged in
Post-Conditions

Summary details in view

Navigation menu available

 
Process Steps
  1. User logs in
  2. System presents summary
  3. User navigates through view
 
Alternative FlowN/A 
RulesValidation rules? 
JIRA ReferenceTBD 
Audit LogTBD 


Process NameT-5 View & Edit Personal DetailsComments
DescriptionUser has the ability to view and update their own details
ActorsTrainee 
Pre-ConditionsTrainee 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

 Which fields should be editable?
Process Steps
  1. User navigates to Personal Details space
  2. System presents personal details in editable view
  3. User makes changes to relevant fields
  4. System validates changes
  5. System saves changes
 
Alternative FlowN/A 
RulesValidation rules? 
JIRA ReferenceTBD 
Audit LogTBD 


Process NameT-6 View ProgrammeComments
DescriptionUser has the ability to view their Programme details 
ActorsTrainee 
Pre-Conditions

User is logged in

Is there a need for detailed Programme view?
Post-ConditionsSystem presents relevant detail 
Process Steps
  1. User navigates to summary view
  2. System presents summary information
  3. User selects to view detail
  4. System presents detail view
  5. User selects to leave Programme Detail view
  6. System presents summary view 

What details are shown on summary v detail?

Should user be presented with previous view or summary screen?

Alternative FlowN/A 
Rules

Validation rules?

  • View only
 
JIRA ReferenceTBD 
Audit LogTBD 


Process NameT-7 View PlacementComments
DescriptionUser has the ability to view their Placement details 
ActorsTrainee 
Pre-ConditionsUser is logged in
Post-ConditionsSystem presents relevant detail 
Process Steps
  1. User navigates to summary view
  2. System presents summary information
  3. User selects to view detail
  4. System presents detail view
  5. User selects to leave Placement Detail view
  6. System presents summary view 
 
Alternative FlowN/A 
Rules

View only

 
JIRA ReferenceTBD 
Audit LogTBD 


Process NameT-8 View AssessmentComments
DescriptionUser has the ability to view their Assessment details 
ActorsTrainee 
Pre-ConditionsUser is logged in
Post-ConditionsSystem presents relevant detail 
Process Steps
  1. User navigates to summary view
  2. System presents summary information
  3. User selects to view detail
  4. System presents detail view
  5. User selects to leave Assessment Detail view
  6. System presents summary view 
 
Alternative Flow
 
RulesView only 
JIRA ReferenceTBD 
Audit LogTBD 


Process NameT-9 View CoursesComments
DescriptionUser has the ability to view their Course details Do we need this as part of the MVP?
ActorsTrainee 
Pre-ConditionsUser is logged in
Post-ConditionsSystem presents relevant detail What details can be seen?
Process Steps
  1. User navigates to summary view
  2. System presents summary information
  3. User selects to view detail
  4. System presents detail view
  5. User selects to leave Course Detail view
  6. System presents summary view 
 Should there be a summary view of courses?
Alternative FlowT-19 Book Course Is this necessary for MVP?
RulesView Only 
JIRA ReferenceTBD 
Audit LogTBD 


Process NameT-10 Submit Form-R (Part A)Comments
DescriptionUser is able to submit the form that will update their personal details with the GMC
ActorsTrainee 
Pre-ConditionsUser is logged in
Post-Conditions

User personal details are updated in TIS across all systems

User personal details are updated with GMC

 
Process Steps
  1. User navigates to Personal Details space
  2. System presents personal details in editable view
  3. User makes changes to relevant fields
  4. System validates changes
  5. System saves changes
  6. User selects to submit Form-R (Part A)
  7. Form-R (Part A) is sent to GMC

Should this be a manual trigger or automated whenever personal details are updated?


Should this be from Personal Details space, or Assessments, alongside Part B?

Alternative FlowT-20 No submission of Form R (Part A)Only relevant if the Part A submission is automated 
RulesValidation rules? 
JIRA ReferenceTBD 
Audit LogTBD 


Process NameT-11 Submit Form-R (Part B)Comments
DescriptionUser 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?
Post-ConditionsForm-R (Part B) is submitted 
Process Steps
  1. User navigates to XXX space
  2. System presents form details in editable view
  3. User completes relevant fields
  4. System validates fields
  5. System saves changes
  6. User selects to submit Form-R (Part B)
  7. Form-R (Part B) is sent to GMC
  8. Historical view of submitted Form's updated
Where should this be located? Alongside Assessments, or in it's own area?
Alternative FlowTBD Are drafts possible?
RulesValidation Rules? 
JIRA ReferenceTBD 
Audit LogTBD 


Process NameT-12 Submit OOPComments
Description

Actors
 
Pre-Conditions

Post-Conditions
 
Process Steps
 
Alternative Flow
 
Rules
 
JIRA Reference
 
Audit Log
 


Process NameT-13 Submit LTFTComments
Description

Actors
 
Pre-Conditions

Post-Conditions
 
Process Steps
 
Alternative Flow
 
Rules
 
JIRA Reference
 
Audit Log
 


Process NameT-14 Submit LTFTComments
Description

Actors
 
Pre-Conditions

Post-Conditions
 
Process Steps
 
Alternative Flow
 
Rules
 
JIRA Reference
 
Audit Log
 


Process NameT-15 Submit ExpensesComments
Description

Actors
 
Pre-Conditions

Post-Conditions
 
Process Steps
 
Alternative Flow
 
Rules
 
JIRA Reference
 
Audit Log
 


Process NameT-16 Access Help & SupportComments
Description

Actors
 
Pre-Conditions

Post-Conditions
 
Process Steps
 
Alternative Flow
 
Rules
 
JIRA Reference
 
Audit Log
 
Process NameT-17 Forgotten UsernameComments
Description

Actors
 
Pre-Conditions

Post-Conditions
 
Process Steps
 
Alternative Flow
 
Rules
 
JIRA Reference
 
Audit Log
 
Process NameT-18 Forgotten PasswordComments
DescriptionUser has ability to navigate to "Posts" area within the UI from their current location on siteStory not needed
ActorsLocal Admin 
Pre-ConditionsLogged in
HEE Admin		Admin is a permission applied by user
Post-ConditionsView Posts landing page 
Process Steps1. View navigation
2. Select "Posts"
3. Present landing page		 
Alternative FlowN/A 
Rules- Error: page unavailable 
JIRA ReferenceN/A 
Audit LogN/A 
Process NameT-19 Book CoursesComments
DescriptionUser has the ability to book new Courses Do we need this as part of the MVP?
ActorsTrainee 
Pre-ConditionsUser is logged in
Post-ConditionsSystem presents relevant detail What details can be seen?
Process Steps
  1. User navigates to summary view
  2. System presents summary information
  3. User selects to view detail
  4. System presents detail view
  5. User selects to book Course
  6. System presents Booking view 
 
Alternative FlowT-9 - View Course ??
RulesValidation Rules? 
JIRA ReferenceTBD 
Audit logTBD
  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.
 

Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213