credit card processing

CREDIT CARD PROCESSING

OBJECTIVE

To study and develop a Credit Card Processing by using object oriented software

development

PROBLEM STATEMENT

Filling application form

Proof verification

Credit limit calculation

Card replacement

Credit card renewal

Purchase through credit card

Payment

Credit card monthly statement ( fine if any + purchase details )

ACTORS

Card holder

Card issuer

Verifier

SRS

TABLE OF CONTENTS:

1.Introduction

1.1 Purpose

1.2 Scope

1.3 Document overview

2. General description

2.1 System environment

2.2 User characteristics

2.3 Non functional requirements

2.3.1 Product requirements

2.3.2 Organizational requirements

2.3.3 External requirements

3. Specific requirements

3.1 Functional requirements

3.2 Use cases

3.2.1 Apply for credit card

3.2.2 Verify proof

3.2.3 Calculate credit limit

3.2.4 Issue credit card

3.2.5 Replace credit card

3.2.6 Renew credit card

3.2.7 Purchase through card

3.2.8 Pay for credit usage

3.2.9 Produce monthly statement

3.3 External interface specification

1. INTRODUCTION

1.1 PURPOSE:

Credit card processing software is used to manage credit card details of a bank. This

includes the sequence of phases involved in the creation of a credit card and the usage details

of the card owned by the bank’s customers.

1.2 SCOPE:

Credit card processing is used in banks all over the world to process their respective

credit cards. The simplicity under the use of credit cards has engrossed a mass of people into

using them bringing a great deal of profit to the bank organizations.

1.3 DOCUMENT OVERVIEW:

This document of software requirement specification contains the functional

requirements, use case identification and the non-functional requirements. The non-functional

requirements would be focussed at a greater detail in a business based development

environment.

2. GENERAL DESCRIPTION

2.1 SYSTEM ENVIROMNENT:

The system composes of a central server for a bank through which the bank itself and

the internet server for credit cards is connected. The credit card purchase is done over the

internet.

2.2 USER CHARACTERISTICS:

The actors associated with the system and their descriptions are as follows :

Card Holder: This is the owner of a credit card. This is a primary actor. The card

holder is the only ine who can purchase through his/her card.

Verifier: This is a supporting actor who verifies the details given by an applicant.

Card Issuer: This is a primary actor whose duty is to issue, renew and replace credit

cards.

2.3 NON-FUNCTIONAL REQUIREMENTS

The following are the requirements that focus on the overall quality of the software.

2.3.1 PRODUCT REQUIREMENTS:

Usability: The product should be simple enough to be operated by the actors

concerned.

Efficiency: The product should occupy the least possible memory space and provide

greater performance.

Reliability: The database must not be corrupted in case of power failure or any

malfunctioning of the underlying system.

2.3.2 ORGANIZATIONAL REQUIREMENTS

Deliverability: The deliverable product must include the database pack necessary to

handle the software along with the software itself.

Implementation: The product should be safe to use and should not be easily

subjected to hacking.

2.3.3 EXTERNAL REQUIREMENTS

Interoperability: This product must include the database pack necessary to handle

the software along with the software itself.

Implementation: The product should be safe to use and should not be easily

subjected to hacking.

3. SPECIFIC REQUIREMENTS

3.1 FUNCTIONAL REQUIREMENTS

The following are the requirements necessary for the system to function for its purpose.

There must be database to store the details of credit cards along with the details.

There must be a way in which an applicant can produce his/her details to the bank to

apply for a credit card.

The details given by the applicant should be put through verification.

Applications that pass the police verification should be put for processing.

The statuses of the credit card phases must be indicated.

The fully processed credit card must be issued to the applicant.

The credit card details must be maintained even after issue.

The credit cards that are obsolete must be put through for renewal.

3.2 USE CASES

The use cases underlined in this stage are as follows:

Apply for credit card

Verify proof

Calculate credit card

Issue credit card

Replace credit card

Renew credit card

Purchase through card

Pay for credit usage

Produce monthly statement

