Beruflich Dokumente
Kultur Dokumente
Stakeholder
needs
Login and Signing
N.A.
To have a secure Login and Signing Mechanism with the following types
Login
• User id / password
• Bankcard
• DP300
Sign
• ldappass
There is no signing under this login
• passtan
The user has to use his TAN list to find the correct response to the challenge
• passsign
The signing is hidden under this login
• DP300
The user has to use his DP300 token to generate the correct response to the
• pocketid
The user has to use his bankcard and the pocketid token to generate the correct respo
Channel
Esecurity
Ebanking
Transaction Validation
Messaging
Core Banking
Payment
Payment
Chanel
Publish
Enter Payment Sign depending Transaction
start 1 Login 1
Details on login type Details
eSecurity
4 5. Failed
6. Succeed
Ebanking
11
Validate
payment details
7
11
essaging
Service
M
Corebanking
Schedule Authorize
Payment Request 1 1 1 1 Execute Paym
Payment Payment
1
employee
banking
ore
Approve Payment
C
Messaging
N.A.
The Client needs a module which will take care of the needs of consumers with respect to messagi
1. To have a messaging system immediately after login which displays mandatory confirmation me
emails
2. To have an Inbox facility to display new messages with a fly time.
3. To have archive facility to store messages permanently with a fly time.
Messaging
Confirmation
start Login Confirm Messages
Messages?
OnLogin
Is Archive
Inbox
Configured?
Print/Delete Message
Message Operations?
End
Overview and Reports
N.A.
Where applicable, the paging size is determined by the result set size of the e-Business Engine.
Authorized Homepage
Account
Account Information
Account Overview
Interest
Interest Overview
Order
Order Search
Edit Validation
Transaction
N.A.
The stakeholder needs are to create a module which can be used to apply for the following ebankin
a) Savings account
b) Current account
c) Youth savings account
d) Levensloop account
e) Continuous credit account
The products are linked to the following actors and are customizable
a) Retail Customer
b) Agent
c) Public
Front End
E Banking
Publish Confirmation
Retrieve Credentials Retreive Product Details Validate
Core Banking
Validate Product
Services(Customer and Product)
N.A.
Customer
1. Change Customer Data
Products
1. Change designated account
2. Delete existing account
3. Change Credit Limit
4. Request Additional Account
Module Usecase
Complexity
Use Case Brief (1 - 5)
Login
This use case describes the process
by which users can login into the e-
banking application and sign . 5
The use case covers the process
Payment flow used in payments and their
variations in the ebanking
application.
The use case covers the 5
methodology used in signing
payment deals 3
The use case covers the process
flow used in order operations for
various type of payments. 4
The use case covers the process
flow used in address book
operations in the ebanking 3
application.
The use case covers the process
flow for order reversal in the
ebanking application. 4
This use case describes the
methodology for purchasing funds
under a user's levensloop employee
account 5
2
4
5
2
2
Overview and Reports The use case aims to describe the account,
account information, transaction and interest
overview screens. 4
This Use case explains in details the
complete functionality related to
Order Overview Functionality 5
Customer Retail Customer Corporate
representative(agent) Customer
Use Case Goal
Precondition
Post Condition
Alternate Flow
Exception Flow
backend for validation.
7. The e-banking backend passes the credentials to the e-security
layer
Exceptionand validates
Flow EF1:the User details
doesn’t for enter
the following
required fields in the login
a.
page(i)Existence of the login id
(ii) If the login id and password match
(iii) from
Begin ResponseMain matching the challenge
Success Scenario Step 5
b.the
If (i)Existence
user doesofnot theenter
logineither
id the login id or the password or
Login
(ii) Ifand
both. Signing
the login id and password match
1. If the user did not enter the
(iii) Response matching bothchallenge
the user id and Password the error
c.
1. (i)Existence of the
message "User id is wrong" the
The user is connected login toid ebanking server
is displayed
2. (ii)the
2. If
The Ifuser
the
user login id and
successfully
did not enter password
logs thematch
theinpassword systemthe error message
(iii) TAN is
"password number
wrong"validation
is displayed
d. (i)Existence of the login id
Flow(ii)continues
If the loginto: idMain
and password
Success Scenario match Step 3
Refer Exception Flow EF2 and Exception Flow EF3
8. If detailsFlow
Exception are validated
EF2: Loginfrom e-security
id doesn’t existlayer,
,Login system
id anddirects the
password
user to
don’t the authorized
match and signing homepage.
is invalid
9. In the landing page, the private navigation bar is displayed
10.
Begin The userMain
from enters into aScenario
Success (financial) transaction
Step 6
a) On submit the response code
1. If the user id is incorrect, system displays is sent to theanebanking backend
error message and
Alternate
b) Ontocancel
asks Flow
contact AF1:
thethe
userUser
help selects
returns
desk to link to change
theproblem
if the password
previouspersists
screen of the
authorized
2. If the user homepage/
id is correct account
and the overview
password without signingsystem
is incorrect, the
Begin from
transactions. Main Success Scenario Step 3
displays an error message and asks to contact the help desk if the
If
11.theThe
problem user chooses
backend
persists Wachtwoord
checks for validity wijzigen
of theoption
response.(to change
If the
password)
response is valid, the transaction
The login error screens are same for is carried out successfully.
1. System
Refer
• User id / directs
Exception
password the EF5
Flow user to the screen 0017.
2. The
• Bankcard user enters the following fields
a)
The User
• DP300User idsuccessfully
– This is prefilled
Logs into if thethelogin screenapplication
ebanking contains a user id
b) Old Password
3. If the sign is invalid, the system displays a error message
c) New Password
indicating "Wrong Signature"
d) New Password Confirmation
e) Option to
Exception Flowchoose
EF3: submit
This error happens when an unsuccessful
f) Option to choose cancel
login attempt happen due to a technical problem with the
On choice of
underlying submit
access the password
control databaseis(LDAP).
successfully
In thischanged
case the login
On choice of cancel Main
failure attempt will not be increased. Success Scenario step 4 is displayed
Exception Flow EF5 User doesn’t enter the correct response code
in the signing page
The same screen is re-displayed with the subtitle Signature error
(“Handtekening fout”), so that the user can try to sign again.
Logout
Precondition
Post Condition
Alternate Flow
Exception Flow
Messaging On Login
The user successfully Confirms Emails and Checks New Emails on Login
Login
No Confir med
Success
Author ize
Delete
Confir m Delete
Messaging After Login
New Messages
Messages
Inbox
Delete Pr int
Ar chive
Pr int
Pr int
Product Details
1. The user is connected to the ebanking server 2. The user 1. The user is connected to the ebanking server 2. The
has successfully logged in. user has successfully logged in.
7B The user has the option to apply bankcard for the 9 B. The agent prints out a form to confirm the customer's
account holders. identity . The form contains details for the customers and
9 The user is displayed with a moving account authorized owner printed on the same page. Provision to
screen(oversstap service) where he can move current print two copies are made so that a copy can be given to
accounts from other banks the agent and the customer.
Exception Flow EF1 Exception Flow EF1
For steps 2 to 9 For steps 2 to 6
If the user did not enter Mandatory Fields, the user is given If the user did not enter Mandatory Fields, the user is given
an message to enter the details. an message to enter the details.
Product Details
Bank Card Application Product Details
If the user did not enter Mandatory Fields, the user is given
an message to enter the details.
Product Details
s
a
Moving Account Service
a
Moving Account Service
creen
Continuous Credit
1. The user is connected to the ebanking server 2. The user has successfully logged in.
1. The product application can be accessed fromproduct application section of the Main
Navigation Bar
2. The product applicaton page has three sections namely loan overview section, income
and expenses section
The fields are
Loan Overview Section
Possible Loan Amount
Loan Amount
Monthly payment
Loan duration
Effective interest rate - Set to an interest rate by ebanking backend
Income Section
Net income
Additional income
Partner net income
Partner additional income
Expenses Section
Housing costs (rent)
Monthly expenses for loans
Pending loans to be repaid
Alimony
The user also enters the number of children and the his marital status
3.The system
AF1 : From displays
Main loan
Success amountstep
Scenario and15
insurance page . This contains loan overview
section and Loan
1. The system amount
displays section. screen if the outcome is NO.
a rejection
4. The system fills the Possible
2. The user acknowledges the screen Loan Amount
and goes Under Loan
to the Overview
authorized Section based on the
homepage
Income and Expenses
5. The user enters the following under Loan Amount Section . Refer Exception Flow EF2
Loan amount
Repayment percentage
Insurance in case of death
6. The system displays the Monthly installment amount and no of installments when he
clicks on calculate
7. The system displays Applicant name and residence page . This contains loan overview
etails
System displays loan overivew , loan amount sections with possible loan amount
vice
nfirmation
vice
nfirmation
1. The user is connected to the ebanking server 2. The user has successfully
logged in.
Levensloop Application(private) Youth Savings Account : Savings Account (Public)
1. The user is connected to the ebanking server 2. The user has 1. The user is connected to the ebanking server 2. The user has
successfully logged in. successfully logged in.
1. The user enters the personal information details 3. The user enters details of the first guardian
2. The user enters the employer details 4. On second guardian selection, the user enters details of the
3. The user enters the employee account number which will be second guardian
used towards the levensloop account(for debit)
4. The user is displayed the confirmation screen that contains
details which are editable.
5. Upon confirmation, the pending status of the account is
displayed .
Employee Personal Details First Account Holder Details
Select Account
Confirmation Screen
Request Additional account Use Case
EF1:
Sign Error
The system displays an error message
"Siganature invalid"
Select Account
Confirmation Screen
Cancel Existing account Use Case
EF1:
Sign Error
The system displays an error message "Siganature invalid"
Select Account
EF1:
If the user did not enter Mandatory Fields, the
user is given an message to enter the details.
EF2:
If the user enters wrong account number, the
system displays an error message.
EF3:
Sign Error
The system displays an error message
1. The user is connected to the e-banking server 2. The user successfully logs into
the system
EF1 : if the credit limit entered is outside the prescribed bounds an error message is
displayed
Account Information
Option to select Current Accounts
isplayed
played
isplayed
played
Authorized Homepage
Change Customer Details Use Case
EF1:
If the user did not enter Mandatory Fields, the user is given an
message to enter the details.
EF2:
Sign Error
The system displays an error message "Siganature invalid"
Pre Conditions
Main Success
Scenario
Post
Conditions
Alternate Flow
Exception Flow
Account,Interest,Transaction Overview Use Case
Account Overview
Interest Overview
Transaction Overview
Edit Transaction
Order Reversal
Delete Transaction
Order Search
Confirm Delete
Payment Order Overview Use Case
1. The user is connected to the ebanking server 2. The user successfully logs into the system
Display Display
Updated Display
Levensloop Order Overview Use Case
1. The user is connected to the ebanking server 2. The user successfully logs into
the system
Display Filter
Display
ncel
Use Case Goal
Pre Conditions
Main Success
Scenario
Technology and
Data Variations
Post Condition
Alternate Flow
Exception Flow
Open Issues
a.Standard Payment and Acceptgiro
(i). The business days of the bank as entered in the ebanking system
(ii). The cut off time for the order type
The user can change it to a future date or time.
b.Standing Order Entry
The payment is carried out periodically like weekly, fortnight, monthly,
quarterly,
Payment half-yearly,
Order Entry yearly etc.
1. The user is connectedout
The user can choose to of
thethe following
ebanking three.
server
(i)Start Date.
2. The user successfully logs using a login method except ldappass
The start date is greater than the execution date.
The payment is done perpetually on a periodical basis(as selected)
(ii)End Date
The payment is done on a periodical basis(as selected) till the end
date
(iii)Number of Iterations
The payment is done on a periodical basis(as selected) for the number of
times specified
Refer Alternate Flow AF2
5. The user can
a. Submit the transaction
b. Submit and move to Acceptgiro order entry screen
c. Submit and move to Periodic order entry screen
d. Cancel the payment and move to Authorized homepage
6. The system stores the transactions in a shopping basket with pending
status.
EF1 The user does not enter proper details in the form
The ebanking application flags an error to enter proper details.
EF2 The user does not have sufficient money for the transfer
The transaction that is committed by the user in the form is executed
at the cut off time of execution date. If the user does not have sufficient
money in his account, an error is flagged by the backend.
1. The system displays valid payments entered by the user. The fields
displayed are
2. The user can perform the following operations on the deals
a. edit
b. delete
3. The user can sign the transaction using the following methods
a. The user signs all the transactions using the signing method
determined by the login
b. The user can sign select transaction from the basket using the
signing method determined by the login
Refer Exception Flow EF1
4. The system deletes the shopping basket on logout
View Transaction
View Transaction
Edit Or der
Sign All Transaction Select Transaction
Sign is Invalid :
Sign Or der
Sign is Invalid :
Sign is Valid :
Confir mation
Order Reversal
1. The user is connected to the ebanking server
2. The user successfully logs using a login method except
ldappass(login without signing)
3. The account must be configured to allow reverse transactions.
4. The user must be allowed to submit reversals.
5. The transaction is scheduled and not executed.
Signing Process
Submit Or der
Sign
Confirmation
alid :
1. The user
Address enters the address book list from
Book
A. The main navigation
1. The user is connected tobar
the ebanking server
2. The user successfully logscounterparty
B. A form which requires using a loginaddress
method except
2. If the address book has not
ldappass(login without signing) reached the maximum limit,
On selecting new
a. The user enters the short name, name, IBAN, address,
city and country of the beneficiary
b. The user enters the BIC, bank name, address, place and
land of the beneficiary bank
c. The user enters description in the standard information
field
d. The use Signs the transaction
e .The system saves the new Address
3. On selecting edit the user can proceed to edit an
existing address and sign the transaction
4. On selecting delete the user can delete an existing
address and sign the transaction
5. On selecting search the user can search from the
existing addresses
6. On selecting back the user can go to the previous screen
Sign
Levensloop : Funds Purchase
1. The user is connected to the ebanking server
2. The user successfully logs using a login method except
ldappass(login without signing)
1. The user selects from a recommended list
a. Equity funds region
b. Funds shares theme
c. Green funds
d. Mix funds
e. Bond funds
f. Real estate funds
g. Specialities
2. Upon selection, the sytem displays the funds available under the
mutual fund.
3. Upon selection, the system displays a trading screen where the
user can purchase mutual funds units. The user can enter an amount
or number of mutual fund units.
4. The user signs the transaction
5. The sytem sends the transaction to the back end for execution.
ADDRESSBOOKENTRY
ASSET
BACKOFFICEENTITY
BANKPRODUCT
BATCH
BIC_BANK
BUDGETCODE
COUNTRY
COUNTRY_GROUP
COUNTRY_GROUP_COUNTRY
DAILYSTATEMENT
DESIGNATEDACCOUNT
ELECTRONICBANK
EXECUTEDTRANSACTION
FOREIGNPAYMENTTRANSACTION
INSTRUMENT
INSTRUMENTASSETCLASS
INSTRUMENTRATE
INSTRUMENTSELECTION
MODELPORTFOLIO
MODELPORTFOLIODEFINITION
MODELPORTFOLIOSELECTION
ORDER_METADATA
PORTFOLIO
PRODUCT
PRODUCTPROPOSAL
PRODUCTPROPOSAL_ARCHIVE
PRODUCTPROPOSALCHILDREN
PRODUCT_RELATIONSHIPS
SCHEDULEDTRANSACTION
SECURITIESPROFILE
SECURITIESPROFILEQA
STANDINGORDER
STANDINGORDERTEST
SWITCHORDER
TRADEORDER
TRADEORDEREXECUTIONS
The rest of the tables are currently specifict to DLO and will become part of the standard product in
Comments
ently specifict to DLO and will become part of the standard product in 7.5
User Interface Screen sub-module use case
Maintenance->Address Book
?
Payments
Account Overview
Account Information
Interest Overview
Payment
Payment
?
Product Application
Payment
Payment
Levensloop Fund Application
?
Payment
?
Payment
How does this table compare with the one above
?
?
?
Account Overview
Account Information
Interest Overview
Messages
Inbox
Archive
Domestic Payments
Standard Payment
Payment by slip
Periodic payment
Foreign Payments
Shopping Basket
Order Selection
All Orders
Overview of Contracts
Scheduled Order Overview
Executed Order Overview
Rejected Order Overview
Standing Order Overview
Order Search Filter
Maintenance
Address Book
Account Overview
Account Information
Interest Overview
Messages
Inbox
Archieve
Local Payments
Transfer
Acceptgiro
Periodical
Foreign Transfers
Send Transactions
Select Orders
Send All
Transaction Overview
Processed
Awaiting processing
Rejected
Periodical
Search Transactions
Maintenance
Address book
Budget Codes
Export data
Change Limits
Request Account
Move Accounts
Change Customer details
Yearly Statement
Information
Contact
Disclaimer
Logout
Help
Request
Convert Account
Commision Overview
Request Overview
Aediles
Argenta y
DLB y
DSB y
Fortis y
Friesland Bank y
NWB y
TRACEABILITY MATRIX FOR FRONT ENDS CLASSIFICATION
y
AND AGENT FRONT
y
y
IMPLEMENTED USING RETAIL FRONT END EXCEPT PRODUCT
y y
APPLICATION
y
RETAIL
ENDS
y y
y
y
S CLASSIFICATION
levensloop employee
- CLIENT MAPPING
Credit
Account Status Active
blocked
Quaestor Status OO OD
eBank Status A C
Cancel order* x x
Change designated account** x x
Close account** x x
Confirm bankcard (only current accounts)** x x
Confirm creditcard (only current accounts)** x x
Edit order*** x x
Enter order** x x
Export Gegevens** x x
Overstapservice (only current accounts)** x
Request bankcard (only current accounts)** x x
Request creditcard (only current accounts)** x x
View Account* x x
*** Account can be selected from a drop down (edit order) or order can be edited/cancelle
Debit
Debit To be Read
credit Closed
blocked closed Blocked
blocked
OC OB OX C ??
D E G B F
x x
x x
x x
x x x x
x
x x
x x
x x x x
on overview
NSACTION
2_S4.EXECUTEDTRANSACTION
2_S4.INSTRUMENTSELECTION
.MODELPORTFOLIOSELECTION
EDULEDTRANSACTION
4.ADDRESSBOOKENTRY
BACKOFFICEENTITY
KPRODUCT
OUNTRY_GROUP
ILYSTATEMENT
S4.DESIGNATEDACCOUNT
ECTRONICBANK
2_S4.EXECUTEDTRANSACTION
EBK_IP2_S4.FOREIGNPAYMENTTRANSACTION
2_S4.INSTRUMENTASSETCLASS
STRUMENTRATE
_S4.INSTRUMENTSELECTION
ODELPORTFOLIO
K_IP2_S4.MODELPORTFOLIODEFINITION
K_IP2_S4.MODELPORTFOLIOSELECTION
PRODUCTPROPOSAL
BK_IP2_S4.PRODUCTPROPOSALCHILDREN
P2_S4.SCHEDULEDTRANSACTION
SECURITIESPROFILE
ANDINGORDER
TANDINGORDERTEST
CHORDER
P2_S4.TRADEORDEREXECUTIONS
DUCTPROPOSAL
CTPROPOSAL
_IP2_S4.PRODUCT_RELATIONSHIPS
DRESSBOOKENTRY
P2_S4.SCHEDULEDTRANSACTION
4.SCHEDULEDTRANSACTION
ANDINGORDER
TANDINGORDERTEST
NGORDER
INGORDERTEST
SWITCHORDER
RADEORDER
FICEENTITY
, PRODUCTTYPEID));
R IN ('Y', 'N')));
N IN (0, 1)));
S', 'NO')));
ACTIONID));
EDTRANSACTIONINTERNALID));
DE, INSTRUMENTID));
RUMENTID));
STRUMENTID));
FOLIOID));
N IN (0, 1)));
DUCTTYPEID));
e', 'approved', 'pending', 'canceled', 'expired', 'accepted', 'rejected', 'incomplete', 'active', 'completed', 'populat
D, CHILDEXTERNALID));
ATIONSHIPID));
N ('N', 'Y')));
NSACTIONINTERNALID));
N ('N', 'Y')));
NSTRUMENTID));
XECUTIONID));
D, ACCOUNTNUMBER, PRODUCTTYPEID)
TTYPEID));
UNTNUMBER, PRODUCTTYPEID)
ODUCTTYPEID));
ACCOUNTNUMBER, PRODUCTTYPEID)
TTYPEID));
D, ACCOUNTNUMBER, PRODUCTTYPEID)
ODUCTTYPEID));
, ACCOUNTNUMBER, PRODUCTTYPEID)
TTYPEID));
LEDTRANSACTIONINTERNALID)
ACTIONINTERNALID));
UMENTID)
ELPORTFOLIOID)
LPORTFOLIOID)
D, ACCOUNTNUMBER, PRODUCTTYPEID)
ODUCTTYPEID));
ERNALID)
NGORDERINTERNALID)
, ACCOUNTNUMBER, PRODUCTTYPEID)
TTYPEID));
ACTIONINTERNALID));
ACTIONINTERNALID));
ACCOUNTNUMBER, PRODUCTTYPEID)
TTYPEID));
UMENTID)
ORDERINTERNALID)
, ACCOUNTNUMBER, PRODUCTTYPEID)
ODUCTTYPEID));
UMENTID)
EORDERINTERNALID)
ACCOUNTNUMBER, PRODUCTTYPEID)
ODUCTTYPEID));
'active', 'completed', 'populated')));