Code-magic IBM FINAL

Code-magic | 2012 1

M-banking. Version : 1.0 Code-magic. Date : 25-01-2012

Team Name/State Name Code-magic/Madhya Pradesh

Code-magic

M-banking.

Synopsis Requirement Specifications

Version:1.0.

Team Name : Code-magic

College Name : Thakral College of Technology Bhopal

Team Guide : Mukesh Batre

Team members : Shubham Pachori

Tanmay Khare

Ratnam Dubey

Yashvardhan Kabra

Code-magic | 2012 2



Date Version Description Author

25-01-2012 1.0 SRS Code-magic

Code-magic | 2012 3



Table of Contents

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Definitions, Acronyms and Abbreviations

1.4 References

1.5 Technologies to be used

1.6 Overview

2. Over all Description

2.1 Product perspective

2.2 Software interface

2.3 Hardware interface

2.4 Communication interface

2.5 Product functionalities

2.6 User characteristics

2.7 Constraints

2.8 Use case model survey

2.9 Class Diagram

2.10 Sequence Diagram

Code-magic | 2012 4

2.11 Sequence Diagram1


2.13 Activity Diagram


2.15 Assumptions and dependency

3. Specific Requirements 3.1 Use Case Reports



Code-magic | 2012 5



Software Requirements Specification

1. Introduction

1.1 Purpose M-banking:-m-banking interface with GPRS and SMS facility for communication and a highly secured 256 level bit encryption for transactional security. One of the major security issue solved is to provide a highly secured code to user each time.

1.2 Scope

Basic features:

•Create different system users and assign different roles with related permissions.

•Group the users together in a single account according to some criteria as personal user account. •Authenticate all user of the system with basic user name, password & highly secured code. •Users have their different login and profile passwords. •Maintain a centralized database to provide security to information which can be accessed only by the admin. •Graphical report on of Account statement and Billing statement are generated in easy downloadable formats. •Provide basic facilities of funds transfer and bill payments through easy payment gateways. •All activities performed by the system users and all transactional data will be

maintained in the form of logs for auditing and maintaining the integrity of the

system.

•Secure code sent to the user registered mobile number to ensure user identification.

Code-magic | 2012 6



Additional features:

•Secure Socket Layer (SSL) connectivity to ensure security. •Optimized AJAX usage for better user interaction.

1.3 Definitions, Acronyms and Abbreviations • End user: End user is categorized on the basis of login as personal user or corporate user. Different facilities are given to each set of users. Users must have their default user name and password for one time login. • Admin: Administrator of the bank who keeps track of all details of users and analyzing logs of customer details, transactional details to avoid any security risk. All kind of privileges are given only with admin profile. •HTML: Hypertext Markup Language is a markup language used to design static web pages as home page of bank website in jsp which only prompts for type of login. •EJB: Enterprise java bean, It is architecture for the development and deployment of

transactional, distributed object applications-based, server-sides software components. •JSP: Java Server Pages. •JAVASCRIPT: scripting language used for client side web development. •JQUERY: light weight Java Script library that emphasizes interaction between JavaScript and HTML. •AJAX: Asynchronous java script and XML.-used to change page content without reload. •DB2:DB2 Database is the database management system that delivers a flexible and cost-

effective database platform to build robust on demand business applications.

•WAS: Web sphere application server is an application server that runs

business applications and supports the J2EE and web services standards.

• RSA: Rational software architect is a designer toolkit which is designed to develop more

Complex projects by providing fully dynamic web service.

Code-magic | 2012 7



• HTTP:Hypertext Transfer Protocol is a transaction oriented client/server

protocol between web browser &a Web Server.

• HTTPS:Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).

• TCP/IP: Transmission Control Protocol/Internet Protocol ,the suite of

communication protocols used to connect hosts on the Internet.TCP/IP use several

protocols ,the two main ones being TCP and IP.

1.4 References

• ProblemDefinition (Provided by IBM)

• IEEE SRS Format

• Object oriented systems development using Unified Modeling Language by Ali

