PROJECT REPORT ON

“Title of the Project”

Submitted in partial fulfillment of the requirements for Software Project
Management Lab (MCA1552P1) for 5th Semester

Master of Computer Applications

Submitted by
Student Name1 Register Number1
Student Name2 Register Number2

Under the guidance of

Dr. Muruganantham A
 CERTIFICATE

This is to certify that the project titled “Title of the Project” has been
satisfactorily completed by Mr. / Ms. Student Name with Reg. No. Ur Reg. No.,
in partial fulfillment of the requirements for Software Project Management Lab
with course code MCA1552P1, for the 5th Semester MCA course during the academic
semester from June 2018 to October 2018 as prescribed by Bangalore University.

Faculty In-charge Head of the Department

Valued by

Examiner 1:_______________________ Date :

Examiner 2:_______________________ Centre: Kristu Jayanti College

 ACKNOWLEDGEMENT

First of all, we would like to thank the God Almighty for all the blessings he
has showered on us. Our spiritual quotient gave us more strength and motivation that
helped immensely.

We would like to thank Rev. Fr. Josekutty P D, our esteemed Principal and
Rev. Fr. Augustine George, our Vice – Principal, for providing us their constant
guidance and support. I would also like to thank Rev. Fr. Lijo P Thomas, our
Financial Administrator and Head, Department of Computer Science (UG), for
providing us with the best facilities.

We are extremely thankful to our Prof. Kumar R, Head, Department of

Computer Science (PG) for giving us the essential support in the form of allocating
comfortable lab hours and necessary resources.

We would like to extend our heartfelt thanks to Dr. Muruganantham A, our

project guide for providing us the necessary details related to project development
and management using the MS Project tool.

We thank all other faculty members who helped us a lot in completing this
project. The computer lab was always open for us. We thank the lab administrator
and other technical staff for their help and support.

We thank our class mates, who have pointed out errors and guided us a lot and
we thank each and every one who has helped us.
Synopsis
 CONTENTS
SI.NO CONTENT Pg. No

1. Introduction

 Problem Definition
 Project Description

2. System Study

2.1 Existing System

2.2 Proposed System

2.3 Data Flow Diagram

3. System Configuration

3.1 Hardware Configuration

3.2 Software Configuration

4. Details of Software

4.1 Overview of Front End

4.2 Overview of Back End

5. System Design

5.1 Architectural Design

5.2 Use Case Analysis

5.3 Activity Diagram

 5.4 Sequence Diagram

5.5 Input Design

5.6 Output Design

5.7 Database Design

6. Source Code

7. Testing

7.1 Test Cases

8. Implementation

9. Screen Shots

10. Conclusion

11. Bibliography

12. User Manual

1. Introduction:
1.1.1 Problem Definition:

Of our days finding the convenience house for satisfy our need become a big problem. Because
most of the time the building may not accomplish the customers requirement. It is in this optic,
The DreamHome leader of the building make available to theses customer a high standing of house
from different model to social price. Therefore all the procedure to get the information relative to
the different model and offer available goes a lot of procedure and it is time consuming also. So
how to facilitate all those manual procedure?

1. 2. Problem Description:

To overcome the above mentioned problem we have introduced an online booking application for
the entire booking management of houses “DreamHome” which is a web application that allows
the customers to book house in just clicking few buttons. DreamHome makes things easier for the
customer it provides a broad knowledge on the different offer available and make a booking
without passing to any intermediate, and manage efficiently his time by a simple click. The
customer has privilege to choose any design that he would like and see the characteristics. After
this step the application redirects to the order place for the customer to confirm the order and take
and generate an appointment for before to finalize the process for the payment.

Objective of DreamHome:

Our main objective of this application is to completely digitize the manual booking of house to
make customer satisfied by buying home responding to his requirement without passing through
any agency. Also to provide a customer friendly application.

1. Uniquely identify customers

2. Select preferred house
3. Place order
4. Having an appointment for visiting
5. Make a payment and billing
Modules of DreamHome:

1. Customer Registration Module:

Customer registration module is the module that allows the customer to provide the details
of customer to create a user-Id to login into the application for further proceedings.
2. Customer Login Module:
The customer login module is the module that allows the customer to login into the
application by a user-Id and password for the further proceedings.
3. Show Module:
Show module is the module that shows the customer the different model of houses
available with the price tags.
4. profile Module:
Profile module is the module that provide all the information about a particular customer
and the booking has been made by him
5. Payment Module:
Payment module is the module for the payment gateway portal which will be possible for
payments using Pay-Pal gateway.
6. Admin Module:
Admin module is the module exclusive for admin for performing special functions with
the applications and to maintain the application.
Admin Login:
Admin login is the module for providing the login for admin with admin Id and password
who only has the privilege to make changes to application to perform the following
functions:
a) Add Product:
Add product is the function that enables the admin to add a product on the show page
b) Update Product:
Update product is the function that enables the admin to edit a product on the show
page and bring some modification.

c) Delete Product:
 Delete product is the function that enables the admin to delete a product on the show
page
d) View Customer details:
View customer details are the function that enables the admin to view all the registered
customers’ details.
e) Report generation:
The report generation is the function that enables the admin to generate the report for
the different event happed according the date.
Admin can generate the following report:
 Customer
 Booking report
 Payment report

2. System Study:

2.1 Existing System

The existing system of house management system lacks computerized booking management
online which has to be done manually through an intermediate or an agency which is not
customer friendly and also the customers are restricted with a confined set of options. And also
the existing system of house is time consuming.
2.2 Proposed System
The proposed system introduces an online house booking system which is completely
computerized which deals with customer friendly application which allows the customers to
choose what type of model ‘house’ they would like to prefer and place the order and get an
appointment to validate his requirement before to proceed the payment. This eliminates the
manual booking and confusions also the time that is wasted, which is convenient for the
customers to get a house at the necessity. The proposed system also provides huge security

2.3 Data Flow Diagram

 The DFD takes an input-process-output view of a system i.e. data objects flow
into the software, are transformed by processing elements, and resultant data objects
flow out of the software.

Data objects represented by labeled arrows and transformation are

represented by circles also called as bubbles. DFD is presented in a hierarchical
fashion i.e. the first data flow model represents the system as a whole. Subsequent
DFD refine the context diagram (level 0 DFD), providing increasing details with each
subsequent level.

The DFD enables the software engineer to develop models of the information
domain & functional domain at the same time. As the DFD is refined into greater
levels of details, the analyst perform an implicit functional decomposition of the
system. At the same time, the DFD refinement results in a corresponding refinement
of the data as it moves through the process that embody the applications.

A context-level DFD for the system the primary external entities produce
information for use by the system and consume information generated by the system.
The labeled arrow represents data objects or object hierarchy.

RULES FOR DFD:

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions

 Reads left to right and top to bottom.

 Identify all inputs and outputs.

 Identify and label each process internal to the system with Rounded circles.

 A process is required for all the data transformation and Transfers.

Therefore, never connect a data store to a data Source or the destinations
or another data store with just a Data flow arrow.

 Do not indicate hardware and ignore control information.

 Make sure the names of the processes accurately convey everything the process is 
Done. There must not be unnamed process.

 Indicate external sources and destinations of the data, with squares.

 Number each occurrence of repeated external entities.

  Identify all data flows for each process step, except simple Record retrievals.

 Label data flow on each arrow.

 Use details flow on each arrow.

 Use the details flow arrow to indicate data movements.

Symbols of Data Flow Diagram

There are only four symbols used to write Data Flow Diagram as follows:
 External Entities –> Rectangular box
 Data Flow –> Arrow headed lines
 Process –> Bubble (Circle or round corner square)
 Data Store –> Narrow opened rectangle

3. System Configuration
3.1 Hardware Configuration

Processor - Intel core (i5)

RAM - 4GB

Hard Disk - 1TB

Mouse - Any pointing device

3.1 Software Configuration

Front End - HTML5, CSS3, Bootstrap, python

Back End - MySQL

Tools - Spring Framework, MySQL Workbench

Operating system - Windows 10

Software - PyCharm IDE, MySQL Workbench

4. Details of Software
4.1 Overview of Front End
 HTML

HTML stands for Hypertext Markup Language, and it is the most widely used language to write
Web Pages.

 Hypertext refers to the way in which Web pages (HTML documents) are linked together.
Thus, the link available on a webpage is called Hypertext.

 As its name suggests, HTML is a Markup Language which means you use HTML to