3.2.1 APPLY FOR CREDIT CARD:

An applicant applies for his/her credit card by giving his/her details necessary for the

credit card ownership.

3.2.2 VERIFY PROOF:

The details given in the apply for credit card use case is put through verification. Only

the applications that pass this phase can proceed further phases in the credit card processing.

3.2.3 CALCULATE CREDIT LIMIT:

The card issuer sets the credit limit of the credit card before issuing to the card holder.

3.2.4 ISSUE CREDIT CARD:

After the credit card is fully processed, it is printed and is ready to be issued by the

card issuer to the card holder who applied for it.

3.2.5 REPLACE CREDIT CARD:

If a credit card is lost or stolen, its card holder can replace the card by requesting the

card issuer. The current card is deactivated first and a new credit is created and issued to the

card holder with the credit card number as the only difference.

3.2.6 RENEW CREDIT CARD:

The credit card becomes obsolete after a specified time after which the card holder

must renew the credit card if he/she wishes to further use it. This must again pass through

verification.

3.2.7 PURCHASE THROUGH CARD:

The card holder can purchase using his/her credit card in online shopping or a credit

card.

3.2.8 PAY FOR CREDIT USAGE

Based on the monthly statement the card holder should pay the bank for the purchase

done with the card, delayed payment would add on to the fine in the monthly statement.

3.2.9 PRODUCE MONTHLY STATEMENT

At the end of every month statement is produced for each card the bill would be the

purchase details along with fine plus tax.

3.3 EXTERNAL INTERFACE SPECIFICATION

The following are the program interfaces that are going to be running:

An applicant program at an application counter.

A card issuer program

A verifier program

All programs are planned to be implemented under VC++ language as a front end interface

and with oracle as the back end database.

RISK MANAGEMENT

1. RISK IDENTIFICATION:

1. Authenticity problem.

2. Updation problem.

3. Data coherency risk.

2. RISK ANALYSIS:

Authenticity problem: Wrong details given by the applicant which may be more

convincing.

Updation problem: The problem with renewal is that you can have a separate thread

to check the renewal status of all entries int the database.

Data coherency risk: The entered data may be inadvertently modified in the phase

transitions.

3. RISK PLANNIG AND AVOIDANCE:

A stricter verification is required to overcome the authenticity problem.

The applicant is given the duty to renew his/her credit card on the renewal date.

A relational database can be used to mitigate the inadvertent data modification.

4. RISK MONITORING:

The practise of unauthenticated detail submission can be stated as a punishable

offence by international law.

The credit card renewal date must always be noted by the verifiers before its use.

The database should be compared before and after a phase transaction.

USE CASE DIAGRAM

AIM:

To identify the business activities and develop an UML use case diagram.

PROCEDURE:

In the Project Explorer view, expand the Analysis Model.

Right-click on the Model

Select Add Diagram > Usecase Diagram.

Name the use cases and actors.

The usecase diagram opens in the Diagram editor.

RESULT:

Thus the use cases are identified and the use case model diagram is successfully

drawn for the Credit Card Processing System.

UML ACTIVIY DIAGRAM

AIM:

To identify the business activities and develop an UML activity diagram.

PROCEDURE:

In the Project Explorer view, expand the Analysis Model.

Right-click on the Model

Select Add Diagram > Activity Diagram.

Name the activity and draw the diagram for the desired use case

The activity diagram opens in the Diagram editor.

UML ACTIVITY DIAGRAM

1.REGISTER

2.LOGIN

3.PURCHASE

4.PAYMENT

5.ENTRY

RESULT:

Thus the UML activity diagram is successfully drawn for the Credit Card Processing

system.

UML CLASS DIAGRAM

AIM:

To identify the conceptual classes and to develop a Design model with UML class

diagram for Credit Card Processing system..

PROCEDURE:

In Rational software Architect’s Model project explorer view, right-click on

the Model and creates an UML Model, A dialog box appears in that select

Design model and click finish, an UML Design Model will be created.

In Rational software Architect’s Model Explorer view, right click on the

