102597789 8 credit card system ooad

7/28/2019 102597789 8 Credit Card System OOAD

1/29

Ex.No : Date :

CREDIT CARD PROCESSING SYSTEM

PROBLEM STATEMENT:Stage 1.) Credit card processing starts the moment the credit card is keyed intothe processing terminal. Stage 2.) The movement of funds begins when the customer gives the merchant their credit/debit information. Initially the funds are authorized but are not placed into the merchants account until the end of the day.Funds are moved between the customers bank and then to the merchants bank that does the processing. Stage 3.) The authorization in Stage 2 occurs after the customers information, i.e. name, account number, is sent to the merchants processing bank by the debit/credit card companies who are: Visa, Master Card, Discover and American Express. These gateways handle the process for using these cards. Stage 4.) The merchant decides if they want to handle American Express and Discover; allof American Expresses and Discovers applications, are handled by them individually which entails banking relationships with merchants etc., The companies issuestheir own cards, processing set-up and all systems related to the transaction(s) is developed and managed by them. Stage 5.) The merchant decides if they wantto handle Visa and Master Card, it is then automatically set up when the merchant decides that they want to accept these cards. Stage 6.) Transactions initiatedat the merchants terminal have all the customers information and are handled by an 800 number or by the internet to the bank that handles the processing for themerchant. Stage 7.) At the moment of transaction the merchant knows within a min

ute of it if it has been accepted or declined. Before midnight, on the day of the transaction, all transactions are placed together orbatched. The merchant, by this batching has to pay a batch fee. Stage 8.) The funds arrive in the merchants account no later than 48 hours of the initial transaction. More often it occurs within 24 hours.


2/29

USECASE DIAGRAM:

MAIN USE CASE DIAGRAM:


3/29

EXTENDED USE CASE DIAGRAM:


4/29

Credit Card Processing System

Version:1.0 Date:17/02/11

Credit Card Processing System Use Case Specification: Submit OrderVersion 1.0

Revision HistoryDate 17/02/11 Version 1.0 Description Abstract for submitting the order Author Credit card

Confidential

Credit card, 2011


5/29



Table of Contents1.

Submit Order1.1 Brief Description

1 1 1 1 1

2.

Flow of Events 2.1 2.2 Basic Flow Alternative Flows

3.

Special Requirements

1

4.

Preconditions

1

5.

Post Conditions 5.1 5.2 Successful Condition Failure Condition

1

1 1

6.

Extension Points

Confidential

Credit card, 2011


6/29



Use Case Specification:Submit OrderSubmit Order1.1 Brief Description This use case specifies about how the customer submits theorder to merchant site.

2.2.1

Flow of EventsBasic Flow1. This use case begins with the customer logging into his account with the username and password.

2. Once the login is successful the user is navigated to home page. 3. Customercan browse the products that he to purchase. 4. The system checks for availability of products. 5. If the products are available, customer selects the productsthat he wants to purchase. 6. After the product is selected the system displaysinformation about each product. 7. Then the order is submitted and validated, the system notifies the customer with success message. 8. Thus this use case endssuccessfully. 2.2 Alternative Flow: If in step 2 of the basic flow of submit ord

er the user does not login successfully, then the use case ends with failure condition. If the order is invalid then also the use case fails.

3.

Special Requirementso The system should have to maintain the customer records.

o

The system should have to response the customer quickly.

4.

Precondition The user should have logged if he is an existing user. In the case of new user,a user account has to be created for further access to information.

5.5.1

Post ConditionSuccessful Condition An unique order number is generated by the system each timean order is submitted by the customer. Failure Condition The user should be notified if there was any problem in submitting order.

5.2

6.

Extension PointsNone.

Confidential

Credit card, 2011


7/29

1


8/29

Credit Card Processing System Use Case Specification: Transfer Fund


Credit Card Processing System Use Case Specification: Transfer FundVersion 1.0

Revision HistoryDate 17/02/11 Version 1.0 Description Abstract for validating the card Author Credit card

Confidential

CreditCard, 2011


9/29

Credit Card Processing System Use Case Specification: Transfer Fund


Table of Contents1. Transfer Fund 1.1 2. Brief Description 1 1 1 1 1 1 1 1


3. 4. 5.

Special Requirements Preconditions Post Conditions 5.1 Successful Condition 5.2Failure Condition

6. Extension Points Error! Bookmark not defined.

Confidential

CreditCard, 2011


10/29


11/29



Use Case Specification: Validate CardVersion 1.0

Revision HistoryDate 17/02/11 Version 1.0 Description Abstract for validating the card Author Credit card

Confidential

Credit card, 2011


12/29



Table of Contents1.Validte Card 1.1 2. Brief Description 1 1 1 1 1


3.

Special Requirements

1

4.

Preconditions

1

5.

Post Conditions 5.1 5.2 Successful Condition Failure Condition

1

1 1

6.