simply "mark-up" a text document with tags that tell a Web browser how to structure it to
display.

Originally, HTML was developed with the intent of defining the structure of documents like
headings, paragraphs, lists, and so forth to facilitate the sharing of scientific information between
researchers.

Now, HTML is being widely used to format web pages with the help of different tags available
in HTML language.

HTML Tags
As told earlier, HTML is a markup language and makes use of various tags to format the content.
These tags are enclosed within angle braces <Tag Name>. Except few tags, most of the tags have
their corresponding closing tags. For example, <html> has its closing
tag </html> and <body> tag has its closing tag </body> tag etc.

SL Tag & Description

No

1 <!DOCTYPE...>

This tag defines the document type and HTML version.

2 <html>

This tag encloses the complete HTML document and mainly comprises of document
header which is represented by <head>...</head> and document body which is
represented by <body>...</body> tags.
3 <head>
 This tag represents the document's header which can keep other HTML tags like
<title>, <link> etc.
4 <title>

The <title> tag is used inside the <head> tag to mention the document title.
5 <body>

This tag represents the document's body which keeps other HTML tags like <h1>,
<div>, <p> etc.
6 <h1>

This tag represents the heading.

7 <p>

This tag represents a paragraph.

The <!DOCTYPE> Declaration

The <!DOCTYPE> declaration tag is used by the web browser to understand the version of the
HTML used in the document. Current version of HTML is 5 and it makes use of the following
declaration −

There are many other declaration types which can be used in HTML document depending on
what version of HTML is being used. We will see more details on this while discussing
<!DOCTYPE...> tag along with other HTML tags.

DJANGO 2.2

Django is a free and open source web application framework, written in Python. A web
framework is a set of components that helps you to develop websites faster and easier.
When you're building a website, you always need a similar set of components: a way to handle
user authentication (signing up, signing in, signing out), a management panel for your website,
forms, a way to upload files, etc.

Django is a high-level Python Web framework that encourages rapid development and clean,
pragmatic design. Built by experienced developers, it takes care of much of the hassle of Web
development, so you can focus on writing your app without needing to reinvent the wheel. It’s
free and open source.

Ridiculously fast.

Django was designed to help developers take applications from concept to completion as quickly
as possible.

Reassuringly secure.

Django takes security seriously and helps developers avoid many common security mistakes.

Exceedingly scalable.

Some of the busiest sites on the Web leverage Django’s ability to quickly and flexibly scale.

4.2Overview of Back End

SQL is a language to operate databases; it includes database creation, deletion, fetching rows,
modifying rows, etc. SQL is an ANSI (American National Standards Institute) standard language,
but there are many different versions of the SQL language.

What is SQL?
SQL is Structured Query Language, which is a computer language for storing, manipulating and
retrieving data stored in a relational database.
SQL is the standard language for Relational Database System. All the Relational Database
Management Systems (RDMS) like MySQL, MS Access, Oracle, Sybase, Informix, Postgres and
SQL Server use SQL as their standard database language.

Also, they are using different dialects, such as −

 MS SQL Server using T-SQL,

 Oracle using PL/SQL,
 MS Access version of SQL is called JET SQL (native format) etc.
Why SQL?
SQL is widely popular because it offers the following advantages −

 Allows users to access data in the relational database management systems.

 Allows users to describe the data.

 Allows users to define the data in a database and manipulate that data.

 Allows embedding within other languages using SQL modules, libraries & pre-compilers.

 Allows users to create and drop databases and tables.

 Allows users to create view, stored procedure, functions in a database.

 Allows users to set permissions on tables, procedures and views.

SQL Process
When you are executing an SQL command for any RDBMS, the system determines the best way
to carry out your request and SQL engine figures out how to interpret the task.

There are various components included in this process.

These components are −

 Query Dispatcher
 Optimization Engines
 Classic Query Engine
  SQL Query Engine, etc.
A classic query engine handles all the non-SQL queries, but a SQL query engine won't handle
logical files.

Following is a simple diagram showing the SQL Architecture −

SQL Commands
The standard SQL commands to interact with relational databases are CREATE, SELECT,
INSERT, UPDATE, DELETE and DROP. These commands can be classified into the following

Groups based on their nature −

DDL - Data Definition Language

Sr.No. Command & Description

1 CREATE
 Creates a new table, a view of a table, or other object in the
