Online Cake Order System Chapter-1: Rrit Dept of Cse 2018-2019

ONLINE CAKE ORDER SYSTEM
CHAPTER-1
INTRODUCTION
1.1 INTRODUCTION
The project “Online Cake Order System” allows users to check for various
bakery products available at the online store and purchase online. The project
consists of list of bakery products displayed in various categories.
The user may browse through these items as per categories. If the user likes
a product he may add it to his shopping cart. Once user wishes to checkout he must
register on the site first. He can then login using same id password next time. Now
he may pay through a credit card or cash on delivery.
Once the user makes a successful transaction he gets a copy of the shopping
receipt on his email id. Here we use .net framework to make the entire frontend.
The middle tier or code behind model is designed in c#. And SQL serves as a
backend to store bakery products lists data. Thus, the online Bakery shopping
project brings an entire bakery shop online and makes it easy for both buyer and
seller.
RRIT Dept of CSE 2018-2019 Page 1

CHAPTER-2
SOFTWARE & HARDWARE REQUIREMENTS
2.1 SYSTEM ANALYSIS
System analysis is a process of gathering and interpreting facts, diagnosing problems and the
information to recommend improvements on the system. It is a problem solving activity that
requires-intensive communication between the system user and system developers. System
analysis or study is an important phase of any system development process. The system is
studied to the minutest detail and analyzed. The system analyst plays the vital role of the
interrogator and dwells deep into the working of the present system. The system is viewed as a
whole and the input to the system are identified. The outputs from the organizations are traced
to the various processes. System analysis is concerned with becoming aware of the problem,
identifying the relevant and decisional variables, analyzing and synthesizing the various factors
and determining an optimal or at least satisfactory solution or program of action. A detailed
study of the process must be made by various techniques like interviews, questionaries etc.
2.1.1 EXISTING SYSTEM
o Here the existing system is a manual that doesn’t maintain details with proper security
and can’t track details easily.
o It doesn’t allow the customer to check their profile in proper way which leads customer
dissatisfaction.
o Does not provide option to download loan form.
o Existing system doesn’t contain functionalities of fast retrieval information.
o Doesn’t user friendly interface.
o It used to take more time to find customers because there are required extra manual
effort such as to hire candidate.
o Difficulty in generating different reports as per the business requirements.
2.1.2 PROPOSED SYSTEM
o Interest rates and the loan details are also available at the click of a mouse.
o Customer can apply for a loan and after approved it they can track their details from
online.
o Using with this system admin can find customer easily and it’s a paperless system so
workload is reduced.
o The decision process becomes faster and more consistent.

o After registration and login customer can use the system easily and also customer can
view any query about loan details as well. So this system saves time.
o Provides good communication for the customer.
o Provides a facility to generate the reports very easily.
2.1.3 AIM OF THE PROJECT
Main objective is to provide good interactive & communication facilities between customer and
administrator. Loan Management System has been design to online the back office activities of
bank and finance company which offers any type of loan. Administrator manage customer
information database more efficiently, loan details, maintain loan type and interest rate
information. Admin can use calculator to give exact payable loan amount for the customer and
generate all these work info as a report of each customers.
2.1.4 OBJECTIVES
 Input Design is the process of converting a user-oriented description of the input into a
computer-based system. The design is important to avoid errors in the data input
process and show the correct direction to the management for getting correct
information from the computerized system.
 It is achieved by creating user-friendly screens for the data entry to handle large volume
of data. The goal of designing input is to make data entry easier and to be free from
errors. The data entry screen is designed in such a way that all the data manipulates can
be performed. It also provides record viewing facilities.
 When the data is entered it will check for its validity. Data can be entered with the help
of screens. Appropriate messages are provided as when needed so that the user will
not be in maize of instant. Thus the objective of input design is to create an input layout
that is easy to follow.

2.2 REQUIREMENT ANALYSIS
2.2.1 SOFTWARE REQUIREMENTS:
The software requirements include:
 Web presentation : HTML,CSS,PHP

 Backend Database : MYSQL
 Operating System : Windows XP/2003 or higher versions
 Web Server : XAMPP
 Browser : IE/Mozilla/Chrome
2.2.2 HARDWARE REQUIREMENTS(MINIMUM):
The hardware requirements include:
 Processor : Intel 5.0 GHz or higher processor

 RAM Capacity : 1 GB(min)
 Hard Disk : 20GB
 Keyboard : Standard keyboard
 Mouse : Optical
 Monitor : “15” Color Monitor