Bahrami, publication: McGraw-Hill, International edition 1999

• http://java.sun.com/developer/technicalArticles/J2EE/AJAX/RealtimeValidation/

1.5Technologiestobeused

• RSA: Development Tool

• WAS: Webserver

• Red Hat Linux: Operating system

• J2EE: Application Architecture

• DB2: Database

1.6Overview

• Over all Description will describe major components of the system ,inter connection and external interfaces.

• Specific Requirements will describe the functions factors, their role in the system

and constraints.

http://java.sun.com/developer/technicalArticles/J2EE/AJAX/RealtimeValidation/

Code-magic | 2012 8



2 Over all Description

Describe the general factors that affect the product and its requirements. 2.1ProductPerspective:

• The web pages (XHTML/JSP) are present to provide the user interface on client side.

Communication between client and server is provided through HTTP/HTTPS protocols.

• The Client Software is to provide the user interface on system user client side and for this

TCP/IPprotocolsareused.

• On the server side web server is for EJB and data base server is for storing the information.

Code-magic | 2012 9



2.2 Software Interface:

Client on Internet: Web Browser, Operating System (any)

Client on Intranet: Client Software, Web Browser, Operating System (any)

Web Server: WAS, Operating System (any)

Database Server: DB2, Operating System (any)

Development End: RAD (Java, J2ME, Jsp, Ejb) ,DB2, Linux, Webserver.

2.3HardwareInterface:

Minimum Hardware Requirements:

ClientSide

Internet Explorer6.0 &above,Mozilla Firefox,Chrome

Processor RAM DiskSpace

PentiumIII at500MHz

128MB 1GB

ServerSide

Websphere application serverv6.1

PentiumIV at1.3GHz

512MB 2GB

DB2V9.1 PentiumIV at1.3GHz

512MB 1GB(Excluding datasize)

Operating System

Red Hat Enterprise Linux Server

512MB 10-15GB

Code-magic | 2012 10



2.4 Communication Interface:

• Client on Internet will be using HTTP/HTTPS protocol.

• Client on Intranet will be using TCP/IP protocol.

2.5ProductFunctionalities:

•User identification: On the basis of login we can identify the user category on which set of facilities depends.

•Virtual keyboard: Virtual keyboard facility is given to enhance security on client end.

• Secure code: A highly secure code is sent to user registered mobile number to ensure user identification.

•Account summary: User able to visit account summary to see account information.

•Funds transfer: User able to transfer funds into different account by add beneficiary. •Inter bank transfer: User also make transfers in different bank accounts. •Bill payments: Several utility bill payments are also possible.

•Account statements: Account statements will provide account description between specified dates.

2.6UserCharacteristics:

Every user should be comfortable of working with computer and net browsing .He must have basic knowledge of English too.

2.7Constraints:

• GUI is only in English.

• Login and password issued for identification of customer and there is no facility for guest.

• Limited to HTTP/HTTPS.




2.8Use-CaseModelSurvey: USECASEDIAGRAM


2.9ClassDiagrams






2.10 Sequence Diagrams

Login of an end user




2.11 Sequence Diagrams 1

Admin added a user





Admin blocked a user




2.13ActivityDiagram





M-user open account summary




2.15 Assumptions and Dependencies • The end user should have basic knowledge of English a nd computer usage.

• Administrator is created in the system already.

• Roles and tasks are pre-defined.

3. Specific Requirements

3.1 Use-Case Reports:

Actors The system consists of following types of user.

1. Personal user

2. Bank administrator

3. Bank employee

4. Data Manager

5. Corporate user

Common Functionalities:

The following functions performed by the actors of the application.

•Login: In order to access functionalities of the system end user must authenticate by

providing login information as valid user name and password with secure code.

Name of use case : Login

Description: End user must provide valid set of user name and password for

authentication.

Pre-conditions: User must registered with bank and have a unique set of user name and

password stored at customer database.




Normal flow of events:

User enters the valid username and password.

JavaScript validates the information.

Jsp page passes the request to servlet.

