team tiger report - (2009 nov exam qn5)

8/8/2019 Team Tiger Report - (2009 Nov Exam Qn5)

1/28

Wee Kim Wee School of Communication and Information

Academic Year 2010/2011

Semester 1

H6675 Systems Analysis and Design

Case Study: Internet

Banking(With reference to Nov 2009 Exam question 5)

Course Coordinator: Mr Richard Xu Rong

Members:

1. Luo Wee Hiang, Sam G0803489K [email protected]

2. Selvaraj Vijayanand G0901659K [email protected]

3. Yin Marlar Myat G0901576B [email protected]

4. Yap Sheue Mui G0801656A [email protected]


2/28

i

Table of contents

1. Case Study ...................................................................................................................... 12. Login ............................................................................................................................... 2

2.1 Clarifications: Login ................................................................................................... 22.2 Use Case Diagram: Login ........................................................................................... 32.3 Use Case Description: Login....................................................................................... 32.4 System Sequence Diagram: Login .............................................................................. 52.5 Detailed Sequence Diagram: Login ............................................................................ 6

3. View Account Summary ................................................................................................. 73.1 Clarifications: View Account Summary ..................................................................... 73.2 Use Case Diagram: View Account Summary ............................................................. 73.3 Use Case Description: View Account Summary ........................................................ 73.4

System Sequence Diagram: View Account Summary .............................................. 10

3.5 Detailed Sequence Diagram: View Account Summary ............................................ 11

4. Inter Account Fund Transfer ......................................................................................... 124.1 Clarifications: Inter Account Fund Transfer ............................................................. 124.2 Use Case Diagram: Inter Account Fund Transfer ..................................................... 124.3 Use Case Description: Inter Account Fund Transfer ................................................ 124.4 System Sequence Diagram: Inter Account Fund Transfer ........................................ 164.5 Detailed Sequence Diagram: Inter Account Fund Transfer ...................................... 17

5. State Transition Diagram .............................................................................................. 185.1 States Transition ........................................................................................................ 18

6. Conclusion .................................................................................................................... 19Appendix ARequirements Description ................................................................................ 20Appendix BThe Thinking Process ....................................................................................... 23References ................................................................................................................................ 24


3/28

ii

List of Figures

Figure 1: Login Use Case Diagram ........................................................................................... 3Figure 2: Login System Sequence Diagram .............................................................................. 5Figure 3: Login Sequence Diagram ........................................................................................... 6Figure 4: View Account Summary Use Case Diagram ............................................................. 7Figure 5: View Account Summary System Sequence Diagram .............................................. 10Figure 6: View Account Summary Detailed Sequence Diagram ............................................ 11Figure 7: Inter Account Fund Transfer Use Case Diagram ..................................................... 12Figure 8: Inter Account Fund Transfer System Sequence Diagram ........................................ 16Figure 9: Inter Account Fund Transfer Detailed Sequence Diagram ...................................... 17Figure 10: Internet Banking Application State transition Diagram ......................................... 18


4/28

iii

List of Tables

Table 1: Login Use Case Narration ........................................................................................... 4Table 2: View Account Summary Use Case Narration ............................................................. 9Table 3: Inter Account Fund Transfer Use Case Narration ..................................................... 15


5/28

1

1. Case StudyJoe is a fresh graduate whom recently joined Centurion Information Systems Pte Ltd as a

System Analyst. Centurion has won a contract to develop an Internet Banking Application for

Trillion Wealth Bank a couple of months back. Joes boss, Don has just completed the

requirements gathering phase and tasked Joe to perform system analysis on the requirements

in order to derive the Use-Case Diagram, Use-Case Description, System Sequence Diagram,

Detailed Sequence Diagram and State Transition Diagram for the following Use-Cases;

Login View Account Summary Perform Inter Account Fund Transfer

Please refer to Appendix ARequirements Description Don has gathered for the above

mentioned Use-Cases.

Imagine yourself as Joe, what would you do in order to derive the above mentioned diagrams?

Being a newbie, Joe has a series of questionnaires to answer in order to deliver the product.