Created UML Design model and select Add Diagram → Class Diagram as

shown below.

Enter Class diagram as the name of the generated diagram to replace the

default name Class diagram1.

Select class in the Palette, then click anywhere in the diagram to create a class

and Name it.

Identify the conceptual classes and give the associated attribute name and

method name for the identified class.

Similarly, create another class and give attributes and method.

Select Association in the Palette.

Draw the association relationship line from one class diagram to another class

diagram Add an entry to initiate a relationship between the two model

elements.

Select ctrl-s to save the program.

CLASS DIAGRAM

RESULT:

Thus the UML class diagram is successfully drawn for the Credit Card Processing

system.

UML INTERACTION DIAGRAM

AIM:

To find the interaction between objects using the scenarios identified for Credit Card

Processing and represent them using UML interaction diagram.

PROCEDURE:

In Rational software Architect’s Model Explorer view, right click on the

Created UML Design model and select Add Diagram → Sequence Diagram

as shown below.

Select the lifeline in the Palette, then click anywhere in the diagram to create a

class.

Identify the object and give the object name.

Similarly, create another object and find the associative message between the

two objects.

The message can be synchronous or asynchronous message.

Draw the relationship line from one object to another object.

UML INTERACTION DIAGRAM

1.REGISTER

2.LOGIN

3.PURCHASE

4.ENTRY

5.PAYMENT

RESULT:

Thus the UML interaction diagram is successfully drawn for the Credit Card

Processing system.

UML STATE MACHINE DIAGRAM

AIM:

To identify the different states in the Credit Card Processing system and to represent

them using a UML State Machine Diagram.

PROCEDURE:

In Rational Software Architect's Project Explorer view, right-click Created UML

Design Model and select Add Diagram > State Machine Diagram.

Enter State diagram as the name of the generated diagram to replace the default name

StateMachineDiagram1.

STATE MACHINE DIAGRAM

RESULT:

Thus the state machine diagram for the mini project Credit Card Processing is drawn

successfully.

UML PACKAGE DIAGRAM

AIM:

To identify and represent the various packages involved in the Credit Card Processing

system using a UML Package Diagram.

PROCEDURE:

In Rational Software Architect's Model Explorer view, right-click Created UML

Design Model and select Add Diagram > Class Diagram as shown below.

Select Package in the Palette, then click anywhere in the diagram to create a Package

diagram and Name it.

PACKAGE DIAGRAM

RESULT:

Thus the package diagram for our project Credit Card Processing is drawn

successfully.

IMPLEMENTATION OF DOMAIN OBJECTS LAYER

AIM:

To implement the Domain objects Layer defined for the Credit Card Processing

system.

PROCEDURE:

FORWARD ENGINEER (from UML to JAVA code):

1. Select all the class Diagram. Go to File → New project.

2. Select Java project and give next.

3. Give “project name(eg javaconference)” → next → Finish.

4. Give “NO” for open this perspective now.

5. Select the project name (eg: javaconference) →Go to the Modelling Menu→

transform → new configuration.

6. Give Name( eg : conference file) → select UML to java v 5.0→ next →select the

source (select all the class diagram from design model) and target file

(javaconference).

7. In Selected source Go to →Models → Design model → select all the class name.

8. Give Next → Disable Getters and setters→ next →next → Finish.

9. Go to the file name given in step :6, Right click on the name → go to transform →

UML to java.

10. Coding is available in default Package inside the project name.

JAVA CODE:

AUTHENTICATION SERVICE

/**

*

*/

/**

* @author 29jecs58

* @generated "UML to Java V5.0

(com.ibm.xtools.transform.uml2.java5.internal.UML2JavaTransform)"

*/

