M.Sc. (C.

S) Programme

Transaction Manager

2015-16

A
PROJECT REPORT
ON
(Transaction Manager App)
SUBMITTED BY
(Yadav Pradnyarani Dilip)
UNDER GUIDANCE
Ms. KAMBLE JAYSHREE
SUBMITTED TO
UNIVERSITY OF PUNE
AS A PARTIAL FULFILLMENT
FOR THE AWARD OF THE DEGREE
MASTER OF COMPUTER SCIENCE (M.Sc. (C.S.))
THROUGH
THE PRINCIPAL
ASMS
COLLEGE OF COMMERCE, SCIENCE &INFORMATION
TECHNOLOGY,CHINCHWAD, PUNE 411019
(2015 - 2016)
SYMCS
Page 1

M.Sc. (C.S) Programme

Transaction Manager

2015-16

ACKNOWLEDGEMENT
It gives me immense pleasure to present this report on
Transaction Manager App. The project work has brought out significance of
sincere efforts, guidance and support that makes a project successful. I take this
opportunity to acknowledge the guidance and encouragement of all those with
whom I have interacted during the course of this project.
I would like to thanks to my project guide Ms.Kamble Jayshree for her valuable
suggestions during the project work .I would also like to thanks to our Principal,
Vice-principal, HOD , Teaching & non-teaching staff of the college for their
support and encouragement.

SYMCS
Page 2

M.Sc. (C.S) Programme

Transaction Manager

2015-16

Index
Sr.no

Topic

Page No

Problem Definition

Existing System and need for new system

Introduction to proposed system

Scope of the work

Feasibility study

Project Specification and Requirement

Fact finding techiniques

10

ER diagram

12

Normalised Database design

13

10

Data Dictionary

14

11

Use Case Diagram

18

12

Class Diagram

19

13

Sequence Diagram

20

14

Activity Diagram

21

15

Component Diagram

22

16

Deployment Diagram

23

17

Project Input Output Screens

24

18

Testing and Implementation Plan

30

19

Future Enhancement

31

20

Conclusion

32

21

Bibliography

33

Problem Definition:

SYMCS
Page 3

M.Sc. (C.S) Programme

Transaction Manager

2015-16

In todays mobile world,almost all monetary transactions are done through

mobiles.The user has to keep track of all transactions done using different bank
accounts.This makes user uncomfortable and ambiguous.To overcome this
problem,we have developed an application which will maintain all the transactions
done using different bank accounts.

Need for the new System:

The above mentioned complexity can be efficiently solved by an automated
system, which will generate non clashing transaction manager for us in seconds.
The account list, creation of new account holder, Transaction Manager etc
will be the inputs to the system, and the Proper, efficient, non clashing transaction
management will be the output of this system.

SYMCS
Page 4

M.Sc. (C.S) Programme

Transaction Manager

2015-16

Introduction about the proposed system:

The actual Manual system was more complex to design and therefore for
the development of this Application. System is designed to manage the account
details for transaction manager.
User is responsible to create the account . He can then view the account
details . More interestingly, if he/she wants to view the transactions done till now
can view it at a glance.
The user can check the details of the account holder.The user can make
multiple transactions with the same account holder.

SYMCS
Page 5

M.Sc. (C.S) Programme

Transaction Manager

2015-16

Scope of the work:

This Application can be used by any individual who makes online
transactions.This app needs no internet connection as it maintains the record
offline. Therefore this Application is beneficial for all individuals.

FEASIBILITY STUDY
SYMCS
Page 6

M.Sc. (C.S) Programme

Transaction Manager

2015-16

Feasibility is the determination of whether or not a project is worth doing.

It is carried out to select the best system that meets the performance
requirements.
Generally feasibility studies are undertaken within tight time constraints &
normally culminate in a written & oral feasibility Report.

Time Feasibility : It is the determination of whether a proposed system can be implemented

fully within a stipulated time frame.
If a project takes too much time, it is likely to be rejected.
The Proposed system is time feasible and is implemented within the given
time. It works very efficiently.

Economic Feasibility : Economic Feasibility is the most frequently used one.

