FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
ID Use Cases owned by this team
BAD-11
2.1.1 Log On to system
To provide a 'Clerk' with secure access to the system and to the permitted functions for which he has the necessary privileges.
BAD-2900
2.1.1.1 Description
In order to prevent unauthorised usage of the system the 'Clerk' is prompted to supply a <Username> and <Password> (which is obscured on
entry). The <Username>/<Password> pair are verified. On successful verification, the system notifies the 'Clerk' of the <Username> logged on,
the last logon date and time and the number of previous failed logon attempts. Where the 'Clerk' provides an incorrect
<Username>/<Password> pair then the 'Clerk' is prompted to re-supply or correct the erroneous input.
For branches and users that are subject to training controls, an additional check is applied that the ‘Clerk’ has completed the necessary
Essentials training. If the requisite training has not been completed then the user will logged on with the COURSEWORK role. Note: Some
users are not subject to training controls e.g. global users or local users.
Once <Username>/<Password> verification is complete the 'Clerk' may be prompted (if the BAL deems it necessary) to confirm that the first
and last name shown on the message prompt is the user's name. If the user refutes the identity displayed then the user is logged off otherwise
the user is prompted to reconcile any incomplete transactions outstanding from the previous <Session>, so that the view of the central system
coincides with that of the 'Clerk' and the actual outcome of the transaction. This process is followed whenever a 'Clerk' is commencing a new
session or following a forced logout scenario. A number of other checks are carried out as part of the logon process and these will result in a
variety of prompts being presented to the user.
BAD-3189
2.1.1.2 Context
The purpose of this use case is to open or recommence a <User Session> for a 'Clerk' to carry out transactional and/or administrational
functions.
The primary scenario for Log On to System demands that the following system checks do not trigger any exceptions, which prevent or interrupt
the log on process to complete and log the permitted branch user on to the system successfully:
# the Is user already logged on to other counter position check passes, (at BAD-3126)
# the 3am system maintenance reload check passes, (at BAD-3564)
Printed on : 15/02/2023 Page I of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
# the Locked/Disabled user account check passes, (at BAD-3126)
# the Identity Confirmation check passes, (at BAD-EUM4-1000)
# the Balancing Not In Progress check passes, (at BAD-3126)
# the Stock/Branch Rollover Not Overdue check passes, (at BAD-3214)
# the Same Stock Unit Trading Period as Branch check passes, (at BAD-3353)
# the Rollover Safe Calc check passes, (at BAD-3214)
# the Balancing Overdue check passes, (at BAD-3353)
# the Cash Declaration Overdue check passes, (at BAD-3194)
# the Is the system off-line check passes, (BAD-3916)
# the Branch and Product Reference Data check passes, (at BAD-3244)
# the Imminent Product Price check passes, (at BAD-3462)
# the Outstanding Transaction Corrections check passes, (at BAD-3195)
# the Outstanding Transaction Acknowledgement check passes, (at BAD-4062)
# the Tidy Session Closure check passes. (at BAD-3207)
# the ‘Clerk’ has completed the “Essentials” Training for branches that are subject to training restricted selling). (at BAD-3126)
# the Locked / Logically Deleted Post Office Identifier check passes (at BAD-3126)
Access to a restricted set of peripheral test and config functions will be available from the Legal Security Agreement prompt without requiring
user authentication and will not be role specific.
Note: All Post Login checks will be performed for the Manager and Supervisor and all post login checks EXCEPT the check for outstanding
TXN corrections will be performed for Migrate, Clerk, Auditor, Emergency manager and Setup users, whilst all other users (e.g. Engineer,
Admin, Trainer) will get no post login checks.
BAD-12
2.1.1.3 Primary Scenario
BAD-3252 System displays Intro screen to 'Clerk'
BAD-3253 'Clerk' interacts with the System in some way (e.g. touches screen or the Enter key)
BAD-14 System requests 'Clerk' to agree to legal / security statement with options to "Accept", "Cancel" or "System Diagnostics". Message
Printed on : 15/02/2023 Page 2 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
MSG00006 displayed.
BAD-3102 'Clerk' accepts legal / security statement
BAD-3916 System performs offline check and determines network status is online.
BAD-3244 System checks if Reference Data is up to date and determines it is safe to proceed _in accordance with Business Rule BRU-1001.
BAD-3103 System requests <username> and <password>
BAD-3104 'Clerk' advises system of <username> and <password>
BAD-3126 System validates <username> and <password> in accordance with Business Rules BRU-83, BRU-85, BRU-88, BRU-236, BRU-701, BRU-
CP2368-1 , BRU-942, BRU-966, BRU-1124, BRU-1080,BRU-1148, BRU-EUM1, BRU-EUM2
BAD-3190 System creates an <Event Log Entry > for Log-on -completion (as specified in the Reports and receipts document SD/DES/005 section 14.2
and document EA/IFS/006 section B.7)
BAD-EUM4- I System determines that the 'Clerk' should not be prompted to confirm identity
1000
BAD-3105 System advises 'Clerk' of date & time of their last log on and the number of failed log on attempts since the last successful log-on displaying
MSG-10102
BAD-3106 ‘Clerk’ checks log on details
BAD-3107 'Clerk' acknowledges message
BAD-3298 System determines that the clerk attempting to log on has the correct privileges as specified by the menu hierarchy document
DES/GEN/SPE/0007.
BAD-3207 System checks if earlier User sessions on this counter were closed tidily and if not whether there are any transactions for this counter requiring
outstanding recovery action in accordance with Business rule BRU-703 and confirms that Recovery action is not required.
BAD-EUM4- I System determines Essentials Curricula are not expired
1101
BAD-EUM4- I System determines Trading Curricula are not expired
1102
BAD-EUM4- I System determines Essentials Curricula are not due to expire
1103
BAD-EUM4- I System determines Trading Curricula are not due to expire
1104
Printed on : 15/02/2023 Page 3 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-EUM4- I System determines the 'Clerk' has Essentials Training (BRU-EUM2)
1105
BAD-3213 The order of the following list is not important up to, (but not including) BAD-3258
BAD-3214 System checks (using <Rollover Safe calculation>) if Stock unit rolled over into current Branch's Trading Period more than 38 days ago, In
accordance with Business Rule BRU-407
BAD-3353 System checks, against Accounting Period calendar and Branch offset, that stock unit Balancing/rollover is not overdue (i.e. If today's date is
later than the end date of current TP), and stock unit is in the same trading period as the branch in accordance with BRU-1015.
BAD-3194 System Checks if a 'cash declaration’ was completed from the previous day in accordance with Business rule BRU-197 & BRU-1143
BAD-3462 System determines that there is no imminent price change and does not print the Office Daily Revalued Product List report according to BRU-
933
BAD-4062 If the user attempting to Log on is a ‘Manager’, ‘Supervisor’ or ‘Clerk’ the system checks if there are any outstanding <Transaction
Acknowledgements> and finds that there are none.
BAD-3195 If the user attempting to Log on is a 'Manager' or 'Supervisor' the System checks if there are any outstanding <Transaction Corrections> and
finds that there are none.
BAD-3258 Invoke Use Case Select function options.
BAD-3108 Use Case ends
BAD-15
2.1.1.4 Variations
BAD-3917
2.1.1.4.1 Perform System Diagnostic tests
(Note: When the System Diagnostics function is selected from the Legal Security Agreement prompt, acess to a restricted subset of
Engineering options will be available to allow peripheral test and configuration functions to be performed at a counter position when the system
is cither on-line/off-line or operating on out of date reference data).
BAD-3918 (At BAD-3102), 'Clerk' requests System Diagnostics function.
BAD-3919 System advises Diagnostic Options MSG04010_ message displaying options for engineering, powerdown, cancel
BAD-3920 'Clerk' requests Engineering option
BAD-3925 System invokes Select Function Options use case.
Printed on : 15/02/2023 Page 4 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-3926 Use case ends
BAD-3599
2.1.1.4.2 Concurrent Log-on: Active Session Successfully Terminated
Note: This can contribute to recovery taking place at the original counter session being terminated as a result of logging into the system at a
different counter position by the same user dependant on the Serve Customer basket containing recoverable/cancellable transactions.
BAD-3600 (At BAD-3126), 'Clerk' attempts to logon on a different terminal (within same branch), or where the <username> is linked to a <Post Office
Identifier> the ‘Clerk’ attempts to logon on a different terminal (across all branches) while another Counter session is not locked
BAD-3601 System detects that ‘clerk’ is already logged on at another counter position.
BAD-CP2368-I System creates an <Event Log Entry> for Concurrent Log-on, awaiting user response.
300
BAD-3602 System advises requesting 'clerk' to confirm if they wish to abandon the new log-on or continue with the new log-on as a result of a failed user
session at the original counter position. MSG04002 is displayed.
BAD-3604 Clerk confirms that the session has failed at the original terminal requiring any active session to be terminated.
BAD-3605 System marks original user session as failed, terminating any detected active session at the original counter position
BAD-4050 System creates an <Event Log Entry > for Concurrent Log-on activity -Session terminated.
BAD-3606 Resume at BAD-3190
Concurrent Logon: User Is Balancing The Stock Unit
BAD-CP2368- I (At BAD-3602), System Detects that the user logging in is linked to a SmartID, and is currently balancing the stock unit, and is logged on at
100 another counter in the branch, and that counter is locked, in violation of BRU-966.
BAD-CP2368- I System requests 'clerk' to confirm if they wish to abandon the new log-on or continue with the new log-on as a result of a failed user session at
110 the original counter position which is balancing the stock unit. MSG40048 is displayed.
BAD-CP2368- I System creates an <Event Log Entry> for Concurrent Log-on while stock unit balancing, awaiting user response.
120
BAD-CP2368- I Clerk confirms that the session has failed at the original terminal requiring the active session to be terminated.
130
BAD-CP2368- I System marks original user session as failed, terminating the active session at the original counter position.
Printed on : 15/02/2023 Page 5 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
140
BAD-CP2368- I System creates an <Event Log Entry> for Concurrent Log-on terminating existing session.
150
BAD-CP2368-I Resume at BAD-3190
160
Concurrent Logon: User Is Balancing The Branch
BAD-CP2368-I (At BAD-3602), System Detects that the user logging in is linked to a SmartID, and is currently balancing the branch, and is logged on at
200 another counter in the branch, and that counter is locked, in violation of BRU-CP2368-1.
BAD-CP2368-I System advises requesting 'clerk' to confirm if they wish to abandon the new log-on or continue with the new log-on as a result of a failed user
210 session at the original counter position which is balancing the branch. MSG40049 is displayed.
BAD-CP2368- I System creates an <Event Log Entry> for Concurrent Log-on while branch balancing, awaiting user response.
220
BAD-CP2368- I Clerk confirms that the session has failed at the original terminal requiring the active session to be terminated.
230
BAD-CP2368- I System marks original user session as failed, terminating the active session at the original counter position.
240
BAD-CP2368- I System creates an <Event Log Entry> for Concurrent Log-on terminating existing session.
250
BAD-CP2368- I Resume at BAD-3190
260
BAD-3566
2.1.1.4.3 User logged on, prior to system maintenance reload
Note:
1. This is not linked to the primary scenario, but can occur at any time throughout the night with users logged on at the branch when a nightly
system update (e.g. menu refresh) is about to take place.
2. If users are concurrently logged on when a software update is about to take place their session will be abnormally terminated possibly
causing recovery action to take place at the next immediate log on.
3. In cases where a user attempts to log on when a system maintenance reload is actively taking place (nightly update or software update) the
Printed on : 15/02/2023 Page 6 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
user will not be presented with the log-on prompt.
4. If the user ignores the initial prompt alerting that they should complete/cancel all unfinished activities and log off immediately, they will be
reminded/prompted again after x minutes time.
5. If the user ignores the reminder prompt the system will temporarily abandon the menu refresh and re-attempt the following night.
BAD-3567 System detects users logged on
BAD-3568 System displays early warning system maintenance reload prompt MSG90088 or MSG90089 is displayed. (refer to section 4.2 SD/DOC/009)
BAD-3569 Clerk accepts message
BAD-3570 Use Case ends, system resumes at BAD-3252 pre-prompt state.
BAD-3299
2.1.1.4.4 User logging on is a Global User
BAD-3300 (at BAD-3298) System determines user attempting to log-on is a 'Global User' and performs log-on checks in accordance with BRU-1012.
BAD-3301 Go to BAD-3258
BAD-3111
2.1.1.4.5 Branch Rollover Overdue:
BAD-3120 (At BAD-3214) System advises 'Clerk' that the branch has not been rolled over. Message MSG-01059 is displayed. (Refer to SD/DOC/009
Section 10).
BAD-3132 'Clerk' acknowledges messages
BAD-3137 Resume at BAD-3213
BAD-3355
2.1.1.4.6 Stock Unit has not been balanced
BAD-3356 (at BAD-3353) System advises 'Clerk' that current _'Stock Unit' has not been balanced displaying message MSG-01022.
BAD-3357 'Clerk' acknowledges message.
BAD-3358 Resume at BAD-3213
BAD-3164
2.1.1.4.7 Stock Unit & Branch Trading Period do not match
BAD-3165 (at BAD-3353) System advises 'Clerk' of variance between the 'Stock unit’ & ‘Branch! 'Trading Period' (including unknown Trading Period)
MSG-10104, MSG-01022, MSG-01023 or MSG-01028 displayed.
Printed on : 15/02/2023 Page 7 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-3134 'Clerk' acknowledges message
BAD-3166 Resume at BAD-3213
BAD-3153
2.1.1.4.8 Cash Declaration not made from previous day
BAD-3135 (at BAD-3194) System advises 'Clerk' cash declaration is outstanding . Business rule BRU-197 or BRU-1143 have been broken. Message
MSG 01005 is displayed.
BAD-3156 Invoke Use case Declare Cash Holdings, declaration must be marked as having been made yesterday.
BAD-3241 Resume at BAD-3213
BAD-3472
2.1.1.4.9 Stock Check Reminder - Revalued Product List report Printed/Previewed
BAD-3473 (At BAD-3462) System determines that there is an Imminent Price Change as determined by Reference Data.
BAD-3474 System advises Clerk of Imminent Price Change by displaying MSG-01068, at every log-on up to and including the effective date (see
SD/DOC/009).
BAD-3475 Clerk acknowledges mesage.
BAD-3479 Invoke BAC-186 Produce Non Cut-Off Report(s)
BAD-4061 Resume at BAD-3213.
BAD-3200
2.1.1.4.10 Transaction corrections outstanding - not processed
BAD-3201 (At BAD-3195) System detects that there are outstanding transaction corrections
BAD-3530 System determines if 'Supervisor/Manager' is attached to the Default Stock Unit in accordance with BRU-696, and determines that they are not
attached to the default Stock Unit.
BAD-3612 System creates an <Event Log Entry > for Outstanding Transaction Correction Reminder Displayed (as specified in the Reports and receipts
document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD-3531 System advises 'Supervisor/Manager’, do you wish to process now or continue with 'log-on'. (Message MSG-01006 is displayed. Refer to
Printed on : 15/02/2023 Page 8 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
SD/DOC/009).
BAD-3202 The 'Supervisor/Manager' advises system to continue with 'log-on'
BAD-3203 Resume at BAD-3213
BAD-3496
2.1.1.4.11 Transaction corrections outstanding - User attached to default Stock Unit
BAD-3497 (At BAD-3530) System determines Supervisor/Manager is attached to Default Stock Unit in accordance with Business Rule BRU-696,
BAD-3613 System creates an <Event Log Entry > for Outstanding Transaction Correction Reminder Displayed (as specified in the Reports and receipts
document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD-3500 System advises 'Supervisor/Manager' that there are transaction corrections outstanding, They cannot be processed while attached to the default
stock unit. Message MSG01061 is displayed.
BAD-3498 ‘Supervisor/Manager' acknowledges message and system continues with 'log-on' checks
BAD-3499 Resume at BAD-3213
BAD-3204
2.1.1.4.12 Transaction corrections outstanding — processed
BAD-3205 (at BAD-3202) The 'Supervisor/Manager' advises system to process corrections now.
BAD-3206 Invoke use case Manage transaction corrections
BAD-3242 Resume at BAD-3213
BAD-3112
2.1.1.4.13 System recovery from system failure:
This process describes the action taken whenever a Log On is done and it is found that the previous session on that terminal did not Log off
cleanly.
BAD-3119 (At BAD-3207), System detects an earlier logon session did not close tidily and recovery is required and that the User logging on has
permission to carry out Recovery in accordance with BRU-703.
BAD-3119A __I System displays MSG04024 informing the clerk that recovery is required.
BAD-3119B _I Clerk selects to Continue.
BAD-CP2459- I System determines that a PIN Pad is installed and finds that is installed and is initialised
10
Printed on : 15/02/2023 Page 9 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-3178 System determines that there was not an incomplete basket session with outstanding <Recovery Data> (i.c. that roll forward recovery is not
required).
BAD-3178A _I System determines that the last counter session may require rollback recovery in accordance with BRU-CP2459-5.
BAD-3179 System determines that the <Session Id> of the last counter session is available on the Counter Disk.
BAD-3281 System compares the <Session Id> of the last counter session as determined by the counter with the <Session Id> of the last counter session as
held at the Data Centre and determines that they are the same.
BAD-3180 System records Event Id 118 "No Recovery Required" and tidies up all incomplete User Sessions associated with this counter (other than the
current User Session).
BAD-3180A ___I System displays MSG04025 informing the clerk that recovery is complete.
BAD-3180B _I Clerk selects to Continue.
BAD-3183 Resume at step BAD-3213.
BAD-3992
2.1.1.4.14 System recovery from failure where <Recovery Data> is found
Note:
1.) If the following is interrupted by a system failure, recovery action will be required at next log-on:
# Banking Transactions (inc. Cash Deposits & Cash Withdrawals).
# Credit Card & Debit Card Payments.
# ETU Sales
# Existing Reversals in general and including Existing Reversals involving Settlement to Debit/Credit cards.
# New Reversals involving Credit/Debit Card Refunds & ETU Refunds..
# AP-ADC/APOP Transactions using the WriteRecoveryData data type.
2.) The Log-on Recovery process will add an item into the Serve Customer Basket for each recoverable item, though in some cases this may be
a zero value transaction if the recovery script determines that the transaction was incomplete. The design and interaction of cach recovery script
is outside the scope of this use case.
BAD-3993 (At BAD-3178 in Variation System Recovery From System Failure), System determines that there was an incomplete basket session with
Printed on : 15/02/2023 Page 10 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
outstanding <Recovery Data> in accordance with BRU-619 & BRU-1024 (i.e. that roll forward recovery is required).
BAD-3994 System invokes specified recovery script for each item of <Recovery Data>_in accordance with BRU-CP2978-1.
BAD-3995 System confirms that all recovery scripts executed successfully.
BAD-3996 System settles Recovery <Basket> in accordance with BRU-1137
BAD-3997 System records Event Id 111 "Recovery Complete", commits the Recovery Basket to the Data Centre and tidies up all incomplete User
Sessions associated with this counter (other than the current user session).
BAD-3998 System display MSG04025 to confirm that recovery is complete.
BAD-3999 Invoke use case Generate Printed Output to force the production of a Recovery 'Broken/Disconnected Session Receipt’.
BAD-4000 Resume at BAD-3213.
BAD-4003
2.1.1.4.15 System recovery from system failure by Reversing Last Basket
BAD-4004 (At BAD-3281 in Variation System recovery from system failure), System compares the <Session Id> of the last counter session with the
<Session Id> of the last counter session as held at the Data Centre confirming that the <Session Id> held at the Data Centre is greater than that
determined at the counter in accordance with BRU-1138.
BAD-4005 System analyses all Basket entries in the last session saved to the Data Centre and generates a Reversal Transaction for all Cancellable Basket
entries in that Basket to a new Recovery Basket.
BAD-4006 System determines that there are entries in the Recovery Basket
BAD-4007 Resume at step BAD-3996 in Variation System Recovery From System Failure Where Recovery Data is Found.
BAD-4009
2.1.1.4.16 System Recovery - No Cancellable Transactions when Reversing Basket
BAD-4010 (At BAD-4006 in Variation System Recovery From System Failure By Reversing Last Basket), System determines that there are no entries in
the Recovery Basket.
BAD-4011 Resume at BAD-3180 in Variation System Recovery From System Failure.
BAD-3384
2.1.1.4.17 Clerk selected Temporary lock
(Note: This is not linked to the primary scenario, but can occur at any time throughout the day with the system in a live state)
BAD-3388 'Clerk' advises system to be temporary locked.
Printed on : 15/02/2023 Page 11 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-3551 System accepts Temp Lock request.
BAD-3550 System creates an <Event Log Entry > for Locked Position (as specified in the Reports and receipts document SD/DES/005 section 14.2 and
document EA/IFS/006 section B.7)
BAD-3389 The system displays <Username> & <password> prompt
BAD-3391 Resume at BAD-3163.
BAD-3371
2.1.1.4.18 System enforced Temporary lock
(This is not linked to the primary scenario, but can occur at any time throughout the day with the system in a live state)
BAD-3552 System creates an <Event Log Entry > for Locked Position (as specified in the Reports and receipts document SD/DES/005 section 14.2 and
document EA/IFS/006 section B.7)
BAD-3385 After a configurable period, currently set at 15 minutes, of non activity the system requests user to confirm <Username> & <password>, in
accordance with Business rule BRU-326
BAD-3386 Resume at BAD-3163.
BAD-3162
2.1.1.4.19 Log on after temporary lock
This is not linked to the primary scenario, but can occur at any time after an innactivity lock out._In accordance with Business Rule BRU-326
BAD-3163 The System advises clerk of <username> and requests <username> and <password>
BAD-3208 The 'Clerk' enters their <password>
BAD-3209 The System checks the <password> is valid for the <username> in accordance with Business rules BRU- 236 & BRU-1080
BAD-EUM4- I In accordance with BRU-701, the System checks that no other Counter sessions are active.
2000
BAD-3425 System creates an <Event Log Entry > for Position Unlocked (as specified in the Reports and receipts document SD/DES/005 section 14.2 and
document EA/IFS/006 section B.7)
BAD-3210 Use Case ends, system resumes to pre-locked state.
BAD-3217
2.1.1.4.20 Log off by a new user after temporary lock- confirmed (No open ‘customer session’)
BAD-3218 (at BAD-3208) New 'User' opts to advise system of their <username> and <Password>
Printed on : 15/02/2023 Page 12 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-3219 Business rule BRU-699 is broken, System advises the 'User' that the session is currently locked by someone else, are you sure you wish to log
out current user. Outstanding transactions will be committed. Message MSG04003 is displayed.
BAD-3220 New 'User' advises system YES.
BAD-3580 System creates an <Event Log Entry > for Forced Log-Out or Manager Forced Log Out against new user logging out user already logged on
(as specified in the Reports and receipts document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7).
BAD-3221 System creates an <Event Log Entry> for Log Out - completion for user being logged out (as specified in the Reports and receipts document
SD/DES/005 section 14.2 and document EA/IFS/006 section B.7) and returns to Opening screen.
BAD-3546 Resume at BAD-3252 in primary flow
BAD-3372
2.1.1.4.21 Log off by a new user after temporary lock- confirmed (Open ‘customer session')
Note: When transactions are committed as a result of of a forced logoff caused by another user at a locked counter position with an ‘open
customer session’, this will automatically commit the transactions in an open basket settling them to cash producing forced receipts and
associated counter events, which will result in logging off the original user's locked session.
BAD-3374 (at BAD-3208) New 'User' opts to advise system of their <username> and <Password>
BAD-3376 System advises the 'User' that the session is currently locked by someone else, are you sure you wish to log out current user. Outstanding
transactions will be committed. Message MSG04003 is displayed in accordance with Business Rule BRU-936
BAD-3378 New 'User' advises system YES.
BAD-3380 Invoke Transact Customer Basket_use case
BAD-3381 System creates an <Event Log Entry > for Forced Log-Out or Manager Forced Log Out against new user logging out user already logged on
(as specified in the Reports and receipts document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7).
BAD-3581 System creates an <Event Log Entry> for Log Out - completion for user being logged out (as specified in the Reports and receipts document
SD/DES/005 section 14.2 and document EA/IFS/006 section B.7) and returns to Opening screen.
BAD-3547 Resume at BAD-3252 at primary flow
BAD-3223
2.1.1.4.22 Log off after temporary lock- Cancelled
BAD-3224 (at BAD-3220) New 'User' advises system No.
BAD-3225 Resume at BAD-3163
BAD-3114
Printed on : 15/02/2023 Page 13 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
2.1.1.4.23 System prompts clerk to change password
BAD-3118 (At BAD-3126) Business Rule BRU-83 or BRU-85 is broken, System requests clerk to enter new <password> inhibiting Cancel option.
Message MSG02158 is displayed.
BAD-3128 Invoke Use Case Change Password
BAD-3452 Resume at BAD-3190 in Primary scenario.
BAD-3849
2.1.1.4.24 Calculate Trading Period For New Office being added to network
BAD-3850 (At BAD-3298), System determines user attempting to log on is a Global user with 'Add New Office' privileges for the first time in a new
office.
BAD-3851 System determines new office has been successfully added to the retail office network ready for the new office Trading Period calculation.
BAD-3852 The 'system' compares the current 'system' date with the <Accounting Period Reference Data>, to identify the <Branch Trading Period> that
the branch should be in, and records the <Branch Trading Period> Identifier for this trading period, and the "next TP"in accordance with BRU-
685 and BRU-686.
BAD-3853 The 'system' informs the user that the Trading Period has been recorded displaying message MSG04020.
BAD-3854 The user acknowledges the message.
BAD-3855 Resume at BAD-3213
BAD-3960
2.1.1.4.25 Global user permitted to log-on to an un-opened Branch
BAD-3961 (At BAD-3298), System detects global user attempting to log-in does not have permission to add the new office to the retail network, but
determines that the log-in can be permitted with a restricted Menu offering in accordance with BRU-1126
BAD-3962 System advises branch not ready to be opened/added to retail network and insufficient permission message MSG04027 is displayed.
BAD-3963 The user acknowledges the message.
BAD-3964 Resume at BAD-3258 bypassing post login checks defined at:
BAD-3213, BAD-3214, BAD-3353, BAD-3194, BAD-3462, BAD-3195, BAD-4062.
BAD-4063
2.1.1.4.26 Outstanding Transaction Acknowledgements need processing
Printed on : 15/02/2023 Page 14 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-4064 (At BAD-4062) System detects that there are outstanding Transaction Acknowledgements.
BAD-4065 System displays MSG00337 stating that there are Transaction Acknowledgements to process
BAD-4066 Clerk acknowledges message
BAD-4067 INCLUDE use case Process Transaction Acknowledgements
BAD-4068 Resumes at BAD-3213
BAD-EUM4-
1110 2.1.1.4.27 Identity Confirmation Prompt — User selects 'Yes'
BAD-EUM4-
1112 (At BAD-EUM4-1000), System determines that the Identity Confirmation prompt (MSG-04034) should be displayed.
BAD-EUM4-
1113 Clerk selects 'Yes' and the system displays MSG-04036
BAD-EUM4-
1114 Resumes at BAD-3105
BAD-EUM4-
1120 2.1.1.4.28 Identity Confirmation Prompt — User selects 'No'
BAD-EUM4-
1121 (At BAD-EUM4- 1000), System determines that the Identity Confirmation prompt (MSG-04034) should be displayed.
BAD-EUM4-
1122 Clerk selects 'No' and the system displays MSG-04035
BAD-EUM4-
1123 System displays MSG-10004
BAD-EUM4-
1124 'Clerk' acknowledges message and is logged off
BAD-EUM4-
1125 Resumes at BAD-3252
BAD-EUM4-
1130 2.1.1.4.29 Essentials Curricula Expired
Printed on : 15/02/2023
Page 15 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-EUM4- I (At BAD-EUM4- 1101), System determines that the 'Clerk' has one or more expired Essentials Curricula
1131
BAD-EUM4- I System displays MSG-04042 for each expired Curricula
1132
BAD-EUM4- I 'Clerk' acknowledges message(s)
1133
BAD-EUM4- I Resumes at BAD-3213
1134
BAD-EUM4- I 2.1.1.4.30 Trading Curricula Expired
1140
BAD-EUM4- I (At BAD-EUM4- 1102), System determines that the 'Clerk' has one or more expired Trading Curricula
1141
BAD-EUM4- I System displays MSG-04040 for each expired Curricula
1142
BAD-EUM4- I 'Clerk' acknowledges message(s)
1143
BAD-EUM4- I Resumes at BAD-3213
1143
BAD-EUM4- I 2.1.1.4.31 Essentials Curricula Are Due To Expire
1150
BAD-EUM4- I (At BAD-EUM4-1103), System determines that the 'Clerk' has one or more Essentials Curricula that are due to expire
L151
BAD-EUM4- I System displays MSG-04041 for each expiring curricula
1152
BAD-EUM4- I 'Clerk' acknowledges message(s)
1153
BAD-EUM4- I Resumes at BAD-3213
Printed on : 15/02/2023
Page 16 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
1154
BAD-EUM4- I 2,1.1.4.32 Trading Curricula Are Due To Expire
1160
BAD-EUM4- I (At BAD-EUM4-1104), System determines that the 'Clerk' has one or more Trading Curricula that are due to expire
1161
BAD-EUM4- I System displays MSG-04039 for each expiring curricula
1162
BAD-EUM4- I 'Clerk' acknowledges message(s)
1163
BAD-EUM4- I Resumes at BAD-3213
1164
BAD-EUM4- I 2,1.1.4.33 Coursework Role is Activated
1170
BAD-EUM4- I (At BAD-EUM4-1105), System determines that the 'Clerk' does not have Essentials training (i.e. BRU-EUM2 is broken)
1171
BAD-EUM4- I System displays MSG-04044
1172
BAD-EUM4- I 'Clerk' acknowledges message
1173
BAD-EUM4- I Resumes at BAD-3213
1174
BAD-CP2459-I 2.1.1.4.34 PIN Pad Not Initialised At Recovery
20
BAD-CP2459- I (At variation "System recovery from system failure" step BAD-CP2459-10), System determines that a PIN Pad is installed but is not initialised
21
Printed on : 15/02/2023
Page 17 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-CP2459- I System initialises PIN Pad
22
BAD-CP2459-I Resume at step BAD-3178
23
BAD-CP2459-I 2,1.1.4.34 Last Counter Session May Require Rollback Recovery
30
BAD-CP2459- I (At variation "System recovery from system failure" step BAD-3178A), System determines that the last counter session may require rollback
31 recovery in accordance with BRU-CP2459-5.
BAD-CP2459-I Resume at step BAD-3180.
32
BAD-18
2.1.1.5 Exceptions
BAD-3949
2.1.1.5.1 New office not initialised - Insufficient Permission Access detected
BAD-3951 (At BAD-3126), System detects global user attempting to log-in does not have permission to proceed with adding the new office to the
network in accordance with BRU-1148.
BAD-3952 System advises branch not ready to be opened/added to retail network and insufficient permission message MSG04021 is displayed.
BAD-3959 The user acknowledges the message.
BAD-3953 Resume at BAD-3252.
BAD-3921
2.1.1.5.2 System Diagnostics Abandoned - User cancels option
BAD-3922 (At BAD-3920), 'Clerk' selects Cancel option.
BAD-3923 Resume at BAD-3252.
BAD-3554
2.1.1.5.3 Concurrent Log on attempted - Active Session Termination Abandoned
BAD-3555 (At BAD-3604), Clerk confirms user logging on in error at different counter position wishing to abandon active session termination.
BAD-3557 System creates an <Event Log Entry > for Failed Log on (as specified in the Reports and receipts document SD/DES/005 section 14.2 and
Printed on : 15/02/2023 Page 18 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
document EA/IFS/006 section B.7)
BAD-3558 Resume at BAD-3252.
BAD-3503
2.1.1.5.4 Log on Failed - Locked/Disabled user detected
BAD-3504 (At BAD-3126), System detects that username’ Account is Locked or Disabled in accordance with
BRU-701.
BAD-3507 System creates an <Event Log Entry > for Failed Log on (as specified in the Reports and receipts document SD/DES/005 section 14.2 and
document EA/IFS/006 section B.7)
BAD-3941 System advises user that user account has been Locked/Disabled. MSG04000 or MSG04004 is displayed. Refer to SD/DOC/009 Section
4.1.3).
BAD-3505 Clerk acknowledges message.
BAD-3506 Resume at BAD-3252.
BAD-3254
2.1.1.5.5 Legal agreement not accepted:
BAD-3255 (at BAD-3102) 'Clerk' advises system to cancel legal agreement
BAD-3256 Resume at BAD-3252.
BAD-3508
2.1.1.5.6 Perform system restart at log on
BAD-3509 (At BAD-3920), 'Clerk' requests powerdown options.
BAD-3928 System advises powerdown options displaying MSG04011 with Restart/Shutdown/Cancel system options available.
BAD-3511 Clerk selects Restart system option
BAD-3512 System advises Confirm Restart message (Refer to SD/DOC/009 Section 4.2) MSG04012 is displayed.
BAD-3513 Clerk accepts message
BAD-3886 System performs restart procedure.
BAD-3514 Resume at BAD-3252
Printed on : 15/02/2023 Page 19 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-3515
2.1.1.5.7 Perform system shutdown at log on
BAD-3516 (At BAD-3511), 'Clerk' requests shutdown option.
BAD-3518 System advises Confirm Shutdown message (Refer to SD/DOC/009 Section 4.2) MSG04013 is displayed.
BAD-3519 Clerk accepts message
BAD-3885 System performs shutdown procedure.
BAD-3520 Resume at BAD-3252
BAD-3521
2.1.1.5.8 Perform system restart/shutdown abandoned
BAD-3522 (At BAD-3511), Clerk selects Cancel option.
BAD-3527 Resume at BAD-3252
BAD-19
2.1.1.5.9 Incorrect user name or password entered
BAD-20 (At BAD-3209 & BAD-3218 & BAD-3126 & BAD-3374) System detects that invalid user credentials have been supplied.
BAD-3426 System creates an <Event Log Entry > for Log-on - Failed wrong password/user name (as specified in the Reports and receipts document
SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
Or,
System creates an <Event Log Entry > for Unlock Failed, Failed Logon (During Temporary Timeout) (as specified in the Reports and receipts
document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD-3942 System advises clerk that an incorrect <username> or <password> has been entered displaying Message MSG-04001 ("IgnInvalidLogon')
BAD-3302 'Clerk' acknowledges message
BAD-3123 Resume at BAD-3103
BAD-3113
2.1.1.5.10 Incorrect user name or password entered 3 times
Note: In circumstances where a counter position terminal is in a Temp Lock state-and the current logged on user returns attempting to unlock
their counter session and enters their username/password wrong 3 times consecutively, the system will automatically Lock their account, whilst
Printed on : 15/02/2023 Page 20 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
keeping the current session active.
However, the original User making a further attempt to Log On after their account has become Unlocked, will be able to resume their session
from where it was last locked.
The following may cause the active User session to terminate, where the Temporary Lock is engaged:
e Auto settlement (see UC Transact Customer Basket) after a timeout period of inactivity
e Another User attempting to Log On causing a forced log off of the current logged on user in Temp Lock (see Variation BAD-3372)
BAD-3115 (At BAD-3209 & BAD-3218 & BAD-3126, BAD-3374 & BAD-3209 ), System applies lock-out to 'Username'’ Account in accordance with
Business rule BRU-236.
BAD-3427 System creates an <Event Log Entry > for Locked user (as specified in the Reports and receipts document SD/DES/005 section 14.2 and
document EA/IFS/006 section B.7)
BAD-3943 System advises clerk their account is locked and they should contact the 'Manager' displaying Message MSG-04000 (lgnAccountLockout
displayed).
BAD-3121 The 'Clerk' acknowledges message.
BAD-3211 The 'Clerk' contacts the 'Manager' to unlock their account
BAD-3122 Resume at BAD-3103.
BAD-3836
2.1.1.5.11 Unable to log on due to unsafe reference data - Ref Data Update in Progress
BAD-3837 (at BAD-3244), System detects that the current version of Branch/Product reference data held for the branch is out of date and not safe to
proceed with the log-on in accordance with BRU-1001.
BAD-3838 System advises clerk and displays message MSG-10101 'that the log on to the system is not allowed at this time and to contact the helpdesk’
BAD-3839 Clerk acknowledges message
BAD-3840 Resume at BAD-3252.
BAD-3856
2.1.1.5.12 Unable to authenicate user due to network failure
BAD-3857 (At BAD-3209, BAD-3218, BAD-3126, BAD-3374 & BAD-3916) System advises clerk that user details cannot be authenicated displaying
displaying one of the following messages:
Printed on : 15/02/2023 Page 21 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
If no network is detected before communications commence then MSG04014 is displayed. If failure occurs during communications then
MSG04015 is displayed.
BAD-3858 'Clerk' acknowledges message
BAD-3859 Resume at BAD-3252.
BAD-4013
2.1.1.5.13 System Recovery - Failure of Recovery Script
BAD-4020 (At BAD-3995 of Variation System Recovery From System Failure Where Recovery Data is Found), System determines that a recovery script
failed to create recovery transactions in the basket.
BAD-4021 System records Event Id 112 "Recovery Complete with Exceptions", commits the Recovery Basket to the Data Centre marking recovery as
incomplete for Recovery Data associated with failed transactions and tidies up all incomplete User Sessions associated with this counter (other
than the current User Session).
BAD-4022 Resume at BAD-3999 in Variation System Recovery From System Failure Where Recovery Data Is Found ensuring that details of the failure
are included in the receipt produced.
BAD-4014
2.1.1.5.14 System Recovery - Failure to save Recovery Basket
BAD-4025 (At BAD-3998 in Variation System Recovery From System Failure Where Recovery Data Is Found), System determines that there was a
failure in saving the Recovery Basket to the Data Centre (other than a timeout).
BAD-4026 Report a System Error informing the user that they will be Logged Out recording diagnostic information.
BAD-4027 Resume at step BAD-3252 in Primary Scenario (Intro wake-up screen).
BAD-4015
2.1.1.5.15 System Recovery - Timeout when attempting to save Recovery Basket
Note: That this Exception assumes that retries have been attempted and have failed repeatedly.
BAD-4028 (At BAD-3998 in Variation System Recovery From System Failure Where Recovery Data is Found), System determines that no response was
received when saving the Recovery Basket to the Data Centre.
BAD-4029 User is informed of the failure and the counter is Logged-Off.
BAD-4030 Resume at BAD-3252.
BAD-4016
Printed on : 15/02/2023 Page 22 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
2.1.1.5.16 System Recovery - Last <Session Id> Not available on Counter Disk
BAD-4031 (At BAD-3179 in Variation System Recovery From System Failure), System determines that the <Session Id> of the last counter session is not
available on the Counter Disk.
BAD-4032 System prompts the Clerk to enter the <Recovery Code> from the broken/disconnected session receipt produced at the time of the forced Log
Out.
BAD-4033 Clerk enters <Recovery Code> from the broken/disconnected session receipt in accordance with BRU-1138.
BAD-4034 System derives <Session Id> of the last completed counter session from <Recovery Code>.
BAD-4035 Resume at BAD-3281.
BAD-4017
2.1.1.5.17 System Recovery - Clerk doesn't know Last <Session Id>
BAD-4036 (At BAD-4033 in Exception System Recovery - Last <Session Id> Not Available on Counter Disk), User is unable to supply <Recovery Code>
from broken/disconnected session receipt.
BAD-4037 System displays details of last saved session retrieved from Data Centre and requests User if this was the last completed counter session.
BAD-4038 User confirms that it was.
BAD-4039 Resume at BAD-3180 in Variation System Recovery From System Failure.
BAD-4018
2.1.1.5.18 System Recovery - Clerk decides last session was incomplete
BAD-4040 (At BAD-4038 of Exception System Recovery - Clerk doesn't know last <Session Id>), Clerk confirms that displayed session was not
completed.
BAD-4041 Resume at BAD-4005 of Variation System Recovery From System Failure by Reversing Last Basket.
BAD-4019
2.1.1.5.19 System Recovery - <Recovery Code> invalid
BAD-4042 (At BAD-4033 of Exception System Recovery - Last <Session Id> Not available on Counter Disk), System determines <Recovery Code> not
valid in accordance with BRU-1138.
BAD-4043 System displays message MSG-90964 advising User that <Recovery Code> is invalid.
BAD-4044 User acknowledges messsage.
Printed on : 15/02/2023 Page 23 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-4045 Resume at BAD-4032 of Exception System Recovery - Last <Session Id> Not available on Counter Disk.
BAD-3110
2.1.1.5.20 Error in Log on details displayed
BAD-3117 (at BAD-3106) Clerk advises 'NBSC'
BAD-3140 'NBSC' gives authority to proceed
BAD-3141 Resume at BAD-3107.
BAD-3491
2.1.1.5.21 Unable to log on shared user - Stock unit balance already in progress
BAD-3492 (At BAD-3126), System determines that the user logging onto the attached Stock unit is in the process of Balancing, and the user is not the
user that is performing the balancing, in accordance with BRU-966.
BAD-3494 System advises clerk logging onto the system will be automatically logged out displaying Message MSG00302. (Note: Message(s) not included
in SD/DOC/009 document).
BAD-3528 Clerk acknowledges message.
BAD-3529 Resume at BAD-3252.
BAD-3845
2.1.1.5.22 Log on Cancelled
BAD-3846 (At BAD-3104), Clerk decides to cancel log on request.
BAD-3847 Resume at BAD-3252.
BAD-
EUM3100 2.1.1.5.23 Essentials Training not Completed
BAD-
EUM3101 (at BAD-3126) The system determines that the ‘Clerk’ has not completed the “Essentials” training.
(Business rule BRU-EUM2 broken)
BAD-
EUM3102 The system displays message MSG-04044 that the ‘Clerk’ has not completed the ‘Essentials’ training and will be assigned the 'Coursework'
role.
BAD-
Printed on : 15/02/2023 Page 24 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
EUM3103
The ‘Clerk’ accepts the message
BAD-
EUM3104 Resume at BAD-3213
BAD-
EUM3200 2.1.1.5.24 Recovery Required & Essentials Training not Completed
BAD-
EUM3201 (at BAD-3126) The system determines that the ‘Clerk’ has not completed the “Essentials” training and (at BAD-3207) the system determines
that Recovery was carried out.
BAD-
EUM3202 System displays MSG-10004 (user is being logged off)
BAD-
EUM3203 'Clerk' acknowledges message and is logged off
BAD-
EUM3204, Resumes at BAD-3252
BAD-21
2.1.1.6 Trigger
BAD-22 'Clerk' wishes to start a new user session or re-commence after a temporary lock or forced system logout.
BAD-23
2.1.1.7 Preconditions
BAD-3835 The 'System' must be connected to the data centre
BAD-24 ‘Clerk’ has a valid user account within the branch
BAD-3290 Any outputs from a previous session are available.
BAD-25
2.1.1.8 Stakeholders and Interests
BAD-26 'Clerk' wishes to operate a stock unit
Printed on : 15/02/2023 Page 25 of 27
FUJ00171900
FUJ00171900
co
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 19/03/2018
Document81 Current DOORS Version Date: 19/08/2011
This is the baseline version at Release 5 and is carried forward to Release 5.50 Current DOORS Version Number: 5.06
BAD-27
2.1.1.9 Minimal Guarantees
BAD-28 The 'Clerk' will only be logged on if all of the validation criteria have been met.
BAD-3909 If Log-on is interrupted by an exception which prevents log-on taking place, the system shall automatically return the user attempting log-on
after acknowledging any error messages to the start of the log-on to system primary use case.
BAD-29
2.1.1.10 Success Guarantees
BAD-30 'Clerk' is successfully logged on to the system.
BAD-31
2.1.1.11 Non-Functional Requirements
BAD-3398 None
BAD-33
2.1.1.12 Business Rules
BAD-34 See Links to Business Rules module.
BAD-35
2.1.1.13 Process Changes
BAD-3184 Enforce BRU-236 when logging on after temporary lock has occurred.
Printed on : 15/02/2023
Page 26 of 27