SEG3430 Systems Analysis and Design Tutorial 9 – Data Modeling (A Case Study)

SEG 3430 Information Systems Analysis & Design

Tutorial 9 — Data Modeling
A Case Study: Credit Card Management System

Functional Requirements:

1. Applying for a credit card

• For a non-cardholder, he/she can apply for a credit card of CBSH by
providing the following information: 1. Name (30 characters); 2. Gender;
3. Nationality (20 characters); 4. Corresponding address (50 characters); 5.
Contact phone number (8 digit); 6. HKID number; 7. Current employment
(15 characters); 8. Financial statements of the past three months; and 9.
Type of credit card to apply (platinum, gold or classic).
• If the applicant is already a cardholder of the bank, CBSH must deny
his/her application. A denial letter is sent to the applicant with the reason
of denial stated in the letter.
• After successfully validating and verifying the information provided by
the applicant, CBSH will send a confirmation letter to the applicant. This
confirmation letter includes: 1. Credit card; 2. Expire date; 3. Available
date; and 4. Credit limit. If the validation and/or the verification processes
are failed, a denial letter is sent to the applicant with the reason(s) of
denial stated in the letter.
• The credit limits for platinum, gold and classic are 500000, 50000, and
15000, respectively.

2. Activating the credit card

• After the applicant received the confirmation letter sent, the applicant
must activate the credit card via telephone; otherwise, the credit card
cannot be used. The required information for activating the credit card are:
1. HKID number and 2. Credit card number (16 digits).

3. Login to the credit card account

• Any cardholder can login to his/her account via Internet by providing a
username and a password. The username is the credit card number and the
password is the HKID number. The cardholder must change this password
once he/she has login to his/her account for the first time. A password
must contain 8 characters where all of the characters must be either
alphanumeric or punctuation.

4. Checking the transaction and billing information

• After the cardholder successfully login to his/her account via Internet,
he/she can check the details of the transaction and billing information.
Specifically, the cardholder must specify a period (1 month ago, 2 months
ago and 3 months ago) and the system displays the transaction and billing
SEG3430 Systems Analysis and Design Tutorial 9 – Data Modeling (A Case Study)

information within that month. The information displays are: 1.

Transaction information; 2. Cash dollar; 3. Credit limit; 4. Date of
statement; 5. Statement balance; 6. Minimum payment; and 7. Due date.
For each transaction, the information displays are: 1. Date; 2. Name of the
merchant (50 characters); 3. Amount.

5. Modifying the personal information

• A cardholder can change the following personal information via Internet:
1. Corresponding address; 2. Contact phone number; 3. Current
employment; and 4. Whether or not to receive the paper-based monthly
statement. Note that if the cardholder declares to receive the paper-based
monthly statement, $10 service charged is debited each month from the
credit card. The paper-based monthly statement includes: 1. Personal
information (Name and corresponding address of the cardholder); 2.
Credit card number; 3. Transaction information; 4. Cash dollar; 5. Credit
limit; 6. Date of statement; 7. Statement balance; 8.Minimum payment;
and 9. Due date.

6. Returning the debt

• A cardholder can choose return the debt by auto-pay. In this case, the
cardholder must provide a valid bank account to CBSH, and the debt
would be paid at the payment due date automatically. Furthermore, the
cardholder can choose auto-pay the minimum amount or the full amount.
• The cardholder must return a minimum of 4% of the total debt on or
before the payment due date or CBSH will charge 0.05% of the total debt
plus another $100 for the late payment.
SEG3430 Systems Analysis and Design Tutorial 9 – Data Modeling (A Case Study)

ER-Model:

Data Dictionary:

Entities Fields Descriptions

Definition An applicant applies for a credit card.
Applicant
Special Notes --
Store the information of the applicants who have
Definition
applied credit cards for CBSH but are unsuccessful.
UnsuccessfulApplicant
It is used for storing the information in the database
Special Notes
temperately. It should be clean up periodically
Definition The customer of this CBSH.
Customer
Special Notes --
Definition The information of the credit card.
Card
Special Notes --
SEG3430 Systems Analysis and Design Tutorial 9 – Data Modeling (A Case Study)

Definition The information of the credit card type.

CardType
Special Notes --
Definition The information of the statement information.
Statement
Special Notes --
Definition The information of the transaction for a specific date
Transaction
Special Notes --
Definition The information of the expense, such as the merchant
Expense
Special Notes --
The information of the payment, such as the type of
Definition
Payment payment
Special Notes --
Definition The bank accounts that are used for auto pay
BankAccount
Special Notes --

Relationships Fields Descriptions