This is the technique for evaluating the effectiveness of a proposed system
more commonly known as Cost/Benefit. The procedure is to determine the
benefits & savings that are expected from a proposed System & compare
them with the cost.

Technical Feasibility : This is concerned with specifying equipment & software that will
successfully satisfy the user requirements.
SYMCS
Page 7

M.Sc. (C.S) Programme

Transaction Manager

2015-16

The technical need of the system may vary considerably but might include :
i.

The facility to produce outputs in a given time.

ii.

Response time under certain conditions.

iii.

Ability to process a certain volume of transactions at a particular

speed .

iv.

Facility to communicate data to distant location.

v.

In examining technical feasibility configuration is given more

importance than the actual make of hardware.

This Proposed system is technically feasible because , any Android Phone

can run this Project. They dont incur further costs. The system develops the
results and reports in no time.

Project Specifications and Requirements:

Front-end:
SYMCS
Page 8

Java SDK

M.Sc. (C.S) Programme

Transaction Manager

IDE:

Eclipse IDE , Android SDK , ADT for Eclipse.

Backend:

SQL Lite

Hardware Requirements:
32 MB RAM or Higher
32 MB Storage space or More
200 MHZ Processor or Better
Software Requirements:
Android 2.3 "Gingerbread"
Android 4.0 "Ice Cream Sandwich"
Android 4.3, Android 4.2 and Android 4.1 "Jelly Bean"
Android 4.4 "KitKat"

Fact Finding Techniques:

SYMCS
Page 9

2015-16

M.Sc. (C.S) Programme

Transaction Manager

2015-16

The specific methods used for collecting data about requirements are called Fact
Finding Techniques. This includes:

Interview:
The interview is the best method of introducing qualitative information like
opinion, polices and subjective description of activities and problems.

Questionnaire:
It is used to collect information about various aspects of the system from
large number of people. It contains a standardize question format and more
reliable than any other fact finding technique. It is appropriate for collecting
actual information.

Record Review:
Records include writer policy manual, regulations and standard operating
procedures used by the organization. Records inspection can be done at the
beginning. Records and reports can provide with valuable information.

Observation:
It allows the analyst to get information, which cannot be obtained from any
other techniques. Through this the analyst can get first hand information of
how things are actually carried out.

The fact finding technique used for this project was Interview.

SYMCS
Page 10

M.Sc. (C.S) Programme

Transaction Manager

2015-16

1) How much time it requires to design the timetables for various classes?
Ans: It takes more time, because allocation of subjects to teachers and
allocating non clashing timeslots to them takes more time.
2) How many subjects are allocated to the staff?
Ans: Every Teacher is allocated at 1 or 2 subjects. If 2 subjects are
allocated, one is same as that of last year and one new subject is given.
3) What do you think, is it possible to design a system which will
automatically generate non clashing timetables?
Ans: Yes, it is possible to design such automated system. But a proper
design and algorithm has to be written.

SYMCS
Page 11

M.Sc. (C.S) Programme

Transaction Manager

2015-16

ER diagram:
Customer_no

Transaction
_id
Acc_id

Branch
account_id

transdate

Holder
s

Accounts

micr

h
a
s

Transaction

ifsc
cheque_deta
ils
transamount
remarks

Bank

SYMCS
Page 12

balance

transtype

M.Sc. (C.S) Programme

Transaction Manager

2015-16

Normalised Database Design and Data Dictionary:

The tables in the system are:

1 : Account(account_id, acno, holders, customerno, bank, branch, address, ifsc,
micr, balance, last_tran_date, remarks)
2: Classes(_id, account_id, transdate, transtype, transamount, cheque_no,
cheque_party, cheque_details, remarks)

SYMCS
Page 13

M.Sc. (C.S) Programme

Transaction Manager

Data
Dictionary

1] Accounts
Sr.no
SYMCS
Page 14

Field Name

Datatype

Constraints

2015-16

M.Sc. (C.S) Programme

Transaction Manager

account_id

Integer

acno

Integer

holders

Varchar(50)

bank

Varchar(50)

address

Varchar(50)

ifsc

Integer

micr

Integer

balance

Integer

last_tran_da
te

Integer

10

remarks

Varchar(50)

2] Transaction :
SYMCS
Page 15

Primary Key

2015-16

