TRUE GRABBER [PRICE COMPARISON]

A PROJECT REPORT

Submitted by

KIRUBHAGARAN V
(Reg. No: 18Y025)

in partial fulfillment for the award of the degree

of

MASTER OF COMPUTER APPLICATIONS

IN
DEPARTMENT OF COMPUTER APPLICATIONS

THIAGARAJARCOLLEGE OF ENGINEERING
(A Govt. Aided Autonomous Institution affiliated to AnnaUniversity)
(An ISO 9001: 2000 Certified Institution)

MADURAI – 625 015

May 2021
 THIAGARAJAR COLLEGE OF
ENGINEERING MADURAI – 625 015

BONAFIDE CERTIFICATE

Certified that this project report “True Grabber” is the bonafide work of
KIRUBHAGARAN V (18Y025), who carried out the project under my
supervision.

Head of the Department Guide

Dr. S. Parthasarathy, Mr. N. Murali,
Department of Computer Applications, Department of Computer Applications,
Thiagarajar college of Engineering Thiagarajar college of EngineeringMadurai
625 015. Madurai 625 015.

Submitted for the Viva – Voce Examination held at Thiagarajar college of

Engineering, Madurai on ………….

Internal Examiner External Examiner

 ACKNOWLEDGEMENT

My endeavor stands incomplete without dedicating my gratitude to a few people who

have contributed a lot towards the successful completion of my project work.

I sincerely thank The Almighty for making my life to be more interesting, challenging
and happier during the project tenure.

I am pleased to convey my gratitude to Dr. S. Mercy Shalinie, ThePrincipal,

Thiagarajar College of Engineering, Madurai, for providing me this opportunity to do my
project at Smartiapps Technologies.

I wish to express my sincere thanks to Dr. S. Parthasarathy, Head of the Department

of Computer Application,Thiagarajar College of Engineering, Madurai for his support and
ardent guidance.

I am extremely thankful at the most to my internal guide Mr. N. Murali, Associate

Professor, Dept. of Computer Applications, Thiagarajar College of Engineering, for his
continual support and enduring guidance throughout my project tenure. My earnest thanks to
all the staff members of the Department of Computer Applications for their constant care and
support.

I express my faithful thanks to External Guide Mr. VetriSelvan, Technical Director,

Smartiapps Technologies for his guidance and expert advice rendered by him in modest
attempt at preparing this project.

I wish to express my deep felt gratitude to my beloved parents for their constant
support and contribution to this project work. Also, I would like to thank all my teachers,
friends and well-wishers who have helped me for doing this project and throughout the MCA
course.
KIRUBHAGARAN V
ABSTRACT

i
 TABLE OF CONTENTS

CHAPTER NO. Title Page No.

ABSTRACT i
LIST OF TABLES v
LIST OF FIGURES vi
LIST OF ABBREVIATIONSvii
1. INTRODUCTION 1
1.1 ORGANIZATION PROFILE 1
1.2 EXISTING SYSTEM 1
1.3 PROPOSED SYSTEM 2
1.3.1 Advantages of the proposed system 2
2. SYSTEM ANALYSIS 3
2.1 FEASIBILITY STUDY 3
2.1.1 Operational Feasibility 3
2.1.2 Technical Feasibility 3 2.1.3 Economical
Feasibility 4
2.2 USE CASE DIAGRAM 5
2.2.1 Primary Use Case Diagram 5

3. SYSTEM REQUIREMENT SPECIFICATION 6

3.1 SCOPE 6

3.2 FUNCTIONAL REQUIREMENTS 6