Please refer to Appendix BThe Thinking Process for the series of questions in Joes mind.

Armed with answers in his mind about the Process to deliver the product, Joe styled his

report in the following order for each Use-Case;

ClarificationsTo address uncertain portions Use-Case DiagramTo reflect the functions Actors may perform Use-Case NarrationDescription of the Use-Case, including System response System Sequence DiagramActor and System interactions Detailed Sequence DiagramApplication of the Model View Control methodology

for classes definition

Lastly, Joe included a single State Transition Diagram to cover all three Use-Cases and

concluded by summarizing the highlights in the adopted approach.


6/28

2

2. Login2.1 Clarifications: Login1. Logging offTrillion Wealth explained that customers can only logged off from the

respective Screens;

a. After successfully logging inb. After execution of the View Account Summaryc. After execution/cancellation of the Inter Account Fund Transferd. After execution/cancellation of the Inter Bank Fund Transfer

2. Account ManagementTrillion Wealth explained that all customers Internet BankingAccount information (such as User IDs, Passwords, Mobile Phone numbers, Security

Question and Answer) are stored in a database application already implemented by

another vendor. The Internet Banking Application to be developed by Centurion may

provide login details to the external database application which perform the first layer of

authentication. Successful authentication would return the customer Internet Banking

Account information (less Security Question and Answer) as well as CustomerID

(primary key) to the Centurion Internet Banking Application. The One Time Password

(OTP) is not necessary as Customer set his/her own password during application, OTP is

required for cases when the System auto generates the password and Customers might be

prompted to change during the first time login

3. Security TokenTrillion Wealth explained that this is the second factor authentication.Customers whose User ID and Password were stolen have to lose their Security Tokens

physically in order to expose their accounts to possible thefts. Each customer Security

Token is unique and each time the button is pressed, customer must log in within 5

minutes or the randomly generated 6 digit pin would expire. This layer of authentication

would be managed by Trillion Wealth in-house IT Department. Centurion Internet

Banking Application will need to send CustomerID and the customer entered 6 digit pin

to the in-house system for second layer of verification. Successful verification would

present the Main Screen of the Internet Banking Application to the customer.

4. Joe added that Log off, Change of password and Retrieve password Use-Cases will bemodeled at a later stage.


7/28


8/28

4

Step 7: Customer enters the pin on

displayed on his/her security token.

Customer is Log off.

Step 5: The System validates Customer

entered login details correctly.

Step 6: The System prompts Customer toenter his/her pin.

Step 8: The System verifies Customer

entered pin correctly.

Step 9: The System displays the Main

Screen.

Alternate

Courses:

Alt-Step 4: If the Customer state is locked or already logged on, notify Customer of the

unavailability.

Alt-Step 5: If Customer entered login details are invalid are the third time, change

Customer state to lock and notify Customer account is locked and to contact bank. If

Customer entered login details are invalid for less than 3 times, warn the Customer and

go to Step 2.

Alt-Step 8: If Customer entered pin is invalid are the third time, change Customer state to

lock and notify Customer account is locked and to contact bank. If Customer entered pin

is invalid for less than 3 times, warn the Customer and go to Step 6.

Conclusion: This use case concludes when the Customer views the Main Screen.

Post condition: Customer state is updated as Log on, any further attempts to log on will be denied.

Business Rules: Customer must apply and register for an Internet Banking Account beforeaccessing the application.

Customer must have the security token in possession. Customer has 3 attempts each for password verification and pin authentication

before being having his/her account locked.

Inform Customer to contact Bank if Account is locked.Implementation

Constraints and

Specifications:

Use case must be available to the Customer round the clock. Able to support up to 2000 concurrent Customers. Validation and Verification process must be completed by the System in not

more than 5 seconds.

Assumptions: Customer can log off only after successful logging in (separate use case). Customer can change or retrieve password (separate use case).

Customer can change security answer/question (separate use case). One Time Password is not necessary as the Password is set by the Customer

during registration

Open Issues: None

Table 1: Login Use Case Narration


9/28

.4 System Sequence Diagram: Login