The servlets check against database and returns true.

A session is created for the user login.

Profile of a user is open.


M-banking. Version : 1.0 Code-magic. Date : 25-01-2012 Team Name/ State Name Code-magic / Madhya Pradesh


M-banking. Version : 1.0 Code-magic. Date : 25-01-2012 Team Name/ State Name Code-magic / Madhya Pradesh

Alternative flow of events:

The end user enters user name and password.

JavaScript validates the provided information.

Thejsp page passes the request to servlet.

The Servlet checks against database and returns true.

Thejsp page is updated with an error message.



Team Name/ State Name Code-magic / Madhya Pradesh




• Logout:

After finishing tasks user may want to logout from the application. After logout user

is not able to use the facilities of the system.

• Password management:

An end user is provided a default password at the beginning. In order to enhance security user

must change the default password using password management.

Name of the use case: Password management

Description: user manages password using this section.

Pre-conditions: user must registered in the database to perform this activity.


User clicks on Password management.

Jsp page requests to servlet

.

Servlet passes this request to EJB.

Servlets checks against database and returns true.

EJB makes changes to database.

EJB reports these changes to database.

Servlets reports the same changes to jsp.


• Help and support:

A24x7help and support is provided to user either online or offline.

• Reset: User is provided with reset option in case of user name and passwords are lost.

• Enable virtual keyboard:

To enhance security level a virtual keyboard is given to provide inputs in jsp page.

User Specific Functionalities:

End user:

• Account summary

End users able to view his/her account summary showing current balance and

latest set of transactions done by the user .

Name of the use case: Account summary

Description: Account brief description.

Pre–condition: User must be registered in the database and logged in his/her profile.


End user selects preferred account number.

User clicks on Account summary button.

Jsp page asynchronously requests the servlet.

Servlet forward the request to EJB.

EJB queries the database.

EJB report the change to servlet.

Servlet similarly reports to jsp page.






• Bill payments

An end user may use this application to perform utility bill payments as electricity

bill.

Name of the use case: Bill payments

Description: As a payment gateway for various interfaces.

Pre–condition: User account exist in the database and the user must be logged in to

use this facility.


User clicks on bill payments.

Jsp page asynchronously requests to servlet.

Servlet queries the database for list of payment gateways.

Servlet provide the list of payment gateways.

Servlet responds to Jsp page.

User must select appropriate biller from the list and press continue button.




.


M-banking

M-banking.

Version : 1.0 Code-magic. Date : 25-01-2012


• Fund transfer:

An end user transfer fund from his/her account to another account by adding beneficiary.

• Inter-bank transfer:

Inter-bank transfer which allows the end user to transfer money from one bank account to

account number of another bank.

ADMIN:

• Add new user:

Administrator performs exclusive functions as adding a new user in

database, lock any existing user and many other tasks that requires large

set of skills of administration.

Name of use case: Add user

Description: Add new user in the customer database by receiving a request of new user

account from bank.

Pre-conditions: User must apply for a new account in bank.

Flow of events:

Users have to apply for a new account in the bank.

After verification of documents this request is transferred to admin.

Admin added the user by updating the database of customer.

User account enabled by the admin.




• Lock existing user:

Lock existing user means temporarily disable the account of a user by admin.

Name of use case: Lock user

Description: Disable the account number of existing user.

Pre-condition: User must already add in the customer database.

Flow of events:

Admin logged into his/her profile.

View log files.

On the basis of log files admin takes a decision of either disable the user profile or

not.

When the account is manually disabled by the admin, user has to go to bank to enable

it again, by following the instructions of bank employee.

• Delete user:

Delete user means delete the records of the user permanently in case of closing an account.

Name of the use case: Delete user

Description: Delete records permanently from customer database.

Pre-condition: User already exist in customer database.

Flow of events:

User has to apply manually in case of closing an account.

Request is forwarded to the admin.

Admin permanently deletes the records of user.

Code-magic IBM FINAL

Documents

Transcript of Code-magic IBM FINAL