Upon successful application, an applicant is a customer,
Definiation
oherwise, he/she will belong UnsuccessfulApplicant
Applicant-Is-A Parent Entity Applicant
Child Entity (1) Customer and (2) UnsuccessfulApplicant
Special Notes --
Definiation A specific customer owns a specific credit card.
Parent Entity Customer
Owns
Child Entity Card
Special Notes --
A credit card belongs to one of the following type: Gold,
Definiation
Platinum and Classic
Belongs Parent Entity Card
Child Entity CardType
Special Notes --
The credit card contains the specific set of transaction
Definiation
record
Contains Parent Entity Card
Child Entity Transaction
Special Notes --
Definiation The credit card outputs the specific statement
Parent Entity Card
Outputs
Child Entity Statement
Special Notes --
For each transistion, it is one of the following type:
Definiation
Expense, Payment
Transaction-Is-A Parent Entity Transaction
Child Entity (1) Expense; (2) Payment
Special Notes --
If the customer declares to use auto pay for payment, then
Definiation
the card is being paid by the specific bank account.
Autopay-from Parent Entity Card
Child Entity BankAccount
Special Notes --
SEG3430 Systems Analysis and Design Tutorial 9 – Data Modeling (A Case Study)

Attributes Fields Descriptions

Definition Applicant Name
Applicant_Name
Data Type Character: {a – z | A – Z}, length: 5 – 30
Special Notes --
Definition
Applicant Sex
Applicant_Sex
Data Type Character: {M | F}
Special Notes --
Definition Applicant Nationality
Applicant_Nat Data Type Character: {a – z | A – Z}, length: 3 – 20
Special Notes --
Definition Applicant Address
Applicant_Add Data Type Character: {a – z | A – Z}, length: 10 – 50
Special Notes --
Definition Applicant contact phone
Applicant_Phone Data Type Character: {0 – 9}, length: 8
Special Notes Must begin with {2 | 3 | 6 | 8 | 9}
Definition Applicant HKID
Applicant_HKID Data Type Character: {a – z | A – Z}, length: 8 – 9
Special Notes Follow the rules of the HKID
Definition Applicant Employment
Applicant_Emp
Data Type Character: {a – z | A – Z}, length: 3 – 15
Special Notes --
Definition The reason of unsuccessful application
Unsuccess_Reason Data Type Character: {a – z | A – Z}, length: 5-50
Special Notes --
Definition The password for online access
Customer_onlinePasswd Data Type Character: {0 — 9 | a — z | A – Z}, length: 8
The default value is the Applicant_HKID in the
Special Notes
entity Applicant
Definition The card number
Card_Number Data Type Character: {0 – 9}, length: 16
Special Notes --
Definition The expire date of the card
Card_ExpireDate Data Type Date (yyyy-mm-dd)
Special Notes --
Definition The date the card available
Card_AvailableDate Data Type Date
Special Notes --
Definition Whether the card is active
Card_IsActive Data Type Boolean
Special Notes --
Definition The cash dollar the card remind
Card_CashDollar Data Type Integer
Special Notes --
Whether the card is being paid by auto pay and its
Card_autoPayOption Definition
related settings
Data Type {01 | 02 | 03}
SEG3430 Systems Analysis and Design Tutorial 9 – Data Modeling (A Case Study)

01: Autopay and pay minimum charge

Special Notes 02: Autopay and pay full charge
03: Not autopay
Definition Whether the customer willing to received paper bill
Card_IsReceivePaperBill Data Type Boolean
True if the customer declares to receive paper bill.
Special Notes
False otherwise
Definition The current debt of the credit card
Card_Debt Data Type Floating point (2 d.p.)
Special Notes --
Definition The type of credit card
Data Type {0 | 1 | 2}
CardType_Type 0: Platinum
Special Notes 1: Gold
2: Classic
Definition The limit of the corresponding type of credit card
Data Type {15000 | 50000 | 500000}
CardType_Limit 15000: Classic
Special Notes 50000: Gold
500000: Platinum
Definition The date of the financial statement
Statement_Date Data Type Date (yyyy-mm-dd)
Special Notes --
Definition The due date of the financial statement
Statement_Due Data Type Date (yyyy-mm-dd)
Special Notes --
The debt up to the date of the specific financial
Definition
statement
Statement_Debt
Data Type Floating point (2 d.p.)
Special Notes --
Definition The minimum payment
Statement_Payment Data Type Integer
Special Notes --
Definition Date of the transaction
Transaction_Date Data Type Date (yyyy-mm-dd)
Special Notes --
Definition The amount of the transaction
Transaction_Amt Data Type Float (2 d.p.)
Special Notes --
Definition Expense_CashDollar
Expense_CashDollar Data Type Integer
Special Notes --
The name of the merchant that contribute to this
Definition
expense
Expense_Merch
Data Type Character: {0 — 9 | a — z | A – Z}, length: 1 – 50
Special Notes --
The type the payment that contribute to the
Payment_Type Definition
transaction
Data Type Character: {0 — 9}, length: 2
SEG3430 Systems Analysis and Design Tutorial 9 – Data Modeling (A Case Study)

01 – Auto pay
02 – Pay by cash
Special Notes 03 – Pay by check
04 – Pay by phone
05 – Others
Definition The bank account for auto pay
BandAccount_Info Data Type Character: {0 – 9}, length: 5 – 30
Special Notes --