"Software Engineering" documentation-banking management-object-oriented analysis and design

Software

Bank business management and cash settlement system

--- object-oriented analysis and design documentation

* * * Original All, this article prohibits all forms of unauthorized reprint, if you need to reprint the contact author , please respect the author's rights .

The following UML modeling diagrams are for informational purposes only.

One, object-oriented Analysis 1. Establish the use case model I. Account

use case Description: the account opening case diagram, the administrator initiated the opening account, the depositors provide account information, identity information, the administrator to verify the legitimacy of the account and identity authenticity after entering account information, depositors set the password, the process involves the verification of legality (account number is correct, identity real, etc.), add account information, etc. The depositor can print the voucher.

II. Sales Account

use case description: pin Household use case diagram, the active pin households by the administrator to initiate the business, the depositors provide account information, identity information, enter the password, the administrator to verify the correct identity of the password to enter account information, and verify the balance of the account, if the balance is returned to the customer to complete the sale, if no balance directly completed. The process involves verifying legality (password is correct, identity is true, etc.), processing balance, deleting account information, etc. The depositor can print the voucher. Passive pin households need to conduct the household Judgment (loss of the subsystem), if the judgment can be sold, then the balance, the completion of the sale of households.

III. Freezing

use case Description: frozen use case diagram, the active freeze by the administrator initiated the frozen transaction, the depositor provides account information, identity information, the administrator to verify the password correct identity authenticity after entering the account information, complete the freeze. The process involves verifying correctness (password is correct, identity is true, etc.), modifying account status information, etc. The depositor can print the voucher. Passive freezing is required to freeze the judgment, if the password is greater than three times, the account freezes.

Iv. Loss-reporting

use case Description: loss of use case diagram, the administrator needs user input account information, can trigger the loss of business, wherein the loss of transactions including the loss of information, to obtain the balance information and the trigger judgment, determine whether the loss of a certain time, automatically trigger the pin households.

V. Deposit

use case Description: In the deposit use case diagram, the administrator needs the user to enter account information, or print the deposit information to trigger the deposit transaction, where the deposit transaction includes modifying the balance information and generating deposit information two functions.

VI. Withdrawals

use case Description: withdrawal use case diagram, the administrator needs the user to enter account information, as well as the account password, after the balance verification can trigger the withdrawal transaction, where the withdrawal transaction includes modifying the balance information and generating the withdrawal information printing voucher two functions.

VII. Transfer

use case Description: in the transfer case diagram, the administrator initiates a transfer transaction, enters the transfer information, and secondly, the depositor can complete the transfer by verifying the account password, which involves calculating the handling fee, verifying the legality (such as sufficient balance, correct account number, etc.), modifying the account balance, generating the transfer information, etc. The transfer party can print the transfer slip and the payee can print the receipt.

Viii. contributions

use case Description: in the payment use case diagram, the administrator initiates the payment transaction, enters the payment information, secondly, the depositor can complete the payment by verifying the account password, which involves verifying the legality (such as sufficient balance, the existence of the payment object, etc.), modifying the account balance, generating payment records, etc. At the same time, depositors (payers) can choose to print the bill of payment.

IX. Management

Use case Description: The administrator manages the use case diagram, initiates the management transaction by the administrator, chooses the transaction type such as inquires the information, modifies the interest rate or the handling fee, the administrator information adds, modifies, deletes, and so on, in which inquires the information involves queries the administrator information and inquires the depositor's deposit and withdrawal transfer and so on information.

2. Building the object model-class diagram

-Class Diagram description

After the administrator (operator) logs in to the main operation window using the work number password, it can initiate various transactions or perform administrative operations on behalf of the depositor, and the specific variables and methods of each transaction operation are given in the class diagram. It should be pointed out that the customer has active and passive two ways, the initiative to sell households by the depositors themselves to handle the business of the household, passive sales of the customer is the loss of business after the expiry of the automatic trigger pin. In addition, query, access, transfer, payment, expenses and other transactions can be printed after the completion of the schedule, and must record the operation of the business staff number waiting to be checked.

3. Building a dynamic model

(1) Sequence diagram

I. Account Opening

-Description

The administrator (operator) enters into the Operation window to select the opening transaction, enter the account information and identity information, the system verifies the legitimacy of the account and the authenticity of the identity, requires the user to set the password, the password is set successfully completed account opening, add account information, depositors can choose to print the account voucher.

II. Sales Account

-Description

Administrator (operator) to the Master Operation window to select the user transactions, enter account information and identity information, the system verifies the legitimacy of the account and the authenticity of the identity, require depositors to enter a password, the correct password to check and process the balance, the completion of the sales account, delete accounts, depositors can choose to print the user certificate.

III. Freezing

-Description

Administrator (operator) to the Master Operation window to choose to freeze transactions, enter account information and identity information, the system to verify the legitimacy of the account and identity authenticity, require depositors to enter a password, correct password to modify the account status to complete the freeze, add frozen records, depositors can choose to print the frozen voucher.

Iv. Loss-reporting

-Description