Figure 2: Login System Sequence Diagram


10/28

.5 Detailed Sequence Diagram: Login

Figure 3: Login Sequence Diagram


11/28

7

3. View Account Summary3.1 Clarifications: View Account Summary1. All of the accounts information and details account transaction of a customer are already

stored in the database application developed by another vendor. Internet banking

application developed by Centurion just needs to retrieve customer requested information

from this database.

2. Customers accounts summary will be retrieved by means of CustomerID. For accountdetails will be retrieved by CustomerID and AccountID for one customer may have more

than one accounts.

3. For security reason, after idle time of 5 minutes, system will alert automatically whetherto drop the screen or not. If the users choice is Yes, the system will be logged out

automatically. Otherwise, the user has to log in again to view account summary.

3.2 Use Case Diagram: View Account Summary

Figure 4: View Account Summary Use Case Diagram

3.3 Use Case Description: View Account SummaryUse-Case Name: View Account Summary Use Case Type

Business Requirements:

System Analysis:

Use-Case ID: Internet Banking Use Case #2

Priority: High

Source: RequirementInternet Banking Requirement #7

Primary Business

Actor:

Trillion Wealth Bank Customer


12/28

8

Primary System

Actor:

Trillion Wealth Bank Database (External Server Actor)

Other

Participating

Actors:

None

Other InterestedStakeholders:

None

Description: This use case describes the event of a Trillion Wealth Bank Customer viewing his/her

account summary. Customer can view the summary of his/her accounts by clicking on

A/C Summary link from the Main Screen. When he/she clicks on one of the account type,

detailed transactions of previous and current month for the selected account will be

displayed.

Precondition: Customer must successfully login to the Internet Banking Application.

Trigger: This use case is initiated when Customer selects View Account Summary option from the

Main Screen.

Typical Course of

Events:

Actor Action System Response

Step 1: Customer selects View AccountSummary.

Step 4: Customer selects one of the

account to view the transactions for default

period (current and previous one month).

Step 2: System retrieves all of Customersaccounts and the accounts current balance

from the Trillion Wealth Bank Database.

Step 3: System displays all of the

Customers account and the accounts

current balance.

Step 5: System retrieves Customer selected

account and its transactions for the stated

period from the Trillion Wealth Bank

Database.

Step 6: System displays all the transactions

within the stated period for selected

account.

Alternate

Courses:

Alt-Step 4: Customer selects exit and this use case terminates.

Alt-Step 4: Customer selects one of the account and the desired period to view the

transactions within the selected period. Go to Step 5.

Alt-Step 6:System finds nil transactions within the stated period and displays Nil

transactions.

Conclusion: This use case concludes when the Customer views his/her account summary or

transactions details for the selected account.

Post condition: None

Business Rules: Customer can only view accounts under their names.Implementation

Constraints and

Specifications:

This use case is available for all Trillion Wealth Internet Banking customers24/7 where internet access is available.

For the usability purpose, web screen provided to customers must be simple sothat they can learn and use easily.


13/28

9

Assumptions: Screen idle time should be not more than 5 minutes for security purpose. If theidle time is 5 minutes, user will be asked that he wants to drop the screen or not.

If he chooses Yes, his account will be logged out automatically. Otherwise, he

will be shown the log in screen again.

The Trillion Wealth Internet Banking System provides Account Summary asone of the main categories and lets customers to access directly from the mainscreen. Other Internet Banking systems put it under Account Information

category.

Open Issues: If the screen design is complicated, novice users may face difficulty even for asimple use case.

Table 2: View Account Summary Use Case Narration


14/28

10

3.4 System Sequence Diagram: View Account Summary

Figure 5: View Account Summary System Sequence Diagram


15/28

11

3.5 Detailed Sequence Diagram: View Account Summary

Figure 6: View Account Summary Detailed Sequence Diagram


16/28

12

4. Inter Account Fund Transfer4.1 Clarifications: Inter Account Fund Transfer1. If there is any system failure, system will roll back to the last successful completed

transaction. Customer will be notified of unsuccessful transaction. This rollback will be