public class authenticationservice {

/**



*/

private String username;

/**



*/

private String email_ID;

/**



*/

private String password;

/**



*/

private String report;

/**



*/

private String reprtname;

/**



*/

private guest guest;

/**



*/

private customer class1;

/**



*/

public void register() {

// begin-user-code

// TODO Auto-generated method stub

// end-user-code

}

/**



*/

public void login() {

// begin-user-code


// end-user-code

}

/**



*/

public void entry() {

// begin-user-code


// end-user-code

}

/**



*/

public void validate() {

// begin-user-code


// end-user-code

}

/**



*/

public void checkaccount() {

// begin-user-code


// end-user-code

}

/**



*/

public void transaction() {

// begin-user-code


// end-user-code

}

/**



*/

public void reportbank() {

// begin-user-code


// end-user-code

}

}

CREDIT PAYMENT SERVICE

/**

*

*/

/**

* @author 29jecs58



*/

public class creditpaymentservice {

/**



*/

private Integer pinno;

/**



*/

private Integer pwd;

/**



*/

private Integer transactpwd;

/**



*/

private customer customer;

/**



*/

public void checkaccount() {

// begin-user-code


// end-user-code

}

/**



*/

public void pinnum() {

// begin-user-code


// end-user-code

}

/**



*/

public void password() {

// begin-user-code


// end-user-code

}

}

CUSTOMER

/**

*

*/

/**

* @author 29jecs58



*/

public class customer {

/**



*/

private authenticationservice authenticationservice;

/**



*/

private String emailid;

/**



*/

private String pwd;

/**



*/

private String products;

/**



*/

private Integer pinnum;

/**



*/

private Integer transpwd;

/**



*/

private Integer passwd;

/**



*/

private identityprovider identityprovider;

/**



*/

private creditpaymentservice creditpaymentservice;

/**



*/

public void login() {

// begin-user-code


// end-user-code

}

/**



*/

public void makepurchase() {

// begin-user-code


// end-user-code

}

/**



*/

public void viewproducts() {

// begin-user-code


// end-user-code

}

/**



*/

public void selectproducts() {

// begin-user-code


// end-user-code

}

/**



*/

public void payment() {

// begin-user-code


// end-user-code

}

/**



*/

public void pinno() {

// begin-user-code


// end-user-code

}

/**



*/

public void paswd() {

// begin-user-code


// end-user-code

}

}

IDENTITY PROVIDER

/**

*

*/

/**

* @author 29jecs58



*/

public class identityprovider {

/**



*/

private String product;

/**



*/

private customer customer;

/**



*/

public void showproducts() {

// begin-user-code


// end-user-code

}}

GUEST

/**

*

*/

/**

* @author 29jecs58



*/

public class guest {

/**



*/

private String username;

/**



*/

private String emailid;

/**



*/

private String pwd;

/**



*/

private authenticationservice authenticationservice;

/**



*/

public void register() {

// begin-user-code


// end-user-code

}}

RESULT:

Thus the java code is generated from class diagram of Credit Card Processing

IMPLEMENTATION OF USER INTERFACE LAYER

AIM:

To implement the User Interface Layer defined for the Credit Card Processing system.

PROCEDURE:

1. Select projectname (e.g javaconference)→Rightclick on the project name→

new →other→Java→ Visual class.

2. Give Next →Give Name(eg UILayer) → select style →swing → Frame →

enable public static void main as shown below → finish.

3. The UI layers .java tab will be opened with the JF Frame .

4. Right click on the JF Frame select as set layout → Null.

5. From the created JFrame select the palette which is present in the side of the

JFrame. From that palette you can draw Menu Bar, Menus, Menu Item,

Buttons, etc…

6. Change to open perspective (java) → go run button →run as → java

application.

1.LOGIN

import javax.swing.SwingUtilities;

import java.awt.BorderLayout;

import javax.swing.JPanel;

import javax.swing.JFrame;

import javax.swing.JTextArea;

import java.awt.Rectangle;

import javax.swing.JTextField;

import javax.swing.JLabel;

import javax.swing.JPasswordField;

import javax.swing.JButton;