CHAPTER-3
DESIGN ANALYSIS
3.1 DESIGN
Design is the first step into the development phase for any engineering product or system.
Design is a creative process. A good design is the key to effective system. The term "design" is
defined as "the process of applying various techniques and principles for the purpose of
defining a process or a system in sufficient details to permit its physical realization". It may be
defined as a process or a system in sufficient detail to permit its physical realization. Software
design sits at the technical kernel of the software engineering process and is applied regardless
of the development paradigm that is used.
As in the case of any systematic approach, this software too has undergone the best possible
design phase fine tuning all efficiency, performance and accuracy levels. The design phase is a
transition form a user oriented document to a document to the programmers or database
personnel. System design goes through two phase of development: Logical and Physical Design.
3.1.1 LOGICAL DESIGN:
The logical flow of a system and define the boundaries of a system. It includes the following
steps:
 Reviews the current physical system- its data flow, file contents, volumes, Frequencies
etc.
 Prepare output specifications- that is, determines the format, content and Frequency of
reports.
 Prepare input specifications- format, content and most of the input functions.
 Prepare edit, security and control specifications.
 Specifies the implementation plan.
 Prepares a logical design walk through of the information flow, output, input, Controls
and implementation plan.
 Reviews benefits, costs, target dates and system constraints.
3.1.2 PHYSICAL DESIGN:
Physical system produces the working systems by define specifications that tell the
programmers exactly what the candidate system must do. It includes the following steps.
 Design the physical system.

 Specify input and output media.

 Design the database and specify backup procedures.
 Design physical information flow through the system and a physical design.
 Plan system implementation.
 Determine training procedures, courses and timetable.
 Devise a test and implementation plan and specify any new hardware/software.
 Update benefits, costs, conversion date and system constraints.
3.1.3 Design/Specification activities:
 Concept formulation.
 Problem understanding.
 High level requirement proposals.
 Feasibility study.
 Requirements engineering.
 Architectural design.
3.1.4 INPUT DESIGN
The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are necessary to
put transaction data in to a usable form for processing can be achieved by inspecting the
computer to read data from a written or printed document or it can occur by having people
keying the data directly into the system. The design of input focuses on controlling the amount
of input required, controlling the errors, avoiding delay, avoiding delay, avoiding extra steps
and keeping the process simple. The input is designed in such a way so that it provides security
and ease of use with retaining the privacy. Input Design considered the following things:
 What data should be given as input?

 How the data should be arranged or coded?
 The dialog to guide the operating personnel in providing input.
3.1.5 OUTPUT DESIGN
A quality output is one, which meets the requirements of the end user and presents the
information clearly. In any system results of processing are communicated to the users and to
other system through outputs. In output design it is determined how the information is to be
displaced for immediate need and also the hard copy output. It is the most important and
direct source information to the user. Efficient and intelligent output design improves the
system's relationship to help user decision making.

 When analysis design computer output, they should Identify the specific output that is
needed to meet the requirements.
 Select methods for presenting information.
 Create document, report, or other formats that contain information produced by the
system.
The output form of an information system should accomplish on or more of the following
objectives.
 Convey information about past activities, current status or projections of the Future.
 Signal important events, opportunities, problems or warnings.
 Trigger an action.
 Confirm an action.

3.2 ER-DIAGRAM

CHAPTER-4
CODING
4.1 SOURCE CODE
4.1.1 INDEX.PHP
<?php
include('includes/connection.php');
?>

<?php include 'includes/header.php';
?>

<?php include 'includes/sidebar.php';
?>


