Professional Documents
Culture Documents
Final Project Report Shivani PDF
Final Project Report Shivani PDF
Final Project Report Shivani PDF
PROJECT PROPOSAL
ON
SALES AND INVENTORY MANAGEMENT SYSTEM
(Online Electronic Store)
BY
SHIVANI SHRIVASTAVA
[Enrollment No. :166248840]
Under Guidance
of
GAYATRI KUMARI GUPTA
(Note: All entries of the proforma of approval should be filled up with appropriate and complete information.
Incomplete proforma of approval in any respect will be summarily rejected.)
………………………………………………………………
………………………………………………………………
……………………………………………………………………………………………………………….
(**Note: At any given point of time, a guide should not provide guidance for more than 5 MCA students of IGNOU)
8. Project title of the Mini Project (MCS-044) and the s/w used………………………………………………
…………………………………………….
Signature, Designation, Stamp of the
Project Proposal Evaluator
Approved Not Approved Date: …………………….
Suggestions for reformulating the Project:
CERTIFICATE OF ORIGINALITY
submitted to Indira Gandhi National Open University in partial fulfilment of the requirement
The matter embodied in this project is genuine work done by the student and has not been
submitted whether to this University or to any other University / Institute for the fulfilment of the
………………………. ...…………………….
Enrolment No…………
ACKNOWLEDGEMENT
I would like to take this opportunity to express my gratitude toward all the people who
have in various ways, helped in the successful completion of my project.
I must convey my gratitude to prof. Gayatri Kumari for giving me the constant sources
of inspiration and help in preparing the project , personally correcting my work and
providing encouragement through the project.
I also thank me all faculty members for steering me through the tough as well as easy
phases of project in a result oriented manner with concern attention.
Thanking You
ABSTRACT
Sales and Inventory Management System is one of the basic problems in almost every
company. Before computer age and integration, paper tables and paperwork solutions were
being used as inventory management tools. These we very far from being a solution,
took so much time, even needed employees just for this section of organization. There was
no an efficient solution available in the many companies during these days. Every process
was based on paperwork, human fault rate was high, the process and the tracing the
inventory losses were not possible, and there was no efficient logging systems. After the computer
age, every process is started to be integrated into electronic environment. Now we have
qualified technology to implement new solutions to these problems. Software based
systems bring the advantages of having the most efficient control with less effort and
employees. These developments provide new solutions for also inventory systems in
this context. In this paper, a new solution for Sales and Inventory System(SIMS) is
designed and implemented.
The Sales and Inventory System is an automated version of manual sales
and inventories system. It can handle all details about an Inventory. The details
includes Inventory personnel details, Sales details, Products details, Annual transection
details ,etc. In case of manual system they need a lot of time, manpower etc. Here
almost all work is computerized. So the accuracy is maintained. It is the job of the
administrator to insert update and monitor the whole process. When a user log into the system, He
would only view details of the Inventory. He can't perform any changes. Sales and
Inventory Management System is software which is helpful for Inventories. In the
current system all the activities are done manually. It is very time consuming and
costly. Our Sales and Inventory Management System deals with the various activities
related to the Inventories.
There are mainly 2 modules in this software
• Inventory Module
• Sales Module
Online Sales and
Inventory Management
System
MCSP – 060
PROJECT PROPOSAL
ON
BY
SHIVANI SHRIVASTAVA
[Enrollment No. :166248840]
Under Guidance
of
GAYATRI KUMARI GUPTA
Table of Contents
1.Introduction
1.1 Background……………………………………………………………………...….....................04
1.2 Objective………………………………………………………………………...….....................05
1.3 Purpose and Scope of Project…………………………………………………...….....................06
2. System Analysis
2.1 Identification of Need……………..……………………………………...…………………....…07
2.2 Preliminary Investigation…………………………………………………………...…….............07
2.3 System Study……………………………………….…………………………….........................08
2.4 Feasibility Study……………………………………….……………………………....................09
2.5 Project Planning……….……………………………………………………………………........10
2.6 Project Scheduling………………………..…………………………….....……………………...11
2.7 Software Requirement Specification…………………………………………….....……….........12
3. Data Model
3.1 Data Flow Diagram……………..…………………………………………...…………………....13
3.2 Context Flow Diagram………..…………………………………………...……………………..18
3.3 Design Flow Chart………..…………………………………………...………………..………..19
3.4 Entity Relationship Model…………………………………………………………...……...........20
3.5 Use Case Diagram……………………………………….……… ……………….........................21
3.6 Class Diagram……….…………………………………………………………………................23
3.7 Activity Diagram……………………………………….....………...............................................24
3.8 State Diagram……………………………………………………………………………….........25
4. System Design
4.1 Modularization Detail…………………………………………………….……………................26
4.2 Data Dictionary………..………………………………………………………………..…..........31
10. Bibliography……………………………………………….……………………………....……….133
11. Conclusion………………………………………………….……………………………….….…..134
12. Appendix……………………………………………….…………………………………..………135
REFFERENCES………………………………………………………………………………..……..136
❖ 1.1 Background :
The “Sales and Inventory Management System” has been developed to override the problem prevailing
and practicing manual system. This software is supported to eliminate and in the same cases reduce the
hardship faced by the existing system. Moreover this system is designed for the Particular Need of
Company to carry out operation in a smooth and effective manner.
Every Organization, whether big or small, has challenge to overcome and managing the information of
Customer, Inventory, Sales, Supplier, Payment. Every “Sales and Inventory Management System” has
Different inventory needs, Therefore we design exclusive employee management system that are
adapted to your managerial requirement. This is design to assist in strategic planning, and will help you
ensure that yourorganization is equipped with the right level of information and details for your future
goal. Also, for those busy executive who are always on the go. Which will allow you to manage your
work force anytime at all times. This system will ultimately allow you to better manage resource.
“Sales And Inventory Management System” as describe above, can lead to error free, Secure reliable
and fast Management system. It can assist to user to concentrate on their other activities rather to
concentrate on the record keeping. Thusit willhelp Organization in better utilization of resources.
The “Sales and Inventory Management System” has been developed to override the problems prevailing
in the practicing manual system. Moreover the system is designed for the particular need of the company
to carry out operations in a smooth and effective manner.
❖ 1.2 Objective :
The main objective of “Sales and Inventory Management System” is to manage the detail of Purchasing,
Payment, Supplier, Customer, Sales. It manage all the information about Purchasing, Inventory, Sales,
Purchasing. The Project is totally built at administrative end and thusonly the administrator is guarantee
to access. The purpose of project build and application program to reduce the manual work for
Customer Sales.
❖ 1.3 Purpose :
The purpose of the project is to build asales and inventory management software in order to reduce
the manual work for maintaining the details of purchasing, inventory and many more tasks. This
software will help the Electronic Store to complete all works fast and efficient without time wastage.
It provide all features and help to both hotel and its subsidiaries.
❖ 1.3 Scope :
It may help collecting perfect management in detail. In a very short time, the collection will be
obvious , Simple & sensible. It will help person to know the management of passed year
perfectly and vividly. It will also help in current all works and relative to “Sales and Inventory
Management System”. It will also reduced the cost of collecting and management & Collection
Our Project aim at Business process automation, i.e, we have tried to computerize various
• In Computer System the person to fill the various forms and number of copies of the forms
• In Computer System , It is not necessary to create the manifest but we can directly print it, which
• The system Generate types of information that can be used for various purpose.
2. SYATEM ANALYSIS
Online Electronic Store (Sales and Inventory Management System) describe above can lead to error
free, secure reliable and fast management system for shopping.
It can assist the staff to concentrate on their related (for shopping) activities rather to
concentrate on record and report of issues Product, registration, and supplier. This will help
organization in better utilization of human resources.
In this phase, the user identifies the need for new or improve system. In large organization this
identification may be a part of a system planning Process.
Benefit to Organization :
The Organization will obviously be able to gain benefit such as a saving in operation cost,
reduction in paper work, better utilization of human resources and more represent able image
increase goodwill. The other benefit are improved services and faster and better access to up-to
date information.
Initial Cost :
The initial cost of setting up the system will include the cost of hardware (server/client, Network
adapter and related hardware), Software (Server OS , add-on software, utilization) & labor (setup
&maintenance ). The same has to bear by the organization.
Running Cost :
Besides, the initial cost the long term cost will include the running cost for system including
the AMC, Product Charges, Cost for human resources, Cost for update/renewals of various
related software.
System Analysis is a detailed study of the various operations performed by a system and
their relationships within and outside of the system. Here the key question is- what all problems exist in
the present system? What must be done to solve the problem? Analysis begins when a user or manager
begins a study of the program using existing system.
During analysis, data collected on the various files, decision points and transactions
handled by the present system. The commonly used tools in the system are Data Flow Diagram,
interviews, etc. Training, experience and common sense are required for collection of relevant
information needed to develop the system. The success of the system depends largely on how clearly
the problem is defined, thoroughly investigated and properly carried out through the choice of solution.
A good analysis model should provide not only the mechanisms of problem understanding but also the
frame work of the solution. Thus it should be studied thoroughly by collecting data about the system.
Then the proposed system should be analyzed thoroughly in accordance with the needs. System analysis
can be categorized into four parts.
• System planning and initial investigation
• Information Gathering
• Applying analysis tools for structured analysis
• Feasibility study
• Cost/ Benefit analysis.
In the current system we need to keep a number of records related to the Inventory and want to enter
the details of the Inventory and the marks manually. In this system only the teacher or the school
authority views the mark of the Inventory and they want to enter the details of the Inventory. This is
time consuming and has much cost.
➢ Technical Feasibility :
Technical Feasibility is concern with the availability of hardware and software required for the
development of the system, to see compatibility and maturity of the technology proposed to be
used and to see the availability of the required technical manpower to develop the system.
After the study we come to conclusion that we proceed further with the tool and
develop environment chosen by us. This was important in our cases as we were working on
two various phases of the department that will need to be integrated in future to make an
extended system.
➢ Operational Feasibility :
Operational Feasibility is just about problem that may arises during operation. There are two
accept related with this issue :
• What is the probability that the situation developed may not be put to user or may not
work ?
➢ Economic Feasibility :
It is the measure of cost effectiveness of project. The economic feasibility is nothing but
judging whether the possible benefit of solving the problems is worthwhile of not. At the
feasibility study level, it is impossible to estimate the cost because member’s requirement and
alternative situation has not been identified at this stage. However, When the specific
requirement and situation has been identified, the analyst weight the cost and benefit of all
situation, this is called “Cost benefit analysis.”
1.Within the Organization : How the Project is to be implemented ? What various constrain
(time cost, staff)? What is market strategy ?
2. With respect to the customer :weekly or timely meeting with the customer with presentation
on status report. Customer feedback is also taken and further modification and developments.
Are done. Project milestone and deliverables are also present to customer.
For a successful software project, the following step can be followed :
• Select a project :
➢ Identifying project’s aim and objective
➢ Understanding requirement and specification
➢ Method of analysis , design and implementation
➢ Testing Technique
➢ Documentation
• Project milestone and delivered
• Budget Allocation
• Project Estimate
➢ Cost
➢ Time
➢ Size of Code
➢ Duration
• Resource Allocation
➢ Hardware
➢ Software
➢ Previous relevant project information
➢ Digital shopping
Gantt Chart :
Gantt chart are a project control technique that can be used for several purpose including scheduling
and planning. Gantt chart is also known bar chart with each box representing an activity.
Gantt charts mainly used to allocate resources to activities. The resources allocated to activities include
staff, hardware, and software. Gantt charts (named after its developer Henry Gantt) are useful for
resource planning. A Gantt chart is special type of bar chart where each bar represents an activity. The
bars are drawn along a timeline. The length of each bar is proportional to the duration of the time
planned for the corresponding activity.
Preliminary Investigation
Investigation
Analysis
Design
Coding
Testing
Documentation
Implementation
Functional Requirement :
• Input Output :-
➢ System shall have a from to accept the customer detail.
➢ System shall have a form to accept the plant details.
➢ System shall display transaction details.
➢ System should provide facility for changes of address.
Processing :
➢ System should automatically generate the bill.
➢ System should inform the pending order and makes changes if the order is dispatched.
Error Handling :
➢ Should report any error on duplicate primary keys.
➢ Should report any data type mismatch any field on the form.
➢ Should report on any ‘Invalid dates’.
➢ Should report any violantation of authorization of right.
➢ Should report any Invalid Login Error.
3. DATA MODEL
A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an
Information System. A data flow diagram can also be used for the visualization of Data Processing. It is
common practice for a designer to draw a context-level DFD first which shows the interaction between
the system and outside entities. This context-level DFD is then "exploded" to show more detail of the
system being modeled.
A DFD represents flow of data through a system. Data flow diagrams are commonly used during
problem analysis. It views a system as a function that transforms the input into desired output. A DFD
shows movement of data through the different transformations or processes in the system.
Dataflow diagrams can be used to provide the end user with a physical idea of where the data they
input ultimately has an effect upon the structure of the whole system from order to dispatch to restock
how any system is developed can be determined through a dataflow diagram. The appropriate register
saved in database and maintained by appropriate authorities.
DATA Diagram Notation
FUNCTION
DATABASE
DATAFLOW
Input/Output
Feedback
Feedback
Sales and
Inventory Transaction Checking
Management
System
Report Review
Feedback
Item
Information
Sales Manager
Admin Feedback
Account Detail
Log In System
New/Categories Detail
New
Price
Change Item Add New
Price Item
Categories
Feedback Feedback
Authenticatio
LogIn
n
LogIn Admin
System Detail
Logou
User t
Username, Feedback
Password
Admin
User
User
Create Feedback
User
User Info
Admin Create a
new user
Feedback
Item
Sales New
Item Feedback
Item’s Detail
Admin Add New
Item
Feedback
LogIn System
Report
Detail
LogIn
System
Username/password Feedback
Exception Create
A Context Flow Diagram is a top level (also known as level 0) data flow diagram. It only contains
one process node (process 0) that generalizes the function of the entire system in relationship to external
entities. A Context Flow Diagram is a diagram that shows the inputs and output of a system. It shows all
the external entities with the system and the data flows between these entities and the system.
Sales and
inventory
management
system
Data base
START
Input Username
& password
Check Username
password on users Display Error
table on db
True
False
True Status =1
False
Display Status=2
Administrator main
Display Inventorary
Manger
STOP
Login_username
#login_id
userpwd
User_name Log In
user_id
Role id
User_mob user has roles
Role_name
User_ema
Per-id
il
permision
User_add n Per role id
Per
cus_name module
manag Inv_date
e
Cus_id
Pay_date Inv_num
Cus_mobil inventory
payment
e custome Inv_id
Pay_id
r
Cus_add ha Inv_ite
Pay_amt
s m
Cus_email
sales
Sales_desc
Sales_type
Sales_id
Checks
Tracks Order
Dispatch Order On
Send Invoice
Update Record
Studies Requirement
Make list of
Order
Makes Payment
Invoice
Order Detail
Orderno.
Credit/Debit Cash On Delivery Materialqty
Materialvalue
Number
CalcSubtotal
Type
Expiry Date
Validating
Product
Productcode
ProductName
ProductDetail
Productprice
Login PAGE
Receive Conformation
Receive Conformation
Logout
Validation
4. SYSTEM DESIGN
❖ 4.1 Modularization Detail :
➢ Modules of Login
➢ Design Assumption:
This module is designed with the intension to provide security to user. The Login contains
the necessary information of the tables and forms included in the applications.
➢ Identification of Module
• Username:
Allows user to enter their name.
• Password:
Allows user to enter their valid password.
Structure chart is a graphical representation of the control logic of processing functions or modules
representing a system. It is one of the most commonly used methods for system design.
In a structure chart, each program module is represented by a rectangular box. Modules at the top level
of the structure chart call the modules at the lower level. The connections between modules are
represented by lines between the rectangular boxes. The connection describes data flows between the
called and calling modules.
LOGIN
MASTER PAGE
➢ Modules of Category :
Design Assumption:
This module of Application will displays the category of the product under which it belongs. It also
maintains the measure type which displays how different types of products are measured
➢ Identification of Modules:
Category Id : Id of category.
Category Name : It displays the category name.
Measure Name : Name of the measurement
➢ Structure chart showing the hierarchy of modules.
MASTER PAGE
CATEGORY
➢ Modules of product :
Design Assumption:
This module is used to add ,save ,delete the products .This module is also used view the whole stock
by the use of grid.
➢ Identification of Modules:
MASTER PAGE
PRODUCT
➢ Modules of Customer:
Design Assumption:
This module stores and maintains the details of the customers.
➢ Identification of Modules:
ORDER
CUSTOMER
➢ Identification of Modules:
➢ Security Module :-
Login Table
Category Table
Product Table
Logic Diagram : -
START
Log In
Post Detail to
View patient database
Report
Finished
The following steps are various guidelines for User Interface Design: -
1. Primary Design Phase: In this phase, the system is designed at block level. The blocks are
created on the basis of analysis done in the problem identification phase. Different blocks are
created for different functions emphasis is put on minimizing the information flow between
blocks. Thus, all activities which require more interaction are kept in one block.
2. Secondary Design Phase: In the secondary phase the detailed design of every block is
performed.
The general tasks involved in the design process are the following:
• Design various blocks for overall system processes.
• Design smaller, compact and workable modules in each block.
Screen Layout of Online Electronic Store (Sales & Inventory Management System) : -
➢ Home Page :
➢ Checkout Page :
➢ Payment Page :
➢ Login Page :
➢ SignUp Page :
➢ Purchase Detail :
The unit testing done included the testing of the following items : -
• Functionality of the entire module/forms.
• Validations for user input.
• Checking of the Coding standards to be maintained during coding.
• Testing the module with all the possible test data.
• Testing of the functionality involving all type of calculations etc.
• Commenting standard in the source files.
will uncover error in the software. As a secondary benefit testing demonstrate that software
function appear to working according to specification, that behavioral and performance
requirement. Appear to have been met. In Addition, data collecting as testing is conducted provide
a good indication of software reliability and some indication of software quality as a whole. But
testing cannot show the absence of error and defect, it can show .
➢ signup.php :
<?php
include('dbconnection.php');
session_start();
if(isset($_POST['submit']))
{
$firstname=$_POST['firstname'];
$lastname=$_POST['lastname'];
$username=$_POST['username'];
$password=$_POST['password'];
$phone=$_POST['phone'];
}
else
{
echo "error".mysql_error();
}
}
?>
<head>
<title> Sign Up </title>
<style>
/*--main--*/
.main-agileits {
margin: 2% auto;
background: rgba(125, 63, 152, 0.52);
width: 32%;
font-family: 'Lato', sans-serif;
}
.sub-head {
font-size: 38px;
padding: 42px;
color: white;
text-transform: uppercase;
letter-spacing: 3px;
}
.sub-main{
position:relative;
}
/*--icons--*/
/*--//main--*/
.mark{
background-color:#000;
height:60px;
}
.head-img{
background:url(../../Shivani/images/medical.png);
height:100px;
width:100%;
}
.color
{
color: red;
}
</style>
</head>
<body>
<!--main-->
<br>
<div class="main-agileits">
<h2 class="sub-head"></h2>
<div class="sub-main">
<form method="post">
<input placeholder="First Name" name="firstname" class="name" type="text" required="">
<span class="icon1"><i class="fafa-user" aria-hidden="true"></i></span><br>
if(array_key_exists('test',$_POST)){
testfun();
?>
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
label {
padding: 12px 12px12px 0;
display: inline-block;
}
input[type=submit] {
background-color: #4CAF50;
color: white;
padding: 12px 20px;
border: none;
input[type=submit]:hover {
background-color: #45a049;
}
.container {
border-radius: 5px;
background-color: #f2f2f2;
padding: 20px;
}
.col-25 {
float: left;
width: 25%;
margin-top: 6px;
}
.col-75 {
float: left;
width: 75%;
margin-top: 6px;
}
/* Clear floats after the columns */
.row:after {
content: "";
display: table;
clear: both;
}
<link
href="//fonts.googleapis.com/css?family=Lato:100,100i,300,300i,400,400i,700,700i,900,900i&a
mp;subset=latin-ext" rel="stylesheet">
<link
href="//fonts.googleapis.com/css?family=Open+Sans:300,300i,400,400i,600,600i,700,700i,800,
800i&subset=cyrillic,cyrillic-ext,greek,greek-ext,latin-ext,vietnamese"
rel="stylesheet">
</head>
<body>
<div class="container">
<div class="tab">
<button class="tablinks" onclick="openCity(event, 'London')">User Detail</button>
</div>
<div id="London" class="tabcontent">
<div class="container">
<form method="POST">
?>
</select>
<input type="submit" name="test" id="test" value="RUN" />
</div>
</div>
<div class="row">
<div class="col-25">
<label for="lname">Product Quantity</label>
</div>
<div class="col-75">
<input type="text" id="lname" name="lastname" value="<?php echo $_SESSION['Last_Name'];
?>">
</div>
</div>
<div class="row">
➢ dbconnection.php :
<?php
$host = "localhost";
$uname = "root";
$pass = "";
$con = mysql_connect("$host","$uname","$pass");
mysql_select_db("shivani_online_portal");
if ($con)
{
echo "success";
}
else
{
echo "Connection Failed";
}
?>
label {
padding: 12px 12px12px 0;
display: inline-block;
}
input[type=submit] {
input[type=submit]:hover {
background-color: #45a049;
}
.container {
border-radius: 5px;
background-color: #f2f2f2;
padding: 20px;
}
.col-25 {
float: left;
width: 25%;
margin-top: 6px;
}
.col-75 {
float: left;
width: 75%;
margin-top: 6px;
}
/* Responsive layout - when the screen is less than 600px wide, make the two columns stack on
top of each other instead of next to each other */
@media screen and (max-width: 600px) {
.col-25, .col-75, input[type=submit] {
width: 100%;
margin-top: 0;
}
}
</style>
<link href="css/bootstrap.css" rel="stylesheet" type="text/css" media="all" />
<link href="css/style.css" rel="stylesheet" type="text/css" media="all" />
<link rel="stylesheet" href="css/fontawesome-all.css">
<link href="css/menu.css" rel="stylesheet" type="text/css" media="all" />
<link
href="//fonts.googleapis.com/css?family=Lato:100,100i,300,300i,400,400i,700,700i,900,900i&a
mp;subset=latin-ext" rel="stylesheet">
<link
href="//fonts.googleapis.com/css?family=Open+Sans:300,300i,400,400i,600,600i,700,700i,800,
800i&subset=cyrillic,cyrillic-ext,greek,greek-ext,latin-ext,vietnamese"
rel="stylesheet">
</head>
<body>
<div class="tab">
<button class="tablinks" onclick="openCity(event, 'London')">User Detail</button>
<button class="tablinks" onclick="openCity(event, 'Paris')">Order History</button>
</div>
<div class="row">
<br>
<center><div class="row">
<input type="submit" name="submit" value="Update">
</div>
</center>
</form>
</div>
</div>
<form method="POST">
<div class="table-responsive">
<th>Quality</th>
<th>Price</th>
<th>Total Amount</th>
<th>Delivery Address</th>
</tr>
</thead>
<tbody>
<?php
$sql = "select c.SL_NO,c.Product_Name,c.Product_Quantity,p.Product_Price,c.Delivery_Address from
cart c, Products p where c.Product_Name=P.Product_Name and c.user='$username' and
c.buying_status='Y'";
$count=1;
$result=mysql_query($sql);
while($row=mysql_fetch_array($result))
{
</div>
</div>
</td>";
</div>
</div>
</td>";
</div>
</div>
</td>
</tr>";
$count++;
}
?>
</tbody>
</table>
</div>
</form>
</div>
</div>
</div>
</div>
</div>
</div>
<script>
functionopenCity(evt, cityName) {
var i, tabcontent, tablinks;
tabcontent = document.getElementsByClassName("tabcontent");
for (i = 0; i <tabcontent.length; i++) {
tabcontent[i].style.display = "none";
</body>
</html>
/*--placeholder-color--*/
::-webkit-input-placeholder{
color: #666;
}
</style>
</head>
</div>
</div>
</div><br><br>
<!-- //login form -->
</body>
</html>
<!--js-files -->
<!--jquery -->
<scriptsrc="js/jquery-2.2.3.min.js"></script>
<!-- //jquery -->
<!--nav smooth scroll -->
<script>
$(document).ready(function () {
$(".dropdown").hover(
function () {
$('.dropdown-menu', this).stop(true, true).slideDown("fast");
$(this).toggleClass('open');
},
function () {
$('.dropdown-menu', this).stop(true, true).slideUp("fast");
$(this).toggleClass('open');
if (isset($_POST['submit']))
{
if (!isset($_SESSION['Username']))
{
echo "<script type='text/javascript'>alert('Please Login To ADD Product To Cart')</script>";
header('Refresh:0.5; url=login.php');
}
elseif ($_POST['req_qty'] > $quantity)
{
$a1 = mysql_query($sql1);
$a2 = mysql_query($sql2);
❖ Checkout.php :
<?php
include('dbconnection.php');
session_start();
if (!isset($_SESSION['Username']))
{
echo "<script type='text/javascript'>alert('Please Login To Check Cart')</script>";
header('Refresh:0.5; url=login.php');
}
$username=$_SESSION['Username'];
$result=mysql_query("SELECT count(*) as total from cart where User='$username' and
buying_status=''");
$data=mysql_fetch_assoc($result);
// echo $data['total'];
if(isset($_POST['submit']))
{
$SL_NO=$_POST['submit'];
$sql1="delete from cart where SL_NO='$SL_NO' and User='$username'";
if(mysql_query($sql1))
{
echo "<script type='text/javascript'>alert('Item Successfully Removed')</script>";
header('Refresh:0.5; url='.$_SERVER['REQUEST_URI']); }
}
if(isset($_POST['submit2']))
{
if($Qty<$used_qty){
echo "<script type='text/javascript'>alert('Required Stock Not Available')</script>";
header('Refresh:0.5; url=checkout.php');
exit();
}
$update_qty=$Qty-$used_qty;
//echo "<script type='text/javascript'>alert(".$update_qty.")</script>";
$sql2="update Products set Product_Quantity='
$update_qty' where Product_Name='$prod_name'";
mysql_query($sql2);
$address=$_POST['name'].",".$_POST['landmark'].",".$_POST['city'].",".$_POST['add_type'].",Phone-
catch(Exception $e) {
mysql_query("ROLLBACK");
echo "<script type='text/javascript'>alert('Failed')</script>";
}
}
?>
<!DOCTYPE html>
<head>
<title>Online Electronic Store</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta charset="UTF-8" />
<script>
addEventListener("load", function () {
setTimeout(hideURLbar, 0);
},
false);
function hideURLbar() {
window.scrollTo(0, 1);
}
<?php
$sql = "select c.SL_NO,c.Product_Name,c.Product_Quantity,p.Product_Price from cart c,
Products p where c.Product_Name=P.Product_Name and c.user='$username' and
c.buying_status=''";
$count=1;
$result=mysql_query($sql);
while($row=mysql_fetch_array($result))
{
echo"<tr class=rem1>
<td class=invert>".$count."</td>";
Echo"<td class=invert>".$row['Product_Name']."</td>";
echo "<td class=invert>".$row['Product_Quantity']."</td>";
echo"<td class=invert>
<div class=quantity>
<div class=quantity-select>
<div class=entry value>
<span>".$row['Product_Price']."</span>
</div>
</div>
echo "<td class=invert>
<div class=rem>
<div class=close1><button name=submit type=submit
value=".$row['SL_NO'].">Remove</button> </div>
</div>
</td>
</tr>";
$count++;
}
?>
</tbody>
</table>
</div>
</form>
</div>
<div class="checkout-left">
<div class="address_form_agile mt-sm-5 mt-4">
<h4 class="mb-sm-4 mb-3">Add a new Details</h4>
<form method="post" class="creditly-card-form agileinfo_form">
<div class="creditly-wrapper wthree, w3_agileits_wrapper">
<div class="information-wrapper">
<div class="first-row">
<div class="controls form-group">
<input class="billing-address-name form-control" type="text" name="name" placeholder="Full
Name" required="">
</div>
<script src="js/jquery-2.2.3.min.js"></script>
<script src="js/scroll.js"></script>
<script src="js/SmoothScroll.min.js"></script>
<script src="js/easing.js"></script>
<script src="js/bootstrap.js"></script>
</body>
</html>
❖ aboutus.php :
<!DOCTYPE html>
<head>
<title>Online Electronic Store</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta charset="UTF-8" />
<script>
addEventListener("load", function () {
setTimeout(hideURLbar, 0);
},
False
);
function hideURLbar() {
window.scrollTo(0, 1);
}
</script>
<style>
.snipcart-details input.button {
width: 80%;
}
.navbar-inner {
background: #F45C5D;
box-shadow: 0px 2px 6px 1px rgba(0, 0, 0, 0.13);
}
.bg-light {
background-color: #F45C5D !important;
}
<body>
<!-- header-bottom-->
<div class="header-bot">
<div class="container">
<div class="row header-bot_inner_wthreeinfo_header_mid">
<!-- logo -->
<div class="col-md-10 logo_agile">
<h1 class="text-center">
<a href="index.html" class="font-weight-bold font-italic">Online Electronics Store</a>
</h1>
</div>
<!-- //logo -->
<!-- cart details -->
<div class="col-md-2 top_nav_right text-center mt-sm-0 mt-2">
<div class="wthreecartaits wthreecartaits2 cart cart box_1">
<form action="#" method="post" class="last">
<input type="hidden" name="cmd" value="_cart">
<input type="hidden" name="display" value="1">
<button class="btn w3view-cart" type="submit" name="submit" value="">
<i class="fas fa-cart-arrow-down"></i>
</button>
</form>
</div>
</div>
<!-- //tittle heading -->
<div class="row">
<h4 class="my-sm-3 my-2">consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore
et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut
aliquip ex ea commodo consequat.</h4>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse porta erat sit amet eros
sagittis, quis hendrerit libero aliquam. Fusce semper augue ac dolor efficitur, a pretium metus
pellentesque.</p>
</div>
<div class="col-lg-6 welcome-right-top mt-lg-0 mt-sm-5 mt-4">
<img src="images/ab.jpg" class="img-fluid" alt=" ">
</div>
</div>
<!-- //about -->
<!-- footer -->
<footer>
<div class="footer-top-first" style="background:#ebebeb">
<div class="container py-md-5 py-sm-4 py-3">
<!-- footer first section -->
<h2 class="footer-top-head-w3l font-weight-bold mb-2">Electronics :</h2>
<p class="footer-main mb-4"> If you're considering a new laptop, looking for a powerful new car
stereo or shopping for a new HDTV, we make it easy to find exactly what you need at a price you
can afford. We offer Every Day Low Prices on TVs, laptops, cell phones, tablets and iPads, video
games, desktop computers, cameras and camcorders, audio, video and more.</p>
</div>
<div class="col-8 text-form-footer">
<h3>Free Shipping</h3>
<p>on orders over Rs.25,00.00</p>
</div></div></div>
<div class="col-md-4 offer-footer my-md-0 my-4">
<div class="row">
<div class="col-4 icon-fot">
<i class="fas fa-shipping-fast"></i>
</div>
<div class="col-8 text-form-footer">
<h3>Fast Delivery</h3>
<p>World Wide</p>
</div>
</div>
</div>
<div class="col-md-4 offer-footer">
<div class="row">
<div class="col-4 icon-fot">
<i class="far fa-thumbs-up"></i>
</div>
<div class="col-8 text-form-footer">
<h3>Big Choice</h3>
<p>of Products</p>
<div>
<!-- //footer second section -->
</div>
The other common type of coding standard is the one used in or between
development teams. Consider that professional code does not simply perform a job. Professional
code performs a job in such a way tha t it is easy to maintain and debug.
6. TESTING
There are different types of software testing strategies, which are selected by the testers
depending upon the nature and size of the software. The commonly used software testing
strategies are listed below.
Analytic testing strategy: This uses formal and informal techniques to access and prioritize risks that
arise during software testing. It takes a complete overview of requirements, design, and
implementation of objects to determine the motive of testing. In addition, it gathers complete
information about the software, targets to be achieved, and the data required for testing the software.
Model-based testing strategy: This strategy tests the functionality of the software according to the
real world scenario (like software functioning in an organization). It recognizes the domain of data and
selects suitable test cases according to the probability of errors in that domain.
Methodical testing strategy: It tests the functions and status of software according to the checklist,
which is based on user requirements. This strategy is also used to test the functionality, reliability,
Process-oriented testing strategy: It tests the software according to already existing standards such as
the IEEE standards. In addition, it checks the functionality of the software by using automated testing
tools.
Dynamic testing strategy: This tests the software after having a collective decision of the testing
team. Along with testing, this strategy provides information about the software such as test cases used
for testing the errors present in it.
Philosophical testing strategy: It tests the software assuming that any component of the software can
stop functioning anytime. It takes help from software developers, users and systems analysts to test the
software.
A TEST PLAN is a document describing software testing scope and activities. It is the basis for
formally testing any software/product in a project.
The format and content of a software test plan vary depending on the processes, standards, and test
management tools being implemented. Nevertheless, the following format, which is based on IEEE
standard for software test documentation, provides a summary of what a test plan can/should contain.
• Provide a unique identifier for the document. (Adhere to the Configuration Management System
if you have one.)
➢ Introduction:
➢ References:
• List the related documents, with links to them if available, including the following:
o Project Plan
o Configuration Management Plan
➢ Test Items:
➢ Features to be Tested:
➢ Approach:
• Specify the criteria that will be used to determine whether each test item (software/product) has
passed or failed testing.
➢ Test Deliverables:
• List test deliverables, and links to them if available, including the following:
o Test Plan (this document itself)
o Test Cases
o Test Scripts
o Defect/Enhancement Logs
o Test Reports
➢ Test Environment:
➢ Estimate:
➢ Schedule:
• Provide a summary of the schedule, specifying key test milestones, and/or provide a link to the
detailed schedule.
➢ Responsibilities:
➢ Risks:
• List the assumptions that have been made during the preparation of this plan.
• List the dependencies.
➢ Approvals:
• Specify the names and roles of all persons who must approve the plan.
• Provide space for signatures and dates. (If the document is to be printed.)
❖ 6.3 Test reports for Unit Test Cases and System Test Cases :
UNIT TESTING is a level of software testing where individual units/ components of a software are
tested. The purpose is to validate that each unit of the software performs as designed. A unit is the
smallest testable part of any software. It usually has one or a few inputs and usually a single output. In
procedural programming, a unit may be an individual program, function, procedure, etc. In object-
oriented programming, the smallest unit is a method, which may belong to a base/ super class, abstract
class or derived/ child class. (Some treat a module of an application as a unit. This is to be discouraged
as there will probably be many individual units within that module.) Unit testing frameworks, drivers,
stubs, and mock/ fake objects are used to assist in unit testing.
Acceptance Testing
System Testing
Integration Testing
Unit Testing
SYSTEM TESTING are the third phase in the Testing Lifecycle. System Tests are the test of the end-
user functionality. System Tests verify the correct functioning of all the required features as given in the
specification document.
Since prior testing phases have tested the internal logic of the application, System Tests should
not repeat detailed, exhaustive testing. Instead System Tests verify that all subsystems are cooperating
successfully to yield the final desired features.
System tests are usually "black box" tests since we are testing the application without seeing the source
code. Create the test cases following the guidelines in the textbook, the black box techniques studied in
class, as well as your own experience or intuition about verifying program correctness. Number each
test case and write it in HTML (or Wiki) format.
Prepare the test cases according to these directions: System Test Case Format
The QA manager is responsible for creating the Test Matrix, which is a grid with Requirement Numbers
on one axis and Test Case Numbers on the other. It shows which test cases cover which requirements.
Use this which shows which test cases were written by which team member and has a link to the test
cases.
• Every functional requirement in the specification has at least one test case.
• Purpose provides specific detail of the behavior or function being tested.
• Actual input data and expected output data are provided. The expected output is precise and
detailed enough to be implemented as an "oracle" for automated testing. The data needs to run
on the actual software being released.
• User Action description is clear and specific enough for independent testers to follow the
directions.
• The test case will correctly verify the requirement.
• Cross-reference is correct.
The main objective of the testing here is to execute a program and find the errors, so that software can
function according to specification specified for behave and performance requirement of the software.
1.Testing Techniques: We have used the following testing technique for finding errors in this software:
(A).White Box Testing Technique: We have used this method to exercise the internal program logic.
During the course of white box testing, I have done the following work.
All independent paths within a module are exercised at least once.
All logical decision on their true and false side is also exercised.
All loops were executed at their boundaries and within their operation bounds.
Validity of internal data structure was also exercised.
Some of white box testing techniques, which we have used for this software, are: -
1. Basis Path Testing: The basis path methods enable me to derive a logical complexity
measure of a procedure design and this measure is used for defining a basis set of execution
path. This path ensures to execute every statement in a program at least once.
2. Control structure testing: Since the basis path testing was not enough, hence the control
structure testing is used to exercise the logical condition in a program module
During the course of testing, I have done the following activities,
Which are described below:-
▪ After testing all conditions, we have found some errors like:
▪ Boolean variable error in the module cost benefit analysis.
Case:-In cost benefit analysis, we have used the concept of relative cell referencing in this contact; we
have taken two types of cell
(i) Variable cell
(ii) Function
Based constant value cell. Only user can modify variable cell but function value cell only display
manipulated value. If cell is functional cell, its return TRUE else FALSE. During course of testing, we
have found this function not return value properly. So we have separately tested this function for
Boolean errors.
(B). Black Box Testing: This method is used to test the functional requirements of the software as
specified in the section of S.E. Requirement Specification. By using this technique I have found errors
in the following categories:
• Incorrect or missing functions Interface errors
• Errors in data structure
• Behavior or performance errors and
• Initialization and termination errors
Testing Strategies: Testing strategy, which I have used here to integrate software test case design
methods into a series of steps, can be categorized into two spectrums: -
Code Testing.
Specifications testing.
The testing strategies, which I have used here, have the following generic characteristics:-
First component level testing are performed and then we moved towards the integration of
the entire software.
During the course of various types of testing, user involvements are also considered.
Different types of testing are performed at different points of time.
• Integration Testing:- During this phase we have combine all the module and perform
integration sting for constructing the program structure while at the same time conducting tests to
uncover errors associated with interfacing. In order to integrate all the modules we have used
Bottom up approach.
• Validation Testing:-After the completion of integration testing removal of interfacing problem,
we have conducted validation testing according to reasonable expectation of user specified in the
S.E.Requirement specification documents. Since this s/w is designed for management, of the
software according to their needs.
7.DATABASE SECURITY
➢ Data Integrity & Constrain :
Introduction to Data Integrity :-
It is important that data adhere to a predefined set of rules, as determined by the database administrator
or application developer. As an example of data integrity, consider the tables Patient and Doctors and
the business rules for the information in each of the tables.
Types of Data Integrity :- This section describes the rules that can be applied to table columns to
enforce different types of data integrity.
Null Rule :- A null rule is a rule defined on a single column that allows or disallows inserts or updates
of rows containing a null (the absence of a value) in that column.
Unique Column Values : - A unique value rule defined on a column (or set of columns) allows the
insert or update of a row only if it contains a unique value in that column (or set of columns).
Primary Key Values : - A primary key value rule defined on a key (a column or set of columns)
specifies that each row in the table can be uniquely identified by the values in the key.
Referential Integrity Rules : - A referential integrity rule is a rule defined on a key (a column or set of
columns) in one table that guarantees that the values in that key match the values in a key in a related
table (the referenced value). Referential integrity also includes the rules that dictate what types of data
manipulation are allowed on referenced values and how these actions affect dependent values.
Oracle uses integrity constraints to prevent invalid data entry into the base tables of the database. You
can define integrity constraints to enforce the business rules you want to associate with the information
in a database. If any of the results of a DML statement execution violate an integrity constraint, then
Oracle rolls back the statement and returns an error.
By default, all columns in a table allow nulls. Null means the absence of a value.
A NOT NULL constraint requires a column of a table contain no null values. For example, you can
define a NOT NULL constraint to require that a value be input in the last_name column for every row of
the doctors table.
Project Cost Management is the process of planning and controlling the project cost effectively. It
defines what costs are required for each deliverable. The cost of the project can be estimated from
various process sources like
• Creating WBS
• Develop Schedule
• Identifying risks
The Project Cost Estimation is the process of approximating the total expenditure of the project.
The accuracy of the cost estimation depends on the accuracy and details of the project scope, which is
the scope baseline. The scope will also define any constraints like date, resources or budget.
The risk register will help to estimate types of costs, the expenses made behind the contingent action and
the expenses made to cope with risks.
To estimate the cost of project you have to categorize various cost types into categories like
• Labor cost
• Equipment cost
• Cost of supplies
• Travel cost
• Training cost
• Overhead cost
Analogous Estimating : This estimating technique is based on expert judgments and information based
on similar previous projects. Where previously done similar project cost is considered with plus or
minus of 20% for existing project.
Parametric estimating
Past data or record is used to estimate cost for the current project.
Bottom-up estimating : Once you have defined the scope of the project, it is the most reliable form of
technique. In this technique, based on WBS, you estimate the cost for each resource or deliverables.
Likewise, there are other techniques which could be useful for estimating cost like PERT
estimating, vendor bid analysis, etc.
The main purpose of this activity is to allocate and authorize the monetary resources required to
complete the project. The main output for determining the budget includes cost performance baseline. It
not only specifies what cost will be incurred but also when costs will be incurred. The inputs for
determining budget includes
The project budgeting is performed in parallel with the project scheduling process. It is highly dependent
on three component –
• Cost estimation
• Task durations
• Allocated resources
During project budgeting, project manager communicates with different people responsible for
managing the work efforts as well as estimating project costs : He will use various project prospects like
work breakdown structure of the project, the cost estimates, historical data and records, resource
information, and policies.
Without risk assessment, the budgeting process is not completed. Risk assessing process considers
factors like time shortage, availability of resources, development team experience, the technology used,
etc. The risk assessment can be an amount between 25 and 30 percent of the overall project cost.
The scope of project include that what all future enhancement can be done in this system to
make it more feasible to use .
❖ Benefit :
10.BIBILIOGRAPHY
The following books were referred for completing this project. This includes books for front end part
and books for back end part.
11.CONCLUSION
While developing the system a conscious effort has been made to create and develop
a software package, making use of available tools, technique and resource - that would be
generate a proper support system.
While making the system , an eye has been kept on making its user - friendly, as cost
effective and flexible as possible. As such one may hope that the system will be acceptable to
any user and will adequately to any user will meet her needs.
As in the case of my system developed process where there a number of shortcoming in the
development of this system also.
12.APPENDIX
1. FORMAT
Size : A4
Normal Text Size : Times New Roman, font size 12.
Heading Text Size : Times New Roman, font size 14 (Bold face)
Sub-Heading Text Size : Times New Roman, font size 12 (Bold face)
Margins : 1.5 inch on the left and top, 1 inch at the bottom and right
Paragraph : At Double Spacing
Line Spacing : 1.5 spacing to be provided throughout the Thesis.
Page number : Bottom centre of each page.
Binding : Hard bound with specified color coding.
REFFERENCES
• https://css-tricks.com
• http://www.php.net
• https://www.w3schools.com
• https://stackoverflow.com
• https://github.com
• https://www.codecademy.com
• https://www.tutorialspoint.com
• https://jquery.com