FUJ00171897
FUJ00171897
POL Use Case Source Document
FUJITSU
FUJITSU SERVICES
Date Document Created:
00/00/0000
Document 1 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
Use Cases owned by this team
DXL Heading and Text
Changes
R2
Commercial
Terms
Release
Introduced
In
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.
CT0772a
Release 2
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. Once <Username>/<Password>
verification is complete the 'Clerk' 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:
CT0772a
Release 2
Printed on : 30/08/2011
Page I of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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 Is user already logged on to other counter position check passes, (at BAD-3126)
# the 3am system maintenance reload check passes, (at BAD-3564)
# the Locked/Disabled user account check passes, (at BAD-3126)
# 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)
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- CT0772a Release 2
12 2.1.1.3 Primary Scenario
BAD- I System displays Intro screen to 'Clerk’
Printed on : 30/08/2011
Page 2 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3252
BAD- I 'Clerk' interacts with the System in some way (e.g. touches screen or the Enter key)
3253
BAD- I System requests 'Clerk' to agree to legal / security statement with options to "Accept",
14 "Cancel" or "System Diagnostics". Message MSG00006 displayed.
BAD- I 'Clerk' accepts legal / security statement
3102
BAD- I System performs offline check and determines network status is online.
3916
BAD- I System checks if Reference Data is up to date and determines it is safe to proceed in
3244 I accordance with Business Rule BRU-1001.
BAD- I System requests <username> and <password>
3103
BAD- I 'Clerk' advises system of <username> and <password>
3104
BAD- I System validates <username> and <password> in accordance with Business Rules BRU-83,
3126 I BRU-85, BRU-88, BRU-236, BRU-701, BRU-934 , BRU-942, BRU-966, BRU-1124, BRU-
1080 & BRU-1148.
BAD- I System creates an <Event Log Entry > for Log-on -completion (as specified in the Reports
3190 _I and receipts document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD- I System advises 'Clerk' of date & time of their last log on and the number of failed log on
3105 _I attempts since the last successful log-on displaying MSG-10102
BAD- I 'Clerk' checks log on details
3106
BAD- I 'Clerk' acknowledges message
3107
BAD- I System determines that the clerk attempting to log on has the correct privileges as specified
3298 _I by the menu hierarchy document DES/GEN/SPE/0007.
Printed on : 30/08/2011
Page 3 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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- I System checks if earlier User sessions on this counter were closed tidily to determine if there
3207 I 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- I The order of the following list is not important up to, (but not including) BAD-3258
3213
BAD- I System checks (using <Rollover Safe calculation>) if Stock unit rolled over into current
3214 _I Branch's Trading Period more than 38 days ago, In accordance with Business Rule BRU-407
BAD- I System checks, against Accounting Period calendar and Branch offset, that stock unit
3353 I 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- I System Checks if a 'cash declaration’ was completed from the previous day in accordance
3194 I with Business rule BRU-197 & BRU-1143
BAD- I System determines that there is no imminent price change and does not print the Office Daily
3462 __I Revalued Product List report according to BRU-933
BAD- I If the user attempting to Log on is a ‘Manager’, ‘Supervisor’ or ‘Clerk’ the system checks if CT0772a Release 2
4062 __I there are any outstanding <Transaction Acknowledgements> and finds that there are none.
BAD- I If the user attempting to Log on is a 'Manager' or ‘Supervisor’ the System checks if there are
3195 _I any outstanding <Transaction Corrections> and finds that there are none.
BAD- I Invoke Use Case Select function options.
3258
BAD- I Use Case ends
3108
BAD-
15 2.1.1.4 Variations
BAD-
3917 I 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
Printed on : 30/08/2011
Page 4 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
peripheral test and configuration functions to be performed at a counter position when the
system is either on-line/off-line or operating on out of date reference data).
BAD- I (At BAD-3102), 'Clerk' requests System Diagnostics function.
3918
BAD- I System advises Diagnostic Options MSG04010 message displaying options for engineering,
3919 powerdown, cancel
BAD- I 'Clerk' requests Engineering option
3920
BAD- I System invokes Select Function Options use case.
3925
BAD- I Use case ends
3926
BAD-
3599 I 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- I (At BAD-3126), 'Clerk’ attempts to logon on a different terminal (within same branch).
3600
BAD- I System detects that 'clerk’ is already logged on at another counter position.
3601
BAD- I System advises requesting 'clerk' to confirm if they wish to abandon the new log-on or
3602 I continue with the new log-on as a result of a failed user session at the original counter
position. MSG04002 is displayed.
BAD- I Clerk confirms that the session has failed at the original terminal requiring any active session
3604 _I to be terminated.
BAD- I System marks original user session as failed, terminating any detected active session at the
Printed on : 30/08/2011
Page 5 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3605 _I original counter position
BAD- I System creates an <Event Log Entry > for Concurrent Log-on activity -Session terminated.
4050
BAD- I Resume at BAD-3190
3606
BAD-
3566 I 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 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- I System detects users logged on
3567
BAD- I System displays early warning system maintenance reload prompt MSG90088 or MSG90089
3568 _I is displayed. (refer to section 4.2 SD/DOC/009)
BAD- I Clerk accepts message
3569
Printed on : 30/08/2011
Page 6 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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- I Use Case ends, system resumes at BAD-3252 pre-prompt state.
3570
BAD-
3299 I 2.1.1.4.4 User logging on is a Global User
BAD- I (at BAD-3298) System determines user attempting to log-on is a 'Global User’ and performs
3300 _I log-on checks in accordance with BRU-1012.
BAD- I Go to BAD-3258
3301
BAD-
3111 I 2.1.1.4.5 Branch Rollover Overdue:
BAD- I (At BAD-3214) System advises 'Clerk' that the branch has not been rolled over. Message
3120 I MSG-01059 is displayed. (Refer to SD/DOC/009 Section 10).
BAD- I 'Clerk' acknowledges messages
3132
BAD- I Resume at BAD-3213
3137
BAD-
3355 I 2.1.1.4.6 Stock Unit has not been balanced
BAD- I (at BAD-3353) System advises 'Clerk' that current 'Stock Unit’ has not been balanced
3356 _I displaying message MSG-01022.
BAD- I 'Clerk' acknowledges message.
3357
BAD- I Resume at BAD-3213
3358
BAD-
3164 I 2.1.1.4.7 Stock Unit & Branch Trading Period do not match
BAD- I (at BAD-3353) System advises 'Clerk' of variance between the 'Stock unit’ & "Branch!
Printed on : 30/08/2011
Page 7 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3165 I 'Trading Period’ (including unknown Trading Period) MSG-10104, MSG-01022, MSG-
01023 or MSG-01028 displayed.
BAD- I 'Clerk' acknowledges message
3134
BAD- I Resume at BAD-3213
3166
BAD-
3153 I 2.1.1.4.8 Cash Declaration not made from previous day
BAD- I (at BAD-3194) System advises 'Clerk' cash declaration is outstanding . Business rule BRU-
3135 197 or BRU-1143 have been broken. Message MSG 01005 is displayed.
BAD- I Invoke Use case Declare Cash Holdings, declaration must be marked as having been made
3156 I yesterday.
BAD- I Resume at BAD-3213
3241
BAD-
3472 I 2.1.1.4.9 Stock Check Reminder - Revalued Product List report Printed/Previewed
BAD- I (At BAD-3462) System determines that there is an Imminent Price Change as determined by
3473 __I Reference Data.
BAD- I System advises Clerk of Imminent Price Change by displaying MSG-01068, at every log-on
3474 I up to and including the effective date (see SD/DOC/009).
BAD- I Clerk acknowledges mesage.
3475
BAD- I Invoke BAC-186 Produce Non Cut-Off Report(s)
3479
BAD- I Resume at BAD-3213.
4061
BAD-
Printed on : 30/08/2011
Page 8 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3200
2.1.1.4.10 Transaction corrections outstanding - not processed
BAD- I (At BAD-3195) System detects that there are outstanding transaction corrections
3201
BAD- I System determines if 'Supervisor/Manager' is attached to the Default Stock Unit in
3530 accordance with BRU-696, and determines that they are not attached to the default Stock
Unit.
BAD- I System creates an <Event Log Entry > for Outstanding Transaction Correction Reminder
3612 I Displayed (as specified in the Reports and receipts document SD/DES/005 section 14.2 and
document EA/IFS/006 section B.7)
BAD- I System advises 'Supervisor/Manager’, do you wish to process now or continue with 'log-on'.
3531 _I (Message MSG-01006 is displayed. Refer to SD/DOC/009).
BAD- I The 'Supervisor/Manager' advises system to continue with 'log-on'
3202
BAD- I Resume at BAD-3213
3203
BAD-
3496 I 2.1.1.4.11 Transaction corrections outstanding - User attached to default Stock
Unit
BAD- I (At BAD-3530) System determines Supervisor/Manager is attached to Default Stock Unit in
3497 accordance with Business Rule BRU-696,
BAD- I System creates an <Event Log Entry > for Outstanding Transaction Correction Reminder
3613 I Displayed (as specified in the Reports and receipts document SD/DES/005 section 14.2 and
document EA/IFS/006 section B.7)
BAD- I System advises 'Supervisor/Manager' that there are transaction corrections outstanding, They
3500 I cannot be processed while attached to the default stock unit. Message MSG01061 is
displayed.
BAD-_I 'Supervisor/Manager' acknowledges message and system continues with 'log-on' checks
Printed on : 30/08/2011
Page 9 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3498
BAD- I Resume at BAD-3213
3499
BAD-
3204 I 2.1.1.4.12 Transaction corrections outstanding - processed
BAD- I (at BAD-3202) The 'Supervisor/Manager' advises system to process corrections now.
3205
BAD- I Invoke use case Manage transaction corrections
3206
BAD- I Resume at BAD-3213
3242
BAD-
3112 I 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- I (At BAD-3207), System detects an earlier logon session did not close tidily and that the User
3119 _I logging on has permission to carry out Recovery in accordance with BRU-703.
BAD- I System determines that there was not an incomplete basket session with outstanding
3178 _I <Recovery Data>.
BAD- I System determines that the <Session Id> of the last counter session is available on the
3179 I Counter Disk.
BAD- I System compares the <Session Id> of the last counter session as determined by the counter
3281 with the <Session Id> of the last counter session as held at the Data Centre and determines
that they are the same.
BAD- I System records Event Id 118 "No Recovery Required" and tidies up all incomplete User
3180 __I Sessions associated with this counter (other than the current User Session).
BAD- I Resume at BAD-3213.
3183
Printed on : 30/08/2011
Page 10 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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-
3992 I 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 each
recovery script is outside the scope of this use case.
BAD- I (At BAD-3119 in Variation System Recovery From System Failure), System determines that
3993 I there was an incomplete basket session with outstanding <Recovery Data> in accordance
with BRU-619 & BRU-1024.
BAD- I System invokes specified recovery script for each item of <Recovery Data>.
3994
BAD- I System conforms that all recovery scripts executed successfully.
3995
BAD- I System settles Recovery <Basket> in accordance with BRU-1137
3996
Printed on : 30/08/2011
Page 11 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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- I System records Event Id 111 "Recovery Complete", commits the Recovery Basket to the Data
3997 I Centre and tidies up all incomplete User Sessions associated with this counter (other than the
current user session).
BAD- I System confirms that Recovery Basket was successfully saved to the Data Centre.
3998
BAD- I Invoke use case Generate Printed Output to force the production of a Recovery
3999 _I 'Broken/Disconnected Session Receipt’.
BAD- I Resume at BAD-3213.
4000
BAD-
4003 I 2.1.1.4.15 System recovery from system failure by Reversing Last Basket
BAD- I (At BAD-3281 in Variation System recovery from system failure), System compares the
4004 I <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- I System analyses all Basket entries in the last session saved to the Data Centre and generates
4005 I a Reversal Transaction for all Cancellable Basket entries in that Basket to a new Recovery
Basket.
BAD- I System determines that there are entries in the Recovery Basket.
4006
BAD- I Resume at step BAD-3996 in Variation System Recovery From System Failure Where
4007 __I Recovery Data is Found.
BAD-
4009 I 2.1.1.4.16 System Recovery - No Cancellable Transactions when Reversing Basket
BAD- I (At BAD-4006 in Variation System Recovery From System Failure By Reversing Last
4010 _I Basket), System determines that there are no entries in the Recovery Basket.
BAD- I Resume at BAD-3180 in Variation System Recovery From System Failure.
4011
Printed on : 30/08/2011
Page 12 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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-
3384 I 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- I 'Clerk' advises system to be temporary locked
3388
BAD- I System accepts Temp Lock request.
3551
BAD- I System creates an <Event Log Entry > for Locked Position (as specified in the Reports and
3550 _I receipts document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD- I The system displays <Username> & <password> prompt
3389
BAD- I Resume at BAD-3163.
3391
BAD-
3371 I 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- I System creates an <Event Log Entry > for Locked Position (as specified in the Reports and
3552 __I receipts document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD- I After a configurable period, currently set at 15 minutes, of non activity the system requests
3385 _I user to confirm <Username> & <password>, in accordance with Business rule BRU-326
BAD- I Resume at BAD-3163.
3386
BAD-
3162 I 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
Printed on : 30/08/2011
Page 13 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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- I The System advises clerk of <username> and requests <username> and <password>
3163
BAD- I The 'Clerk' enters their <password>
3208
BAD- I The System checks the <password> is valid for the <username> in accordance with Business
3209 _I rules BRU- 236 & BRU-1080
BAD- I System creates an <Event Log Entry > for Position Unlocked (as specified in the Reports and
3425 _I receipts document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD- I Use Case ends, system resumes to pre-locked state.
3210
BAD-
3217 I 2.1.1.4.20 Log off by a new user after temporary lock- confirmed (No open
‘customer session’)
BAD- I (at BAD-3208) New 'User' opts to advise system of their <username> and <Password>
3218
BAD- I Business rule BRU-699 is broken, System advises the 'User’ that the session is currently
3219 I locked by someone else, are you sure you wish to log out current user. Outstanding
transactions will be committed. Message MSG04003 is displayed.
BAD- I New User’ advises system YES.
3220
BAD- I System creates an <Event Log Entry > for Forced Log-Out or Manager Forced Log Out
3580 I 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- I System creates an <Event Log Entry> for Log Out - completion for user being logged out (as
3221 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- I Resume at BAD-3252 in primary flow
3546
Printed on : 30/08/2011
Page 14 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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-
3372 I 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- I (at BAD-3208) New 'User' opts to advise system of their <username> and <Password>
3374
BAD- I System advises the 'User' that the session is currently locked by someone else, are you sure
3376 I you wish to log out current user. Outstanding transactions will be committed. Message
MSG04003 is displayed in accordance with Business Rule BRU-936
BAD- I New 'User' advises system YES.
3378
BAD- I Invoke Transact Customer Basket use case
3380
BAD- I System creates an <Event Log Entry > for Forced Log-Out or Manager Forced Log Out
3381 I 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- I System creates an <Event Log Entry> for Log Out - completion for user being logged out (as
3581 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- I Resume at BAD-3252 at primary flow
3547
BAD-
3223 I 2.1.1.4.22 Log off after temporary lock- Cancelled
BAD- I (at BAD-3220) New 'User' advises system No.
Printed on : 30/08/2011
Page 15 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3224
BAD- I Resume at BAD-3163
3225
BAD-
3114 I 2.1.1.4.23 System prompts clerk to change password
BAD- I (At BAD-3126) Business Rule BRU-83 or BRU-85 is broken, System requests clerk to enter
3118 I new <password> inhibiting Cancel option. Message MSG02158 is displayed.
BAD- I Invoke Use Case Change Password
3128
BAD- I Resume at BAD-3190 in Primary scenario.
3452
BAD-
3849 I 2.1.1.4.24 Calculate Trading Period For New Office being added to network
BAD- I (At BAD-3298), System determines user attempting to log on is a Global user with 'Add New
3850 _I Office! privileges for the first time in a new office.
BAD- I System determines new office has been successfully added to the retail office network ready
3851 for the new office Trading Period calculation.
BAD- I The 'system' compares the current 'system! date with the <Accounting Period Reference
3852 I 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- I The'system! informs the user that the Trading Period has been recorded displaying message
3853 MSG04020.
BAD- I The user acknowledges the message.
3854
BAD- I Resume at BAD-3213
3855
BAD- CT0772a Release 2
Printed on : 30/08/2011
Page 16 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3960
2.1.1.4.25 Global user permitted to log-on to an un-opened Branch
BAD- I (At BAD-3298), System detects global user attempting to log-in does not have permission to
3961 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- I System advises branch not ready to be opened/added to retail network and insufficient
3962 _I permission message MSG04027 is displayed.
BAD- I The user acknowledges the message.
3963
BAD- I Resume at BAD-3258 bypassing post login checks defined at: CT0772a Release 2
3964 _I BAD-3213, BAD-3214, BAD-3353, BAD-3194, BAD-3462, BAD-3195, BAD-4062.
BAD- CT0772a Release 2
4063 I 2.1.1.4.26 Outstanding Transaction Acknowledgements need processing
BAD- I (At BAD-4062) System detects that there are outstanding Transaction Acknowledgements. CT0772a Release 2
4064
BAD- I System displays MSG00337 stating that there are Transaction Acknowledgements to process CT0772a Release 2
4065
BAD- I Clerk acknowledges message CT0772a Release 2
4066
BAD- I INCLUDE use case Process Transaction Acknowledgements CT0772a Release 2
4067
BAD- I Resumes at BAD-3213 CT0772a Release 2
4068
BAD-
18 2.1.1.5 Exceptions
BAD-
3949 I 2.1.1.5.1 New office not initialised - Insufficient Permission Access detected
Printed on : 30/08/2011
Page 17 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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- I (At BAD-3126), System detects global user attempting to log-in does not have permission to
3951 _I proceed with adding the new office to the network in accordance with BRU-1148.
BAD- I System advises branch not ready to be opened/added to retail network and insufficient
3952 __I permission message MSG04021 is displayed.
BAD- I The user acknowledges the message.
3959
BAD- I Resume at BAD-3252.
3953
BAD-
3921 I 2.1.1.5.2 System Diagnostics Abandoned - User cancels option
BAD- I (At BAD-3920), 'Clerk' selects Cancel option.
3922
BAD- I Resume at BAD-3252.
3923
BAD-
3554 I 2.1.1.5.3 Concurrent Log on attempted - Active Session Termination Abandoned
BAD- I (At BAD-3604), Clerk confirms user logging on in error at different counter position wishing
3555 __I to abandon active session termination.
BAD- I System creates an <Event Log Entry > for Failed Log on (as specified in the Reports and
3557 __I receipts document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD- I Resume at BAD-3252.
3558
BAD-
3503 I 2.1.1.5.4 Log on Failed - Locked/Disabled user detected
BAD- I (At BAD-3126), System detects that 'username’ Account is Locked or Disabled in accordance
3504 I with
BRU-701.
Printed on : 30/08/2011
Page 18 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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- I System creates an <Event Log Entry > for Failed Log on (as specified in the Reports and
3507 _I receipts document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD- I System advises user that user account has been Locked/Disabled. MSG04000 or MSG04004
3941 is displayed. Refer to SD/DOC/009 Section 4.1.3).
BAD- I Clerk acknowledges message.
3505
BAD- I Resume at BAD-3252.
3506
BAD-
3254 I 2.1.1.5.5 Legal agreement not accepted:
BAD- I (at BAD-3102) 'Clerk' advises system to cancel legal agreement
3255
BAD- I Resume at BAD-3252.
3256
BAD-
3508 I 2.1.1.5.6 Perform system restart at log on
BAD- I (At BAD-3920), 'Clerk' requests powerdown options.
3509
BAD- I System advises powerdown options displaying MSG04011 with Restart/Shutdown/Cancel
3928 I system options available.
BAD- I Clerk selects Restart system option
3511
BAD- I System advises Confirm Restart message (Refer to SD/DOC/009 Section 4.2) MSG04012 is
3512 __I displayed.
BAD- I Clerk accepts message
3513
BAD- I System performs restart procedure.
Printed on : 30/08/2011
Page 19 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3886
BAD- I Resume at BAD-3252
3514
BAD-
3515 I 2.1.1.5.7 Perform system shutdown at log on
BAD- I (At BAD-3511), 'Clerk' requests shutdown option.
3516
BAD- I System advises Confirm Shutdown message (Refer to SD/DOC/009 Section 4.2) MSG04013
3518 I is displayed.
BAD- I Clerk accepts message
3519
BAD- I System performs shutdown procedure.
3885
BAD- I Resume at BAD-3252
3520
BAD-
3521 I 2.1.1.5.8 Perform system restart/shutdown abandoned
BAD- I (At BAD-3511), Clerk selects Cancel option.
3522
BAD- I Resume at BAD-3252
3527
BAD-
19 2.1.1.5.9 Incorrect user name or password entered
BAD- I (At BAD-3209 & BAD-3218 & BAD-3126 & BAD-3374) System detects that invalid user
20 credentials have been supplied.
BAD- I System creates an <Event Log Entry > for Log-on - Failed wrong password/user name (as
3426 I specified in the Reports and receipts document SD/DES/005 section 14.2 and document
Printed on : 30/08/2011
Page 20 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
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- I System advises clerk that an incorrect <username> or <password> has been entered
3942 _I displaying Message MSG-04001 ("IgnInvalidLogon')
BAD- I 'Clerk' acknowledges message
3302
BAD- I Resume at BAD-3103
3123
BAD-
3113 I 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 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- I (At BAD-3209 & BAD-3218 & BAD-3126, BAD-3374 & BAD-3209 ), System applies lock-
3115 __I out to 'Username’ Account in accordance with Business rule BRU-236.
BAD- I System creates an <Event Log Entry > for Locked user (as specified in the Reports and
Printed on : 30/08/2011
Page 21 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3427 _I receipts document SD/DES/005 section 14.2 and document EA/IFS/006 section B.7)
BAD- I System advises clerk their account is locked and they should contact the 'Manager’ displaying
3943 I Message MSG-04000 (IgnAccountLockout displayed).
BAD- I The 'Clerk' acknowledges message.
3121
BAD- I The 'Clerk' contacts the 'Manager' to unlock their account
3211
BAD- I Resume at BAD-3103.
3122
BAD-
3836 I 2.1.1.5.11 Unable to log on due to unsafe reference data - Ref Data Update in
Progress
BAD- I (at BAD-3244), System detects that the current version of Branch/Product reference data
3837 I held for the branch is out of date and not safe to proceed with the log-on in accordance with
BRU-1001.
BAD- I System advises clerk and displays message MSG-10101 'that the log on to the system is not
3838 I allowed at this time and to contact the helpdesk’
BAD- I Clerk acknowledges message
3839
BAD- I Resume at BAD-3252.
3840
BAD-
3856 I 2.1.1.5.12 Unable to authenicate user due to network failure
BAD- I (At BAD-3209, BAD-3218, BAD-3126, BAD-3374 & BAD-3916) System advises clerk that
3857 I user details cannot be authenicated displaying displaying one of the following messages:
If no network is detected before communications commence then MSG04014 is displayed. If
failure occurs during communications then MSG04015 is displayed.
BAD-_I 'Clerk' acknowledges message
Printed on : 30/08/2011
Page 22 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3858
BAD- I Resume at BAD-3252.
3859
BAD-
4013 I 2.1.1.5.13 System Recovery - Failure of Recovery Script
BAD- I (At BAD-3995 of Variation System Recovery From System Failure Where Recovery Data is
4020 I Found), System determines that a recovery script failed to create recovery transactions in the
basket.
BAD- I System records Event Id 112 "Recovery Complete with Exceptions", commits the Recovery
4021 I 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- I Resume at BAD-3999 in Variation System Recovery From System Failure Where Recovery
4022 _I Data Is Found ensuring that details of the failure are included in the receipt produced.
BAD-
4014 I 2.1.1.5.14 System Recovery - Failure to save Recovery Basket
BAD- I (At BAD-3998 in Variation System Recovery From System Failure Where Recovery Data Is
4025 I Found), System determines that there was a failure in saving the Recovery Basket to the Data
Centre (other than a timeout).
BAD- I Report a System Error informing the user that they will be Logged Out recording diagnostic
4026 _I information.
BAD- I Resume at step BAD-3252 in Primary Scenario (Intro wake-up screen).
4027
BAD-
4015 I 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-_I (At BAD-3998 in Variation System Recovery From System Failure Where Recovery Data is
Printed on : 30/08/2011
Page 23 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
4028 I Found), System determines that no response was received when saving the Recovery Basket
to the Data Centre.
BAD- I User is informed of the failure and the counter is Logged-Off.
4029
BAD- I Resume at BAD-3252.
4030
BAD-
4016 I 2.1.1.5.16 System Recovery - Last <Session Id> Not available on Counter Disk
BAD- I (At BAD-3179 in Variation System Recovery From System Failure), System determines that
4031 __I the <Session Id> of the last counter session is not available on the Counter Disk.
BAD- I System prompts the Clerk to enter the <Recovery Code> from the broken/disconnected
4032 session receipt produced at the time of the forced Log Out.
BAD- I Clerk enters <Recovery Code> from the broken/disconnected session receipt in accordance
4033 __I with BRU-1138.
BAD- I System derives <Session Id> of the last completed counter session from <Recovery Code>.
4034
BAD- I Resume at BAD-3281.
4035
BAD-
4017 I 2.1.1.5.17 System Recovery - Clerk doesn't know Last <Session Id>
BAD- I (At BAD-4033 in Exception System Recovery - Last <Session Id> Not Available on Counter
4036 __I Disk), User is unable to supply <Recovery Code> from broken/disconnected session receipt.
BAD- I System displays details of last saved session retrieved from Data Centre and requests User if
4037 _I this was the last completed counter session.
BAD- I User confirms that it was.
4038
BAD- I Resume at BAD-3180 in Variation System Recovery From System Failure.
4039
Printed on : 30/08/2011
Page 24 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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-
4018 I 2.1.1.5.18 System Recovery - Clerk decides last session was incomplete
BAD- I (At BAD-4038 of Exception System Recovery - Clerk doesn't know last <Session Id>), Clerk
4040 _I confirms that displayed session was not completed.
BAD- I Resume at BAD-4005 of Variation System Recovery From System Failure by Reversing Last
4041 I Basket.
BAD-
4019 I 2.1.1.5.19 System Recovery - <Recovery Code> invalid
BAD- I (At BAD-4033 of Exception System Recovery - Last <Session Id> Not available on Counter
4042 _I Disk), System determines <Recovery Code> not valid in accordance with BRU-1138.
BAD- I System displays message MSG-90964 advising User that <Recovery Code> is invalid.
4043
BAD- I User acknowledges messsage.
4044
BAD- I Resume at BAD-4032 of Exception System Recovery - Last <Session Id> Not available on
4045 _I Counter Disk.
BAD-
3110 I 2.1.1.5.20 Error in Log on details displayed
BAD- I (at BAD-3106) Clerk advises 'NBSC'
3117
BAD- I 'NBSC' gives authority to proceed
3140
BAD- I Resume at BAD-3107.
3141
BAD-
3491 I 2.1.1.5.21 Unable to log on shared user - Stock unit balance already in progress
BAD- I (At BAD-3126), System determines that the user logging onto the attached Stock unit is in
Printed on : 30/08/2011
Page 25 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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
3492 _I the process of Balancing in accordance with BRU-934 and BRU-966.
BAD- I System advises clerk logging onto the system will be automatically logged out displaying
3494 I Message MSG00302. (Note: Message(s) not included in SD/DOC/009 document).
BAD- I Clerk acknowledges message.
3528
BAD- I Resume at BAD-3252.
3529
BAD-
3845 I 2.1.1.5.22 Log on Cancelled
BAD- I (At BAD-3104), Clerk decides to cancel log on request.
3846
BAD- I Resume at BAD-3252.
3847
BAD-
21 2.1.1.6 Trigger
BAD- I 'Clerk' wishes to start a new user session or re-commence after a temporary lock or forced
22. system logout.
BAD-
23 2.1.1.7 Preconditions
BAD- I The 'System' must be connected to the data centre
3835
BAD- I 'Clerk' has a valid user account within the branch
24
BAD- I Any outputs from a previous session are available.
3290
BAD-
25 2.1.1.8 Stakeholders and Interests
Printed on : 30/08/2011
Page 26 of 28
FUJ00171897
FUJ00171897
POL Use Case Source Document FUJITSU
FUJITSU SERVICES
Date Document Created: 00/00/0000
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- I 'Clerk' wishes to operate a stock unit
26
BAD-
27 2.1.1.9 Minimal Guarantees
BAD- I The 'Clerk' will only be logged on if all of the validation criteria have been met.
28
BAD- I If Log-on is interrupted by an exception which prevents log-on taking place, the system shall
3909 I 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- I 'Clerk' is successfully logged on to the system.
30
BAD-
31 2.1.1.11 Non-Functional Requirements
BAD- I None
3398
BAD-
33 2.1.1.12 Business Rules
BAD- I See Links to Business Rules module_
34
BAD-
35 2.1.1.13 Process Changes
BAD- I Enforce BRU-236 when logging on after temporary lock has occurred.
3184
Printed on : 30/08/2011
Page 27 of 28