3.3 PERFORMANCE REQUIREMENTS 7
3.3.1. Reusability 7
3.3.2. Flexibility ` 7
3.3.3. Scalability 7
3.3.4. Performance 8
3.3.5. Functionality 8
3.3.6. Response Time 8
3.4 SOFTWARE SPECIFICATION 8
3.5 HARDWARE SPECIFICATION 8

ii
 3.6 TECNOLOGIES USED 9
4. SYSTEM DESIGN 12
4.1 SYSTEM ARCHITECTURE DIAGRAM 12
4.2 DATA FLOW DIAGRAM 12
4.2.1 Level 0 DFD 13

4.3 ER DIAGRAM 14
4.4 PROCESS FLOW DIAGRAM 15
4.5 LOGICAL DESIGN USING UML 16
4.5.1 Class Diagram 16
4.5.2 Sequence Diagram 17

4.5.3 State Chart 18

4.5.4 Activity Diagram 20
4.7 MODULE DESCRIPTION 21
4.7.1 User Module 21

4.7.2 Admin Module 21

4.8 DATA BASE DESIGN 23
5. TESTING 26
5.1 TESTING OBJECTIVE 26
5.2 UNIT TESTING 27
5.3 INTEGRATION TESTING 28

5.4 USER INTERFACE TESTING 30

5.5. PERFORMANCE TESTING 30

5.6.SYSTEM TESTING 30

6. IMPLEMENTATION 31
7. CONCLUSION 33
8. BIBLIOGRAPHY 34

9. APPENDICES 35
9.1 APPENDIX –A PROJECT SCREEN SHOTS 35
iii
 9.2 APPENDIX –B PHP TESTING SCREEN SHOTS 45

LIST OF TABLES
TABLE INDEX NAME OF THE TABLE PAGE NO.

4.8.1 User 28

4.8.2 Product 28

4.8.3 Store 28

4.8.4 Special 29

4.8.5 Country 29

iv
 LIST OF FIGURES

FIGURE PAGE
INDEX TITLE OF THE FIGURE
NO.
FIGURE
2.2.1 Primary Use Case 5
2.2.2 User requests access to use job dashboard Use Case 6
2.2.3 User Logins to the Job Dashboard Use Case 6
2.2.4 User Requests the Group Report Use Case 7
2.2.5 User Requests the Job Report Use Case 7
2.2.6 User Generates a Report as CSV Use Case 8
2.2.7 User Requests user view Use Case 8
2.2.8 User Analyze the User View Use Case 8
4.1.1 Architecture Diagram 15
4.2.1 DFD Level 0 16
4.2.2 DFD Level 1 17
4.3.1 Entity Relationship Diagram 18
4.4 Process Flow Diagram 19
4.5.1 Class Diagram 20
4.5.2 Sequence Diagram 21
4.5.3 State Chart 22
4.5.4 Activity Diagram 24
4.6.1 Package Diagram 25
4.6.2 Component Diagram 26
4.6.3 Deployment Diagram 26
4.8.1 Database Design 30

v
 LIST OF ABBREVIATIONS
S.No. ABBREVIATION/ACRONYM DESCRIPTION
1 SLA Service Level Agreement
2 JSON JavaScript Object Notation
3 CSV Comma Separated Values
4 Control-M Control-Monitor
5 AJAX Asynchronous JavaScript and XML
6 PHP Hypertext Preprocessor
7 CSS Cascading Style Sheet
8 DFD Data Flow Diagram
9 SQL Structured Query Language
10 SVG Scalable Vector Graphics
11 API Application Programming Interface
12 HTML Hypertext Markup Language
13 CGI Common Gateway Interface

vi
 INTRODUCTION

1.1 Organization Profile

1.2 Existing System

The problem statement of transaction is the data theft which is stored in the
open source like server. There is no any security in transferring the account
number and amount details to bank. Persons that commit online transaction
crime largely go unpunished and repeatedly victimize consumers and
businesses. Typically, the fraudster causes a credit card and debit card of
another person to be charged for a purchase. Today, half of all credit card
and debit card fraud is conducted online, meaning that the fraudsters make
online purchases with the credit card details of other people.

1
1.3 Proposed System

The main work of the proposed methodology is providing systems that

ensure more security to the E-commerce and payment applications, core
banking applications and internet banking facilities. The objective of the
proposed method is achieved by involving valuable technique: Cryptography
for secure online shopping and maintaining user privacy. Online transaction
consists of fetching the account information via Internet through online
portals. Identity theft is the most common dangers of online transaction.
Stealing of someone’s personal information and misusing the stolen
information for making purchase or creating new bank accounts, arranging
credit cards etc. Admin and user will view the mini statement which
transaction made by the user.

1.3.1 Advantages of the Proposed System

• A secure transaction is enhanced using this system
• Unknown third party will avoided
• Encryption helps to for a high level secured system

2
 2. SYSTEM ANALYSIS

2.1 Feasibility Study

A feasibility study is a test of the system proposal regarding its workability;

impact on the organization; ability to meet the user needs; and effective use of the
resources. Thus, when a new application is proposed, it normally goes through a
feasibility study before it is approved for development. Thus, during the feasibility
study of this project, the above primary areas are to be considered. The objective of
the feasibility study is to analyze whether the proposed system is feasible while
operating under the existing environment. The primary considerations involved in
the feasibility analysis are discussed in the subsequent paragraphs.

2.1.1 Operational Feasibility

Operational feasibility is a basic necessity as it ensures that the project

developed can successfully be implemented. This feasibility study covers
Technical performance aspects and Acceptance within the organization. The
proposed system will benefit the organization, by instant communication
comparing with the existing system. The users can easily adapt to the new
system, reducing their workload.

2.1.2 Technical Feasibility

Technical feasibility centres on the existing computer system and analyses to

what extent it can support proposed additions. For example, if the current
computer is operating at 80% capacity an arbitrary ceiling-then running another
application could overload the system or require additional hardware. Technical
Feasibility is the most difficult area to ensure at initial stages. Since the objective
function and performance cannot be predicted to the fullest, everything seems
possible provided, proper assumptions are made. The process of analysis and
definition must be conducted in parallel with an assessment with technical
feasibility. The consideration that is normally associated with the technical
feasibility includes resource availability at the organization where the project is to
be developed and implemented. This involves financial considerations to
accommodate technical enhancement. If it is not satisfied, then the project is
judged not feasible.

3
 2.1.3 Economic Feasibility

Economic analysis is the most frequently used method for evaluating the
effectiveness of a proposed system. Most commonly known, is the cost/benefit
analysis, the procedure is to determine the benefits and savings that all expected
from the proposed system and compare them with costs. The software involved in
the proposed system is Open Source software. There will not be any software
costs incurred in the proposed system. The costs that will be incurred in
implementing the proposed system are developing and operating costs.

4
2.2 Usecase Diagram

5
 3. SYSTEM REQUIREMENT SPECIFICATION

3.1 Scope

The scope of this project is to provide service for price monitoring, analysis
and generation of reports in the form of a dashboard in the Self-Service Portal. This
scope of this project is limited within the Self-Service Portal. It allows consumers to
see different lists of prices for the product chosen by user and it helps consumers to
make an informed decision about which to choose in order to save money.

3.2 Functional Requirements

The configuration module includes:

User Function:

Users to register, log in, and log out. ... Each user is assigned one or more roles.

By default there are three roles: anonymous (a user who has not logged in) and
authenticated (a user who is registered), and administrator (a signed in user who will be
assigned site administrator permissions)

Users can view the products and their prices and can add the products to their cart and
switchover to any E-Commerce platform easily.

Admin Function:

Admin adds a new products and manage user’s data their data to the AWS database, so it
needs an active internet connection. The internet speed is not much cared. It can be
minimum of speed to upload the data to the database.

When a request comes from the admin the API gets called and the API contacts with the
server to update the necessity changes to the database whenever needed.

6
 View user

In these function admin can view all the users and user work process on these
modules.

Transaction

User can make transaction on these function every users can send money to the
others and make mini statement deposit on this function.

3.3 Performance Requirements

Performance Requirements (PR) are necessary for system design and

development. There are three classes of performance requirements: response time
(how fast the system can handle individual requests, what a real user would
experience), throughput (how many requests the system can handle), and
concurrency (how many users or threads work simultaneously). The performance
requirements are given below:

3.3.1 Reusability

In this System, to reduce implementation time, reusable modules and classes

are used, that is, a segment of source code that can be used again to add new
functionalities with slight or no modification.

3.3.2 Flexibility

The application is developed with the custom MVC structure. It is very easy
for adding functionalities without affecting existing functionalities and also
provides the facility to make modifications to the Application.

3.3.3 Scalability

The application meets the performance requirements when the demand

increases. It handles increasing job requests of users, gives the expected reports
with great accuracy and handles the large volume of the data.

3.3.4 Performance

The application is available to the user once they login to the system and

7
 lasts up to the session expires or until the user sign’s out. And it’s fast and
reliable because of its runs only in the internal server of the organization.

3.3.5 Functionality

The functionalities in the application will be more efficient. It provides easy

access to the user and the application is user friendly.

3.3.6 Response Time

This Application should respond to the user within a minimum duration of

time so that there is a minimum delay in getting output from the system.

3.4 Software Specification

Server Software Specification

Component Software Configurations

Operating System Windows Server 2013

Tools Visual Studio Code, MySQL

Web Server Apache Server

Browser Chrome

Client Software Specification

Component Software Configurations
Operating System Windows 7, 8.1, 10 or Ubuntu
Internet Browser Firefox, Chrome, Edge

3.5 Hardware Specification

Server Hardware Specification

Component Configuration
Processor AMD Threadripper 1990
Memory 32GB Ram
Hard disk 1TB HDD

Client Hardware Specification

Component Configuration(Minimum)
Processor Intel Pentium Duo
Memory 4GB Ram
Hard disk 256GB HDD

8
3.6 Technologies Used

Technologies: HTML/CSS, JavaScript, jQuery, PHP, MySQL, Dart.

3.6.1 HTML/CSS

HTML:

HTML or Hypertext Markup Language is the main markup language for

creating web pages and other information that can be displayed in a web
browser.HTML is written in the form of HTML elements consisting
of tags enclosed in angle, within the web page content.
HTML elements form the building blocks of all websites. HTML
allows images and objects to be embedded and can be used to create interactive
forms. It provides a means to create structured documents by denoting
structural semantics for text such as headings, paragraphs, lists, links, quotes
and other items. It can embed scripts written in languages such
as JavaScript which affect the behavior of HTML web pages.

CSS:
Cascading Style Sheets is a style sheet language used for describing the
presentation of a document written in a markup language like HTML. CSS is a
cornerstone technology of the World Wide Web, alongside HTML and
JavaScript.
3.6.2 JavaScript

JavaScript (JS) is a dynamic computer programming language. It is most

commonly used as part of web browsers, whose implementations allow client-
side scripts to interact with the user, control the browser,
communicate asynchronously, and alter the document content that is displayed.
It is also being used in server-side programming, game development and the
creation of desktop and mobile applications.

3.6.3 jQuery

jQuery is a fast, small, and feature-rich JavaScript library. It makes things

like HTML document traversal and manipulation, event handling, animation,
and Ajax much simpler with an easy-to-use API that works across a multitude

9
of browsers. With a combination of versatility and extensibility, jQuery has
changed the way that millions of people write JavaScript.

3.6.4 PHP

PHPis a server-side scripting language designed primarily for web

development but also used as a general-purpose programming language.
Created by RasmusLerdorf in 1994, the PHP reference implementation is now
produced by The PHP Development Team. PHP originally stood for Personal
Home Page, but it now stands for the recursive acronym PHP: Hypertext
Preprocessor.

PHP code may be embedded into HTML or HTML5 markup, or it can be

used in combination with various web template systems, web content
management systems and web frameworks. PHP code is usually processed by a
PHP interpreter implemented as a module in the web server or as a Common
Gateway Interface (CGI) executable. The web server software combines the
results of the interpreted and executed PHP code, which may be any type of
data, including images, with the generated web page. PHP code may also be
executed with a command-line interface (CLI) and can be used to implement
standalone graphical applications.

The standard PHP interpreter, powered by the Zend Engine, is free software
released under the PHP License. PHP has been widely ported and can be
deployed on most web servers on almost every operating system and platform,
free of charge.

3.6.5 Flutter

Flutter is an open-source UI software development kit created by Google. It is

used to develop applications for Android, iOS, Linux, Mac, Windows, Google
Fuchsia, and the web from a single codebase. Flutter apps are written in the
Dart language and make use of many of the language's more advanced features.

On Windows, macOS, and Linux. Flutter runs in the Dart virtual machine,
which features a just-in-time execution engine. While writing and debugging an
app, Flutter uses Just In Time compilation, allowing for "hot reload", with
which modifications to source files can be injected into a running application.

10
 3.6.6 MS SQL Server

SQL Server is a relational database management system, developed by Microsoft.

SQL Queries can be used to retrieve large amounts of records from a database quickly
and efficiently. One of the most essential functions of SQL Server is to provide data to
other software applications (clients). To interact with SQL Server databases and manage
or query their data, you can use the Transact-SQL (T-SQL) language, an extension of the
SQL standard.it is easier to manage database without having to write a substantial amount
of code.

3.6.7 Laravel

Laravel is a free, open-source PHP web framework, created by Taylor Otwell and
intended for the development of web applications following the model–view–
controller (MVC) architectural pattern and based on Symfony. Some of the
features of Laravel are a modular packaging system with a dedicated dependency
manager, different ways for accessing relational databases, utilities that aid in
application deployment and maintenance

11
 4. SYSTEM DESIGN

System design is the major process that can be termed as the backbone in the
development of any software product. The design phase in any project will consider the
results of the analysis phase and comes out with the prototype of the product, which is almost
similar to the product which is being developed.

4.1 System Architecture Diagram

SECURED ONLINE TRANSACTION USING

CRYPTOGRAPHY
ADMIN USER

LOGIN REGISTER

VIEW USERS LOGIN

VIEW
TRSANSACTION
VIEW
TRANSACTION LOGOUT

LOGOUT

Fig 4.1.1 Architecture Diagram

4.2 Data Flow Diagram

A data flow diagram shows the way information flows through a process or
system. It includes data inputs and outputs, data stores, and the various subprocesses
the data moves through. DFDs are built using standardized symbols and notation to
describe various entities and their relationships. It shows how data enters and leaves
the system, what changes the information, and where data is stored. The objective of
a DFD is to show the scope and boundaries of a system as a whole.
DFD may be used to perform a system or software at any level of abstraction.
Levels in DFD are numbered 0, 1, 2 or beyond.
 Level-0 DFD: It is also known as the context diagram. It is designed to be an
abstraction view, showing the system as a single process with its relationship

12
 to external entities. It represents the entire system as a single bubble with
input and output data indicated by incoming/outgoing arrows.
 Level-1 DFD: In level-1 DFD, the context diagram is decomposed into
multiple bubbles or processes. In this level, we highlight the main functions
of the system and breakdown the high-level process of level-0 DFD into
subprocesses.

4.2.1 Level 0 DFD or Context Analysis

Diagram

Admin User

View data Add Data

Encryption

Secure and Smart Transaction System

Fig 4.2.1 Level 0 DFD

13
4.3 ER Diagram

Fig 4.3.1 ER Diagram

14
4.4 Process Flow Diagram

Admin Login Transaction

Mini Statement

DATABASE

Mini Statement Transaction

Encryption

User Register & Login Make Transaction

15
Fig 4.4 Process Flow Diagram

16
4.5 Logical Design using UML
4.5.1 Class Diagram

Fig 4.5.1 Class Diagram

17
 4.5.2 Sequence Diagram

Fig 4.5.2 Sequence Diagram

18
 4.5.3 State Chart
Admin:

Fig 4.5.3.1 State Chart Admin

19
 4.5.4 Activity Diagram

Fig 4.5.4 Activity Diagram

20
 4.7 Module Description

USER REGISTRATION

USER LOGIN

USER TRANSACTIONS

ADMIN LOGIN

ADMIN VIEW

MODULE DESCRIPTION
USER REGISTRATION
In this module, user has to register with the basic details such as username, mobile
number and PIN. These details will be saved in the database.
USER LOGIN
In this module, the login method is explained. Login can be done by using any of the
two methods. First, username should be entered. Then user should select the login method as
PIN method. In the PIN method is chosen, user has to enter the PIN. All the numbers in the
keypad will look like number 8. If the entered details match with the available details, the
user can proceed to the next step.
USER TRANSACTIONS
In this module, user transactions will be explained. Once the entered details are
correct, user’s home page will be displayed. User can do various transactions like withdraw,
transfer money and deposit.
ADMIN LOGIN
In this module, user can login into the system using admin and admin as username
and password respectively.
ADMIN VIEW
In this module, admin can view the list of users available with the system. Also,
admin can view the list of transactions done between users.

21
4.6 Database Design

Fig 4.8.1 DB Design

22
USER REGISTRATION
Field Type Null Default
id int(11) Yes NULL
name varchar(100) Yes NULL
address varchar(100) Yes NULL
contact varchar(100) Yes NULL
email varchar(100) Yes NULL
uname varchar(100) Yes NULL
pass varchar(100) Yes NULL
rdate varchar(100) Yes NULL

TRANSACTION DETAILS
Field Type Null Default
id int(11) Yes NULL
user varchar(50) Yes NULL
Amount varchar(50) Yes NULL
Date varchar(50) Yes NULL
sender varchar(20) Yes NULL
Receiver varchar(20) Yes NULL

23
 5. TESTING
5.1 TESTING OBJECTIVE
Software testing is defined as an activity to check whether the actual results
match the expected results and to ensure that the software system is Defect free.
Testing is the most important activity in the development phase.

Software testing provides an independent view and objective of the software

and gives surety of the fitness of the software. It involves testing of all components
under the required services to confirm that whether it is satisfying the specified
requirements or not.

The process is also providing the client with information about the quality of
the software. Testing is mandatory because it will be a dangerous situation if the
software fails any of the time due to a lack of testing. So, without testing software
cannot be deployed to the end-user.

Testing includes an examination of code and also the execution of code in

various environments, conditions as well as all the examining aspects of the code.
Testing determines whether the software is giving the result as per the requirements
addressed in the requirement phase or not.

 Unit testing
 Integration testing
 User Interface Testing
 Functional Testing

 System Testing

24
5.2 UNIT TESTING

Table 5.1 Unit Testing

25
5.3 INTEGRATION TESTING

Integration testing is the level of software testing where individual units are
combined and tested as a group. The purpose of this level of testing is to expose faults
in the interaction between integrated units. Test drivers and test stubs are used to
assist in Integration Testing. Testing performed to expose defects in the interfaces and
the interactions between integrated components or systems.

It tests the interface between two software units or modules. It focuses on

determining the correctness of the interface. The purpose of the integration testing is
to expose faults in the interaction between integrated units. Once all the modules have
been unit tested, integration testing is performed.

 User module
 Admin module

All the above modules are tested and the errors are fixed.
Hence, the objective of integration testing is to take unit tested modules and build a
final program structure. In this project, modules are combined to find the overall
performance of the system.

In this project, the modules are integrated properly, the

emphasis being and testing interfaces between modules. Internal and External
interfaces are tested as each module is incorporated into the structure. This test is
designed to uncover errors associated with local is global data structures are
conducted. It is also designed to verify the performance levels established during
software design are conducted

Thus, all these modules are combined, verified and the

information about the items is properly carried on to the next module and then it is
checked.

26
 Test
Test Condition Test case/ scenario/
Case Expected Result Actual Result Pass/Fail
Description data description
No.
When admin enters
Check whether
login credentials
admin can Navigate to admin Admin Home page is
1 admin should be Pass
navigate to admin home page loaded
navigated to admin
Homepage.
homepage
When organization
Check whether user enters login
Navigate to
Organization user credentials admin Organization Home
2 organization home Pass
can navigate to should be navigated page is loaded
page
admin Homepage. to organization
homepage
When driver user
Check whether
enters login
driver can Navigate to driver Driver Home page is
3 credentials admin Pass
navigate to admin home page loaded
should be navigated
Homepage
to driver homepage

Table 5.3 Integration Testing

5.4 USER INTERFACE TESTING

27
 UI testing is a software testing method that checks the Graphical User
Interface (GUI) of the Application under Test. GUI testing involves checking the
screens with the controls like menus, buttons, icons, and all types of bars - toolbar,
menu bar, dialog boxes, and windows, etc. The purpose of Graphical User Interface
Testing is to ensure UI functionality works as per the specification. All the Screen
validations and navigations are tested in the web application. This can be done by the
Capture and Replay approach (i.e) During Capture, test steps are captured by the
automation tool. During playback, the recorded test steps are executed on the
Application under Test.

5.5 FUNCTIONAL TESTING

Functional Testing is a type of software testing that ensures software
applications to perform properly under their expected workload. It is a testing
technique carried out to determine system performance in terms of sensitivity,
reactivity, and stability under a particular workload. Performance Testing is the
process of analyzing the quality and capability of a product. It is a testing method
performed to determine the system performance in terms of speed, reliability, and
stability under varying workloads.

5.6 SYSTEM TESTING

Testing the fully integrated applications including external peripherals to
check how components interact with one another and with the system as a whole.
This is also called End to End testing scenario. It verifies thorough testing of every
input in the application to check for desired outputs. It also tests to find discrepancies
between the system and its original objective, current specifications and systems
documentation. The primary concern is the compatibility of individual modules.

28
 6. IMPLEMENTATION
Implementation forms an important phase in the development life cycle. This
phase of software development is concerned with translating design specifications into a
working model. Implementation is the final phase in achieving a successful system and in
giving the users confidence that the system will work efficiently. Usually, this phase is the
longest of all life cycle phases and is characterized by four distinct changes.
 Changeover Routine
 maintenance stage
 User-acceptance review
 Post-implementation reviews

CHANGEOVER
Initially, the new system must be introduced to the business activity stream.
This state is called Changeover. The changeover transaction may take weeks or even months.

ROUTINE MAINTENANCE STAGE

After the completion of the changeover, the system enters the operation and
routine maintenance stage. Early in this stage, the evaluation should be made based on
performance measurements that determine whether the specific benefits claimed for the
system have been achieved.

USER ACCEPTANCE / POST IMPLEMENTATION

After this system was implemented, a user-acceptance review was conducted

to gather information for the maintenance of the system. This review was done to determine
whether the system has met the expectations and objectives of the user.

As new activities begin, or change in the procedures occur due to the internal
or external factors the system is prone to modification needs. Thus, for the maintenance
requirements, these post-implementation reviews provide the first source of the users.

29
AUTHORIZATION

The System has been developed successfully. All the functions of the application
need not be executed by all the persons. An admin can only able to approve/manage
User/Customer and manage reports created by the system. Customers can only able to
see the reports and analyze, they can also create user view and edit, update, delete it. For
this Authorization, checks have been included for all functionality. This application is
implemented through web hosting through organization servers.

30
 7. CONCLUSION AND FUTURE
ENHANCEMENTS
7.1 CONCLUSION
Graphical passwords use easily seen images that attracts human attention. It
is an easy task for the shoulder-surfer to obtain the account's password since
the password attempt is not masked. This flaw makes most of the graphi-cal
password scheme vulnerable to shoulder-surfer attackers. Many schemes
proposed have shown flaws such as requiring the user to spend too much
time on complex mental activities to derive the correct image to click on.
Others schemes do not conceal the images in the challenge set during
authenti-cation which allows direct shoulder-surfing. These two major
drawbacks make graphical password schemes very vulnerable to shoulder-
surfer attackers. In this paper, a new scheme to hide and conceal the
mechanism or activity required to derive the password-images generation is
proposed. This activity is simple enough to reduce login time while the
images clicked seem to be random and can only be obtained by the complete
knowledge of the registered password along with the activity rules. This
combination makes it tougher for a shoulder-surfer to identify the user's
actual password. From the user study results, it shows that the average login
process for the proposed method is really fast as it was successfully
performed by the participants in less than half a minute. Moreover, the
proposed method is able to resist shoulder-surfing attacks although the
adversaries have the knowledge of how the proposed method works.

31
The term “graphical password” refers to a user authentication method where
pictorial information is used for validation, instead of an alphanumerical
password. This method poses many challenges, such as memo ability
(which refers to how easy the password is to remember), usability, and
security, since graphical passwords may tend to be visually simple and
easily forged. Graphical passwords have become popular due to the
proliferation of touch screen devices, in particular smart phones and
tablets. The prevalent approaches are based on simple graphical
passwords, which can be easily remembered and reproduced by potential
attackers. In this work, we study user authentication based on finger-
drawn doodles (i.e., free-form gestures or sequences of gestures) and on
pseudo signatures, which are implied versions of the signature drawn
with the fingertip. Authentication is based on features extracted from the
dynamics of the gesture drawing process (e.g., speed or
acceleration).These features contain behavioral biometric information,
which has been successfully used for automatic user verification based on
handwritten signatures. As a consequence, a potential attacker would
have to copy not only what the user draws, but also how the user draws it.
Unfortunately, graphical passwords tend to be much simpler than
signatures and are no composed, in general, of previously learned or
heavily practiced movements. This can lead to a higher intra-user
variability (i.e., variations between samples produced by the same person)
than in the case of signatures or may cause users to forget part of or the
whole graphical password.

.
7.2 FEATURES
 Easy to use.
 Data Shown in the Graph format for clear Understanding.
32
  Real time progress of the report.
 User-Friendly Screens.
 A simple button click operation is enabled.
 All data fetched from the database in the server and no need to upload the
data every time.
 Customers change their normal view into customized user views where they
can view what should in the report.
 Easy for modification and future Enhancement.

7.3 FUTURE ENHANCEMENTS

The main focus of this proposed system is to give a more secure PIN entry method for
common user authentication with high usability and give compatibility and cost effectiveness
(means no additional expensive hardware) by the session key method. Session key method is
a graphical password method which is easier to the user as well as hard to the shoulder surfer.
The one way hybrid pin password is used to secure the PIN after the logon procedure. In this
system, the human shoulder surfing attack is prevented and a secure transaction between the
mobile App and Server is established by using The Session Key Method.

7.4 LIMITATIONS

 For our True secure online transaction system to work effectively, tie
up with an e-commerce solution is a must.

33
 8. BIBLIOGRAPHY
8.1 Book References

 Beginning Flutter: A Hands On Guide to App Development by Marco

L. Napoli

 Laravel Essentials by Martin Bean

8.2 Web References

 Laravel : https://laravel.com/docs/8.x

 Angular : https://angular.io/docs

 Flutter : https://flutter.dev/docs

34
 9. APPENDICES

9.1 APPENDIX –A: PROJECT SCREENSHOTS

35
Fig 3 Hybrid shuffled digital pin password

10.Fig 4 User Home Page

36
 Fig 5 Deposit amount in the bank

Fig 6 Amount Withdrawn in the bank

37
11.Fig 7 Amount Transa

38