Extension Points

Confidential

Credit card, 2011


13/29



Use Case Specification: Validate CardValidate Card1.1 Brief Description In this use case customer details are verified by the credit card issuer and then it validates the card deponding upon the available details.

2.2.1

Flow of EventsBasic Flow

1. Customer presents a card to pay for products. 2. Merchant processes the cardand transaction information and gives requests to merchant bank for authorization. 3. Merchant gives the request to credit card network. 4. Credit card networkpasses that request to card issuer. 5. The card issuer issuer approves/declinesthe request. 6. Credit card network forward the card issuer response to the merchant bank. 7. Merchant bank forward that response to merchant. Deponding on theresponse merchant does the transaction. 2.2 Alternative Flow: If in step 5 of the basic flow of validate card fails then the card is invalid. Then the use case

ends with failure condition.

3.

Special RequirementsThe system should contain the updated details of the customer.

The speed of the system should be fast.

4. 5.5.1 5.2

Precondition

The Customers need to have credit card.

Post ConditionSuccessful Condition Amount gets transferred from customer account to merchant account. Failure Condition The customer should be notified of unsuccessful transactions

6.

Extension PointsNone.

Confidential

Credit card, 2011

1


14/29

ACTIVITY DIAGRAMS:SUBMIT ORDER

VALIDATE CARD


15/29

TRANSFER FUNDS

DELIVER PRODUCT


16/29

CLASS DIAGRAMS:

SUBMIT ORDER

VALIDATE CARD


17/29

TRANSFER FUNDS

DELIVER PRODUCT


18/29

INTEGRATED CLASS DIAGRAM:

SEQUENCE DIAGRAMS:SUBMIT ORDER:


19/29

VALIDATE CARD:

TRANSFER FUNDS:


20/29

DELIVER PODUCT:

COMMUNICATION DIAGRAM:SUBMIT ORDER:


21/29

VALIDATE CARD:

TRANSFER FUNDS:


22/29

DELIVER PRODUCT:

STATE CHART DIAGRAM:SUBMIT ORDER:


23/29

DELIVER PRODUCT:

LOGIN:

PACKAGE DIAGRAM:


24/29

COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:


25/29

IMPLEMENTATION & TESTING:Submitui.java package submitorder; import java.io.*; import javax.swing.*; import java.awt.*; import java.awt.event.*; public class submitui{ Frame fr; GridLayout gr; JTextField name,address,pincode,phone_no,p_id,card_no,PIN_no; Label nme,add,pcode,pn,pid,cardno,PINno; Button bt;

public void displayform() { JFrame fr=new JFrame("Submit Order"); fr.setSize(400,400); gr=new GridLayout(10,2); name=new JTextField(20); address=new JTextField(20); pincode=new JTextField(20); phone_no=new JTextField(20); p_id=new JTextField(20); card_no=new JTextField(20); PIN_no=new JTextField(20); nme=new Label("Enter name"); add=new Label("Enter address"); pcode=new Label("Enter pincode"); pn=new Label("Enter phone number"); pid=new Label("Enter Product id"); cardno=new Label("Enter card number"); PINno=new Label("Enter PIN number"); bt=new Button("Submit");

//bt.addActionListener(); bt.addActionListener(new MyAction());


26/29

fr.setLayout(gr); fr.add(nme); fr.add(name); fr.add(add); fr.add(address); fr.add(pcode); fr.add(pincode); fr.add(pn); fr.add(phone_no); fr.add(pid); fr.add(p_id); fr.add(cardno); fr.add(card_no); fr.add(PINno); fr.add(PIN_no); fr.add(bt);fr.setVisible(true); fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE); } publicvoid notifySubmitFailure() { JFrame frame=new JFrame("Registration fails"); op=new Label("Registration Fails - Check All the Fields adn enter Properly"); frame.add(op); frame.setSize(500,400); frame.setVisible(true); frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);

} public void notifySubmitSuccess() { JFrame frame=new JFrame("Registration Success"); op=new Label("Registraion sucess"); frame.add(op); frame.setSize(400,400); frame.setVisible(true); frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);}


27/29

public class MyAction implements ActionListener{ public void actionPerformed(ActionEvent e) { String s1=name.getText(); String s2=address.getText(); String s3=pincode.getText(); String s4=phone_no.getText(); String s5=p_id.getText(); Strings6=card_no.getText(); String s7=PIN_no.getText(); if(s1.equals("")||s2.equals("")||s3.equals("")||s4.equals("")||s5.equals("")||s6.equals("")||s7.equals(" "))notifySubmitFailure(); else notifySubmitSuccess(); } } public static void main(String args[]) { submitui a=new submitui(); a.displayform(); }} SAMPLE OUTPUT:


28/29

RESULT:Thus the UML model for Credit Card Processing System has been designed and implemented successfully using Rational Software Architect.


29/29

102597789 8 credit card system ooad

Documents