Use Cases

Challenge Description
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
Login Store Authorized Home Page Enter Transaction
Esecurity
Login Validation Retrieve Credentials

Sign Va
Ebanking
Transaction Validation
Messaging
Core Banking
Payment
The challenge descriptions are

SEPA payment compliance
<<Compliance Reports to be obtained>>
The stakeholder needs are

To have a front end interface for making
• Domestic
a) Standard
b) SEPA
c) Periodic Payment
• SEPA and
• foreign payments
The above functionality should satisfy the challenge description.
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
New Messages Authorized Home

Window Page
Is Archive
Inbox
Configured?
Message View Archive

After Login
Print/Delete Message
Message Operations?
Message View Print
End
Overview and Reports
N.A.
To generate Various Overview and Reports for Bank and Customers

The reports are
1. Executing order overview descending on planned execution date
2. Standing order overview ascending on next execution date
3. Scheduled order overview ascending on planned execution date
4. Rejected order overview descending on planned execution date
5. Pending order overview (shopping basket) ascending on planned execution date
6. Transaction overview descending on book date
7. Order search results descending on book date (for executed orders) or planned execution date (
executing and rejected orders)
8. Account Overview
9. Interest Overview
In addition, customer specific implementations might choose to also sort:

1. On beneficiary account ascending
2. On amount ascending (without calculation of amount in Euro for orders in foreign currencies)
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
Updated Order Overview

Order Overview
Delete Confirm Delete
Transaction
Transaction Overview Error Message
Assign Budget Code Budget Code Assigned Updated Transaction Overview

Product Application
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
Login Request Product Apply Product Display Confirmation
E Banking
Publish Confirmation
Retrieve Credentials Retreive Product Details Validate
Core Banking
Product Application Receipt Confirm Product
Core Banking Employee
Validate Product
Services(Customer and Product)
N.A.
To have facilities to provide services with respect to customers and products
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
flow used in order operations for
various type of payments. 4
flow used in address book
operations in the ebanking 3
application.
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
Services This Use case explains in details the complete

functionality related to Request Additional
Account Functionality 3
This Use case explains in details the complete
functionality related to Cancel Existing Account
Functionality 3
functionality related to Cancel Designated
Account Functionality 3
functionality related to Change Credit Limit Use
Case Functionality 3
functionality related to Change Customer
Details Functionality 3
Messaging This Use Case describes on how a user will

access the messages immediately on
successful login 4
This Use Case describes on how a user will
access the messages after successful login 5
Product Application
functionality related to Bank Card Application 3
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
Login and Signing Use Case
Payment Order Entry Use

Case
Pending Shopping Basket Use
Case
Payment Order Operations

Use Case
Address Book Use Case
Order Reversal Use Case
Levensloop Funds Purchase
Request Additional account Use Case
Cancel Existing account Use Case
Change Designated account Use Case
Change Credit Limit Use Case
Change Customer Details Use Case
Messaging On Login Use Case
Messaging After Login Use Case

Bank Card Use Case
Savings Account(Public)
Current Account(Public) :
Savings Account(Private):
Current Account(Private) :
Current Account(Public)
Continuous Credit
Levensloop(Public)
Levensloop(Private)
Youth Savings Account *
Account,Transaction and Interest

Overview Use Case
Order Overview Use Case

* only as an additional
account
Levensloop Levensloop Public
Employee Employer
Use Case Goal
Precondition
Main Success Scenario
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 EF4: User doesn’t enter required fields in the

Change Password Page
The Change Password error page 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
1. The user is connected to the ebanking server

2. The user successfully logs in the system
1. The logout happens when
a. The user clicks logout on the Main Navigation Bar.
b. The session of the ebanking application ends.
2. The system clears
a. The payment shopping basket
b. Data that is not submitted to the backend.
3. The system displays the Login screen.
The User successfully Logs out of the ebanking application
<no send action > Users Logs Out
System Clears Payment Shopping Basket
System Clears Unsubmitted Information

System Clears Payment Shopping Basket
System Clears Unsubmitted Information

Use Case Goal
Precondition
Main Success Scenario
Post Condition
Alternate Flow
Exception Flow
Messaging On Login

1. The user can have message overview

A. When he successfully logs into the system
B. When he accesses the mailbox from the Main Navigation bar
2. The user is presented with emails for confirmation. The confirmation of emails
is mandatory.
3. The user is presented with a list of new messages. If there are no new
messages, a message “No New Messages” is displayed.
4. On finish, the user enters the authorized homepage.
The user successfully Confirms Emails and Checks New Emails on Login
Login
No Confir med
Success
Confir mation Messages
Author ize
Delete
Confir m Delete
Messaging After Login

1. The user has his private navigation bar displayed after

successful login
2. The user enters the inbox from the main navigation bar
3. The user reads new messages which are within the fly time
a. On delete, the user can delete a user message.
b. A delete confirmation screen is shown for delete
4. On Print, the user can print Messages
The user successfully checks the Mails and performs the

operations of delete, print
No Confir med Messages
New Messages
Messages
Author ized Home Page
Inbox
Delete Pr int
nfir m Delete View Pr int Dialog
Ar chive
Pr int
View Pr int Dialog

Ar chive
Pr int
View Pr int Dialog

Use Case Goal Savings Account(Public)
Pre Conditions 1. The user is connected to the ebanking server

2. The user has successfully logged in.
Main Success 1. The user selects the product application page

Scenario 2. The user enters the details of the first account owner.
The user enters the following fields
Account type
Name
Prefix
Maiden name
Prefix maiden name
Initials
Gender
Date of birth
Street
House number
House number detail
Post code
City
Phone home
Phone work
Phone mobile
Email
Confirm email
Identification
Identification number
Expiration date
Alternate Flow Issue date
Issue place
Tax number
Nationality
Residency in the Netherlands
3. The user is given a choice of entering a second account
holder
The fields are same as that of step 2
4. On second account owner selection, the user enters
details of the second account owner
Exception Flow Exception Flow EF1
For steps 2 to 8
If the user did not enter Mandatory Fields, the user is given
an message to enter the details.
Exception Flow EF2
From Main Success Scenario 5
If the date of birth entered in the previous sections are less
than 18, then the date of birth should be more than 18
First Account Holder Details
Second Account Holder Details

Authorized Account Holder Details

Product Details
Confirm All Data

Acknowledge Bank Conditions
Bank Card Application Product Details

Print Confirmation Screen
Edit All Data
Moving Account Service

Edit All Data

Current Account(Public) : Savings Account(Public) Savings Account(Private): Savings Account(Public)
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.
First Account Holder Details First Account Holder Details
Second Account Holder D

Authorized Account Holder

Product Details
Bank Card Application Product Details
Confirm All Data

Edit All Data

Print Customer Identity Confirmation
Confirm All Data
Edit All Data


Current Account(Private) : Current Account(Public)
1. The user is connected to the ebanking server 2. The user

has successfully logged in.
10B The agent prints out a form to confirm the customer's

identity . The form contains details for the customers and
authorized owner printed on the same page. Provision to
print two copies are made so that a copy can be given to
the agent and the customer.
Exception Flow EF1
If the user did not enter Mandatory Fields, the user is given
an message to enter the details.

Details
Product Details
s
Confirm All Data
a

onfirmation
Confirm All Data
a

onfirmation

onditions
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 Overview , Income and Expenses section
System displays loan overivew , loan amount sections with possible loan amount
System displays EMI , No of Installments
System displays loan overview , resident details
System displays loan overview , resident details
System displays loan overview , health declaration
vice
User selects from list of diseases
nfirmation
User enters ongoing loans

a
System displays loan overview , health declaration
vice
User selects from list of diseases
nfirmation
User enters ongoing loans
nditions User enters account no for EMI debit
User confirms all information

reen
System calculates credit scoring , BKR
System displays loan rejection page
System displays general terms & conditions
System displays loan confirmation

Levensloop Application(public)
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
First Guardian Details

Employer Details
Second Guardian Details

Employee Account Details for debit
Display Confirmation Screen
Display Pending Status

Product Details
Edit All Data

Edit All Data

Use Case Goal Bank Card Use Case
Pre Conditions 1. The user is connected to the e-banking server

2. The user successfully logs into the system
Main Success 1. The user selects from the list of

Scenario available accounts(Account
Name,Account Number,Account
Type,Amount)
2. The user selects the account holder(s)
for whom the bank card is required
3. The system displays the bankpass
application under Confirm bankpass
section after the ebanking backend
approves it.
4. In the Confirm Bankpass Section, the
user selects the account from which he
applied for the bankpass
5. The user enters the bankpass number
5. The system displays the signing page
in accordance to his login type.
8. The user signs and the bankpass
receipt is confirmed.Refer Exception Flow
EF1
The User successfully applies for a Bank

Post Condition
Card
Alternate Flow
Exception Flow EF1:
Sign Error
The system displays an error message
"Siganature invalid"
Select Account
Select Account Holders for Bank Pass
Signing Page Display (depending on Login)

Select Account Holders for Bank Pass
Confirmation Screen
Request Additional account Use Case
1. The user is connected to the e-banking

server 2. The user successfully logs into the
system
1. The user selects form the list of available
accounts(Account Name,Account
Number,Account Type,Amount)
2. The user enters new account details
Account Name
Account Number
Place
3. The user submits the page.
4. The system displays the signing page in
accordance to his login type..
5. The user signs the transaction. Refer
Exception Flow EF1
6. The system displays the confirmation page
7. The user confirms the application and
return to the authorized homepage
The user successfully requests for an