database.

2 ALTER

Modifies an existing database object, such as a table.

3 DROP

Deletes an entire table, a view of a table or other objects in

the database.

DML - Data Manipulation Language

Sr.No. Command & Description

1 SELECT

Retrieves certain records from one or more tables.

2 INSERT

Creates a record.

3 UPDATE

Modifies records.

4 DELETE

Deletes records.

DCL - Data Control Language

Sr.No. Command & Description

1 GRANT
 Gives a privilege to user.

2 REVOKE

Takes back privileges granted from user.

System Design

5.1 Architectural Design

Register for
Booking House Details
Booking
Details
 5.2 Use Case Analysis

A UML use case diagram is the primary form of system/software requirements for a new
software program under developed. Use cases specify the expected behavior (what), and not the
exact method of making it happen (how). Use cases once specified can be denoted both textual
and visual representation (such as UML). A key concept of use case modeling is that it helps us
design a system from end user's perspective. It is an effective technique for communicating
system behavior in the user's terms by specifying all externally visible system behavior.
A use case diagram is usually simple. It does not show the detail of the use cases:
 It only summarizes some of the relationships between use cases, actors, and systems.
 It does not show the order in which steps are performed to achieve the goals of each use
case.
As said, a use case diagram should be simple and contains only a few shapes. If yours contain
more than 20 use cases, you are probably misusing use-case diagram.
A UML use case diagram is the primary form of system/software requirements for a new
software program under developed. Use cases specify the expected behavior (what), and not the
exact method of making it happen (how). Use cases once specified can be denoted both textual
and visual representation (such as UML). A key concept of use case modeling is that it helps us
design a system from end user's perspective. It is an effective technique for communicating
system behavior in the user's terms by specifying all externally visible system behavior.
A use case diagram is usually simple. It does not show the detail of the use cases:
 It only summarizes some of the relationships between use cases, actors, and systems.
 It does not show the order in which steps are performed to achieve the goals of each use
case.
As said, a use case diagram should be simple and contains only a few shapes. If yours contain
more than 20 use cases, you are probably misusing use-case diagram.
Purpose of Use Case Diagram
Use case diagrams are typically develop in early stage of development and people often apply
use case modeling for the following purposes:
 Specify the context of a system
 Capture the requirements of a system
 Validate a systems architecture
 Drive implementation and generate test cases
 Developed by analysts together with domain experts

Symbols used in use-case diagram:

1) Actor:
2) Use Case

3) Connection Link

4) Extends

5) Include
5.3 Activity Diagram
Activity diagram is another important diagram in UML to describe the dynamic
aspects of the system.

Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.

The control flow is drawn from one operation to another. This flow can be
sequential, branched, or concurrent. Activity diagrams deal with all type of flow
control by using different elements such as fork, join, etc

Purpose of Activity Diagrams

The basic purposes of activity diagrams is similar to other four diagrams. It

captures the dynamic behavior of the system. Other four diagrams are used to show
the message flow from one object to another but activity diagram is used to show
message flow from one activity to another.

Activity is a particular operation of the system. Activity diagrams are not only used
for visualizing the dynamic nature of a system, but they are also used to construct
the executable system by using forward and reverse engineering techniques. The
only missing thing in the activity diagram is the message part.

It does not show any message flow from one activity to another. Activity diagram
is sometimes considered as the flowchart. Although the diagrams look like a
flowchart, they are not. It shows different flows such as parallel, branched,
concurrent, and single.

The purpose of an activity diagram can be described as −

Draw the activity flow of a system.

 Describe the sequence from one activity to another.
Describe the parallel, branched and concurrent flow of the system.

How to Draw an Activity Diagram?

Activity diagrams are mainly used as a flowchart that consists of activities

performed by the system. Activity diagrams are not exactly flowcharts as they have
some additional capabilities. These additional capabilities include branching,
parallel flow, swimlane, etc.

Before drawing an activity diagram, we must have a clear understanding about the
elements used in activity diagram. The main element of an activity diagram is the
activity itself. An activity is a function performed by the system. After identifying
the activities, we need to understand how they are associated with constraints and
conditions.

Before drawing an activity diagram, we should identify the following elements −

Activities
Association
Conditions
Constraints
 5.4 Sequence Diagram

Actor