handled by the External Server Actor Trillion Wealth Bank Database.

2. Clicking the Refresh or Reload during a transaction session will terminate the current sessionand customer has to wait 5 minutes to be able to login again.

4.2

Use Case Diagram: Inter Account Fund Transfer

Figure 7: Inter Account Fund Transfer Use Case Diagram

4.3 Use Case Description: Inter Account Fund TransferUse-Case Name: Inter Account Fund Transfer Use Case Type

Business Requirements:

System Analysis:

Use-Case ID: Internet Banking Use Case #3

Priority: High

Source: RequirementInternet Banking Requirement #9

Primary Business

Actor

Trillion Wealth Bank Customer


17/28

13

Primary System

Actor:

Trillion Wealth Bank Database (External Server Actor)

Other

Participating

Actors:

None

Other Interested

Stakeholders:

None

Description: This use case describes the event of a customer performing an inter account fund transfer

(Fund transfer within Trillion Wealth Bank). Customer can select which account to

transfer fund out and which account to receive funds from. Customer enters the amount

for transfer and selects immediate transfer or future transfer. When the transfer is

completed, the customer will receive a SMS notification if this option is activated.

Precondition: Customer must successfully login to the Internet Banking Application.

Trigger: This use case is initiated when Customer selects Inter Account Fund Transfer option from

the Main Screen.

Typical Course of

Events:

Actor action System response

Step 1: Customer selects Inter Account

Fund Transfer.

Step 3: Customer selects from one of

his/her own account to transfer fund out.

Step 4: Customer selects from one of

his/her own account to receive funds.

Step 5: Customer enters the amount for

transfer.

Step 6: Customers selects immediate

transfer and commits selection.

Step 12: Customer confirms the selection.

Step 2: System displays Inter Account

Fund Transfer Screen.

Step 7: System checks that the amount

transferred is greater or equal than the

minimum sum ($1.00).


transferred is within the minimum

resolution ($0.01).


transferred is less than the selected account

available balance.

Step 10: System checks that the remainingbalance after transferred is greater than the

minimum balance ($20.00).

Step 11: System displays the transfer

details for customer to verify.


18/28

14

Step 13: System invokes the external

Trillion Wealth Bank Database with

Customer entered details to perform the

fund transfer transaction.

Step 14: System received the successful

transferred confirmation from the external

Trillion Wealth Bank Database.

Step 15: System informs Customer of the

successful completion of transaction.

Step 16: System send SMS notification to

the Customer if he/she opt in for the

service and that the transfer type is to other

person.

Alternate

Courses:

Alt-Step 3, 4, 5, 6, 12: Customer selects cancel and this use case terminates.

Alt-Step 6: Customer entered a postdated date. Go to Step 7.

Alt-Step 7: System checks that the amount transferred is greater or equal than the

minimum sum ($1.00) and informs the Customer. Go to Step 2.

Alt-Step 8: System checks that Customer entered a transferred amount is not within the

minimum resolution ($0.01) informs the Customer. Go to Step 2.

Alt-Step 9: System checks that the amount transferred is less than the selected account

available balance and informs Customer. Go to Step 2.

Extension Point

(Extends from

Typical Course of

Event Step 4):

Actor action System response

Ext-Step 1: Customer selects another

persons account to receive funds.

Ext-Step 3: Customer enters the receiving

account holder initials.


account type.


account number.

Go to Step 5 in Typical Course of

Events.

Ext-Step 2: System responds by prompting

for the receiving account information.

Conclusion: This use case concludes when the customer receives a transfer confirmation message.

Post condition: The right amount of fund is transferred from the selected account to the designated

account.


19/28

15

Business Rules: Funds transferred are in local currency. Customer can only transfer funds out of accounts under their names. Only 3 types of accounts that funds can be transferred outPersonal Savings,

Joint Savings and Current.

Minimum sum of $20.00 to be maintained after the transfer for Personal Savingsand Joint accounts

Current account can be $0.00 after transfer but cannot be negative. Minimum amount to be transferred is $1.00 and minimum resolution is $0.01.