M.Sc. (C.S) Programme

Transaction Manager

Sr.no

Field Name

Datatype

Constraint

_id

Integer

Primary Key

account_id

Varchar(20)

Foreign Key

transdate

date

transtype

Varchar(20)

transamoun Integer
t

cheque_no

Integer

cheque_par
ty

Varchar(20)

cheque_det
ails

Integer

remarks

Varchar(20)

SYMCS
Page 16

2015-16

M.Sc. (C.S) Programme

Transaction Manager

Diagrams

Use Case Diagram

SYMCS
Page 17

2015-16

M.Sc. (C.S) Programme

Class Diagram
SYMCS
Page 18

Transaction Manager

2015-16

M.Sc. (C.S) Programme

Sequence Diagram

SYMCS
Page 19

Transaction Manager

2015-16

M.Sc. (C.S) Programme

SYMCS
Page 20

Transaction Manager

2015-16

M.Sc. (C.S) Programme

Activity Diagram

SYMCS
Page 21

Transaction Manager

2015-16

M.Sc. (C.S) Programme

Component Diagram

SYMCS
Page 22

Transaction Manager

2015-16

M.Sc. (C.S) Programme

Transaction Manager

Deployment Diagram

User

Request Data
Fetch Data

Android
Application

Fetch Required Data

Make a Data Request

Database
(SQL Lite)

SYMCS
Page 23

2015-16

M.Sc. (C.S) Programme

Transaction Manager

Project InPUT
OUTPUT sCREENS

SYMCS
Page 24

2015-16

M.Sc. (C.S) Programme

Add account

Update Account

SYMCS
Page 25

Transaction Manager

2015-16

M.Sc. (C.S) Programme

SYMCS
Page 26

Transaction Manager

2015-16

M.Sc. (C.S) Programme

Add Transaction

SYMCS
Page 27

Transaction Manager

2015-16

M.Sc. (C.S) Programme

Transaction Manager

Delete Account

List of Accounts
SYMCS
Page 28

2015-16

M.Sc. (C.S) Programme

Testing

SYMCS
Page 29

Transaction Manager

2015-16

M.Sc. (C.S) Programme

Transaction Manager

2015-16

Software testing is a critical element of software quality assurance and

represents the ultimate review of specification, design and coding. In fact, testing is
the one step in the software engineering process that could be viewed as
destructive rather than constructive.
A strategy for software testing integrates software test case design methods
into a well-planned series of steps that result in the successful construction of
software. Testing is the set of activities that can be planned in advance and
conducted systematically. The underlying motivation of program testing is to
affirm software quality with methods that can economically and effectively apply
to both strategic to both large and small-scale systems.

Future Enhancements:

SYMCS
Page 30

M.Sc. (C.S) Programme

Transaction Manager

2015-16

As we know that life is not static, rather than, it is dynamic. Therefore,

change for the better is necessary. Hence, in every system there should be a scope
for improvement. Grouping and Prospecting is part of nature. Therefore
enhancement is necessary in project. Following are some enhancements in the
Project:
1)

Notification of each transaction can be displayed.

2)

Provision for face identification of account holder for more security.

Conclusion:

SYMCS
Page 31

M.Sc. (C.S) Programme

Transaction Manager

2015-16

This System is basically developed for Computer Lab Assistant for automatic
attendance marking on student login. The system is reliable, as it does not produce
any failures that are dangerous or unavoidable. Reasonability implies that the
System or Software produces results in a consistent manner free from failures and
errors.
Thus, the system is technologically more reliable and feasible than the
existing system. We have got the opportunity to learn many things with the system.
We do sincerely believe that we have been able to achieve the objectives and
provide the ultimate output called User Satisfaction. This practical work really
gives us a chance to learn something different from typical reference books and
text books.
Sincere thanks to our Project Guide Ms. Kamble Jayshree for her guidance in our
project and giving timely instructions regarding the project.

Bibliography:
1) Website: www.w3schools.com
2) Java Complete Reference
SYMCS
Page 32

M.Sc. (C.S) Programme

Transaction Manager

3) Android Complete Reference

4) www.google.com
5) www.wikipedia.com
6) Android Programming

SYMCS
Page 33

2015-16