A type of role played by an entity that interacts with the subject (e.g., by
exchanging signals and data)

External to the subject (i.e., in the sense that an instance of an actor is not a part of
the instance of its corresponding subject).

Represent roles played by human users, external hardware, or other subjects.

Note that:

An actor does not necessarily represent a specific physical entity but merely a
particular role of some entity

A person may play the role of several different actors and, conversely, a given
actor may be played by multiple different person.
Lifeline

A lifeline represents an individual participant in the Interaction.

Activations

A thin rectangle on a lifeline) represents the period during which an element is

performing an operation.

The top and the bottom of the of the rectangle are aligned with the initiation and
the completion time respectively
Call Message

A message defines a particular communication between Lifelines of an Interaction.

Call message is a kind of message that represents an invocation of operation of

target lifeline.

Return Message

A message defines a particular communication between Lifelines of an Interaction.

Return message is a kind of message that represents the pass of information back
to the caller of a corresponded former message.

Self-Message

A message defines a particular communication between Lifelines of an Interaction.

Self-message is a kind of message that represents the invocation of message of the

same lifeline.
Recursive Message

A message defines a particular communication between Lifelines of an Interaction.

Recursive message is a kind of message that represents the invocation of message

of the same lifeline. It's target points to an activation on top of the activation where
the message was invoked from.

Create Message

A message defines a particular communication between Lifelines of an Interaction.

Create message is a kind of message that represents the instantiation of (target)

lifeline.
5.5 Input Design

In the input design, user-oriented inputs are converted in to a computer based

format. It also includes determining the record media, method of inputs, speed of
capture and entry on to the screen. Online data entry accepts commands and data
through a keyboard. The major approach to input design is the menu and the
prompt design. In each alternative, the user’s options are predefined. The data flow
diagram indicates logical date flow, data stores, source and destination. Input data
are collected and organized in to a group of similar data. Identified input media are
selected for processing. In this software importance is given to develop Graphical
User Interface (GUI), which is an important factor in developing efficient and user-
friendly software. For inputting user data attractive forms are designed. User can
also select desired options from the menu, which provides all possible facilities.

5.6 Output Design

In the output design, the emphasis is on producing a hard copy of the information
requested or displaying the output on the CRT screen in a predetermined format.
Two of the most output media today are printers and the screen. Most users now
access their reports from a hard copy or screen display. Computer’s output is the
most important and direct source of information to the user, efficient, logical,
output design should improve the systems relations with the user and help in
decision-making. As the outputs are the most important source of information to
the user, better design should improve the system’s relation and also should help in
decision-making. The output device’s capability, print capability, response time
requirements etc should also be considered form design elaborates the way output
is presented and layout available for capturing information. It’s very helpful to
produce the clear, accurate and speedy information for end users.
5.7 Database Design

6. Source Code

7. Testing

Testing is a process of executing a program with the intent of finding an error.

Testing is a crucial element of software quality assurance and presents ultimate
review of specification, design and coding. System Testing is an important phase.
Testing represents an interesting anomaly for the software. Thus a series of testing
are performed for the proposed system before the system is ready for user
acceptance testing. A good test case is one that has a high probability of finding an
as undiscovered error. A successful test is one that uncovers an as undiscovered
error.

Testing Objectives:

 Testing is a process of executing a program with the intent of finding an

error
 A good test case is one that has a probability of finding an as yet
undiscovered error
 A successful test is one that uncovers an undiscovered error

Testing Principles:
  All tests should be traceable to end user requirements.
 Tests should be planned long before testing begins
 Testing should begin on a small scale and progress towards testing in large
 Exhaustive testing is not possible
 To be most effective testing should be conducted by a independent third
party.

The primary objective for test case design is to derive a set of tests that has the
highest livelihood for uncovering defects in software. To accomplish this objective
two different categories of test case design techniques are used. They are: White
box testing and Black box testing.

White-box testing:

White box testing focus on the program control structure. Test cases are derived to
ensure that all statements in the program have been executed at least once during
testing and that all logical conditions have been executed.

Black-box testing:

Black box testing is designed to validate functional requirements without regard to

the internal workings of a program. Black box testing mainly focuses on the
information domain of the software, deriving test cases by partitioning input and
output in a manner that provides through test coverage. Incorrect and missing
functions, interface errors, errors in data structures, error in functional logic are the
errors falling in this category.