Implementation

Constraints and

Specifications:

Use case must be available to the customer round the clock Validation of account numbers and verification of minimum sum must be in not

more than 5 seconds

A cancel button available to Customer before confirmation.Assumptions: Rollback capability provided by Trillion Wealth Bank Database (External Server

Actor).

Background worker in to detect the Reload/Refresh button of the browser wouldtrigger an automated logoff. The Background worker is transparent to the

Customer and therefore need not model here.

Open Issues: None

Table 3: Inter Account Fund Transfer Use Case Narration


20/28

.4 System Sequence Diagram: Inter Account Fund Transfer

Figure 8: Inter Account Fund Transfer System Sequence Diagram


21/28

.5 Detailed Sequence Diagram: Inter Account Fund Transfer

Figure 9: Inter Account Fund Transfer Detailed Sequence Diagram


22/28


23/28

19

6. ConclusionFrom this Internet Banking Application case study, the sequential application of analysis

processes and methodologies are the main takeaways in System Analysis and Design.

The processbegins with Users requirements which form the scope of the project. Analyst

should clarify all ambiguous requirements prior to analysis.

The next step is to perform analysis modelling which Analyst needs to identify role playing

actors and use cases for functional as well as non-functional requirements. The actors and use

cases are translated into Use Case diagram followed by the narration of the Use Case diagram.

From the Use Case narration, the nouns (objects) and verbs (methods) are identified and translate

into System Sequence Diagram that describes the ActorSystem interactions. The detailed

Sequence Diagram is then derived based on the Model View Control (MVC) approach whereby

the classes, methods and arguments are specified in details for implementation into codes byprogrammers.

Lastly, a consolidated State Transition diagram is derived to describe the required screens and

the navigation between them.

This case study emphasised on the importance of analysis process, applied methodologies and

techniques. Resulting output (diagrams and documentation) for one process becomes the input of

the next process and by adopting this set of sequential approach, Analysis and Design can be

applied to all developing Systems in a systematic and comprehensive manner.

Future studies

Efforts can be spend to improve on three areas; Development Scope, Time and Cost.

ScopeApply PIECES framework to ensure scope are comprehensively covered TimeAdopt the hybrid approach of the waterfall model during analysis and design CostExplore the feasibility for COTS products


24/28

20

Appendix ARequirements Description

Login

All Trillion Wealth Bank customers need to register and be issued with an Internet Bankingaccount before they can access the Internet Banking Application. During registration, customer

must provide the following;

User ID6 to 12 alphanumeric characters to represent each customer Password6 to 12 alphanumeric characters for authentication Security Question and AnswerQuestion and Answer each in string of not more than

250 characters for retrieval of password

Mobile phone number (optional)For SMS notification of Internet Banking transactions(Inter Account Fund Transfer and Inter Bank Fund Transfer only) carried out by requester.

Customer may opt out of the service

Upon registration, customer will be issued a security token whereby customer manually pressed

the button on the token to display a 6 digit pin for verification purpose during login.

Customer can access the login URL from the Banks main URL. During login, customer enters

his/her unique User ID and password for authentication. Thereafter, customer enters the 6 digit

pin generated from the security token for verification. Customer has 3 attempts for authentication

and verification after which his/her Internet Banking account would be locked. Locked accounts

can be unlocked at any branches or by phone call to Trillion Wealth Bank customer service.

Upon successful login, the main screen is displayed and customer may select options to View

Account Summary, perform Inter Account Bank Transfer and Inter Bank Account Transfer.


25/28

21

View Account Summary

Each customer may have up to 5 categories of accounts and each category may have its own

types of account;

Savings accountUp to 1 Personal Savings account & 1 Joint Savings account

Current account Credit Card accountTrillion Wealth Visa & Trillion Wealth Master Investment accountUnit Trust & Fixed Deposit Loan accountHousing loan and Car loan

Upon request, the latest account balance for each of the customer available account types would

be displayed. Customer may select each account type for detailed view (previous month and

current month transactions). If there are no transactions during this period, the term Nil

transactions would be displayed.