additional account
EF1:
Sign Error
"Siganature invalid"
Select Account
Enter New Account Details

Enter New Account Details
Confirmation Screen
Cancel Existing account Use Case
1. The user is connected to the e-banking server 2. The user successfully

logs into the system
1. The user selects form the list of available accounts(Account

Name,Account Number,Account Type,Amount)
2. The user enters another account for the transfer of money
3. The user is displayed the signing page. The signing page contains his
account number, type of account, name, target account.
4. The user signs the transaction. Refer Exception Flow EF1
5. The system displays the confirmation screen
6. The user confirms the account deletion and a confirmation form is
displayed with details of his existing account and target account.
7. The user confirms the transaction and returns to the authorized
homepage. The account cancellation is
The user successfully cancels the existing account
EF1:
Sign Error
The system displays an error message "Siganature invalid"
Select Account
Select Account for transfer of money
Signing Page Display(depending on Login)

Select Account for transfer of money
Signing Page Display(depending on Login)
Confirmation Screen with Mandatory Print Option

Change Designated account Use Case
1. The user is connected to the e-banking

server 2. The user successfully logs into the
system
1. The user selects form the list of available
accounts(Account Name,Account
2. The system displays designated accounts
with prefilled fields
3. The user edits the information. Refer
Exception Flow EF1, EF2
4. The system displays signing page
according to the login type.
5. The user signs the transaction.Refer
Exception EF3
along with print button. The page contains the
old account details, new account details and
placeholder for account holder signatures.
7. The user prints the designated account
change details and returns to the authorized
homepage.
The user successfully changes the designated

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
Option to select Account Holder details , Account Information
On Selection , edit screen is displayed
On edit, signing page is displayed

On Selection , edit screen is displayed
On edit, signing page is displayed
On signing , confirmation screen is displayed

Change Credit Limit Use Case
1. The user is connected to the e-banking server 2. The user successfully logs into
the system
1. The user selects form the list of available accounts(Account Name,Account

2. The system displays the income and expenses page
Net Income Requestor
Other Income Requestor
Net Income Partner
Other Income Partner
Living Expenses
Expenses Other Loans
Expenses Alimony Requestor
Expenses Alimony Partner
3. The system displays a page for setting the new(higher) limit. Refer Exception Flow
EF1
4. The system displays the employment details page.
Type of Employment
Start date of Employment
Name Employer
Place Employer
Marital Status
Living Situation
5. The user enters the employment details. Refer Exception EF2
6. The system displays the confirmation page with separate sections containing
information entered in sections 2,3,4 and 5
7. The user confirms the credit limit change and returns to the authorized homepage
The user successfully changes the credit limit
EF1 : if the credit limit entered is outside the prescribed bounds an error message is
displayed
Account Information
Option to select Current Accounts
isplayed
Income & Expense Details
played
isplayed
Income & Expense Details
played
Set Credit Limits within calculated bounds

s displayed
Enter Employment Information
The new limit is withing the calculated limits
Authorized Homepage
Change Customer Details Use Case
1. The user is connected to the e-banking server 2. The user

successfully logs into the system
1. The user is displayed with the options of Account holder

details(1st Account holder, 2nd Account holder and Authorized
owner)
2. The system displays an edit screen with prefilled fields once
the user selects an account. Refer Exception Flow EF1
Name
Initials
Prefix
Street
House number
House number suffix
Postcode
City
Phone home
Phone work
Phone mobile
Email
Confirm email
3. The user edits any of the fields
4. The system displays the signing page depending on the login
5. The user signs the transaction.Refer to Exception EF2
7. The user confirms the transaction and returns to the
authorized homepage
The user successfully changes the Customer details
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"
Option to select Account Holder Details
On Selection, edit screen is displayed

On Selection, edit screen is displayed
On edit, signing screen is displayed
On signing, confirmation screen is displayed

Export Data
1. The user is connected to the e-banking server 2. The

user successfully logs into the system
The user successfully exports data

Static Reports
1. The user is connected to the e-banking server 2. The

user successfully logs into the system
1. The user requests the following static report from the

Main Navigation Bar
a. information
b. disclaimer
c. help
and under the Maintenance section
a. Annual Report
2. The system displays the report to the user
3. The user returns to the authorized homepage after he
closes the report
The user successfully views static reports
User Requests Report
System Displays Report

System Displays Report
Agent Specific Reports
Use Case Goal
Pre Conditions
Main Success
Scenario
Post
Conditions
Alternate Flow
Exception Flow
Account,Interest,Transaction Overview Use Case

2. The user successfully logs into the system
1. The user is displayed Authorized homepage after successful login

2. On selecting Account overview, the user is displayed the account overview
screen. It contains an overview of the user's associated accounts and their
balances and the time of the last login for the user.
3. On selecting Account Information overview, the user is displayed the account
information overview screen. This screen shows an overview of the user's
accounts, this time with the type of account and the IBAN and BIC numbers.
4. On selecting Interest overview, the user is displayed interest overview screen.
This report screen shows an overview of the user's associated accounts, and
their accrued interests.
5. On selecting a particular Account from the Account Overview or Interest
Overview, the transaction screen is shown. The transaction screen displays the
user’s executed transactions on a particular account.
The user successfully gets an overview of Account, Account

information,Transactions and accrued Interest.
Alternative Flow AF1
1. Continued from Main Success Scenario step 5
The user selects Account Overview from the Main Navigation Bar. The default
account is pre selected in the list of available accounts.
Authorized Homepage
Account Overview
Interest Overview
Transaction Overview
Edit Transaction
Order Reversal
Delete Transaction
Order Search
Assign Budget Code
Confirm Delete
Payment Order Overview Use Case
1. The user is connected to the ebanking server 2. The user successfully logs into the system
1. The report module consists of the following reports

a. Scheduled order overview
b. Executed order overview
c. Rejected order overview
d. Standing order overview
e. Order search filter
2. On selection of Scheduled order overview, the user is shown a list of scheduled orders. The user
cancel the payment orders. The user can edit the payment orders except the standing order.
3.On selection of executed order overview, the user is shown a list of executed payment order. The
can assign budged code and reverse order on special conditions.
4. On selection of rejected order overview, the user is shown a list of rejected orders and reason fo
rejection. The rejected payment orders can be resubmitted or cancelled.
5. On selection of standing order overview, the user is shown a list of standing orders. The user can
or cancel the payment order
6. On selection of order search, the user can search within a particular orders or all orders
The search can be filtered on important fields of
The user successfully performs order overview
a. Account details
b. Personal details
Alternative
c. Date etc. Flow AF1 : Editing/Resubmitting a scheduled transaction
Continued from Main Success Scenario step 2,4 and 5
1. The system displays the payment order screen with prefilled fields of the particular transaction.
2. The user can change the fields and submits the transaction
3. The user signs the payment transaction
4. The system submits the transaction to the backend
4. On submission, the system displays a confirmation message
Alternative Flow AF2 : Deleting a Scheduled transaction

Continued from Main Success Scenario step 2,4 and 5
1. The user is displayed a confirmation screen
2. On Confirmation, the transaction is submitted to the backend for deletion
Authorized Homepage
Scheduled Executed Rejected
Display Display
Resubmit Edit Cance
Budget Code Reverse Order

Updated 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
1. The user is allowed the facility to select the following reports.

A. Executed Order Report
B. Rejected Order Report
C. Scheduled Order Report
2. On selection of Scheduled order overview, the user is shown a list of
scheduled orders.
3.On selection of executed order overview, the user is shown a list of executed
orders. The user can assign budged code and reverse order on special
conditions.
4. On selection of rejected order overview, the user is shown a list of rejected
orders. The rejected orders can be resubmitted, edited or cancelled.
The user successfully performs levensloop orders overview
Alternative Flow AF1 : Editing/Resubmitting a scheduled transaction

Continued from Main Success Scenario step 2 and 4
1. The system displays the payment order screen with prefilled fields of the
particular transaction.
2. The user can change the fields and submits the transaction
3. The user signs the payment transaction
4. The system submits the transaction to the backend
Alternative Flow AF2 : Deleting a Scheduled transaction

Continued from Main Success Scenario step 2 and 4
1. The user is displayed a confirmation screen
2. On Confirmation, the transaction is submitted to the backend for deletion
Standing Order Order Search
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.
The user successfully performs the payment transaction

AF1 : Enter New Address
Refer Address Book Use Case
AF2 : Rush Payment

Continued from Main Success Scenario 7
1. The user selects the check box to enable Rush Payment
2. The system displays a warning message
3. The execution date is disabled
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.
Order Entry The Address already Exists

Order Entry The Address already Exists
Use Existing Address
Enter payment and other details Enter New Address
Counterparty address does'nt exist
Pending Order Basket

Pending Shopping Basket Transactions
2. The user successfully logs using a login method except ldappass
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 Transaction Delete Transaction
Edit Or der
Sign All Transaction Select Transaction
Sign is Invalid :
Sign Selected Transaction

Payment Order Operations
2. The user successfully logs using a login method except
ldappass(login without signing)
3. The user has made a valid order entry
1. The screen can be entered from the main navigation bar or

by submitting the transactions form the order entry/edit
screens.
2. When the edit link is selected then the user will be
prompted with the edit order screen with the fields populated
from the information of the current order. On signing the
order in the pending list is changed.
3. When the delete link is selected, the user will be prompted
by a confirmation screen. On confirmation the order is
removed from the pending list.
4. A. The user can submit the transactions in the basket for
signing. The signing screens open depending on the login
method. Refer Login and Signing Use Case.
B. The user can select transactions and open a second
The user
screen successfully
and performs the
sign the transaction paymentontransaction
depending the login
method. Refer Login and Signing Use Case.
5. On successful signing, the order submission confirmation
screen is displayed. On signing error, the pending order
screen is re-displayed with an error message.
Or der Oper ation Scr een
Edit Or der Delete Or der Submit Or der
Sign Or der
Sign is Invalid :
Sign is Valid :
Confir mation
Order Reversal
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.
1. The system facilitates reversal transactions to be executed

from the order search criteria or from the transaction overview
screens.
2. On selection of order reversal the reversal status becomes
pending.
3. The order reversal signing screen is opened for signing the
transaction. The singing method corresponding to the login
method is shown.
4. On successful signing the confirmation screen is shown.
The user successfully performs order reversal

Address Bo
Order Reversal Operation
New Edit Del
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
The user successfully performs operations in Address book

AF1: From Main Success Scenario 1B
1. The system displays the list of existing addresses on
click of search
a. The user can select an address
b. The user can edit an address
c. The user can delete an address
2. If the address book has not reached the maximum limit,
On selecting new the user can enter a new address and
sign the transaction. Refer Main Success Scenario 2.
3. On selecting back the user can go to the relevant order
screen
EF1: From Main Success Scenario step 2 and AF1 step 2

if the user does not enter valid details, an error message is
shown
Address Book Page
New Edit Delete Search
Sign
Levensloop : Funds Purchase
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.
The user successfully buys from the recommended financial

instruments
User Chooses Mutual Fund
System Displays Funds Available
User Chooses Fund
System displays Trading Screen Error Message
User Purchases Mutual Funds Units User Purchases for an Amount
Ebanking sends Transaction to BackEnd

TABLE
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
Standard New Functionality in ABS 7.0
Standard New Functionality in ABS 7.0
Standard Functionality added for FRB in 6.x(October

2007)
Standard Functionality added for Argenta 6.5 used

for managing risk when processing new bank card
requests
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
?
Levensloop Fund Application
Payment
?
Payment
How does this table compare with the one above
?
?
?
ndard product in 7.5

Retail
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
Foreign Address Book

Budget Code
Export Data
Change Credit Limit
Request Additional Account
Request Bankpass
Confirm Bankpass Receipt

Moving Accout Service(for Current Account only)
Change Customer Details
Change designated account
Account Cancellation
Annual task report
Information
Contact us
Questions and Conditions
Disclaimer
Logout
Help
UC Number
Use Cases Name
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
Foreign Address Book
Budget Codes
Export data
Change Limits
Request Account
Request Bank Card
Confirm Reception of Bank Card
Move Accounts
Change Customer details
Change designated account
Request Account Closure
Yearly Statement
Information
Contact
Questions and Conditions
Disclaimer
Logout
Help
Request
Convert Account
Commision Overview
Request Overview
Documents and Guidelines

Prority
Date
Business
Actor Goal Brief Complexity Assignee
Need
Main Frontends
Sub Frontends Retail
domestic and SEPA - 14 y
overview and reports- 7 y
product application - 10
foreign payment - 7 y
messaging - 2 y
maintenance - 12 y
Login and Signing - 6 y
Aediles
Argenta y
DLB y
DSB y
Fortis y
Friesland Bank y
NWB y
TRACEABILITY MATRIX FOR FRONT ENDS CLASSIFICATION
public corporate agent brokerage levensloop employer

y
IMPLEMENTED USING
y
AND AGENT FRONT
y
y
IMPLEMENTED USING RETAIL FRONT END EXCEPT PRODUCT
y y
APPLICATION
y
RETAIL
ENDS
y y
TRACEABILITY MATRIX FOR FRONT END - CLIENT MAPPING

Retail Agent Public Levensloop Brokerage
y y
y y y y
y
y
y
S CLASSIFICATION
levensloop employee
L FRONT END EXCEPT PRODUCT

LICATION
- 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 is visible in account overview, interest overview, transaction overview
** Account can be selected from a drop down
*** 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
can be edited/cancelled from an order overview (edit/cancel icons are available)

CREATE TABLE EBK_IP2_S4.ADDRESSBOOKENTRY
(
ENTRYID VARCHAR2(20) NOT NULL,
RELATIONNUMBER VARCHAR2(20) NOT NULL,
NICKNAME VARCHAR2(15) NOT NULL,
COUNTERPARTYACCOUNTNAME VARCHAR2(80),
COUNTERPARTYACCOUNTCITY VARCHAR2(35),
COUNTERPARTYACCOUNTNUMBER VARCHAR2(35),
AMOUNT NUMBER(15,2),
CURRENCY CHAR(3),
PAYMENTDESCRIPTION VARCHAR2(255),
BUDGETCD VARCHAR2(20),
AEDILESUSERID VARCHAR2(20),
ADDRESSBOOKTYPEID CHAR(3) NOT NULL,
COUNTERPARTYIBAN CHAR(34),
COUNTERPARTYACCOUNTSTREET VARCHAR2(80),
COUNTERPARTYACCOUNTCOUNTRY VARCHAR2(35),
BANKNAME VARCHAR2(105),
BANKSTREET VARCHAR2(140),
BANKCITY VARCHAR2(35),
BANKCOUNTRY VARCHAR2(35),
BANKCODE VARCHAR2(20),
BANKBIC CHAR(13)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.ASSET

(
ASSETTYPE VARCHAR2(10) NOT NULL,
PORTFOLIOID VARCHAR2(20) NOT NULL,
INSTRUMENTID VARCHAR2(20) NOT NULL,
QUANTITY NUMBER(20,7) NOT NULL,
POSITION NUMBER(15,2) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.BACKOFFICEENTITY

(
ID VARCHAR2(20) NOT NULL,
ENTITYTYPE VARCHAR2(50) NOT NULL,
BANKID VARCHAR2(20) NOT NULL,
EXTERNALID VARCHAR2(20) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.BANKPRODUCT

(
ACCOUNTNUMBER VARCHAR2(35) NOT NULL,
PRODUCTTYPEID CHAR(3) NOT NULL,
DEBITINTERESTRATE NUMBER(7,3) NOT NULL,
CREDITINTERESTRATE NUMBER(7,3) NOT NULL,
ACCRUEDGAINS NUMBER(15,2) NOT NULL,
ACCRUEDLOSSES NUMBER(15,2) NOT NULL,
OVERDRAWLIMIT NUMBER(15,2) NOT NULL,
TRANSACTIONLIMIT NUMBER(15,2) NOT NULL,
DAYLIMIT NUMBER(15,2) NOT NULL,
DAYTOTAL NUMBER(15,2)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.BATCH

(
BATCHINTERNALID VARCHAR2(20) NOT NULL,
BATCHEXTERNALID VARCHAR2(20),
BATCHTYPEID CHAR(6),
BATCHDESCRIPTION VARCHAR2(255),
CREATIONDATE DATE NOT NULL,
ORIGIN VARCHAR2(255),
DATEOFEXECUTION DATE NOT NULL,
TOTALAMOUNT NUMBER(15,2) NOT NULL,
CURRENCY CHAR(3) NOT NULL,
TOTALACCOUNTNUMBERS NUMBER(18),
NUMBEROFORDERS NUMBER(7),
COMPRESSIONINDICATOR CHAR(1) DEFAULT 'N' NOT NULL,
CLIEOPSEQUENCENUMBER NUMBER(4),
CLIEOPSENDERIDENTIFICATION CHAR(5),
CLIEOPFILEIDENTIFICATION CHAR(4),
CLIEOPTRANSACTIONGROUP CHAR(2),
CLIEOPNAMECODE NUMBER(1),
CLIEOPACCOUNTNUMBER NUMBER(10),
CLIEOPACCOUNTNAME VARCHAR2(35),
CLIEOPDELIVERYCURRENCY CHAR(3),
CLIEOPDUPLICATECODE CHAR(1),
CLIEOPTESTCODE CHAR(1),
PENDINGACTIVITYTYPE CHAR(1) NOT NULL,
PENDINGAUTHORISATION NUMBER(1) DEFAULT 0 NOT NULL,
PENDINGACTIVITYID VARCHAR2(20) NOT NULL,
STATUS VARCHAR2(35) NOT NULL,
CHECKOUTUSER VARCHAR2(20)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.BIC_BANK

(
ID CHAR(20) NOT NULL,
BIC CHAR(11) NOT NULL,
OFFICIAL_BIC CHAR(1) NOT NULL,
SUBTYPE CHAR(4),
NAME_1 CHAR(35) NOT NULL,
NAME_2 CHAR(35),
NAME_3 CHAR(35),
ADDRESS_1 CHAR(35),
ADDRESS_2 CHAR(35),
ADDRESS_3 CHAR(35),
ADDRESS_4 CHAR(35),
CITY CHAR(35),
POB_NUMBER CHAR(35),
POB_CITY_1 CHAR(35),
POB_COUNTRY_1 CHAR(35),
POB_COUNTRY_2 CHAR(35),
LOG_USERID CHAR(10) NOT NULL,
LOG_DATE DATE NOT NULL,
LOG_TIME DATE NOT NULL,
FK_COUNTRY_FYSICAL CHAR(2)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.BUDGETCODE

(
BUDGETCODE VARCHAR2(20) NOT NULL,
CODEDESCRIPTION VARCHAR2(255) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.COUNTRY
(
ISO VARCHAR2(2) NOT NULL,
NAME VARCHAR2(64) NOT NULL,
IBANSIZE NUMBER NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.COUNTRY_GROUP

(
ID VARCHAR2(32) NOT NULL,
NAME VARCHAR2(32) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.COUNTRY_GROUP_COUNTRY

(
COUNTRY_GROUP_ID VARCHAR2(32) NOT NULL,
COUNTRY_ISO VARCHAR2(2) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.DAILYSTATEMENT

(
STATEMENTID VARCHAR2(20) NOT NULL,
STATEMENTDATE DATE NOT NULL,
STATEMENTNUMBER NUMBER(5) NOT NULL,
NUMBEROFTRANSACTIONS NUMBER(8) NOT NULL,
OPENINGBALANCE NUMBER(15,2) NOT NULL,
CLOSINGBALANCE NUMBER(15,2) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.DESIGNATEDACCOUNT
(
DESIGNATEDACCOUNTID VARCHAR2(20) NOT NULL,
DESIGNATEDACCOUNTNUMBER VARCHAR2(35) NOT NULL,
DESIGNATEDACCOUNTNAME VARCHAR2(80),
DESIGNATEDACCOUNTCITY VARCHAR2(35),
DESIGNATEDPRODUCTEXTERNALID VARCHAR2(20)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.ELECTRONICBANK

(
LASTDATALOAD DATE,
BIC CHAR(11)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.EXECUTEDTRANSACTION

(
EXECUTEDTRANSACTIONID VARCHAR2(20) NOT NULL,
EXTERNALID VARCHAR2(20) NOT NULL,
TRANSACTIONTYPE VARCHAR2(5),
AMOUNT NUMBER(15,2) NOT NULL,
DEBITCREDITINDICATOR CHAR(1) NOT NULL,
COUNTERPARTYACCOUNTNUMBER VARCHAR2(35) NOT NULL,
COUNTERPARTYNAME VARCHAR2(70),
COUNTERPARTYCITY VARCHAR2(70),
REQUESTEDEXECUTIONDATE DATE NOT NULL,
BOOKDATE DATE NOT NULL,
VALUEDATE DATE NOT NULL,
MUTATIONCODEBANK CHAR(12) NOT NULL,
COMPRESSIONINDICATOR CHAR(1) DEFAULT 'N' NOT NULL,
COUNTERPARTYSTREET VARCHAR2(256),
PAYMENTCODE VARCHAR2(256),
CHECKOUTUSER VARCHAR2(20),
SCHEDULEDTRANSACTIONEXTERNALID VARCHAR2(20),
ORIGINATORSIDENTIFICATION VARCHAR2(35),
BENEFICIARYIDENTIFICATION VARCHAR2(35),
BENEFICIARYNAME VARCHAR2(35)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.FOREIGNPAYMENTTRANSACTION

(
SCHEDULEDTRANSACTIONINTERNALID VARCHAR2(20) NOT NULL,
COUNTERPARTYACCOUNTCITY VARCHAR2(35),
BANKNAME VARCHAR2(105),
BANKSTREET VARCHAR2(140),
BANKCITY VARCHAR2(35),
BANKCOUNTRY VARCHAR2(35),
BANKCODE VARCHAR2(20),
TRANSACTIONCOSTINDICATOR CHAR(3) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.INSTRUMENT

(
INSTRUMENTTYPE VARCHAR2(12),
INSTRUMENTCODE VARCHAR2(20),
INSTRUMENTNAME VARCHAR2(35),
BLOCKED CHAR(1),
DENOMINATION NUMBER(6),
DEFAULTMARKETID VARCHAR2(20),
ASSETCATEGORY VARCHAR2(35),
DERIVATIVEKIND CHAR(3),
DERIVATIVESYMBOL CHAR(5),
DERIVATIVESTRIKEPRICE NUMBER(15,2),
DERIVATIVEEXPIRATIONDATE DATE,
EXTERNALID VARCHAR2(20),
ISINCODE VARCHAR2(20),
ISSUER VARCHAR2(35)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.INSTRUMENTASSETCLASS

(
ASSETCLASSCODE VARCHAR2(12) NOT NULL,
WEIGHT NUMBER(7,3)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.INSTRUMENTRATE

(
RATETYPE VARCHAR2(6) NOT NULL,
CURRENCY CHAR(3),
DATETIMESTAMP DATE
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.INSTRUMENTSELECTION

(
CHANNELID VARCHAR2(20) NOT NULL,
INSTRUMENTID VARCHAR2(20) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.MODELPORTFOLIO

(
MODELPORTFOLIOID VARCHAR2(20) NOT NULL,
WEIGHT NUMBER(7,3)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.MODELPORTFOLIODEFINITION
(
MODELPORTFOLIOID VARCHAR2(20) NOT NULL,
MODELPORTFOLIONAME VARCHAR2(35)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.MODELPORTFOLIOSELECTION

(
INVESTMENTCATEGORYID VARCHAR2(20) NOT NULL,
CHANNELID VARCHAR2(20) NOT NULL,
MODELPORTFOLIOID VARCHAR2(20) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.ORDER_METADATA

(
ID NUMBER(19) NOT NULL,
NAME VARCHAR2(20) NOT NULL,
VALUE VARCHAR2(255) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.PORTFOLIO

(
BANKID VARCHAR2(20),
ACCOUNTNUMBER VARCHAR2(35),
PRODUCTTYPEID CHAR(3),
PORTFOLIOTYPEID CHAR(4),
PORTFOLIONAME VARCHAR2(35),
EXTERNALID VARCHAR2(20) NOT NULL,
PORTFOLIOBANKID VARCHAR2(20) NOT NULL,
PORTFOLIONUMBER VARCHAR2(20)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.PRODUCT
(
PRODUCTEXTERNALID VARCHAR2(20) NOT NULL,
ACCOUNTNAME VARCHAR2(100),
DESCRIPTION VARCHAR2(255),
CURRENCY CHAR(3),
BALANCE NUMBER(15,2) DEFAULT 0 NOT NULL,
LASTBALANCEUPDATE DATE NOT NULL,
COLLECTIONSALLOWED CHAR(1) DEFAULT 'T' NOT NULL,
PENDINGACTIVITYTYPE CHAR(1) DEFAULT 'X' NOT NULL,
PENDINGACTIVITYID VARCHAR2(20) DEFAULT '0' NOT NULL,
RESERVEDBALANCE NUMBER(15,2),
LASTEXECUTEDTRANSACTIONID VARCHAR2(20)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.PRODUCTPROPOSAL

(
PROPOSALID VARCHAR2(20) NOT NULL,
CUSTOMERNAME VARCHAR2(50),
CUSTOMERINITIALS VARCHAR2(10),
OFFBALANCEAMOUNT NUMBER(15,2),
CURRENCY CHAR(3),
STARTDATE DATE,
ENDDATE DATE,
PENDINGACTIVITYID VARCHAR2(20) DEFAULT NULL,
PRODUCTEXTERNALID VARCHAR2(20),
CREDITSCOREEXTERNALID VARCHAR2(20),
CUSTOMERADDRESS VARCHAR2(50),
CUSTOMERLEGALID VARCHAR2(35),
CUSTOMFIELD1 VARCHAR2(48),
CUSTOMFIELD2 VARCHAR2(48),
CUSTOMERCITY VARCHAR2(50)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.PRODUCTPROPOSALCHILDREN

(
CHILDEXTERNALID VARCHAR2(20) NOT NULL,
CHILDACCOUNTNUMBER VARCHAR2(35),
CHILDTYPE CHAR(3)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.PRODUCTPROPOSAL_ARCHIVE

(
CUSTOMERNAME VARCHAR2(50),
CUSTOMERINITIALS VARCHAR2(10),
OFFBALANCEAMOUNT NUMBER(15,2),
CURRENCY CHAR(3),
STARTDATE DATE,
ENDDATE DATE,
STATUS VARCHAR2(35),
PENDINGACTIVITYID VARCHAR2(20),
PRODUCTEXTERNALID VARCHAR2(20),
CREDITSCOREEXTERNALID VARCHAR2(20)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.PRODUCT_RELATIONSHIPS

(
PRODUCT_RELATIONSHIPID VARCHAR2(20) NOT NULL,
RELATION_FIRSTNAME VARCHAR2(100),
RELATION_LASTNAME VARCHAR2(255),
RELATION_EMAIL VARCHAR2(255),
RELATION_ROLE VARCHAR2(50) NOT NULL,
RELATION_EXTERNALID VARCHAR2(20) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.SCHEDULEDTRANSACTION

(
STANDINGORDERINTERNALID VARCHAR2(20),
SCHEDULEDTRANSACTIONTYPEID CHAR(3) NOT NULL,
PARENTEXTERNALID VARCHAR2(20),
REPLACINGINTERNALID VARCHAR2(20),
REPLACEDBYINTERNALID VARCHAR2(20),
DATEOFEXECUTION DATE NOT NULL,
PAYMENTCODE VARCHAR2(35),
FORMCODE NUMBER(2),
HANDLINGCODE CHAR(1),
COUNTERPARTYPRODUCTEXTERNALID VARCHAR2(20),
WRITEPROTECTED CHAR(1) DEFAULT 'N' NOT NULL,
BATCHINTERNALID VARCHAR2(20),
TRANSACTIONSUBTYPE CHAR(4),
CONFIDENTIALITYINDICATOR CHAR(1) DEFAULT 'F' NOT NULL,
REJECTION_REASON VARCHAR2(255),
BANKBIC CHAR(13)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.SECURITIESPROFILE
(
MODELPORTFOLIOID VARCHAR2(20),
USESECURITIES CHAR(1),
ADVICE CHAR(1),
DIVIDENTCASHPIECES CHAR(1),
INVESTMENTCATEGORYID VARCHAR2(20),
TOTALQASCORE NUMBER(5)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.SECURITIESPROFILEQA

(
QUESTION VARCHAR2(256),
ANSWER VARCHAR2(256),
SCORE NUMBER(5),
PORTFOLIOID VARCHAR2(20) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.STANDINGORDER

(
STANDINGORDERINTERNALID VARCHAR2(20) NOT NULL,
STANDINGORDEREXTERNALID VARCHAR2(20),
FREQUENCYNUMBER NUMBER(3),
FREQUENCYUNIT CHAR(1),
FIRSTEXECUTIONDATE DATE NOT NULL,
NEXTEXECUTIONDATE DATE,
TERMINATIONDATE DATE,
TARGETAMOUNT NUMBER(15,2),
CUMMULATIVEAMOUNT NUMBER(15,2),
PERCENTAGEOFBALANCE NUMBER(3,1),
MINIMUMBALANCE NUMBER(15,2),
NUMBEROFREPETITIONS NUMBER(3),
NUMBEROFTIMESPERFORMED NUMBER(3),
WRITEPROTECTED CHAR(1) DEFAULT 'N' NOT NULL,
BANKBIC CHAR(13),
PAYMENTCODE VARCHAR2(35)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.STANDINGORDERTEST

(
STANDINGORDERINTERNALID VARCHAR2(20),
STANDINGORDEREXTERNALID VARCHAR2(20),
CURRENCY CHAR(3),
DEBITCREDITINDICATOR CHAR(1),
FREQUENCYNUMBER NUMBER(3),
FREQUENCYUNIT CHAR(1),
FIRSTEXECUTIONDATE DATE,
NEXTEXECUTIONDATE DATE,
TERMINATIONDATE DATE,
TARGETAMOUNT NUMBER(15,2),
CUMMULATIVEAMOUNT NUMBER(15,2),
PERCENTAGEOFBALANCE NUMBER(3,1),
MINIMUMBALANCE NUMBER(15,2),
NUMBEROFREPETITIONS NUMBER(3),
NUMBEROFTIMESPERFORMED NUMBER(3),
WRITEPROTECTED CHAR(1) DEFAULT 'N',
PENDINGACTIVITYTYPE CHAR(1),
PENDINGAUTHORISATION NUMBER(1) DEFAULT 0,
BANKBIC CHAR(13)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.SWITCHORDER

(
TRADEORDERINTERNALID VARCHAR2(20) NOT NULL,
WEIGHT NUMBER(7,3)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.TRADEORDER

(
TRADEORDERINTERNALID VARCHAR2(20) NOT NULL,
TRADEORDERTYPEID CHAR(3),
REPLACINGINTERNALID VARCHAR2(20),
REPLACEDBYINTERNALID VARCHAR2(20),
BUYSELLINDICATOR VARCHAR2(10),
OPENCLOSEINDICATOR CHAR(1),
LIMITPRICEINDICATOR CHAR(1),
MARKETSPECIFIEDINDICATOR CHAR(1),
ORDERREFERENCE VARCHAR2(255),
DATEOFEXECUTION DATE,
QUANTITY NUMBER(20,7),
CURRENCY CHAR(3),
LATESTPRICE NUMBER(15,2),
LIMITPRICE NUMBER(15,2),
LIMITPERCENTAGE NUMBER(7,3),
LIMITPRICEDIVIDENTINDICATOR CHAR(1),
CONFIRMATIONINDICATOR CHAR(1),
EXPIRATIONTYPE CHAR(3),
DATEOFEXPIRATION DATE,
WRITEPROTECTED CHAR(1),
PENDINGACTIVITYTYPE CHAR(1),
PENDINGAUTHORISATION NUMBER(1),
INSTRUMENTID VARCHAR2(20),
MARKET VARCHAR2(35),
MARKETFLOOR VARCHAR2(35)
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE TABLE EBK_IP2_S4.TRADEORDEREXECUTIONS

(
TRADEORDEREXECUTIONID VARCHAR2(20) NOT NULL,
TRADEORDERINTERNALID VARCHAR2(20),
EXECUTIONDATETIME DATE,
QUANTITY NUMBER(20,7),
CURRENCY CHAR(3),
TRADEORDEREXTERNALID VARCHAR2(20),
EXTERNALID VARCHAR2(20) NOT NULL
)
LOGGING
NOCACHE
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.BANKPRODUCTFK ON EBK_IP2_S4.PRODUCT

(BANKID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.BATCH_EXTID ON EBK_IP2_S4.BATCH

(BANKID, BATCHEXTERNALID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.BICPK ON EBK_IP2_S4.BIC_BANK

(BIC)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.DESIGNATEDACCOUNTPRODUCTFK ON EBK_IP2_S4.DESIGNATEDACCOUNT

(BANKID, ACCOUNTNUMBER, PRODUCTTYPEID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.ET_BATCH_EXTID ON EBK_IP2_S4.EXECUTEDTRANSACTION

(BATCHEXTERNALID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.EXECUTEDTRANSACTIONPRODUCTFK ON EBK_IP2_S4.EXECUTEDTRANSACT

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK ON EBK_IP2_S4.DAILYSTATEMENT

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK13 ON EBK_IP2_S4.PRODUCTPROPOSAL

(ACCOUNTNUMBER, PRODUCTTYPEID, BANKID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK14 ON EBK_IP2_S4.BATCH

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK15 ON EBK_IP2_S4.INSTRUMENTASSETCLASS

(INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK16 ON EBK_IP2_S4.INSTRUMENTRATE

(INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK17 ON EBK_IP2_S4.PORTFOLIO

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK18 ON EBK_IP2_S4.ASSET

(PORTFOLIOID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK19 ON EBK_IP2_S4.ASSET

(INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK21 ON EBK_IP2_S4.SECURITIESPROFILE

(MODELPORTFOLIOID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK211 ON EBK_IP2_S4.SECURITIESPROFILEQA

(PORTFOLIOID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK22 ON EBK_IP2_S4.TRADEORDER

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK23 ON EBK_IP2_S4.TRADEORDEREXECUTIONS

(TRADEORDERINTERNALID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK24 ON EBK_IP2_S4.TRADEORDEREXECUTIONS

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK25 ON EBK_IP2_S4.MODELPORTFOLIO
(INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK26 ON EBK_IP2_S4.MODELPORTFOLIO

(MODELPORTFOLIOID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK27 ON EBK_IP2_S4.PRODUCTPROPOSALCHILDREN

(PROPOSALID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK33 ON EBK_IP2_S4.EXECUTEDTRANSACTION

(BANKID, EXTERNALID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.FK6 ON EBK_IP2_S4.SCHEDULEDTRANSACTION

(BATCHINTERNALID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.INSTRUMENTSELECTIONCHANNEL_FK ON EBK_IP2_S4.INSTRUMENTSELECT

(INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.MODELDEFINITIONSELECTION_FK ON EBK_IP2_S4.MODELPORTFOLIOSELEC

(MODELPORTFOLIOID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.PARENTSTANDINGORDERFK ON EBK_IP2_S4.SCHEDULEDTRANSACTION

(STANDINGORDERINTERNALID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_ADDRESSBOOKENTRY ON EBK_IP2_S4.ADDRESSBOOKENTRY

(ENTRYID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_ASSET ON EBK_IP2_S4.ASSET

(PORTFOLIOID, INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_BACKOFFICEENTITY ON EBK_IP2_S4.BACKOFFICEENTITY

(ID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_BANKPRODUCT ON EBK_IP2_S4.BANKPRODUCT

LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_BATCH ON EBK_IP2_S4.BATCH

(BATCHINTERNALID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_BIC_BANK ON EBK_IP2_S4.BIC_BANK

(ID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_BUDGETCODE ON EBK_IP2_S4.BUDGETCODE

(BUDGETCODE, RELATIONNUMBER)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_COUNTRY ON EBK_IP2_S4.COUNTRY

(ISO)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_COUNTRY_GROUP ON EBK_IP2_S4.COUNTRY_GROUP

(ID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_DAILYSTATEMENT ON EBK_IP2_S4.DAILYSTATEMENT

(STATEMENTID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_DESIGNATEDACCOUNT ON EBK_IP2_S4.DESIGNATEDACCOUNT

(DESIGNATEDACCOUNTID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_ELECTRONICBANK ON EBK_IP2_S4.ELECTRONICBANK

(BANKID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_EXECUTEDTRANSACTION ON EBK_IP2_S4.EXECUTEDTRANSACT

(EXECUTEDTRANSACTIONID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_FOREIGNPAYMENTTRANSACTION ON EBK_IP2_S4.FOREIGNPAYM

(SCHEDULEDTRANSACTIONINTERNALID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_INSTRUMENT ON EBK_IP2_S4.INSTRUMENT

(INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_INSTRUMENTASSETCLASS ON EBK_IP2_S4.INSTRUMENTASSETC

(ASSETCLASSCODE, INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_INSTRUMENTRATE ON EBK_IP2_S4.INSTRUMENTRATE

(RATETYPE, INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_INSTRUMENTSELECTION ON EBK_IP2_S4.INSTRUMENTSELECTIO
(CHANNELID, INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_MODELPORTFOLIO ON EBK_IP2_S4.MODELPORTFOLIO

(MODELPORTFOLIOID, INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_MODELPORTFOLIODEFINITION ON EBK_IP2_S4.MODELPORTFOL

(MODELPORTFOLIOID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_MODELPORTFOLIOSELECTION ON EBK_IP2_S4.MODELPORTFOL

(INVESTMENTCATEGORYID, CHANNELID, MODELPORTFOLIOID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_PORTFOLIO ON EBK_IP2_S4.PORTFOLIO

(PORTFOLIOID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_PRODUCT ON EBK_IP2_S4.PRODUCT

LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_PRODUCTPROPOSAL ON EBK_IP2_S4.PRODUCTPROPOSAL

(PROPOSALID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_PRODUCTPROPOSALCHILDREN ON EBK_IP2_S4.PRODUCTPROP

(PROPOSALID, CHILDEXTERNALID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_SCHEDULEDTRANSACTION ON EBK_IP2_S4.SCHEDULEDTRANSA

(SCHEDULEDTRANSACTIONINTERNALID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_SECURITIESPROFILE ON EBK_IP2_S4.SECURITIESPROFILE

(PORTFOLIOID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_STANDINGORDER ON EBK_IP2_S4.STANDINGORDER

LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_STANDINGORDER_ ON EBK_IP2_S4.STANDINGORDERTEST

LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_SWITCHORDER ON EBK_IP2_S4.SWITCHORDER

(TRADEORDERINTERNALID, INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_TRADEORDER ON EBK_IP2_S4.TRADEORDER

LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PK_TRADEORDEREXECUTIONS ON EBK_IP2_S4.TRADEORDEREXEC

(TRADEORDEREXECUTIONID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PORTFOLIO_AK ON EBK_IP2_S4.PORTFOLIO

(PORTFOLIOBANKID, EXTERNALID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.PRODUCTPROPOSAL_EXTID ON EBK_IP2_S4.PRODUCTPROPOSAL

(BANKID, PRODUCTEXTERNALID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.PRODUCTPROPOSAL_REL ON EBK_IP2_S4.PRODUCTPROPOSAL

(RELATIONNUMBER, STATUS)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PRODUCT_AK ON EBK_IP2_S4.PRODUCT

(BANKID, PRODUCTEXTERNALID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.PRODUCT_RELATIOSHIPS_ID_PK ON EBK_IP2_S4.PRODUCT_RELATI

(PRODUCT_RELATIONSHIPID)
LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.RELATIONNICKNAME ON EBK_IP2_S4.ADDRESSBOOKENTRY

(RELATIONNUMBER, NICKNAME)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.RELATION_7557_FK ON EBK_IP2_S4.PORTFOLIO

(PORTFOLIOBANKID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.SCHEDULEDTRANSACTIONPRODUCTFK ON EBK_IP2_S4.SCHEDULEDTRANS

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.SCHEDULEDTRANSACTION_EXTID ON EBK_IP2_S4.SCHEDULEDTRANSACTIO

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.STANDINGORDERPRODUCTFK ON EBK_IP2_S4.STANDINGORDER

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.STANDINGORDERPRODUCTFK_ ON EBK_IP2_S4.STANDINGORDERTEST
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.STANDINGORDER_EXTID ON EBK_IP2_S4.STANDINGORDER

(BANKID, STANDINGORDEREXTERNALID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.STANDINGORDER_EXTID_ ON EBK_IP2_S4.STANDINGORDERTEST

(BANKID, STANDINGORDEREXTERNALID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.SWITCHORDERINSTRUMENT_FK ON EBK_IP2_S4.SWITCHORDER

(INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.TRADEORDERINSTRUMENT_FK ON EBK_IP2_S4.TRADEORDER

(INSTRUMENTID)
LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.TRADEORDER_EXTID ON EBK_IP2_S4.TRADEORDER

LOGGING
NOPARALLEL;
CREATE INDEX EBK_IP2_S4.TRADESWITCHORDER_FK ON EBK_IP2_S4.SWITCHORDER

LOGGING
NOPARALLEL;
CREATE UNIQUE INDEX EBK_IP2_S4.UNIQUE_EXT_ID ON EBK_IP2_S4.BACKOFFICEENTITY

(ENTITYTYPE, BANKID, EXTERNALID)
LOGGING
NOPARALLEL;
ALTER TABLE EBK_IP2_S4.ADDRESSBOOKENTRY ADD (

CONSTRAINT PK_ADDRESSBOOKENTRY PRIMARY KEY (ENTRYID));
ALTER TABLE EBK_IP2_S4.ADDRESSBOOKENTRY ADD (

CONSTRAINT RELATIONNICKNAME UNIQUE (RELATIONNUMBER, NICKNAME));
ALTER TABLE EBK_IP2_S4.ASSET ADD (

CONSTRAINT PK_ASSET PRIMARY KEY (PORTFOLIOID, INSTRUMENTID));
ALTER TABLE EBK_IP2_S4.BACKOFFICEENTITY ADD (

CONSTRAINT PK_BACKOFFICEENTITY PRIMARY KEY (ID));
ALTER TABLE EBK_IP2_S4.BACKOFFICEENTITY ADD (

CONSTRAINT UNIQUE_EXT_ID UNIQUE (ENTITYTYPE, BANKID, EXTERNALID));
ALTER TABLE EBK_IP2_S4.BANKPRODUCT ADD (

CONSTRAINT PK_BANKPRODUCT PRIMARY KEY (BANKID, ACCOUNTNUMBER, PRODUCTTYPEID));
ALTER TABLE EBK_IP2_S4.BATCH ADD (

CONSTRAINT BATCH_COMP_IND_VALUES CHECK (COMPRESSIONINDICATOR IN ('Y', 'N')));

CONSTRAINT BATCH_PENDING_ACTIVITY_VALUES CHECK (PENDINGACTIVITYTYPE in ('X', 'C', 'D', 'U', '

CONSTRAINT BATCH_PEND_AUTH_VALUES CHECK (PENDINGAUTHORISATION IN (0, 1)));

CONSTRAINT BATCH_STATUS_VALUES CHECK (STATUS IN ('new', 'scheduled', 'failed', 'rejected', 'can

CONSTRAINT PK_BATCH PRIMARY KEY (BATCHINTERNALID));
ALTER TABLE EBK_IP2_S4.BIC_BANK ADD (

CONSTRAINT PK_BIC_BANK PRIMARY KEY (ID));
ALTER TABLE EBK_IP2_S4.BUDGETCODE ADD (

CONSTRAINT PK_BUDGETCODE PRIMARY KEY (BUDGETCODE, RELATIONNUMBER));
ALTER TABLE EBK_IP2_S4.BUDGETCODE ADD (

CONSTRAINT RELATIONBUDGETCODE UNIQUE (RELATIONNUMBER, BUDGETCODE));
ALTER TABLE EBK_IP2_S4.COUNTRY ADD (

CONSTRAINT PK_COUNTRY PRIMARY KEY (ISO));
ALTER TABLE EBK_IP2_S4.COUNTRY_GROUP ADD (
CONSTRAINT PK_COUNTRY_GROUP PRIMARY KEY (ID));
ALTER TABLE EBK_IP2_S4.DAILYSTATEMENT ADD (

CONSTRAINT PK_DAILYSTATEMENT PRIMARY KEY (STATEMENTID));
ALTER TABLE EBK_IP2_S4.DESIGNATEDACCOUNT ADD (

CONSTRAINT PK_DESIGNATEDACCOUNT PRIMARY KEY (DESIGNATEDACCOUNTID));
ALTER TABLE EBK_IP2_S4.ELECTRONICBANK ADD (

CONSTRAINT PK_ELECTRONICBANK PRIMARY KEY (BANKID));
ALTER TABLE EBK_IP2_S4.EXECUTEDTRANSACTION ADD (

CONSTRAINT EXT_TR_DEB_CRED_IND_VALUES CHECK (DEBITCREDITINDICATOR IN ('D', 'C')));

CONSTRAINT EXT_TR_PENDING_ACTIVITY_VALUES CHECK (PENDINGACTIVITYTYPE in ('X', 'C', 'D', 'U',

CONSTRAINT EX_TR_MUTCODEBANK CHECK (MUTATIONCODEBANK IN ('YES', 'NO')));

CONSTRAINT EX_TR_STATUS_VALUES CHECK (STATUS IN ('reversed', 'executed')));

CONSTRAINT PK_EXECUTEDTRANSACTION PRIMARY KEY (EXECUTEDTRANSACTIONID));

CONSTRAINT UNIQUE_BANK_EXT_ID UNIQUE (BANKID, EXTERNALID));
ALTER TABLE EBK_IP2_S4.FOREIGNPAYMENTTRANSACTION ADD (

CONSTRAINT FOR_PAY_TRAN_COST_IND_VALUES CHECK (TRANSACTIONCOSTINDICATOR IN ('BEN', 'O

CONSTRAINT PK_FOREIGNPAYMENTTRANSACTION PRIMARY KEY (SCHEDULEDTRANSACTIONINTERNA
ALTER TABLE EBK_IP2_S4.INSTRUMENT ADD (

CONSTRAINT PK_INSTRUMENT PRIMARY KEY (INSTRUMENTID));
ALTER TABLE EBK_IP2_S4.INSTRUMENTASSETCLASS ADD (

CONSTRAINT PK_INSTRUMENTASSETCLASS PRIMARY KEY (ASSETCLASSCODE, INSTRUMENTID));
ALTER TABLE EBK_IP2_S4.INSTRUMENTRATE ADD (
CONSTRAINT PK_INSTRUMENTRATE PRIMARY KEY (RATETYPE, INSTRUMENTID));
ALTER TABLE EBK_IP2_S4.INSTRUMENTSELECTION ADD (

CONSTRAINT PK_INSTRUMENTSELECTION PRIMARY KEY (CHANNELID, INSTRUMENTID));
ALTER TABLE EBK_IP2_S4.MODELPORTFOLIO ADD (

CONSTRAINT WEIGHT_IS_NOT_NULL CHECK ("WEIGHT" IS NOT NULL));

CONSTRAINT PK_MODELPORTFOLIO PRIMARY KEY (MODELPORTFOLIOID, INSTRUMENTID));
ALTER TABLE EBK_IP2_S4.MODELPORTFOLIODEFINITION ADD (

CONSTRAINT PK_MODELPORTFOLIODEFINITION PRIMARY KEY (MODELPORTFOLIOID));
ALTER TABLE EBK_IP2_S4.MODELPORTFOLIOSELECTION ADD (

CONSTRAINT PK_MODELPORTFOLIOSELECTION PRIMARY KEY (INVESTMENTCATEGORYID, CHANNELID
ALTER TABLE EBK_IP2_S4.ORDER_METADATA ADD (

PRIMARY KEY (ID));
ALTER TABLE EBK_IP2_S4.PORTFOLIO ADD (

CONSTRAINT PK_PORTFOLIO PRIMARY KEY (PORTFOLIOID));
ALTER TABLE EBK_IP2_S4.PRODUCT ADD (

CONSTRAINT PRODUCT_COL_ALLOWED_VALUES CHECK (COLLECTIONSALLOWED IN ('F', 'T')));

CONSTRAINT PRODUCT_PENDING_ACT_VALUES CHECK (PENDINGACTIVITYTYPE in ('X', 'C', 'D', 'U', 'R'

CONSTRAINT PRODUCT_STATUS_VALUES CHECK (STATUS IN ('A', 'B', 'C', 'D', 'E', 'F', 'G')));

CONSTRAINT PROD_PEND_AUTH_VALUES CHECK (PENDINGAUTHORISATION IN (0, 1)));

CONSTRAINT PK_PRODUCT PRIMARY KEY (BANKID, ACCOUNTNUMBER, PRODUCTTYPEID));
ALTER TABLE EBK_IP2_S4.PRODUCTPROPOSAL ADD (

CONSTRAINT PROPOSAL_STATUS_VALUES CHECK (STATUS IN ('new', 'maybe', 'approved', 'pending',
ALTER TABLE EBK_IP2_S4.PRODUCTPROPOSAL ADD (

CONSTRAINT PK_PRODUCTPROPOSAL PRIMARY KEY (PROPOSALID));
ALTER TABLE EBK_IP2_S4.PRODUCTPROPOSALCHILDREN ADD (

CONSTRAINT PK_PRODUCTPROPOSALCHILDREN PRIMARY KEY (PROPOSALID, CHILDEXTERNALID));
ALTER TABLE EBK_IP2_S4.PRODUCT_RELATIONSHIPS ADD (

CONSTRAINT PRODUCT_RELATIOSHIPS_ID_PK PRIMARY KEY (PRODUCT_RELATIONSHIPID));
ALTER TABLE EBK_IP2_S4.SCHEDULEDTRANSACTION ADD (

CONSTRAINT SCHED_TR_CONF_IND_VALUES CHECK (CONFIDENTIALITYINDICATOR IN ('F', 'T')));

CONSTRAINT SCHED_TR_DEB_CRED_IND_VALUES CHECK (DEBITCREDITINDICATOR IN ('D', 'C')));

CONSTRAINT SCHED_TR_PENDING_ACT_VALUES CHECK (PENDINGACTIVITYTYPE in ('X', 'C', 'D', 'U', 'R

CONSTRAINT SCHED_TR_PEND_AUTH_VALUES CHECK (PENDINGAUTHORISATION IN (0, 1)));

CONSTRAINT SCHED_TR_STATUS_VALUES CHECK (STATUS IN ('new', 'scheduled', 'failed', 'rejected', '

CONSTRAINT SCHED_TR_WRITEPROT_VALUES CHECK (WRITEPROTECTED IN ('N', 'Y')));

CONSTRAINT PK_SCHEDULEDTRANSACTION PRIMARY KEY (SCHEDULEDTRANSACTIONINTERNALID));
ALTER TABLE EBK_IP2_S4.SECURITIESPROFILE ADD (

CONSTRAINT PK_SECURITIESPROFILE PRIMARY KEY (PORTFOLIOID));
ALTER TABLE EBK_IP2_S4.STANDINGORDER ADD (

CONSTRAINT ST_ORDER_DEB_CRED_IND_VALUES CHECK (DEBITCREDITINDICATOR IN ('D', 'C')));

CONSTRAINT ST_ORDER_PENDING_ACT_VALUES CHECK (PENDINGACTIVITYTYPE in ('X', 'C', 'D', 'U', 'R

CONSTRAINT ST_ORDER_PEND_AUTH_VALUES CHECK (PENDINGAUTHORISATION IN (0, 1)));

CONSTRAINT ST_ORDER_STATUS_VALUES CHECK (STATUS IN ('new', 'active', 'failed', 'rejected', 'canc

CONSTRAINT ST_ORDER_WRITEPROT_VALUES CHECK (WRITEPROTECTED IN ('N', 'Y')));

CONSTRAINT PK_STANDINGORDER PRIMARY KEY (STANDINGORDERINTERNALID));
ALTER TABLE EBK_IP2_S4.SWITCHORDER ADD (

CONSTRAINT PK_SWITCHORDER PRIMARY KEY (TRADEORDERINTERNALID, INSTRUMENTID));
ALTER TABLE EBK_IP2_S4.TRADEORDER ADD (

CONSTRAINT PK_TRADEORDER PRIMARY KEY (TRADEORDERINTERNALID));
ALTER TABLE EBK_IP2_S4.TRADEORDEREXECUTIONS ADD (

CONSTRAINT PK_TRADEORDEREXECUTIONS PRIMARY KEY (TRADEORDEREXECUTIONID));

CONSTRAINT FK_ASSET_ASSETINST_INSTRUME FOREIGN KEY (INSTRUMENTID)
REFERENCES EBK_IP2_S4.INSTRUMENT (INSTRUMENTID));

CONSTRAINT FK_ASSET_PORTFOLIO_PORTFOLI FOREIGN KEY (PORTFOLIOID)
REFERENCES EBK_IP2_S4.PORTFOLIO (PORTFOLIOID));
ALTER TABLE EBK_IP2_S4.BANKPRODUCT ADD (

CONSTRAINT FK_BANKPROD_BANKPRODU_PRODUCT FOREIGN KEY (BANKID, ACCOUNTNUMBER, PRO
REFERENCES EBK_IP2_S4.PRODUCT (BANKID,ACCOUNTNUMBER,PRODUCTTYPEID));

CONSTRAINT FK_BATCH_BATCH_BANKPROD FOREIGN KEY (BANKID, ACCOUNTNUMBER, PRODUCTTYP
REFERENCES EBK_IP2_S4.BANKPRODUCT (BANKID,ACCOUNTNUMBER,PRODUCTTYPEID));
ALTER TABLE EBK_IP2_S4.COUNTRY_GROUP_COUNTRY ADD (

CONSTRAINT COUNTRY_GROUP_ID_FK FOREIGN KEY (COUNTRY_GROUP_ID)
REFERENCES EBK_IP2_S4.COUNTRY_GROUP (ID));
ALTER TABLE EBK_IP2_S4.COUNTRY_GROUP_COUNTRY ADD (

CONSTRAINT COUNTRY_ISO_FK FOREIGN KEY (COUNTRY_ISO)
REFERENCES EBK_IP2_S4.COUNTRY (ISO));
ALTER TABLE EBK_IP2_S4.DAILYSTATEMENT ADD (

CONSTRAINT FK_DAILYSTA_PRODUCTDA_PRODUCT FOREIGN KEY (BANKID, ACCOUNTNUMBER, PROD
ALTER TABLE EBK_IP2_S4.DESIGNATEDACCOUNT ADD (

CONSTRAINT FK_DESIGNAT_BANKPRODU_BANKPROD FOREIGN KEY (BANKID, ACCOUNTNUMBER, PRO

CONSTRAINT FK_EXECUTED_PRODUCTTR_PRODUCT FOREIGN KEY (BANKID, ACCOUNTNUMBER, PROD

CONSTRAINT FK_FOREIGNP_FOREIGNPA_SCHEDULE FOREIGN KEY (SCHEDULEDTRANSACTIONINTERN
REFERENCES EBK_IP2_S4.SCHEDULEDTRANSACTION (SCHEDULEDTRANSACTIONINTERNALID));
ALTER TABLE EBK_IP2_S4.INSTRUMENTASSETCLASS ADD (

CONSTRAINT FK_INSTRASSETCL_INSTRUMENT FOREIGN KEY (INSTRUMENTID)
ALTER TABLE EBK_IP2_S4.INSTRUMENTRATE ADD (

CONSTRAINT FK_INSTRRA_INSTRUMEN_INSTRUME FOREIGN KEY (INSTRUMENTID)
ALTER TABLE EBK_IP2_S4.INSTRUMENTSELECTION ADD (

CONSTRAINT FK_INSTRSEL_INSTRUMENT FOREIGN KEY (INSTRUMENTID)

CONSTRAINT FK_MODELPOR_MODELPORT_INSTRUME FOREIGN KEY (INSTRUMENTID)

CONSTRAINT FK_MODELPOR_MODELPORT_MODELPOR FOREIGN KEY (MODELPORTFOLIOID)
REFERENCES EBK_IP2_S4.MODELPORTFOLIODEFINITION (MODELPORTFOLIOID));
ALTER TABLE EBK_IP2_S4.MODELPORTFOLIOSELECTION ADD (

CONSTRAINT FK_MODELPOR_MODELDEFI_MODELPOR FOREIGN KEY (MODELPORTFOLIOID)
REFERENCES EBK_IP2_S4.MODELPORTFOLIODEFINITION (MODELPORTFOLIOID));
ALTER TABLE EBK_IP2_S4.PORTFOLIO ADD (

CONSTRAINT FK_PORTFOLI_BANKPRODU_BANKPROD FOREIGN KEY (BANKID, ACCOUNTNUMBER, PRO

CONSTRAINT FK_PRODUCT_EBANKPROD_ELECTRON FOREIGN KEY (BANKID)
REFERENCES EBK_IP2_S4.ELECTRONICBANK (BANKID));
ALTER TABLE EBK_IP2_S4.PRODUCTPROPOSALCHILDREN ADD (

CONSTRAINT FK_PRODUCTP_PRODUCTPR_PRODUCTP FOREIGN KEY (PROPOSALID)
REFERENCES EBK_IP2_S4.PRODUCTPROPOSAL (PROPOSALID));

CONSTRAINT FK_SCHEDULE_BATCHORDE_BATCH FOREIGN KEY (BATCHINTERNALID)
REFERENCES EBK_IP2_S4.BATCH (BATCHINTERNALID));

CONSTRAINT FK_SCHEDULE_CHILDTRAN_STANDING FOREIGN KEY (STANDINGORDERINTERNALID)
REFERENCES EBK_IP2_S4.STANDINGORDER (STANDINGORDERINTERNALID));

CONSTRAINT FK_SCHEDULE_PRODUCTSC_PRODUCT FOREIGN KEY (BANKID, ACCOUNTNUMBER, PROD

CONSTRAINT FK_SCHEDULE_REPLACEDBY FOREIGN KEY (REPLACEDBYINTERNALID)

CONSTRAINT FK_SCHEDULE_REPLACING FOREIGN KEY (REPLACINGINTERNALID)
ALTER TABLE EBK_IP2_S4.SECURITIESPROFILE ADD (

CONSTRAINT FK_SECURITI_PORTFOLIO_PORTFOLI FOREIGN KEY (PORTFOLIOID)
REFERENCES EBK_IP2_S4.PORTFOLIO (PORTFOLIOID));
ALTER TABLE EBK_IP2_S4.SECURITIESPROFILEQA ADD (

CONSTRAINT FK_SECURITI_SECURITIE_SECURITI FOREIGN KEY (PORTFOLIOID)
REFERENCES EBK_IP2_S4.SECURITIESPROFILE (PORTFOLIOID));

CONSTRAINT FK_STANDING_PRODUCTST_PRODUCT FOREIGN KEY (BANKID, ACCOUNTNUMBER, PROD

CONSTRAINT FK_SWITCHOR_SWITCHORD_INSTRUME FOREIGN KEY (INSTRUMENTID)

CONSTRAINT FK_SWITCHOR_TRADESWIT_TRADEORD FOREIGN KEY (TRADEORDERINTERNALID)
REFERENCES EBK_IP2_S4.TRADEORDER (TRADEORDERINTERNALID));

CONSTRAINT FK_TRADEORD_SECURITIE_BANKPROD FOREIGN KEY (BANKID, ACCOUNTNUMBER, PROD

CONSTRAINT FK_TRADEORD_TRADEORDE_INSTRUME FOREIGN KEY (INSTRUMENTID)

CONSTRAINT FK_TRADEORD_TRADEORDE_TRADEORD FOREIGN KEY (TRADEORDERINTERNALID)
REFERENCES EBK_IP2_S4.TRADEORDER (TRADEORDERINTERNALID));

CONSTRAINT FK_TRORDEXE_SECURITIE_BANKPROD FOREIGN KEY (BANKID, ACCOUNTNUMBER, PROD
S4.DESIGNATEDACCOUNT
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')));
YTYPE in ('X', 'C', 'D', 'U', 'R')));
N IN (0, 1)));
d', 'failed', 'rejected', 'canceled', 'executed', 'delayed', 'deleted')));

TOR IN ('D', 'C')));
TYTYPE in ('X', 'C', 'D', 'U', 'R')));
S', 'NO')));
ACTIONID));
STINDICATOR IN ('BEN', 'OUR', 'SHA')));
EDTRANSACTIONINTERNALID));
DE, INSTRUMENTID));
RUMENTID));
STRUMENTID));
FOLIOID));
CATEGORYID, CHANNELID, MODELPORTFOLIOID));
OWED IN ('F', 'T')));
YPE in ('X', 'C', 'D', 'U', 'R')));
', 'E', 'F', 'G')));
N IN (0, 1)));
DUCTTYPEID));
e', 'approved', 'pending', 'canceled', 'expired', 'accepted', 'rejected', 'incomplete', 'active', 'completed', 'populat
D, CHILDEXTERNALID));
ATIONSHIPID));
CATOR IN ('F', 'T')));
ICATOR IN ('D', 'C')));
TYPE in ('X', 'C', 'D', 'U', 'R')));
ATION IN (0, 1)));
uled', 'failed', 'rejected', 'canceled', 'submitted', 'executed', 'delayed', 'deleted')));
N ('N', 'Y')));
NSACTIONINTERNALID));
ICATOR IN ('D', 'C')));
TYPE in ('X', 'C', 'D', 'U', 'R')));
ATION IN (0, 1)));

e', 'failed', 'rejected', 'canceled', 'terminated', 'inactive')));
N ('N', 'Y')));
NSTRUMENTID));
XECUTIONID));
D, ACCOUNTNUMBER, PRODUCTTYPEID)
TTYPEID));
UNTNUMBER, PRODUCTTYPEID)
ODUCTTYPEID));
ACCOUNTNUMBER, PRODUCTTYPEID)
TTYPEID));
ODUCTTYPEID));
, ACCOUNTNUMBER, PRODUCTTYPEID)
TTYPEID));
LEDTRANSACTIONINTERNALID)
ACTIONINTERNALID));
UMENTID)
ELPORTFOLIOID)
LPORTFOLIOID)
ODUCTTYPEID));
ERNALID)
NGORDERINTERNALID)
TTYPEID));
ACTIONINTERNALID));
ACTIONINTERNALID));
TTYPEID));
UMENTID)
ORDERINTERNALID)
ODUCTTYPEID));
UMENTID)
EORDERINTERNALID)
ODUCTTYPEID));
'active', 'completed', 'populated')));

Use Cases

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Use Cases

Загружено:

Авторское право:

Доступные форматы

Challenge Description

Login Store Authorized Home Page Enter Transaction

Login Validation Retrieve Credentials

The challenge descriptions are

The stakeholder needs are

The above functionality should satisfy the challenge description.

New Messages Authorized Home

Message View Archive

Message View Print

To generate Various Overview and Reports for Bank and Customers

In addition, customer specific implementations might choose to also sort:

Updated Order Overview

Delete Confirm Delete

Transaction Overview Error Message

Assign Budget Code Budget Code Assigned Updated Transaction Overview

Login Request Product Apply Product Display Confirmation

Product Application Receipt Confirm Product

Core Banking Employee

To have facilities to provide services with respect to customers and products

Services This Use case explains in details the complete

Messaging This Use Case describes on how a user will

Login and Signing Use Case

Payment Order Entry Use

Payment Order Operations

Address Book Use Case

Order Reversal Use Case

Levensloop Funds Purchase

Request Additional account Use Case

Cancel Existing account Use Case

Change Designated account Use Case

Change Credit Limit Use Case

Change Customer Details Use Case

Messaging On Login Use Case

Messaging After Login Use Case

Account,Transaction and Interest

Order Overview Use Case

Main Success Scenario

Exception Flow EF4: User doesn’t enter required fields in the

1. The user is connected to the ebanking server

The User successfully Logs out of the ebanking application

<no send action > Users Logs Out

System Clears Payment Shopping Basket

System Clears Unsubmitted Information

System Clears Unsubmitted Information

Main Success Scenario

1. The user is connected to the ebanking server

1. The user can have message overview

Confir mation Messages

1. The user is connected to the ebanking server

1. The user has his private navigation bar displayed after

The user successfully checks the Mails and performs the

No Confir med Messages

Author ized Home Page

nfir m Delete View Pr int Dialog

View Pr int Dialog

View Pr int Dialog

Pre Conditions 1. The user is connected to the ebanking server

Main Success 1. The user selects the product application page

First Account Holder Details

Second Account Holder Details

Authorized Account Holder Details

Confirm All Data

Authorized Account Holder Details