<?php
if (isset($_SESSION['userid']))
if ($_SESSION['position']=='Admin')
include 'includes/breadcrumbs.php';

}elseif
($_SESSION['position']=='Customer')
include 'includes/cakes.php';
else{
include 'includes/cakes.php';
?>


<?php /*include 'includes/iconcards.php'*/;
?>



<?php include 'includes/footer.php';
?>
4.1.2 LOGIN.PHP
<!DOCTYPE html>
<html lang="en">
<head>

<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<meta name="description" content="">
<meta name="author" content="">
<title>Login</title>

<link href="vendor/bootstrap/css/bootstrap.min.css" rel="stylesheet">

<link href="vendor/fontawesome-free/css/all.min.css" rel="stylesheet" type="text/css">

<link href="css/sb-admin.css" rel="stylesheet">
<link rel="stylesheet" type="text/css" href="css/sb-new.css">
</head>
<body class="bg-dark">
<div class="container">
<div class="card card-login mx-auto mt-5">
<div class="card-header"><h3> Login</h3></div>
<div class="card-body">
<?php session_start();
if (isset($_GET['error'])) {
if ($_GET["error"]=="wrongpwd") {
echo '<p class="signuperror">Wrong password</p>';

?>
<form action="includes/signin.php" method="post">
<div class="form-group">
<div class="form-label-group">
<input type="text" id="inputEmail" name="mailuid" class="form-control"

placeholder="Email/Username" required autofocus="autofocus">
<label for="inputEmail">Email/Username</label>
</div>
</div>
<div class="form-label-group">
<input type="password" id="inputPassword" name="pwd" class="form-control"

placeholder="Password" >
<label for="inputPassword">Password</label>
</div>
</div>
<div class="checkbox">
<label>
<input type="checkbox" value="remember-me">
Remember Password
</label>
</div>
</div>

<button class="btn btn-primary btn-block" name="login-submit">Login</button>
</form>
<div class="text-center">
<a class="d-block small mt-3" href="register.php">Signup</a>
<a class="d-block small mt-3" href="index.php">Home</a>
</div>
</div>
</div>
</div>

<script src="vendor/jquery/jquery.min.js"></script>
<script src="vendor/bootstrap/js/bootstrap.bundle.min.js"></script>

<script src="vendor/jquery-easing/jquery.easing.min.js"></script>
</body>
</html>
4.1.4 INSERTCUSTOMER.PHP
<?php
?>
<!DOCTYPE html>
<html>
<head>
<title></title>

</head>
<body>
<?php
$fname = $_POST['firstname'];
$lname = $_POST['lastname'];
$email = $_POST['Email'];
$contct = $_POST['Contact'];
$address = $_POST['Address'];
switch($_GET['action']){
case 'add':
$query = "INSERT INTO tblcustomer (customer_id,fname, lname,

email,contact,address) VALUES
('Null','".$fname."','".$lname."','".$email."','$contct','".$address."')";
mysqli_query($db,$query)or die ('Error in updating Database');
break;
?>
<script type="text/javascript">
alert("Successfully added.");
window.location = "customer.php";
</script>
</body>
</html>

4.1.5 INSERTPRODUCT.PHP
<?php
require('includes/connection.php');
?>
<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body>
<?php
$product = $_POST['product'];
$qntty = $_POST['qntty'];
$quantity = $_POST['quantity'];
$available = $_POST['available'];
$price = $_POST['price'];
$profit = $_POST['profit'];
$sale = $_POST['sale'];
$date = $_POST['date'];
$cat = $_POST['cat'];
$user = $_POST['user'];
$nq = $_POST['nq'];

$supplier = $_POST['supplier'];
case 'add':
$query= " INSERT INTO

tblproducts(product_id,product_name,quantity,available,price,profit,selling_price,date_in,cate
gory_id,user_id,supplier_id,product_code,status) VALUES
('Null','".$product."','.$qntty.','.$qntty.','.$price.','.$profit.','.$sale.','$date','".$cat."','".$user."','"
.$supplier."','".$nq."','available')";
break;
?>
window.location = "product.php";
</script>
</body>
</html>
4.1.6 INSERTSUPPLIER.PHP
<?php
include('includes/connection.php');
?>
<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body>
<?php
$sm = $_POST['supplier'];
$contacts = $_POST['contact'];
$emails = $_POST['email'];
$address = $_POST['address'];
case 'add':
$query = "INSERT INTO tblsupplier(supplier_id,supplier_name,contact,email,address)
VALUES ('Null','".$sm."','.$contacts.','".$emails."','".$address."')";
break;
?>
window.location = "supplier.php";
</script>
</body>
</html>

4.1.7 ORDER.PHP
<?php include('includes/connection.php');?>

<?php include 'includes/header.php'; ?>

<?php include 'includes/sidebar.php'; ?>
<ol class="breadcrumb">
<li class="breadcrumb-item">
<a href="#">Dashboard</a>
</li>
<li class="breadcrumb-item active">List of Orders</li>
</ol>
<?php
if(!isset($_SESSION["userid"])){
header("Location: index.php");
else{
?>
<?php

?>
<div class="card mb-3">
<div class="card-header">
<center> <div class="border" style="width: 500px"><h1>List of

Order</h1></div></center>
<div class="table-responsive">
<table class="table table-bordered table-hover table-striped" id="dataTable"

width="100%" cellspacing="0">
<thead>
<tr>
<th>ID</th>
<th>Order No.#</th>
<th>Order Date</th>
<th>Delivery Date</th>
<th>Total Price</th>
<th>Status</th>
<th width="250">Remarks</th>
<th></th>

</tr>
</thead>
<tbody>
<?php

$query = "SELECT * FROM tbltransacdetail WHERE

customer_id='".$_SESSION['userid']."'";
$result = mysqli_query($db, $query) or die (mysqli_error($db));
while ($row = mysqli_fetch_assoc($result)) {
echo '<tr>';
echo '<td>'. $row['detail_id'].'</td>';
echo '<td>'. $row['transac_code'].'</td>';
echo '<td>'. $row['date'].'</td>';
echo '<td>'. $row['delivery_date'].'</td>';
echo '<td>&#8369 '. $row['totalprice'].'</td>';
echo '<td>'. $row['status'].'</td>';
echo '<td>'. $row['remarks'].'</td>';
echo '<td> ';
echo '<center> <a class="btn btn-info" title="View list Of Ordered"

href="orderdetail.php?id='. $row['transac_code'].'">View detail</a> </center></td>';
echo '</tr> ';
?>
</tbody>
</table>
</div>
</div>
</div>
</div>


<?php
include 'includes/footer.php';
?>
<?php
include 'addtransac.php';
?>
4.1.8 CUSTOMER.PHP
<?php include('includes/connection.php');
?>

<?php
include 'includes/header.php';
?>

<?php include 'includes/sidebar.php'; ?>
<ol class="breadcrumb">
<li class="breadcrumb-item">
<a href="#">Dashboard</a>
</li>
<li class="breadcrumb-item active">Customers</li>
</ol>


<?php
if(!isset($_SESSION["userid"])){
header("Location: index.php");
else{
?>
<?php
?>
<div class="card mb-3">
<div class="card-header">
<h2>Customers </h2> 
<div class="table-responsive">
<table class="table table-bordered table-hover table-striped"id="dataTable"

width="100%" cellspacing="0">
<thead>
<tr>
<th>ID</th>
<th>First Name</th>
<th>Last Name</th>
<th>Email</th>

<th>Contact</th>
<th>Address</th>
<th>Options</th>
</tr>
</thead>
<tbody>
<?php
$query = 'SELECT * FROM tblusers WHERE position="Customer"';
$result = mysqli_query($db, $query) or die (mysqli_error($db));
while ($row = mysqli_fetch_assoc($result)) {
echo '<tr>';
echo '<td>'. $row['user_id'].'</td>';
echo '<td>'. $row['fname'].'</td>';
echo '<td>'. $row['lname'].'</td>';
echo '<td>'. $row['email'].'</td>';
echo '<td>'. $row['contact'].'</td>';
echo '<td>'. $row['address'].'</td>';
echo '<td> ';
echo ' <a title="Update Customer" type="button" class="btn btn-lg btn-warning

fas fa-user-edit" href="updatecustomer.php?action=edit & id='.$row['user_id'] . '"></a> </td>';
echo '</tr> ';

?>
</tbody>
</table>
</div>
</div>
</div>
</div>


<?php include 'addcustomer.php';
?>

4.4 SQL SOURCE CODE

CREATE TABLE IF NOT EXISTS `tblcustomer` (
`customer_id` int(30) NOT NULL,
`fname` varchar(30) NOT NULL,
`lname` varchar(30) NOT NULL,
èmail` varchar(30) NOT NULL,
`contact` varchar(11) NOT NULL,
àddress` text NOT NULL
) ENGINE=InnoDB AUTO_INCREMENT=58 DEFAULT CHARSET=latin1;
--
-- Dumping data for table ` tblcustomer `
INSERT INTO `tblcustomer` (`customer_id`, `fname`, `lname`, èmail`, `contact`, àddress`)

VALUES
(44, 'Adrian', 'Mercurio', 'mercurio@yahoo.com', '09561666494', 'Brgy. Suay Himamaylan City

Neg. Occ'),
(45, 'ads', 'mers', 'maaaae@yahoo.com', '0980989', 'hgjgjg'),
(54, 'ads', 'mer', 'mamans@yahoo.com', '9999999', 'mmmss'),
(55, 'Adrian', 'Mercurio', 'admerc@yahoo.com', '09561666494', 'Brgy. Su-ay Himamaylan City

Neg. Occ'),
(56, 'Adrian', 'Mercurio', 'admerc@yahoo.com', '09561666494', 'Brgy. Su-ay Himamaylan City

Neg. Occ'),
(57, 'Nico', 'Raluto', 'ralutonico@yahoo.com', '09561666494', 'Brgy. Su-ay Himamaylan City Neg.
Occ');
--

Table structure for table `tblproducts`
--
CREATE TABLE IF NOT EXISTS `tblproducts` (
`product_id` int(11) NOT NULL,
`product_name` varchar(50) NOT NULL,
`quantity` int(11) NOT NULL DEFAULT '1',
àvailable` int(11) NOT NULL DEFAULT '1',
`price` int(20) NOT NULL,
`profit` int(22) NOT NULL,
`selling_price` int(22) NOT NULL,
`date_in` varchar(50) NOT NULL,
`category_id` int(11) NOT NULL,
`supplier_id` int(11) NOT NULL,
ùser_id` int(11) NOT NULL,
`product_code` varchar(11) NOT NULL,
`status` varchar(200) NOT NULL
-- --------------------------------------------------------
Dumping data for table `tblproducts`
--
INSERT INTO `tblproducts` (`product_id`, `product_name`, `quantity`, àvailable`, `price`,

`profit`, `selling_price`, `date_in`, `category_id`, `supplier_id`, ùser_id`, `product_code`,
`status`) VALUES
(124, 'Caramel Cake', 50, 50, 300, 100, 400, '2019-03-16', 1, 1, 22, '1001', 'available'),
(125, 'Chocolate cake', 60, 49, 300, 100, 400, '2019-03-16', 1, 12, 22, '1002', 'available'),

(126, 'Banana Cake', 50, 50, 200, 100, 300, '2019-03-16', 1, 1, 22, '1003', 'available'),
(127, 'Strawberry Cake', 40, 40, 400, 100, 500, '2019-03-16', 1, 18, 22, '1004', 'available'),
(128, 'Vanilla Cake', 70, 70, 200, 100, 300, '2019-03-16', 1, 45, 22, '1005', 'available'),
(131, 'Chocolate Roll', 80, 78, 300, 50, 350, '2019-03-16', 1, 46, 22, '100', 'available');
--
Table structure for table `tblsupplier`
--
CREATE TABLE IF NOT EXISTS `tblsupplier` (
`supplier_id` int(11) NOT NULL,
`supplier_name` varchar(30) NOT NULL,
`contact` int(11) NOT NULL,
àddress` text NOT NULL
--
Dumping data for table `tblsupplier`
--
INSERT INTO `tblsupplier` (`supplier_id`, `supplier_name`, `contact`, èmail`, àddress`) VALUES
(1, 'James Bond', 21474836, 'james@gmail.com', 'Bacolods'),
(12, 'Niel James', 2147483647, 'nielcompan@yahoo.com', 'Himamaylan'),
(18, 'Henry King', 2147483647, 'kingcakes@yahoo.com', 'Himamaylan'),

(45, 'Vince Dela Cruz', 2147483647, 'vinceyum@yahoo.com', 'Hinigaran'),
(46, 'Peter Parker', 98751234, 'parker@yaoo.com', 'Bacolod');
--
Table structure for table `tbltransac`
--
CREATE TABLE IF NOT EXISTS `tbltransac` (
`transac_id` int(11) NOT NULL,
`transac_code` int(100) NOT NULL,
`date` varchar(50) NOT NULL,
`product_code` varchar(200) NOT NULL,
`qty` int(20) NOT NULL,
`price` int(11) NOT NULL,
`total` int(11) NOT NULL
--
Dumping data for table `tbltransac`
--
INSERT INTO `tbltransac` (`transac_id`, `transac_code`, `date`, ùser_id`, `product_code`, `qty`,

`price`, `total`) VALUES
(31, 1554235838, '2019-04-03', 39, '100', 1, 350, 350),

(32, 1554235838, '2019-04-03', 39, '1002', 1, 400, 400),
(33, 1554251111, '2019-04-03', 39, '100', 1, 350, 350);
Table structure for table `tbltransacdetail`
--
CREATE TABLE IF NOT EXISTS `tbltransacdetail` (
`detail_id` int(11) NOT NULL,
`transac_code` int(11) NOT NULL,
`date` varchar(11) NOT NULL,
`customer_id` int(11) NOT NULL,
`deliveryfee` int(11) NOT NULL,
`totalprice` int(11) NOT NULL,
`status` varchar(200) NOT NULL,
`remarks` text NOT NULL,
`delivery_date` varchar(200) NOT NULL
--
-- Dumping data for table `tbltransacdetail`
--
INSERT INTO `tbltransacdetail` (`detail_id`, `transac_code`, `date`, `customer_id`, `deliveryfee`,

`totalprice`, `status`, `remarks`, `delivery_date`) VALUES

(18, 1554235838, '2019-04-03', 39, 150, 900, 'Confirmed', 'Your order has been confirmed!',
'2019-04-05'),
(19, 1554251111, '2019-04-03', 39, 150, 500, 'Pending', '', '2019-04-05');
-- --------------------------------------------------------
--
-- Table structure for table `tblusers`
--
CREATE TABLE IF NOT EXISTS `tblusers` (
`fname` varchar(20) NOT NULL,
`lname` varchar(20) NOT NULL,
`contact` bigint(100) NOT NULL,
àddress` text NOT NULL,
`position` varchar(50) NOT NULL,
ùsername` varchar(30) NOT NULL,
`pass` longtext NOT NULL
--
-- Dumping data for table `tblusers`

--
INSERT INTO `tblusers` (ùser_id`, `fname`, `lname`, èmail`, `contact`, àddress`, `position`,
ùsername`, `pass`) VALUES
(22, 'Adrian', 'Mercurio', 'mercurio@yahoo.com', 0, '', 'Admin', 'admerc',

'$2y$10$0bR0yeMq58tPpMBWx2nuau9jWuzcslpUQVqb81RNMvArQKn/x6D76'),
(23, 'niko', 'curaza', 'curaza@yahoo.com', 0, '', 'Admin', 'merc',

'$2y$10$OnIOsgNRMn3Zk5rvBFmZM.9TBrmWvJBiE7YYn5C9qHNcsMFBv963u'),
(24, 'Nico', 'Raluto', 'raluto@yahoo.com', 0, '', 'Admin', 'qwerty',

'$2y$10$fwsyyHkLWCmMn2bk5uu/RehETPLpZOpu0Uyn.RaMIKOi2.J8Gz5YO'),
(39, 'Adrian', 'Mercurio', 'admerc@yahoo.com', 9561666494, 'Brgy. Su-ay Himamaylan City Neg.
Occ.', 'Customer', 'adam',
'$2y$10$2bzJCkDR3EzQ1pFu8uskMuj65VTcznEyepurqjTbc5AgZ6/9EdvfW'),
(40, 'Nico', 'Raluto', 'ralutonico@yahoo.com', 9561666494, 'Brgy. Su-ay Himamaylan City Neg.
Occ.', 'Customer', 'adams',
'$2y$10$1bqSwPPZO0nb/QWXAYCBcuto38CDf.rg.YjGdK.Xpc6X9h85tIvmW');

CHAPTER-5
TESTING AND SCEREENSHOT
5.1 Testing Introduction
Software testing is the process of executing software in a controlled manner, in order to answer
the question – Does the software behave as specified?. Software testing is often used in
association with the term verification and validation. Validation is the checking or testing of
items, includes software, for conformance and consistency with an associated specification.
Software testing is just one kind of verification, which also uses techniques such as reviews,
analysis, inspections, and walkthroughs. Validation is the process of checking that what has
been specified is what the user actually wanted.
Validation : Are we doing the right job?
Verification : Are we doing the right job?
Software testing should not be confused with debugging. Debugging is the process of analysis
and localizing bugs when software does not behave as expected. Although the identification of
some bugs will be obvious from playing with the software, a methodical approach to software
testing is a much more thorough means for identifying bugs. Debugging is therefore an activity
which supports testing, but cannot replace testing.
Other activities which are often associated with software testing are static analysis and dynamic
analysis. Static analysis investigates the source code of the software, looking for problems and
gathering metrics without actually executing the code. Dynamic analysis looks at the behavior
of software while it is executing, to provide information such as execution traces, timing
profiles, and test coverage information.
Testing is a set of activity that can be planned in advanced and conducted systematically.
Testing begins at the module level and work towards the integration of entire computers based
system. Nothing is complete without testing, as it is vital success of the system testing
objectives, there are several rules that can serve as testing objectives. They are
 Testing is a process of executing a program with intend of

finding error.
 A good test case is one that has possibility of finding an
undiscovered error.
 A successful test is one that uncovers an undiscovered
error.

 If a testing is conducted successfully according to the

objectives as stated above, it would uncover errors in the
software also testing demonstrate that the software
function appear to be working according to the
specification, that performance requirement appear to
have been met.
There are three ways to test program
 For correctness
 For implementation efficiency
 For computational complexity
Test for corrections are supposed to verify that a program does exactly what it was designed to
do. This is much more difficult than it may at first appear, especially for large programs.
5.1.1. Test Plan

A test plan implies a series of desired course of action to be followed in accomplishing various
testing methods. The Test Plan acts as a blue print for the action that is to be followed. The
software engineers create a computer program, its documentation and related data structures.
The software developers is always responsible for testing the individual units of the programs,
ensuring that each performs the function for which it was designed. There is an independent
test group (ITG) which is to remove the inherent problems associated with letting the builder to
test the thing that has been built.
So that the mean time to failure, the cost to find and fix the defects, remaining defect density
or frequency of occurrence and test work-hours per regression test all should be stated within
the test pan.
The levels of testing include:
 Unit Testing
 Integration Testing
 Data Validation Test
5.1.2. Unit Testing

Unit testing focuses verification effort on the smallest unit of software design – the software
component or module. Using the component level design description as a guide, important
control paths are tested to uncover errors within the boundary of the module. The relative
complexity of tests and uncovered scope established for unit testing. The unit testing is white

box oriented, and step can be conducted in parallel for multiple components. The modular
interface is tested to ensure that information properly flows into and out of the program unit
under test. The local data structure is examined to ensure that data stored temporarily
maintains its integrity during all steps in an algorithm’s execution. Boundary conditions are
tested to ensure that all statements in a module have been executed at least once.
Tests of data flows across a module interface are required before any other test is initiated. If
data do not enter and exit properly, all other tests are moot. Selective testing of executed paths
is an essential task during the unit test. Good design dictates that error conditions be
anticipated and error handling paths set up to reroute or cleanly terminate processing when an
error does occur. Boundary testing is the last task of unit testing step. Software often fails at its
boundaries.
Unit testing was done in Sell-Soft system by treating each module as separate entity and testing
each one of them with a wide spectrum of test inputs. Some flaws in the internal logic of the
modules were found and were rectified.
5.1.3 INTEGRATION TESTING

Integration testing is systematic technique for constructing the program structure while at the
same time conducting tests to uncover errors associated with interfacing. The objective is to
take unit tested components and build a program structure that has been dictated by design.
The entire program is tested as whole. Correction is difficult because isolation of causes is
complicated by vast expanse of entire program. Once these errors are corrected, new ones
appear and the process continues in a seemingly endless loop.
After unit testing in Sell-System all the modules were integrated to test for any inconsistencies
in the interfaces. Moreover differences in program structures were removed and a unique
program structure was evolved.
5.1.4 OUTPUT TESTING OR USER ACCEPTANCE TESTING

The system considered is tested for user acceptance; here it should satisfy the firm’s need. The
software should keep in touch with perspective system; user at the time of developing and
making changes whenever required. This is done with respect to the following points.
 Input screen Designs,

 Output Screen Designs,
Online message to guide the user and the like. The above testing is done taking various kinds of
test data. Preparation of test data plays a vital role in the system testing.

Validation checking:
At the culmination of integration testing, software is completely assembled as a package;

interfacing errors have been uncovered and corrected, and a final series of software test-
validation checks may begin. Validation can be defined in many ways, but a simple definition
(Albeit Harsh) is that validation succeeds when software functions in a manner that can be
reasonably expected by a customer. Software validation is achieved through a series of black-
box tests to be conducted and a test procedure defines specific test cases that will be used in
attempts to uncover errors in conformity with requirements are satisfied; all performance
requirements are achieved; documentation is correct and human. Engineering and other
requirements are met. Once the application was made free of all logical and interface errors,
inputting dummy data to ensure that the software developed satisfied all the requirements of
the user did validation checks. However, the data are created with the intent of determiming
whether the system will process them correctly.
In the proposed system, if the clients click the send button after selecting a files from his file
list, then the system will show the confirmation message for sending files. Similarly if a client
makes an attempt to download a file from the server file list, then also the system will show the
configuration message for downloading. This is how the data validations were made in the
proposed system.

5.2. SCREENSHOT
5.2.1 Login Screen
5.2.2 HOME SCREEN

5.2.3 SIGN UP
5.2.4 MY CART

5.2.5 ORDER DETAIL
5.2.4 LIST OF ORDER

CHAPTER-6
TEST REPORT AND CONCLUSIONS

CHAPTER-7
CONCLUSION
The project title as “LOAN MANAGEMENT SYSTEM” is a web based application. This software
provides facility for reporting online crimes, complaints, missing persons, show most wanted
person details mailing as well as chatting. This software is developed with scalability in mind.
Additional modules in the system have been tested with valid data and invalid data and
everything work successfully. Thus the system has fulfilled all the objectives identified and is
able to replace the existing system.
The project has been completed successfully with the maximum satisfaction of the
organization. The constraints are met and overcome successfully. The system is designed as like
it was decided in the design phase. The project gives good idea on developing a full-fledged
application satisfying the user requirements.
The system is very flexible and versatile. This software has a user friendly screen that
enables the users to user without any inconvenience. Validation checks induced have greatly
reduced errors. Provisions have been made to upgrade the software. The application has been
tested with live data and has provided a successful result. Hence the software has proved to
work efficiently.

7.2 FUTURE WORK

In future we can use image recognization instead of using heterogenious database more over
high speed, accuracy and non-redundant data are the main advantages of the proposed system.
In the proposed system the user is provided with a choice of data screen, which are similar in
formats to the source documents. Data entry errors can be minimized through validity checks.
After the verification only the data are placed the permanent database. The software can be
developed further to include a lot of modules because the proposed system is developed on
the view of future, for example we should develop the system as a database independent using
JDBC so we can connect it to any other database. Now the proposed system is based on PC and
intranet but in the future if we need to convert it into internet then we need to change the
front end only because we are developing this on the vases of OOP technology and most of the
business logic’s are bounded in the class files and module like reusable component.

Online Cake Order System Chapter-1: Rrit Dept of Cse 2018-2019

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Online Cake Order System Chapter-1: Rrit Dept of Cse 2018-2019

Загружено:

Авторское право:

Доступные форматы

ONLINE CAKE ORDER SYSTEM

RRIT Dept of CSE 2018-2019 Page 1

2.1.1 EXISTING SYSTEM

2.1.2 PROPOSED SYSTEM

RRIT Dept of CSE 2018-2019 Page 2

2.1.3 AIM OF THE PROJECT

RRIT Dept of CSE 2018-2019 Page 3

2.2 REQUIREMENT ANALYSIS

2.2.1 SOFTWARE REQUIREMENTS:

The software requirements include:

 Web presentation : HTML,CSS,PHP

2.2.2 HARDWARE REQUIREMENTS(MINIMUM):

The hardware requirements include:

 Processor : Intel 5.0 GHz or higher processor

RRIT Dept of CSE 2018-2019 Page 4

3.1.1 LOGICAL DESIGN:

3.1.2 PHYSICAL DESIGN:

 Design the physical system.

RRIT Dept of CSE 2018-2019 Page 5

 Specify input and output media.

3.1.3 Design/Specification activities:

3.1.4 INPUT DESIGN

 What data should be given as input?

3.1.5 OUTPUT DESIGN

RRIT Dept of CSE 2018-2019 Page 6

RRIT Dept of CSE 2018-2019 Page 7

RRIT Dept of CSE 2018-2019 Page 8

4.1 SOURCE CODE

<?php include 'includes/header.php';

<?php include 'includes/sidebar.php';

RRIT Dept of CSE 2018-2019 Page 9

<?php /*include 'includes/iconcards.php'*/;

<?php include 'includes/footer.php';

RRIT Dept of CSE 2018-2019 Page 10

<meta http-equiv="X-UA-Compatible" content="IE=edge">

<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">

<meta name="description" content="">

<meta name="author" content="">

<link href="vendor/bootstrap/css/bootstrap.min.css" rel="stylesheet">

<link href="vendor/fontawesome-free/css/all.min.css" rel="stylesheet" type="text/css">

<link href="css/sb-admin.css" rel="stylesheet">

<link rel="stylesheet" type="text/css" href="css/sb-new.css">

<div class="card card-login mx-auto mt-5">

<div class="card-header"><h3> Login</h3></div>

echo '<p class="signuperror">Wrong password</p>';

RRIT Dept of CSE 2018-2019 Page 11

<form action="includes/signin.php" method="post">

<input type="text" id="inputEmail" name="mailuid" class="form-control"

<input type="password" id="inputPassword" name="pwd" class="form-control"

<input type="checkbox" value="remember-me">

RRIT Dept of CSE 2018-2019 Page 12

<button class="btn btn-primary btn-block" name="login-submit">Login</button>

<a class="d-block small mt-3" href="register.php">Signup</a>

<a class="d-block small mt-3" href="index.php">Home</a>

<?php /include 'includes/iconcards.php'/;