E.g. If Johnny has a Personal Savings account, a Joint Savings account & Trillion Wealth Visa

account; selecting the View Account Summary for him would display the 3 accounts latest

balance. Johnny selects his Trillion Wealth Visa account and the previous month as well as

current month transactions would be displayed.


26/28

22

Inter Account Fund Transfer

For Inter Account Fund Transfer within Trillion Wealth, all customers can only transfer funds

out of accounts under their names, including Joint Savings account. There are only 3 types ofaccounts that funds can be transferred out from and to certain account types only. The types of

Inter Account Fund Transfer are as follows;

Types of account: - Transfer

From Trillion Wealth To Trillion Wealth

Own accounts Others accounts

Personal Savings account - Joint Savings account- Current account- Fixed Deposit

- Personal Savings account- Joint Savings account

Joint Savings account - Personal Savings account- Current account- Fixed Deposit

- Personal Savings account- Joint Savings accountCurrent account - Personal Savings account

- Joint Savings account- Fixed Deposit

- Nil

Personal Savings account and Joint Savings account has to maintain a minimum sum of $20.00

after the transfer. There is no minimum sum to be maintained for Current account, can be $0.00

but cannot be negative. There are no charges for Internal Account Fund Transfer but the

minimum amount to be transferred is $1.00 and the minimum amount resolution is $0.01. If

customer opts in for the SMS notification, he/she would be notified of the transaction for transfer

to others account only indicating the amount transferred from/to respective account numbers.

E.g. Husband and Wife are customers of Trillion Wealth Bank and both opted for SMS

notification. Husband has $21.01 in his Personal Savings account. He transfers $1.01 to Wifes

Personal Savings account at no charges and receives a SMS notification citing:From Trillion

Wealth: Inter Account Fund Transfer - $1.01 has been transferred from Personal Savings

Account: 008-44144-0 to Personal Savings Account: 168-88188-1. Wife receives no

notification as she is not the one initiating the transaction.


27/28

23

Appendix BThe Thinking Process

Below are a series of questionnaires Joe must find out;

1. Clarification of RequirementsWere the requirements clear, concise, complete andunambiguous? The set of Requirements would become the baseline for software testing

which in turn determine the results of the final implementation.

2. Identify the actorsWho are the role players here? What are the external Systems thatrequired interfacing were already in place? Can generalization of the actors take place here?

The actors are outside the System boundaries which are already implemented.

3. Identify the Use-CasesThe 4 Use-Cases were already identified here. Joe must ask himselfwhat are the scale of these Use-Cases? Are there too large to be implemented? Can the Use-

Cases be further broken down? Any missing Use-Cases?

4. Draw the Use-Case DiagramsWhat are the relationships between the Use-Cases? Anyinclude, extend or dependencies? What about the relationships (association or initiates) to the

actors?

5. Describe the Use-CasesNarrate the Use-Case Diagrams in Users perspective. This enablesUsers to envision how the System would be used even before its implementation. Do the

descriptions lead to the fulfillment of the requirements? What are the scenarios (alternate

flows) in the Use-Cases?

6. Draw the Sequence DiagramsThis is done using the Use-Cases description. The sequencediagrams describe the process flows and interactions among the entities. What are the data,control and boundary entities? What are the persistence data of the entities? What should be

the logical sequence of the interactions? What are the arguments in the interactions? Through

the design of this diagram; Joe slowly realized the structure of his coding. The entities will

become Classes and their persistence data become the Attributes. The set of interactions will

lead to Methods and the arguments become the Parameters inside.

7. Draw the State Transition DiagramWhat are the available screens in the Internet BankingApplication? What are the conditions for these screens to be realized and how does the

transition occurred? How should the System react to each state?

8. Repeat Step 1 through 7Go back to requirements to ensure all are covered. Are they anymissing/broken links? Keep refining the Use-Cases.


28/28

24

References

1. Bentley and Whitten, Systems Analysis & Design for the Global Enterprise (7thedition),McGraw-Hill International Edition, New York, 2008.

team tiger report - (2009 nov exam qn5)

Documents