public class uil extends JFrame {

private static final long serialVersionUID = 1L;

private JPanel jContentPane = null;

private JLabel Email_ID = null;

private JTextField jTextField = null;

private JLabel jLabel = null;

private JPasswordField jPasswordField = null;

private JButton jButton = null;

/**

* This method initializes jTextField

*

* @return javax.swing.JTextField

*/

private JTextField getJTextField() {

if (jTextField == null) {

jTextField = new JTextField();

jTextField.setBounds(new Rectangle(98, 27, 132, 20));

jTextField.setText("[email protected]");

}

return jTextField;

}

/**

* This method initializes jPasswordField

*

* @return javax.swing.JPasswordField

*/

private JPasswordField getJPasswordField() {

if (jPasswordField == null) {

jPasswordField = new JPasswordField();

jPasswordField.setBounds(new Rectangle(94, 58, 136, 20));

jPasswordField.setText("creditcard");

}

return jPasswordField;

}

/**

* This method initializes jButton

*

* @return javax.swing.JButton

*/

private JButton getJButton() {

if (jButton == null) {

jButton = new JButton();

jButton.setBounds(new Rectangle(82, 111, 96, 25));

jButton.setText("Login");

}

return jButton;

}

/**

* @param args

*/

public static void main(String[] args) {


SwingUtilities.invokeLater(new Runnable() {

public void run() {

uil thisClass = new uil();

thisClass.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);

thisClass.setVisible(true);

}

});

}

/**

* This is the default constructor

*/

public uil() {

super();

initialize();

}

/**

* This method initializes this

*

* @return void

*/

private void initialize() {

this.setSize(300, 200);

this.setContentPane(getJContentPane());

this.setTitle("Login");

}

/**

* This method initializes jContentPane

*

* @return javax.swing.JPanel

*/

private JPanel getJContentPane() {

if (jContentPane == null) {

jLabel = new JLabel();

jLabel.setBounds(new Rectangle(22, 62, 65, 16));

jLabel.setText("Password");

Email_ID = new JLabel();

Email_ID.setBounds(new Rectangle(20, 28, 66, 16));

Email_ID.setText("Email_ID");

jContentPane = new JPanel();

jContentPane.setLayout(null);

jContentPane.add(Email_ID, null);

jContentPane.add(getJTextField(), null);

jContentPane.add(jLabel, null);

jContentPane.add(getJPasswordField(), null);

jContentPane.add(getJButton(), null);

}

return jContentPane;

}

} // @jve:decl-index=0:visual-constraint="48,41"

2.REGISTER









import java.awt.Dimension;


public class uil2 extends JFrame {





private JLabel jLabel1 = null;

private JTextField jTextField1 = null;



private JPasswordField jPasswordField1 = null;



private JButton jButton1 = null;

/**


*


*/





jTextField.setText("Siddharth");

}

return jTextField;

}

/**

* This method initializes jTextField1

*


*/

private JTextField getJTextField1() {

if (jTextField1 == null) {

jTextField1 = new JTextField();

jTextField1.setBounds(new Rectangle(109, 67, 148, 20));

jTextField1.setText("[email protected]");

}

return jTextField1;

}

/**


*


*/






}


}

/**

* This method initializes jPasswordField1

*


*/

private JPasswordField getJPasswordField1() {

if (jPasswordField1 == null) {

jPasswordField1 = new JPasswordField();

jPasswordField1.setBounds(new Rectangle(111, 128, 86, 20));

jPasswordField1.setText("creditcard");

}

return jPasswordField1;

}

/**


*


*/





jButton.setText("submit");

}

return jButton;

}

/**

* This method initializes jButton1

*


*/

private JButton getJButton1() {

if (jButton1 == null) {

jButton1 = new JButton();

jButton1.setBounds(new Rectangle(131, 172, 68, 18));

jButton1.setText("reset");

}

return jButton1;

}

/**

* @param args

*/




public void run() {

uil2 thisClass = new uil2();



}

});

}

/**


*/

public uil2() {

super();

initialize();

}

/**


*

* @return void

*/




this.setTitle("JFrame");

}

/**


*


*/



jLabel3 = new JLabel();

jLabel3.setBounds(new Rectangle(29, 129, 72, 16));

jLabel3.setText("confirm pwd");