By the administrator to enter the account information, through the Account management module to determine whether the account exists, if present, through the transaction management of the account loss.

V. Deposit

-Description

By the administrator input password to the input device, through the account management for password determination, through, the administrator can issue a deposit transaction, through the transaction management to determine the deposit amount, if the confirmation information, modify the relevant records and return to the user deposit vouchers.

VI. Withdrawals

-Description

By the administrator input password to the input device, through the account management for password determination, through, the administrator can issue a withdrawal transaction, through the transaction management to determine the balance, if the balance is sufficient, then the cash counter will be issued and returned to the user withdrawal vouchers.

VII Transfer

-Description

The administrator (operator) enters the master Operation window to select the Transfer transaction, enter the transfer information, the system calculates the fees and determine the validity of the balance, such as checking the legality, requiring depositors to enter the password, correct the password to modify the corresponding account balance and add the transfer records, depositors can choose to print the transfer record documents.

Viii. Payment

-Description

The administrator (operator) enters into the Operation window to select the payment transaction, enter the payment information, the system calculates the fees and determine the validity of the balance of the test, require depositors to enter a password, the correct password to modify the corresponding account balance and add payment records, depositors can choose to print payment details.

IX Management

-Description

Administrator login Select Management Transaction, in the Management window can choose the type of management such as query information (query administrator information, query account deposit and withdrawal transfer payment details, query account cost accounts and other records, etc.), modify the interest rate or fees, add, delete, modify administrator information and other operations.

(2) State diagram

I. Account Opening

-Description

Account to enter the status of waiting for input information, entered after entering the account status, enter the password to enter the password status, complete the account opening.

II. Sales Account

-Description

Account for the user to enter the status of waiting for input information, entered after entering the active PIN status, provide identity information into the authentication status, after successful authentication, check the balance into processing balance status, delete account information to complete the sales. Loss of seven days after the loss of automatic access to the passive PIN status, check the balance into the processing balance status, delete account information to complete the sale of the user.

III. Freezing

-Description

The account freezes into the status of waiting for input information, enters the active frozen state after entering, provides the identity information to enter the authentication status, verifies the identity information success, modifies the account status, completes the freezing. Enter the password more than three times to automatically enter the passive frozen state, modify the account status, complete the freeze.

Iv. Loss-reporting

-Description

Report loss status diagram describes the account from the initial state triggered loss of reporting transactions into the reporting status, followed by waiting for input information, and so on in turn through the waiting state and the status of the verification, the operation of the account status to the accounts into the data update status.

V. Deposit

-Description

Deposit status Diagram describes the account is triggered by the initial state of deposit transactions into the deposit status, followed by waiting for input information, and so on in turn through the waiting state and the state of verification, the operation of the account status of the accounts into the data update status.

VI. Withdrawals

-Description

The withdrawal status diagram describes the account from the initial state trigger withdrawal transactions into the withdrawal status, followed by waiting for input information, and so on wait and verify the status of verification information is legitimate, and to enter the verification state to verify the balance, after the operation of the account State to make the account into the data update status.

VII Transfer

-Description

Account transfer into the status of waiting for input information, enter the modified state after input, modify the balance of the account, then record the transfer information, complete the transfer, if the print voucher entered the print status, otherwise end.

Viii. Payment

-Description

Account payment into the status of waiting for input information, enter the modified state after input, modify the account balance, then record the payment information, complete the payment, if the printed voucher into the print state, otherwise end.

IX Management

-Description

Admin to enter the selected state of management, the administrator to choose the type of management to enter the modified state, if the change in interest rates or fees and add, delete, modify the administrator information into the modified state to modify the account balance, if the query information, then enter the status of the query, if the print voucher into the print state, otherwise end.

Second, object-oriented design 1. Architecture Module Design Diagram (1) package diagram

-Description

Program initialization, establish a database connection, generate interface window, through the database connection package and Interface window operations for transactional operations, transaction completion to generate a statement or a record sheet for the system to print, here with the use of a detailed order template package to generate a printed form.

(2) Component diagram

-Description

Graphical interface components and databases exist interfaces, administrators, accounts, transactions are dependent on the user interface to participate in activities, in addition, the account depends on the administrator to operate, the transaction is issued by the administrator, the transaction under the cash business, non-cash business, management, payment and other construction.

2. Class Diagram (1) Cash business subsystem

(2) Non-cash business subsystem

(3) Management subsystem

3. Activity Diagram I. Account

II. Sales Account

III. Freezing

Iv. Loss-reporting

V. Deposit

VI. Withdrawals

VII. Transfer

Viii. Payment

IX. Management

* * * Original All, this article prohibits all forms of unauthorized reprint, if you need to reprint the contact author, please respect the author's rights.

The UML modeling diagram above is for reference only.

------------------------------------------------------------------------------------

For the original document, please visit my personal page ycxblog download.If the link is not available, please lose www.ycxblog.com

Special thanks to co-editor Huang, Rui. You know.

------------------------------------------------------------------------------------End 2016/05/24

"Software Engineering" documentation-banking management-object-oriented analysis and design