Testing strategies:
A strategy for software testing must accommodate low-level tests that are
necessary to verify that all small source code segment has been correctly
implemented as well as high-level tests that validate major system functions
against customer requirements.

Testing fundamentals:

Testing is a process of executing program with the intent of finding error. A good
test case is one that has high probability of finding an undiscovered error. If testing
is conducted successfully it uncovers the errors in the software. Testing cannot
show the absence of defects, it can only show that software defects present.

Testing Information flow:

Information flow for testing flows the pattern. Two class of input provided to test
the process. The software configuration includes a software requirements
specification, a design specification and source code. Test configuration includes
test plan and test cases and test tools. Tests are conducted and all the results are
evaluated. That is test results are compared with expected results. When erroneous
data are uncovered, an error is implied and debugging commences.

Unit testing:

Unit testing is essential for the verification of the code produced during the coding
phase and hence the goal is to test the internal logic of the modules. Using the
detailed design description as a guide, important paths are tested to uncover errors
within the boundary of the modules. These tests were carried out during the
programming stage itself. All units of Vienna SQL were successfully tested.

Integration testing:
Integration testing focuses on unit tested modules and build the program structure
that is dictated by the design phase.

System testing:

System testing tests the integration of each module in the system. It also tests to
find discrepancies between the system and it’s original objective, current
specification and system documentation. The primary concern is the compatibility
of individual modules. Entire system is working properly or not will be tested here,
and specified path ODBC connection will correct or not, and giving output or not
are tested here these verifications and validations are done by giving input values
to the system and by comparing with expected output. Top-down testing
implementing here.

Acceptance Testing:

This testing is done to verify the readiness of the system for the implementation.
Acceptance testing begins when the system is complete. Its purpose is to provide
the end user with the confidence that the system is ready for use. It involves
planning and execution of functional tests, performance tests and stress tests in
order to demonstrate that the implemented system satisfies its requirements.

Tools to special importance during acceptance testing include:

 Test coverage Analyzer – records the control paths followed for each test
case.
 Timing Analyzer – also called a profiler, reports the time spent in various
regions of the code are areas to concentrate on to improve system
performance.
  Coding standards – static analyzers and standard checkers are used to inspect
code for deviations from standards and guidelines.

7.1 Test Cases

Test cases are derived to ensure that all statements in the program have been
executed at least once during testing and that all logical conditions have been
executed. Using White-Box testing methods, the software engineer can drive test
cases that guarantee that logical decisions on their true and false sides. Exercise all
logical decisions on their true and false sides. Execute all loops at their boundaries
and within their operational bounds. Exercise internal data structure to assure their
validity. The test case specification for system testing has to be submitted for
review before system testing commences.

8. Implementation

Implementation is the stage where the theoretical design is turned into a working system. The most
crucial stage in, achieving a new successful system and in giving confidence on the new system
for the users that will work efficiently and effectively.
The system can be implemented only after thorough testing is done and if it is found to work
according to the specification. It involves careful planning, investigation of the current system and
its constraints on implementation, design of methods to achieve the change over and an evaluation
of change over methods a part from planning. Two major tasks of preparing the implementation
are education and training of the users and testing of the system.
The more complex the system is being implemented, the more involved will be the systems
analysis and design effort required just for implementation. The implementation phase comprises
of several activities. The required hardware and software acquisition is carried out. The system
may require some software to be developed. For this, programs are written and tested. The user
then changes over to his new fully tested system and the old system is discontinued.
9. Screen Shots

Conclusion

To conclude, the computerized online booking system of the Co-operate as of now is reliable in
making the customers of house baying – DreamHome in successfully booking their house in just
one click. When compared to the manual work done by the Co-operate our system reduces the
work load of the co-operate making them beneficial. Therefore, this system is now a complete
booking management application that is mainly for providing the customers with an integrated
online booking system for buying house where they are allowed to choose the type of houses over
different models. The system will collect the details of the customer as when logged in and would
assist them throughout the application about the details and cost and availability and if the
customer is interested to book their choice of house and payment bill will be generated. This
system can be further improvised in making banking transactions such as Net banking facility and
Credit card transactions and also to be implemented as mobile application as its future
enhancement.

Bibliography

User Manual