Professional Documents
Culture Documents
Project Report Finance Expense Manager Uvais
Project Report Finance Expense Manager Uvais
by
Uvais Saifi
(Roll No. 1810201010)
Submitted to:
INVERTIS UNIVERSITY
Invertis Village, Bareilly - Lucknow National Highway, NH-24, Bareilly,
Uttar Pradesh - 243123
JUNE - 2021
Department of Computer Applications, Invertis University, Bareilly
2
CERTIFICATE
This is to certify that Uvais Saifi , student of BCA course of Faculty of Computer
Applications, Invertis University, Bareilly, has undergone a mandatory “SIXTH
SEMESTER PROJECT” in our esteemed organization.
During the course of his project development he has completed a project on “FINACE
EXPENCE MANAGER”.
ACKNOWLEGDEMENT
I am also thankful to Ms. Kalpana Gangwar for their guidelines and valuable efforts in
completion of my project.
I sincerely thank him for responding great confidence and faith in my work and being
with me to encourage and guide me to successful project completion.
I should also like to thank Mr. Jitendra Chaudhary, HOD, Department of Computer
Applications for their support and all our friends and colleagues who have created an
atmosphere to encourage me from time to time making our work easy.
Thank You…..
Signature:
LIST OF TABLES
5. Table 5 Page No
6. Table 6 Page No
LIST OF FIGURES
Department of Computer Applications, Invertis University, Bareilly
5
1. Waterfall Model 17
2. ER Diagram 18
TABLE OF CONTENTS
Department of Computer Applications, Invertis University, Bareilly
6
CHAPTER 1: INTRODUTION
INTRODUCTION
AIM
CHAPTER 2:
PROBLEM DEFINITION
When We were creating this project We faces many problems on the server side when we
want to create database on the myphpadmin as a local host we faces lots of issues
regarding the creating and importing the files in our local drive .
As we faces these kind of issue it is common for the organization’s project
One engineer gave an example of a process that takes twice as long on the current server.
When asked if server performance was ever considered as a root cause and investigated
by support, the engineers presumed it had but no one knew who had raised a ticket.
The project was already beginning to take on a whole new direction.
Once contacted, the support team investigated, found, and removed a rogue process and
the engineering team saw an immediate improvement in performance, retracting their
request for the new server.
Without this step in the definition process, a needless project could have been completed,
introducing unnecessary costs for the engineering team. The engineering team also
introduced a new process for handling the investigation of anomalies in their production
process.
Once the root causes or problems are identified, a decision needs to be made about which
problems to address first. The decision-making approach may differ from one company
to another for example; simply using your gut, forming a holistic approach, or group
consensus.
When final decisions are made, they should be documented and communicated to the
entire team so everyone is on the same page. This phase will form the Problem
Statement, a clear and short description of the issues that need to be addressed by a
problem-solving team.
CHAPTER 3
1) Operational Feasibility
2) Technical Feasibility
3) Economical Feasibility
OPERATIONAL FEASIBILITY
TECHNICAL FEASIBILITY
This involves questions such as whether the technology needed for the system exists, how
difficult it will be to build, and whether the firm has enough experience using that
technology. The assessment is based on outline design of system requirements in terms of
input, processes, output, fields, programs and procedures. This can be qualified in terms
of volume of data, trends, frequency of updating in order to give an introduction to the
technical system. The application is the fact that it has been developed on windows XP
platform and a high configuration of 1GB RAM on Intel Pentium Dual core processor.
This is technically feasible .The technical feasibility assessment is focused on gaining an
understanding of the present technical resources of the organization and their
applicability to the expected needs of the proposed system. It is an evaluation of the
hardware and software and how it meets the need of the proposed system
ECONOMICAL FEASIBILITY
CHAPTER 4:
PROPOSED SYSTEM
system at registration time, the user will be provided id, which will
a day to day basis. This application takes Income from user and
will cut if from your income and give new daily expense allowed
add the savings amount which you had saved for some particular
SCOPE
CHAPTER 5 :
SOFTWARE REQUIREMENT:
2. LANGUAGE HTML/CSS/PHP
HARDWARE REQUIREMENT:
NUMBER DESCRIPTION
2. PC WITH 2 GB RAM.
CHAPTER 6:
WATERFALL MODEL:
ER DIAGRAM
CHAPTER 7:
$servername = "localhost";
$username = "root";
$password = "";
$dbname = "test";
// Create connection
// Check connection
if ($conn->connect_error) {
echo "<h2 style='text-align:center;'>The connection failed. Please provide proper local server details
and keep the files in the HTDOCS of localhost.<br>In case you want to See the design demo, <a
href='demo.html' style='color:green;'>Please Visit Here</a></h2>";
$today = date("d/m/Y");
$sql = "SELECT id, amount, comment, day, type FROM expense ORDER BY day DESC, type ASC ";
$result = $conn->query($sql);
$sql0 = "SELECT id, amount, comment, day, type FROM expense WHERE day = '$today' ORDER BY
type ASC ";
$result0 = $conn->query($sql0);
// adding expenses for that current day with all sorted catogeries
$money = array("Grocery" => 0, "Entertainment" => 0, "Vehicle" => 0, "Food" => 0, "Miscellaneous"
=> 0, "total" => 0);
$result2 = $conn->query($sql2);
if ($result2->num_rows > 0) {
$k = $row["type"];
} else {
echo 'fao';
?>
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<style>
html,
body {
background-color: #fafbfc;
color: #636b6f;
font-weight: 300;
height: 100vh;
margin: 0;
overflow: auto;
a{
text-decoration: none;
.content {
margin: 0;
width: 100%;
position: relative;
top: 15vh;
/*text-align: center;*/
.title {
font-size: 2em;
.header {
z-index: 1;
background: white;
position: fixed;
top: 0;
left: 0;
width: 100%;
/*font-size: 1.25rem;*/
color: #525c65;
ul {
margin-bottom: 0;
.left {
width: 20%;
float: left;
margin-top: 0;
.right {
float: right;
padding-right: 5vw;
margin-top: 0;
.tabb li {
float: right;
list-style-type: none;
padding: 20px;
.tabb li p {
margin: 0;
padding: 10px;
text-align: center;
cursor: pointer;
padding-right: 5px;
padding-left: 5px;
.btnB {
background: #02ccba;
color: white;
/*width: 7.75rem;*/
text-transform: capitalize;
border-radius: 5px;
margin: 0;
padding: 10px;
text-align: center;
cursor: pointer;
#btnB {
padding-right: 20px;
padding-left: 20px;
.btnB:hover {
.total {
width: 100%;
margin: auto;
.six {
width: 100%;
float: left;
padding-top: 5vh;
padding-bottom: 5vh;
background: #fafbfc
.lapi {
display: none;
.mobi {
display: block;
.hamburger {
display: block;
@media(min-width: 62em) {
.lapi {
display: block;
.mobi {
display: none;
.six {
width: 50%;
float: left;
padding-top: 5vh;
padding-bottom: 5vh;
background: #fafbfc
#piechart {
background: white;
margin: 3vh;
padding: 40px;
text-align: center;
padding-top: 0;
border-radius: .375rem;
#piechart:hover {
cursor: pointer;
.boxx {
color: black;
margin: 3vh;
padding: 40px;
background: white;
border-radius: .375rem;
text-align: center;
.boxx:hover {
cursor: pointer;
input {
margin-bottom: 20px;
padding: 8px;
border-radius: 2px;
font-size: .9em;
select {
margin-bottom: 20px;
padding: 8px;
border-radius: 2px;
font-size: .9em;
</style>
</head>
<body>
<div class="header">
<b style="margin: 0;
padding: 10px;
text-align: center;
cursor: pointer;
padding-right: 5px;
FinEx Manager
</a></b>
margin: 0;
padding: 10px;
text-align: center;
cursor: pointer;
padding-right: 5px;
color: #525c65;">Manager</a></b>
</li>
</ul>
<li>
</a>
</li>
<li>
</a>
</li>
</ul>
</div>
<div class="content">
<div class="total">
<div class="six">
<div class="boxx">
<div>
<div class="">
margin-top: 0;
color: white;
font-weight: 400;
letter-spacing: 1px;
font-size: 1.4em;
line-height: 2.8em;
</div>
<option value="">SELECT</option>
<option value="Grocery">Grocery</option>
<option value="Entertainment">Entertainment,</option>
<option value="Vehicle">Vehicle</option>
<option value="Food">Food</option>
<option value="Miscellaneous">miscellaneous</option>
</select>
<br />
<br />
<br />
padding-left: 20px; box-shadow: 8px 10px 20px 0 rgba(46, 61, 73, .15);border: none;background-
color: #02b3e4;font-size: 105%;">Update</button>
<br />
</form>
</div>
</div>
</div>
</div>
</div>
<div class="six">
<div id="piechart"></div>
</div>
</div>
<div class="container">
<div class="row">
<div class="col-xs-12">
<div class="table-responsive">
<thead>
<tr>
</tr>
</thead>
<tbody>
<?php
if ($result0->num_rows > 0) {
"</td><td>"
. $row["type"] . "</td><td>"
. $row["comment"] . "</td>";
?>
</tbody>
</table>
</div>
<!--end of .table-->
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="col-xs-12">
<div class="table-responsive">
<thead>
<tr>
</tr>
</thead>
<tbody>
<?php
if ($result->num_rows > 0) {
"</td><td>"
. $row["type"] . "</td><td>"
. $row["comment"] . "</td><td>"
. $row["day"] . "</td></tr>";
?>
</tbody>
<tfoot>
<tr>
</tr>
</tfoot>
</table>
</div>
<!--end of .table-->
</div>
</div>
</div>
</div>
<script type="text/javascript">
google.charts.load('current', {
'packages': ['corechart']
});
google.charts.setOnLoadCallback(drawChart);
function drawChart() {
]);
// Optional; add a title and set the width and height of the chart
var options = {
'title': 'Today\'s Expenses by Category, Total Rs:<?php echo $money['total'] ?> ',
'width': 550,
'height': 400
};
chart.draw(data, options);
</script>
</body>
</html>
CHAPTER 8:
OUTPUNT SCREEN-1
OUTPUT SCREEN-2
OUTPUT SCREEN-3
OUTPUT SCREEN-4
OUTPUT SCREEN-5
OUTPUT SCREEN-6
CHAPTER 9 :TESTING
UNIT TESTING
Benefits
TEST CASES
Black-Box Testing:
Black-box testing is a method of software testing that examines the
functionality of an application without peering into its internal
structures or workings. This method of test can be applied virtually
to every level of software testing: unit, integration, system and
acceptance. It typically comprises most if not all higher level
testing, but can also dominate unit testing as well.
Test Procedures:
Specific knowledge of the application's code/internal structure and
programming knowledge in general is not required. The tester is
aware of what the software is supposed to do but is not aware of
how it does it. For instance, the tester is aware that a particular
input returns a certain, invariable output but is not aware of how the
software produces the output in the first place.
White-Box Testing:
Procedures:
White-box testing's basic procedures involves the tester having a
deep level of understanding of the source code being tested. The
programmer must have a deep understanding of the application to
know what kinds of test cases to create so that every visible path is
exercised for testing. Once the source code is understood then the
source code can be analyzed for test cases to be created. These are
the three basic steps that white-box testing takes in order to create
test cases:
CHAPTER 10:
IMPLEMENTATION
HTML
JavaScript
Css
CHAPTER 11:
CONCLUSION
After making this application we assure that this application will help its users to
manage the cost of their daily expenditure. It will guide them and aware them
about there daily expenses. It will prove to be helpful for the people who are
frustrated with their daily budget management, irritated because of amount of
expenses and wishes to manage money and to preserve the record of their daily
cost which may be useful to change their way of spending money. In short, this
application will help its users to overcome the wastage of money
BIBLIOGRAPHY
https://www.tutorialspoint.com/index.htm
https://www.javatpoint.com
https://www.w3schools.com
https://html.com