jLabel2.setText("Pwd");



jLabel1.setText("Email_ID");



jLabel.setText("Name");





jContentPane.add(jLabel1, null);

jContentPane.add(getJTextField1(), null);



jContentPane.add(getJPasswordField1(), null);



jContentPane.add(getJButton1(), null);

}


}


3.PURCHASE







import javax.swing.JRadioButton;



public class juj extends JFrame {






private JRadioButton jRadioButton = null;

private JRadioButton jRadioButton1 = null;






/**

* This method initializes jRadioButton

*

* @return javax.swing.JRadioButton

*/

private JRadioButton getJRadioButton() {

if (jRadioButton == null) {

jRadioButton = new JRadioButton();

jRadioButton.setBounds(new Rectangle(13, 75, 115, 21));

jRadioButton.setText("Samsung");

}

return jRadioButton;

}

/**

* This method initializes jRadioButton1

*


*/

private JRadioButton getJRadioButton1() {

if (jRadioButton1 == null) {

jRadioButton1 = new JRadioButton();

jRadioButton1.setBounds(new Rectangle(187, 72, 88, 21));

jRadioButton1.setText("Nokia");

}

return jRadioButton1;

}

/**


*


*/





jRadioButton2.setText("Sony");

}


}

/**


*


*/





jRadioButton3.setText("LG");

}


}

/**


*


*/





jRadioButton4.setText("Ericsson");

}


}

/**


*


*/





jRadioButton5.setText("Motorola");

}


}

/**


*


*/





jButton.setText("Purchase");

}

return jButton;

}

/**

* @param args

*/




public void run() {

juj thisClass = new juj();



}

});

}

/**


*/

public juj() {

super();

initialize();

}

/**


*

* @return void

*/




this.setTitle("Purchase");

}

/**


*


*/





jLabel2.setText("Mobile");



jLabel1.setText("Tv");



jLabel.setText("Select the product");






jContentPane.add(getJRadioButton(), null);

jContentPane.add(getJRadioButton1(), null);






}


}


4.PAYMENT











public class amm extends JFrame {








private JPasswordField jPasswordField1 = null;


/**


*


*/





jTextField.setText("01007064");

}

return jTextField;

}

/**


*


*/






}


}

/**

* This method initializes jPasswordField1

*


*/

private JPasswordField getJPasswordField1() {

if (jPasswordField1 == null) {

jPasswordField1 = new JPasswordField();

jPasswordField1.setBounds(new Rectangle(152, 106, 94, 20));

jPasswordField1.setText("creditcards");

}

return jPasswordField1;

}

/**


*


*/





jButton.setText("submit");

}

return jButton;

}

/**

* @param args

*/




public void run() {

amm thisClass = new amm();



}

});

}

/**


*/

public amm() {

super();

initialize();

}

/**


*

* @return void

*/




this.setTitle("Payment");

}

/**


*


*/





jLabel2.setText("TXN Password");



jLabel1.setText("Password");



jLabel.setText("Pin_no");








jContentPane.add(getJPasswordField1(), null);


}


}


RESULT:

Thus the user interface layers for Credit Card Processing is drawn

successfully.

UML COMPONENT DIAGRAM

AIM:

To identify the different components present in the Credit Card Processing system and

design an UML Component diagram.

PROCEDURE:


Design Model and select Add Diagram > Component Diagram as shown below.

COMPONENT DIAGRAM

RESULT:

Thus the component diagram for the project Credit Card Processing is drawn

successfully.

UML DEPLOYMENT DIAGRAM

AIM:

To illustrate the deployment of the Credit Card Processing system using UML

Component diagram.

PROCEDURE:


Design Model and select Add Diagram > Deployment Diagram as shown below.

DEPLOYMENT DIAGRAM

RESULT:

Thus the deployment diagram for the project Credit Card Processing is drawn

successfully.

credit card processing

Documents

credit card issue credit

credit card details

credit card purchase

hisher credit card

credit card phases

processed credit card

credit card ownership

hisher card