Spicekarthardcpymain

Project Report 2019 SPICE KART
1. INTRODUCTION
Al-Ameen college edathala 1

1.1 PROJECT OVERVIEW
The project entitled “ SPICE KART ”- Online Spice Selling System is a complete system
for management of sales, purchases. This system will also help you in creation of bills,
payment receipts, and item names with dimensions and price such as MRP and DP. This
software has the power to regulate, dominate, or manipulate Services and items, written
specifically for the Windows® desktop environment. This project envisages the use of
MYSQL to process database so that data from them are embedded in the SQL Server. The
PHP as the front end, which is processed to manipulate SQL server for the processes like
addition, update, deletion etc. Apart from this, it is assured that the user friendliness of the
system will help the end user simplify the processes involved in the system
In modern world all fields of endeavour have been touched by the computer revolution.
The advantage of computers does not end just with speed. The accuracy, need for less
space for data storage security from discrepancies etc are just a few of its innumerable
advantages.
The project deals with web based shopping. Users of the site can login to the site by
using their user id and password. After login they can choose different products they
want. Inside the site, they feel, they are in a Shopping Mall. They can buy the products as
much as they want. In side the site we are using a shopping cart to enable easy shopping.
First the users can choose the products and then they can customize the quantity and
products.

1.2 LITERATURE SURVEY

Online Spice selling System helps the customers to order the details they would like to
purchase through the net. It also gives the details of the products like its category,
subcategory, rate etc. The customers can purchase the products through the net. It helps
them to reduce the difficulties of shopping in a shop.
The main objective of “Online Spice Selling System” is to develop a user friendly
computerized system to manage all the manual works. It reduces the difficulties of
purchasing products from the shops. This will help the customers to buy the products
using only mouse clicks and they can receive the products at their home by VPP. They
had to pay the money only that time.
Certain important objectives to be provided in the system are,
Decrease in the workload.
The system should be user friendly
Minimized processing time
The system should be error free &System should possess maximum efficiency

2. SYSTEM ANALYSIS

2.1EXISTING SYSTEM:
The existing system operates manually.A wide variety of reports should also be
maintained by the management in order to carry out the activities in an efficient and
effective manner. In such circumstances the staff has to work hard for the preparation
of manual report. Information is meaningful only if it is available in time. There may
be a chance of occurring errors at the time of manual preparation.
The management cannot obtain all the information in time. The company
administrators and the managers have to wait till the report work is completed.
Finally the report should be submitted to the higher-level people manually. The
networking effect of making information instantly available is not possible with the
existing system.
2.2 PROPOSED SYSTEM:

management of “Online Spice selling System”. It provides easy manipulation of data for
the users of the system.The proposed system offers the following services.
Give details about a customer’s details.
Give details of the Products and their Price.
Give details about the type of works and the amount per square feet
Advantages:
The main advantage of the proposed system is user convenience. In this system, each
module is built in such a way that the user needs to enter relevant data. The system is
secured because only authorized users can enter into the system using the username and
password. Further improvement in the system is maintained by providing validation test
at each field and also by providing proper messages at each step. This helps in reducing
the bugs and also improves the efficiency of the system.

2.3 FEASIBILITY STUDY
2.3.1 Introduction
Feasibility study is a procedure that identifies, describes and evaluates

candidate systems and selects the best system for the job. An estimate is made of whether
the identified user needs may be satisfied using current software and hardware
technologies. The study will decide if the proposed system will be the cost effective from
a business point of view and if it can be developed given existing budgetary constraints.
The key considerations involved in the feasibility analysis are economic, technical,
behavioral and operational.
On the basis of result of the initial study, feasibility study takes
place. The feasibility study is basically the test of the proposed system in the light of its
workability, meeting user’s requirements, effective use of resources and of course, the
cost effectiveness. The main goal of feasibility study is not to solve the problem but to
achieve the scope. In the process of feasibility study, the cost and benefits are estimated
with greater accuracy. During system analysis, the feasibility study of the system of the
proposed system is to be carried out. The main objective of this study is to determine
whether the proposed system is feasible or not i.e., to ensure that proposed system is not a
burden to the company. The study can be categorized into three types. They are:
Economic feasibility
Technical feasibility
Behavioral feasibility
2.3.2 Technical Feasibility
The system must be evaluated from the technical point of view first. The assessment of
this feasibility must be based on an outline design of the system requirement in the
terms of input, output, programs and procedures.
Technical issues raised during the investigation are:
 Does the existing technology sufficient for the suggested one?

 Can the system expand if developed?

2.3.3 Economic Feasibility
The developing system must be justified by cost and benefit. Criteria to ensure that
effort is concentrated on project, which will give best, return at the earliest. The
following are some of the important financial questions asked during preliminary
investigation:
 The costs conduct a full system investigation.

 The cost of the hardware and software.
 The benefits in the form of reduced costs or fewer costly errors.
2.3.4 Behavioral Feasibility

The project would be beneficial because it satisfies the objectives when
developed and installed. All behavioral aspects are considered carefully and conclude
that the project is behaviorally feasible. This includes the following questions:
 Is there sufficient support for the users?

 Will the proposed system cause harm?
2.4 ANALYSIS MODELLING
2.4.1 Data Modeling
It defines all data objects that are processed within the system, the relationship
between the data objects, and other information that is pertinent to the relationships.
The entity –relationship diagram(ERD) addresses these issues and represents all data
objects that are entered, stored, transformed, and produced within an application. Data
modeling tools provide a software engineer with the ability to represent data object,
their characteristics, and their relationships. Used primarily for large database
applications and other information systems projects, data modeling tools provide an
automated means for creating comprehensive entity relation diagrams, data object
dictionaries, and related models.

Data Flow Diagrams
Data flow design is concerned with designing a sequence of functional transformations

that converts system input into the required outputs.DFD can be drawn using the
following symbols
 A square defines a source (originator) or destination of system data.
 An arrow identifies data flow in motion. It is a pipeline through which information

symbols.
 A circle or bubble represents the process that transforms the incoming data flows
into outgoing data flows.
 A rectangle represents a data store or temporary repository.
DATA FLOW DIAGARAM:

Context Level:

Level 1.1
Level 1.2

2.4.2Entity Relationship Diagrams
Entity Relationship Diagrams (ERDs) illustrate the logical structure of databases. An

entity is an object or concept about which you want to store information. Attributes are
the properties or characteristics of an entity. Relationships illustrate how two entities
share information in the database structure.
ER Diagram:

3. SYSTEM DESIGN

3.1 INPUT DESIGN
3.1.1 User Interface Design
The interface describes how the website

communicates with itself. The user interface is the link between the audience and the
capabilities of our website. A well designed user interface makes it very easy for audience
to learn website. The user interface portion of website is responsible for all interaction
with the user .Development of good user interface usually takes a significant portion of the
total system development effort.GUI can be defined as a program interface that takes
advantages of the computer’s graphic capabilities to make the program easier to use.
The SPICE KART is a web based application. Web

application use MVC architecture. The web application resides on a server and responds to
request from multiple clients over the Internet on the client side, a browser, such as
Internet Explorer, Netscape Navigator, hosts the Web application. The application’s user
interface takes the form of jsp pages that are interpreted and displayed by the client’s
browser. On the server side, the Web application runs under WAMP Server. It manages
the application,passes requests from clients to the application, and returns the application’s
response to the client.
3.1.2 Content Design
Content design focuses on two different design tasks, each addressed by

individuals with different skill test sets. First, a design representation for content objects
and the mechanisms required to establish their relationship to one another is developed.
In addition, the information within a specific content object is created. The latter task
may be conducted by copywriters, graphic designers, and others who generate the
content to be used within a WebApp.

3.2 OUTPUT DESIGN
Once the WebApp Architecture has been established and the component of
the architecture has been identified, you must define navigation path way that enable
users to access WebApp content and functions. To accomplish this, you should
(1) Identify the semantics of navigation for different users of the site.
(2)Define the mechanics of achieving the navigation.
The main pages used in the system are,
Admin’s pages
 Admins home page

 Category delete page
 SubCategory edit page
 Category edit page
 Item delete page
 Item edit page
 Category adding page
 SubCategory adding page
 Item adding page
 SubCategory delete page
 Customer report page
 Sales report page
 Item report page
Customers’s pages
 Customer home page
 Customer profile page
 Customer product page
 Customer cart page
 Product viewing page

 Payment pages
Company’s pages
 Company home page

 Company about page
 Contact us page
 login page
 Customer registration page
The SPICE KART contains a Login page from there each users are directed to
their corresponding home pages according to their user type. In the administrator’s
home page administrator can view all current customers, companies, products, and add
product categories. Also he is able to frequent analysis on the site to find which all
categories of products have the highest selling count. Using this data he is able to create
offers on a product combo’s. He is also responsible for activating, deactivating and
deleting the offers that he creates.
The user who initially comes into the site is a guest who is able to view all the
products but cannot purchase the products. The guest is able to login or register to the
site. A guest can either register as a customer or a company. But in order for a company
to be registered the admin have to approve the company. This will be done once a
company registers into the site and the admin contacts the company to review the
company status and details the company have entered. A customer is able to purchase
the products in the site once he/she login to the site. The customer is given the ability to
update his/her details like address, contact etc in the event of any changes occurring in
their life. After purchase of a product the customer is liable to rate the products (out of
10) so that the admin can see which all products has the highest ratings.
Once a company is approved by the company the company is able to add their
products to the site of sale. The company is able to delete or update the products as they
wish. They are also able to update the company details. They are also capable of
viewing the orders on their products and also view which of their products are selling
faster.

Modern WebAPP delivers increasingly sophisticatedprocessing functions that,
(1) Perform localized processing to generate content and navigation capability in a

dynamic fashion,
(2) Provide computation or data processing capability that is appropriate for the
WebApp’s business domain,
(3) Provide sophisticated database query and access,
(4) Establish data interface with external cooperate system.
To achieve these capabilities you must design and construct program component that are
identical in form to software components for traditional software.Component level
design occurs after the first iteration of architectural design has been completed .At this
stage, the overall data and program structure of the software has been established. The
intent is to translate the design model into operational software. The component level
design represents the software in a way that allows you to review the details of the
design for correctness and consistency with other design representations.

3.3 DATA BASE DESIGN
After designing the input and output the next step is

to concentrate on file designed how data should be organized around user requirements.
A database is a collection of interrelated data with minimum redundancy to serve many
users quickly and efficiently. The general objective is to make information access easy,
quick, inexpensive and flexible for the user. The most important aspect of building an
application is the design of tables or the database schema. The data stored in the tables
must be organized in some manner, which is meaningful. The overall objective in the
process of table design has been to treat data as an organizational resource and as an
integrated whole in the database. The tables used are listed in the next page.
SPICE KART Tables:
 cart
 tbl_category
 tbl_customer
 tbl_item
 tbl_login
 tbl_paymet
 tbl_sale
 tbl_stock
 tbl_subcategory

1. cart
Column Type Null Discription
id int(11) No customer id
c_fname varchar(20) No Customer name
img varchar(20) No Product image
item_name varchar(20) No Product name
cqty int(20) No Product quantity
crate int(20) No Product rate
ctotal int(20) No Cart total
2. tbl_category
Column Type Null Description
cat_id int(20) No Category id
cat_name varchar(20) No Category name
cat_desc varchar(50) No Category discription
3.tbl_login
id int(20) No Customer id
username varchar(20) No Customer username
password varchar(20) No Customer password

4.tbl_customer
cust_id int(20) No Customer id
c_fname varchar(20) No First name
c_lname varchar(20) No Last name
c_hname varchar(20) No House name
c_street varchar(20) No street
c_city varchar(20) No city
c_gender varchar(20) No gender
c_phn varchar(50) No Phone number
c_email varchar(20) No Email id
5.tbl_item
item_id int(20) No Item id
item_name varchar(20) No Item name

6.tbl_payment
pay_id int(20) No Payment id
c_fname varchar(20) No Customer name
status varchar(10) No Payment status
7.tbl_sales
s_id int(20) No Sales id
om_id int(20) No Order id
fname varchar(20) No Customer name
status varchar(20) No status
8.tbl_stock
stock_id int(20) No Stock id
item_name varchar(20) No Item name
batch_id int(20) No Catogery id

9.tbl_subcategory
sc_id int(20) No Subcategory id
Subcategory
sc_name varchar(20) No
name
3.4 MODULE DESIGN
3.4.1 Introduction
It is tied to the goals established for a web App, the content to be presented, the
user who will visit and the navigation philosophy that has been established. As an
architectural designer, you must identify content architecture and WebApp Architecture.
Content architecture focuses on the manner in which content objects are structured for
presentation and navigation. WebApp Architecture addresses the manner in which the
application is structured to manage user interaction, handle internal processing tasks,
effect navigation and present content.
3.4.2 Modules of the Project
 CUSTOMER:
Customers are required to register on the website before they can do the
buying of products. Customers have ability to browse and search product by name and
categories, adding products to the shopping basket for check out and register order.
Non-registered users can visit and view the products. But they cannot do the buying
before registration.
 SHOPPING CART:
Shopping cart module tries to simulate the working of a store where user can
view each design, color, size and price of the product available. The items they like can
be added to the logical cart and can be removed if not required later. Billing and other
payment related matters are handled here.

 COMPANY:
Companies are required to register on the website and they can login to the site
only after the approval of Administrator. Then the company can add, delete or update
the product information and also view the ordered product of that company.
 ADMINISTRATION:
Administrators are responsible for approving and removing the companies from
the website. Different categories of items are added by administrator. The admin is
responsible for producing offers by analysing apriori data. The offer’s created can then
be activated, deactivated and deleted according to the wish of the admin.
1. User Management
The User Management module deals with the registration of Customers. It

includes adding, deleting, and updating of company details and customer details. The
Administrator has the ability to approve or delete a company through this module.
Input:-
New customer details
New company details
Updating Company Details.
Updating Customer details
Processing:-
Adding of a new Company.

Adding of new Customer.
Editing Information.
Delete Company.
Approval of company
Output:-
Information of Companies.
Information of Customers.

2. Product Management
In this module the product for different companies are managed. It consist of
adding, updating and deleting of product and their details.
Input:-
Add product details of Company.
Edit Information.
Processing :-
Add Details.
Edit Details.
Delete Product.
Output :-
Status Information of Products.
3. Shopping
The users can browse product hosted by various companies and can buy them if
they like it.
Input :-
Adding Products to cart.

Processing :-
Calculating Product Cost.

Output:-
Refined Cart List.

4. Order Management and Billing
Order management consist of calculation of cost for users and the billing
procedures.
Input :-
Billing Information
Billing Address
Processing :-
Process Billing.
Output :-
View Order Information.
5. Knowledge Base Management
Here the transaction database is processed using the Apriori algorithm to

construct a knowledgebase that allows the user to select product efficiently.
Input :-
Purchase Information
Processing :-
Apriori Algorithm
Output :-
Strong Rules

4. SYSTEM SPECIFICATION

System specification results in the specification of software’s operational

characteristics and establish constraints that software must meet. Requirement analysis
allows a software engineer to elaborate on basic requirements establish during the
inception, elicitation and negotiation tasks that are part of requirements engineering. The
requirements modeling action results in one or more types of model. These models
provide a software engineer with information that can be translated to architectural and
component level designs. Finally, the requirements model provides the developer and
the customer with the means to access quality once software is built.
4.1 HARDWARE SPECIFICATION

CPU :Intel® Pentium IV Processor 3.20GHz, 512K / 800MHz
FSB
Memory :1GB (min) RAM, 10 GB (min) HD
Keyboard :Entry Level Quiet key Keyboard, PS/2
Mouse :PS/2, 2 button with scroll
Monitor :15 inch Monitor
Front Side Bus :800 MHz
LAN :100.0 Mbps
4.2 SOFTWARE SPECIFICATION
Operating System :Microsoft® Windows XP Professional
Browser : Internet Explorer 6 or Mozilla Fire Fox
Programming Tool :Eclipse juno
Programming Technology :j2EE
Client side Script Language :Jquery
Server side Script Language :JAVA
Back End :mysql-essential-5.1.71
Web Server
Operating System :MS Windows Server 2008 or Higher
Web Server :Apache-tomcat-7.0.42

Implementation Specification
Operating System :Linux, windows 98 above, Solaris, etc
Web browser :Any java enabled browser
4.3 OVERVIEW OF PHP
PHP is an intuitive, server side scripting language. Like any other scripting
language it allows developers to build logic into the creation of web page content and
handle data returned from a web browser. PHP also contains a number of extensions that
make it easy to interact with databases, extracting data to be displayed on a web page and
storing information entered by a web site visitor back into the database.
PHP consists of a scripting language and an interpreter. Like other scripting

languages, PHP enables web developers to define the behavior and logic they need in a
web page. These scripts are embedded into the HTML documents that are served by the
web server. The interpreter takes the form of a module that integrates into the web server,
converting the scripts into commands the computer then executes to achieve the results
defined in the script by the web developer.

4.4 OVERVIEW OF MySql
MySQL isthe world's second most widely used open-source relational database
management system (RDBMS). It is named after co-founder Michael Widenius's
daughter, My. The SQL phrase stands for Structured Query Language.
The MySQL development project has made its source code available under the
terms of the GNU General Public License, as well as under a variety of proprietary
agreements. MySQL was owned and sponsored by a single for-profit firm, the Swedish
company MySQL AB, now owned by Oracle Corporation.
MySQL is a popular choice of database for use in web applications, and is a

central component of the widely used LAMP open source web application software
stack (and other 'AMP' stacks). LAMP is an acronym for "Linux, Apache, MySQL,
Perl/PHP/Python." Free-software-open source projects that require a full-featured
database management system often use MySQL.
For commercial use, several paid editions are available, and offer additional
functionality. Applications which use MySQL databases include: TYPO3, MODx,
Joomla, WordPress, phpBB, MyBB, Drupal and other software. MySQL is also used in
many high-profile, large-scale websites, including Wikipedia, Google (though not for
searches), Facebook, Twitter, Flickr, and YouTube.

5. SYSTEM DEVELOPMENT

5.1 MODULE DESCRIPTION
 CUSTOMER:
Customers are required to register on the website before they can do the
buying of products. Customers have ability to browse and search product by name and
categories, adding products to the shopping basket for check out and register order.
Non-registered users cannot visit and view the products. and they cannot do the buying
before registration.
 SHOPPING CART:
Shopping cart module tries to simulate the working of a store where user can
view each design, color, size and price of the product available. The items they like can
be added to the logical cart and can be removed if not required later. Billing and other
payment related matters are handled here.
 ADMINISTRATION:
Administrators are responsible for approving and removing the companies from
the website. Different categories of items are added by administrator. The admin is
responsible for producing offers by analysing apriori data. The offer’s created can then
be activated, deactivated and deleted according to the wish of the admin.
1. User Management
The User Management module deals with the registration of different companies
and Customers. It includes adding, deleting, and updating of company details and
customer details. The Administrator has the ability to approve or delete a company
through this module.
2. Product Management
In this module the product for different companies are managed. It consist of
adding, updating and deleting of product and their details.

3. Shopping
The users can browse product hosted by various companies and can buy them if
they like it. This includes the process of adding the products to the logical cart. The
customer is then able to remove the products he do not want and redefine the cart. After
this he is able to undergo payment for the items he bought and finalise the transaction.
4. Order Management and Billing
Order management consist of calculation of cost for users and the billing
procedures.
5. Knowledge Base Management
Here the transaction database is processed using the Apriori algorithm to

construct a knowledgebase that allows the user to select product efficiently.

6. SYSTEM TESTING

6.1. TESTING
Testing is a set of activity that can be planned in advance and conducted

systematically, which is aimed at ensuring that the system works accurately and
efficiently before live operations commences. Software testing is the process used to
measure the quality of developed computer software. Usually, quality is constrained to
such topics as correctness, completeness, security, but can also include more technical
requirements as described under the ISO standard ISO 9126, such as capability,
reliability, efficiency, portability, maintainability, compatibility, and usability. Testing is
a process of technical investigation, performed on behalf of stakeholders, that is intended
to reveal quality-related information about the product with respect to the context in
which it is intended to operate. An important point is that software testing should be
distinguished from the separate discipline of Software Quality Assurance (SQA), which
encompasses all business process areas, not just testing.
There are many approaches to software testing, but effective testing of

complex products is essentially a process of investigation, not merely a matter of creating
and following routine procedure. One definition of testing is "the process of questioning a
product in order to evaluate it", where the "questions" are operations the tester attempts to
execute with the product, and the product answers with its behavior in reaction to the
probing of the tester.
In general, software engineers distinguish software faults from software

failures. In case of a failure, the software does not do what the user expects. A fault is a
programming error that may or may not actually manifest as a failure. A fault can also be
described as an error in the correctness of the semantic of a computer program.
 Testing is the process of correcting a program with intend of finding an error.

 A good test case is one that has high probability of finding a yet undiscovered error.
 A successful test is one that uncovers a yet undiscovered error.

Testing Objectives
 Testing is a process of executing a program with the intent of finding an error.
 A good test case is one that has high probability finding an undiscovered error.
 A successful test is one that uncovers an undiscovered error.
Testing is vital to the success of the system. System testing makes a logical
assumption that if all parts of the system are subject to variety of tests on-line response,
volume, stress, recovery and security and usability tests. A series of tests are performed
before the system is ready for user acceptance testing.
Test Procedure
The procedure is as follows:
 Prepare the test case.

 Record the expected results and verify whether in tune with actual results.
 If actual results are not in tune with the expected results, do the necessary
rework?
 Test again and check for the results.
 If the results are satisfactory, wind up testing.
Item Pass / Fail Criteria
The test case consists of different inputs with the expected results in each case.
During testing, the Tester records the Actual Test Results against the expected ones and if
found matching, the test case is assigned as a Pass. Otherwise, the Test Case is assigned
as a Fail and orders for Rework and Retest.
Stop Criteria
The testing can be wrapped up when
 Actual Test Results match with the expected ones.

 System performs well in the specified environment.
The different testing criteria conducted are following

6.1.1 Unit Testing
The strategy for unit testing is that unit would be the standard approach for
performing unit testing, unless specifically stated. The unit test cases would have to be
created before coding. The unit test cases should be created for all public methods of
classes developed, unless specifically stated. Unit testing should be done for each class as
soon as its development is completed. Irrespective of methodology used, developers
should ensure code coverage specified in MTP is met during unit testing. Unit testing of a
developer’s code should be mandatory be performed before integration of code. Interface
testing can be considered complete, when unit testing of the business interfaces is
completed. Inter-subsystem integration and Client-server integration should not be done
unless interface testing is completed.
Advantages:
 Reduction in number of defects

 Reduction in development time and effort
 Reduction in integration and testing time and effort
Detailed Strategy
Server side
The unit test cases would be created for the public methods of all server side
classes. Unit Test Cases need not be created for Query Constructor and VO classes.
Interface testing would be done once all classes for a business method are unit tested and
developed. Unit testing of delegate classes in isolation is not required. Testing can be
done after integrating with server. Server developers should do this testing.
Client side
Client side testing should be done before integration with server code. Dummy
delegates are to be used for the testing all flows as per use case have to be tested. The data
displayed in the screen correctly represents the data got from the delegate. The correct
Screens/ Pop ups/ Messages are displayed. The testing should also check correctness
against the GUI Specification of the corresponding screen.

6.1.2 Integration Testing
Integration testing is a 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 the design.
Bottom-up integration
Bottom-up integration testing begins construction and testing with atomic

modules (i.e., modules at the lowest levels in the program structure). Because the
modules are integrated from the bottom up, processing required for the modules
subordinate to a given level is always available and the need of stubs is eliminated.
A bottom-up integration strategy may be implemented with the help of the

following steps:
 Low level modules are combined into clusters (sometimes called builds) that
perform a specific software sub-function.
 A driver (a control program for testing) is written to coordinate test case input
and output.
 The cluster is tested.
 Drivers are removed and clusters are combined moving upward in the program
structure.
6.1.3 System Testing
System testing was done on a complete, integrated system in order to evaluate

whether the system compliance with its specified requirements. The system was tested
and checked whether it gives the results that are expected from the software.

6.1.4 Validation testing
Validation testing is done on the Virtual Classroom system to check whether all
the data are filled appropriately in the various text boxes and combo boxes. In this
Software all the validations are done using java script. The software validates each data
provided through the various forms and gives appropriate messages accordingly so that
the user will not be able to proceed without giving relevant information. The system was
given various wrong values to see the proper display of error messages.
6.2 TEST CASES
 Test cases of Login Module
No. Test Scenario Expected Result Result
Enter wrong user name and

1 Display an ‘invalid’ message Passed
password
Enter correct user name and Load login page again with ‘invalid’
2. Passed
wrong password message
Enter correct user name and

3 correct password of Administrator can login to the system. Passed
Administrator
User can login to the system. The

Enter correct user name and
4 corresponding page should load with Passed
correct password of user
menu.

 Test cases of User Add
Select the ‘User’ option from the given Displays the form for User
1 list Passed
registration
Enter values to the fields which are not
corresponding to the database fields Displays a message tells the
2 (eg: non-letters to the candidate name, values entered are non -type Passed
phone numbers containing non-
numerals, etc)
Enter non matching passwords Display a message prompting

3 Passed
passwords do not match
Click Submit button without entering Displays Error message to the

4 Passed
values to all necessary fields necessary fields
Stores the data entered into

All data enter correctly and click the data base, and display the
5 Passed
Submit. ‘Submission was successful’
message to the User.
 Test cases of adding product to cart
Select the product from the user home Displays the product viewing
1 page form for User for adding Passed
product to the cart
Displays a message tells the
Enter the quantity in the quantity box values entered are non -type
2 Passed
box
Click ADD button without entering Displays Error message to the

3 Passed
All data enter correctly and click product added to the cart
4 Passed
ADD. successfully

 Test cases of ProductAdd
Select the ‘add product’ option from Displays the form for adding
1 the given list Passed
products
Enter values to the fields which are not Displays a message tells the
1 Passed
corresponding to the database fields values entered are non –type
Click Submit button without entering Displays Error message to the

2 Passed
Stores the data entered into

All data enter correctly and click the data base, and display the
3 Passed
Submit. ‘Submission was successful’
message to the User.
INTEGRATION TESTING
After the completion of testing each individual module, the modules are linked
together. Now it should work properly apart from working individually. This linking
of modules often referred as interfacing. Data loss may occur at the time of
interfacing. This should be carefully avoided because this will affect the other
modules also. Integration testing is systematic technique for constructing the program
linkage while conducting tests at the same time to uncover errors associated with that
interface. The tests were carried out each time a module was linked.

Integration test report
Working of software with the It should work properly apart from

1 modules linked Passed
working individually
SYSTEM TESTING
When a system is developed, it is hoped that it performs properly. In practice,

however, some errors always occur. The main purpose of testing an information system is
to find the errors and correct them. A successful test is one which finds an error.Test is
done by checking comprehensive evaluation of the programs, manual procedures,
computer operation and controls.
System testing report
No. Test Scenario Result
1 During operation system should perform as per specification. Passed
2 During operation system should meet user requirement. Passed
3 Whether controls incorporated in the system function as intended Passed
4 When correct inputs are entered output should be correct Passed
5 Make sure that during operation, incorrect inputs will be deleted. Passed

The common view of testing held by users is that it is performed to prove that
there are no errors in a program. However, as indicated earlier, this is virtually
impossible, since analyst cannot prove that website is free and clear of errors. The tester,
who may be the program fail. A successful test, then, is one that finds an error. Analysts
know that an effective testing program does not guarantee system reliability. Therefore,
reliability must be designed into the system.
Testing Strategies
A test is a set of data that the system will process as normal input.
However, the data are created with the express intent of determining whether the system
will process them correctly. There are two general strategies for testing website. Code
Testing have to test cases that result in executing every instruction in the program or a
module; but is every path through the program is tested.

7. SYSTEM IMPLEMENTATION

7.1 IMPLEMENTATION OF THE PROJECT
The implementation is the final stage and it is an important phase. It involves the
individual programming; system testing, user training and the operational running of
developed proposed system that constitutes the application subsystems. One major task of
preparing for implementation is education of users, which should really have been taken
place much earlier in the project when they were being involved in the investigation and
the design.
The implementation phase of the website development is concerned with

translating design specifications into source code. The user tests the developed system
and changes are made according to their needs. Our system has been successfully
implemented. Before implementation several tests have been conducted to ensure that no
errors are encounter during the operation. The implementation phase ends with an
evaluation of the system after placing it into operation for a period of time.
Implementation is the third phase of the system process. In order to achieve the objectives
and the expected performance the system has been developed in a highly interactive and
user-friendly manner.
7.2 POST-IMPLEMENTAION AND SOFTWARE MAINTENANCE
Maintenance involves the software industry captive, typing up system resources. It

means restoring something to its original condition. Maintenance involves a wide range
of activities including correcting, coding, and design errors, updating documentation and
test data, and upgrading user support. Maintenance was done after the success
implementation. Maintenance is continued till the product is reengineered or deployed to
another platform. Maintenance is also done based on fixing the problems reported,
changing the interface with other software or hardware enhancing the software.

8. RESULTS

The system is designed for effective implementation of Market Basket Analysis
and products are managed and sold on the system. The outputs are optimum.
The customers are able to buy the items in the website and all payment related
information is given to the customer as well as the company. The companies are able to
add their products to the site and the orders on their products are viewed by the
company along with the customer details. The administrator is able to frequently
analyse which all categories of products gets sold together and he is able to create
effective offers for the customers.

9. CONCLUSION

This project, SPICE KART, was successfully completed within the time span
allotted. All the modules are tested separately and put together to form the main system.
Finally the system is tested with real data and everything worked successfully. Thus the
system has fulfilled the entire objective identified.
The system had been developed in an attractive dialog fashion. So user with
minimum knowledge about computers can also operate the system easily to conclude
this, we thank all people who help us to complete this project successfully.

10. FUTURE ENHANCEMENT

For the future enhancement, this system includes several things. This system
currently does not give any printable reports. The system can be modified to give
printed reports of activities and transactions. We can set up a more efficient way for
users to communicate within the website.
The main thing is that, currently when a hardware or software reaching its
warranty period, it does not giving any information about it. So in future it can be
integrated with the system. All the customer problems can record for future references.
And also we can implement a SMS or mail server for providing confirmation to the
customers about the status of requests. It also has to implement a mail server for
providing feedback to the site. Another thing is to produce invoices of the purchasing
items. It is very essential in organization management.

ANNEXURE 1

SCREENSHOTS
1.home page
2.CustomerRegistration page


3.About
4. Contact us

5. Log in
6. Admin_home

7. Add item
8. edit or delete

8.Reports

ANNEXURE 2

SAMPLE CODES
DB connection :
<?php
mysql_connect("localhost","root","");
mysql_select_db("dbspicekart");
?>
Home page code:
<!DOCTYPE html>
<html lang="zxx">
<head>
<title> Spice kart</title>

<link href="css/bootstrap.min.css" rel="stylesheet" type="text/css" media="all">


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


<link rel="stylesheet" href="css/flexslider.css" type="text/css" media="all" />

<link href="css/JiSlider.css" rel="stylesheet">

<link rel="stylesheet" href="css/shop.css" type="text/css" />



<link href="css/style.css" rel='stylesheet' type='text/css' media="all">

<link href="//fonts.googleapis.com/css?family=Sunflower:500,700" rel="stylesheet">
<link href="//fonts.googleapis.com/css?family=Open+Sans:400,600,700"
rel="stylesheet">
</head>
<?php
include "connect.php";
?>
<body>
<div class="header-outs" id="home">
<div class="header-bar">
<div class="info-top-grid">
<div class="info-contact-agile">
<ul>
<li>
</li>
</ul>
</div>
</div>
<div class="container-fluid">
<div class="hedder-up row">
<div class="col-lg-3 col-md-3 logo-head">
<h1><img src= "pic/1111.png" width=125 height=100/>  <a class="navbar-

brand"> Spice Kart</a></h1>
</div>
<div class="col-lg-5 col-md-6 search-right">
<form class="form-inline my-lg-0">
</form>

</div>
</div>
</div>
<nav class="navbar navbar-expand-lg navbar-light">
<button class="navbar-toggler" type="button" data-toggle="collapse" data-
target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-
expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse justify-content-center"
id="navbarSupportedContent">
<ul class="navbar-nav ">
<li class="nav-item active">
<a class="nav-link" href="index.php">Home <span class="sr-
only">(current)</span></a>
</li>
<li class="nav-item ">
<a class="nav-link" href="about.php">About <span class="sr-only"></a>
</li>
<a class="nav-link" href="contact.php">Contact Us <span class="sr-only"></a>
</li>
<li class="nav-item">
<a href="login.php" class="nav-link" style="color: black">Login</a>
</li>
<a href="cregister.php" class="nav-link" style="color: black">Sign up</a>

</li>
</ul>
</ul>
</div>
</nav>
</div>

<div class="slider text-center">
<div class="callbacks_container">
<ul class="rslides" id="slider4">
<li>
<div class="slider-img one-img" style="background-image: url(spices/spices-1.jpg)">
<div class="container">
<div class="slider-info ">
<h5>Explore the world of<br>Spices</h5>
<div class="bottom-info">
<p>We have the world's best spicesjust for you </p>
</div>
<div class="outs_more-buttn">
<a href="about.php">Read More</a>
</div>
</div>
</div>
</div>
</li>
<li>
<div class="slider-img two-img" style="background-image: url(spices/1234.jpg)">

<div class="slider-info ">
<h5>World's best Arabian spices<br></h5>
<p></p>
</div>
<div class="outs_more-buttn"> </div>
</div>
</div>
</div>
</li>
<li>
<div class="slider-img three-img" style="background-image:
url(spices/spices_seasonings_additives_bags_black_background_78727_3840x2400.jpg)"
>
<div class="slider-info">
<h5>Come and grab them at <br> amazing prices</h5>
<p>Hurry up....</p>
</div>
<div class="outs_more-buttn">
<a href="about.php">Read More</a>
</div>
</div>
</div>
</div>
</li>
</ul>
</div>



<div class="clearfix"></div>
</div>
</div>
<section class="subscribe">
<div class="row"></div>
</div>
</section>


<footer class="py-lg-4 py-md-3 py-sm-3 py-3 text-center">
<div class="copy-agile-right">
</div>
</footer>


<script src='js/jquery-2.2.3.min.js'></script>


<script src="js/minicart.js"></script>
<script>
toys.render();

toys.cart.on('toys_checkout', function (evt) {

var items, len, i;
if (this.subtotal() > 0) {
items = this.items();
for (i = 0, len = items.length; i < len; i++) {}

}
});
</script>


<script src="js/responsiveslides.min.js"></script>
<script>
// You can also use "$(window).load(function() {"
$(function () {
// Slideshow 4
$("#slider4").responsiveSlides({
auto: true,
pager:false,
nav:true ,
speed: 50,
namespace: "callbacks",
before: function () {
$('.events').append("<li>before event fired.</li>");
},
after: function () {
$('.events').append("<li>after event fired.</li>");

}
});
});
</script>


<script src="js/jquery.flexisel.js"></script>
<script>
$(window).load(function() {
$("#flexiselDemo1").flexisel({
visibleItems: 3,
animationSpeed: 3000,
autoPlay:true,
autoPlaySpeed: 2000,
pauseOnHover: true,
enableResponsiveBreakpoints: true,
responsiveBreakpoints: {
portrait: {
changePoint:480,
visibleItems: 1
},
landscape: {
changePoint:640,
visibleItems:2
},
tablet: {
changePoint:768,
visibleItems: 2

}
}
});
});
</script>


<script src="js/move-top.js"></script>
<script src="js/easing.js"></script>
<script>
jQuery(document).ready(function ($) {
$(".scroll").click(function (event) {
event.preventDefault();
$('html,body').animate({
scrollTop: $(this.hash).offset().top
}, 900);
});
});
</script>

<script>
$(document).ready(function () {
var defaults = {
containerID: 'toTop', // fading element id
containerHoverID: 'toTopHover', // fading element hover id
scrollSpeed: 1200,

easingType: 'linear'
};
$().UItoTop({
easingType: 'easeOutQuart'
});
});
</script>


<script src="js/bootstrap.min.js"></script>

</body>
</html>
Registration page :
<!DOCTYPE html>
<html lang="zxx">
<head>
<title>Customer registration</title>




rel="stylesheet">
<style type="text/css">
body,td,th {
font-family: Sunflower, sans-serif;
}
body {
margin-left: 0px;
}
</style>
</head>
<?php
?>
<body>

<h1><a href="index.php"><img src= "pic/1111.png" width=125
height=100/></a>  <a class="navbar-brand" href="index.php"> Spice
kart</a></h1>
</div>
</div>
</div>
</button>
<a class="nav-link" href="index.php">Home <span class="sr-only"></a>
</li>
<a href="about.php" class="nav-link">About</a>
</li>
</ul>
</div>
</nav>
</div>
</div>


<div class="inner_page-banner one-img" style="background-image: url(pic/new/pexels-
photo-1086719.jpeg)">
</div>



<section class="contact py-lg-4 py-md-3 py-sm-3 py-3">
</section>
<div class="modal-body" align="justify">
<div class="container py-lg-5 py-md-4 py-sm-4 py-3">
<h3 class="title text-center mb-lg-5 mb-md-4 mb-sm-4 mb-3" >Create new
account</h3>
<div class="contact-list-grid">
<form action="#" method="post">
<div class=" agile-wls-contact-mid" style="color:black">
<div class="form-group contact-forms">
First name
<input type="text" class="form-control" name="c_fname" pattern="[A-Za-z]+"
placeholder="First name" style="width: 530px; height: 40px; color: black" required>
</div>
<p>
Last name
<input type="text" class="form-control" name="c_lname" pattern="[A-Za-z]+"
placeholder="Last name" style="width: 530px; height: 40px;" required>
</p>
</div>
User name
<input type="username" class="form-control" name="username"
placeholder="Username" style="width: 530px; height: 40px;" required>
</div>
Password

<input type="password" class="form-control" name="password"
placeholder="Password" style="width: 530px; height: 40px;" required>
</div>

Confirm Password
<input type="password" class="form-control" name="cpassword" placeholder="Confirm
Password" style="width: 530px; height: 40px;" required>
</div>

<p>
House name
<input type="text" class="form-control" name="c_hname" placeholder="House name"
style="width: 530px; height: 40px;"required>
</p>
</div>
<p>
Street
<input type="text" class="form-control" name="c_street" placeholder="Street"
style="width: 530px; height: 40px; color: black" required>
</p>
</div>
<p>
City
<input type="text" class="form-control" name="c_city" placeholder="city" style="width:
530px; height: 40px; color: black" required>
</p>
</div>

</div>
<p>
Mobile Number
<input type="text" pattern="[789][0-9]{9}" class="form-control" name="c_phn"
placeholder="Mobile Number" style="width: 530px; height: 40px; color: black"
required>
</p>
</div>
<p>
Email
<input type="email" class="form-control" name="c_email" placeholder="Email"
</p>
</div>
<div align="left">
<label>Date of Birth
<div align="left">
<input type="date" name="c_dob" placeholder="Date of Birth" value="date"
</label>
</div>
<div align="left">
<p>

<br>
<label>Gender</label>

<label>
<input type="radio" name="c_gender" value="M" id="gender_0" required="">

Male</label>

<label>
<input type="radio" name="c_gender" value="F" id="gender_1" required="">
Female</label>
</p>
</div>
</form>




<div align="center">




<button type="submit" class="btn btn-block sent-butnn align-middle" name="submit"
value="submit" style="width: 530px; height: 40px;" >Sign Up</button>
</div>
</div>
</div>

</div>
<?php
if(isset($_REQUEST['submit']))
{
$c_fname=$_REQUEST['c_fname'];
$c_lname=$_REQUEST['c_lname'];
$c_hname=$_REQUEST['c_hname'];
$c_street=$_REQUEST['c_street'];
$c_city=$_REQUEST['c_city'];
$c_gender=$_REQUEST['c_gender'];
$c_phn=$_REQUEST['c_phn'];
$c_email=$_REQUEST['c_email'];
$c_dob=$_REQUEST['c_dob'];
$username=$_REQUEST['username'];
$password=$_REQUEST['password'];
$cpassword=$_REQUEST['cpassword'];
// $rs="select count(*) as cnt from tbl_customer where c_phn='$c_phn'";

$rs="select count(*) as cnt from tbl_login where username='$username' and
password='$password'";
$res=mysql_query($rs);
$rst=mysql_fetch_array($res);
$r="select count(*) as c from tbl_login where username='$username'";

$s=mysql_query($r);
$t=mysql_fetch_array($s);
if($rst['cnt']>0)
{
clr();
echo"<script>alert('Already Registerd');</script>";
header("Location:cregister.php");
}
else if($rst['c']>0)
{
echo"<script>alert('Username already taken');</script>";
}
else if($password!=$cpassword)
{
echo"<script>alert('Password mismatch');</script>";
}
else
{
$qry="insert into
tbl_customer(c_fname,c_lname,c_hname,c_street,c_city,c_gender,c_phn,c_email,c_dob,u
sername,password)values('$c_fname','$c_lname','$c_hname','$c_street','$c_city','$c_gend
er',$c_phn,'$c_email','$c_dob','$username','$password')";
$qr="insert into tbl_login(username,password,type)

values('$username','$password','customer')";
mysql_query($qry);
echo $qry;
mysql_query($qr);
echo $c_dob;

clr();
echo "saved";
header("Location:login.php");
}
function clr()
{
$c_fname="";
$c_lname="";
$c_hname="";
$c_street="";
$c_city="";
$c_gender="";
$c_phn="";
$c_email="";
$c_dob="";
$username="";
$password="";
}
?>


</div>
</section>




<script>
toys.render();

var items, len, i;

}
});
</script>


<script>
}, 900);
});
});
</script>
<script>
var defaults = {
scrollSpeed: 1200,
};
$().UItoTop({
});
});

</script>
 
</body>
</html>
Product page:
<!DOCTYPE html>
<html lang="zxx">
<head>
<title>Product</title>



rel="stylesheet">
</head>
<?php
?>
<body>

<h1><img src= "pic/1111.png" width=125 height=100/>  <a class="navbar-
brand">Spice Kart</a></h1>
</div>
</div>
</div>
</button>
<a class="nav-link" href="customer.php">Home <span class="sr-
</li>
</ul>

</div>
</nav>
</div>
</div>


</div>


<section class="contact py-lg-4 py-md-3 py-sm-3 py-3">

<h3 class="title text-center mb-lg-5 mb-md-4 mb-sm-4 mb-3">Our Products</h3>
<div class="contact-list-grid" align="center">
<?php
$qry="select * from tbl_item";

$res=mysql_query($qry);
while($rs=mysql_fetch_array($res))
{
$names=$rs['item_name'];
$qty=$rs['qty'];
$rate=$rs['rate'];
if($rs['qty']>0)
{
$sta="AVAILABLE";
}
// else
// {
// $sta="NOT AVAILABLE";
// }
echo"<div width=200px height=200px style=border-color:green;border-

width:2px;float:left;padding_right:10px;>";echo"<div></div>";
echo"<div style='padding:50px;'><a
href=product_view.php?name1=$names&sta=$sta><img src='".$rs["img"]."' width=200
height=200 border=3px onclik='msg()'/></div></a>";
echo $names;
?>
<br>
<?php
echo"<align=center>Rs".$rate;
?>
<br>
<?php
echo"<align=center>".$sta;
echo"</div>";
// echo $sta;
}
?>
</form>
<script>
function msg()
{
var reg=document.URL;
alet(reg);
}
</script>
</div>
</div>

</section>



<script>
toys.render();


var items, len, i;

}
});
</script>

<script>
}, 900);
});
});
</script>
<script>

var defaults = {
scrollSpeed: 1200,
};
$().UItoTop({
});
});
</script>
</body>
</html>
Item page:
<!DOCTYPE html>
<html lang="zxx">
<head>
<title>Item</title>




rel="stylesheet">
</head>
<?php
include "connect.php"
?>
<body>

<h1><a href="index.php"><img src= "pic/1111.png" width=125
height=100/></a>  <a class="navbar-brand" href="index.php"> Spice
kart</a></h1>
</div>

</div>
</div>
</button>
id="navbarSupportedContent" align="left">
<a class="nav-link" href="admin.php">Home <span class="sr-
</li>
</ul>
</div>
</nav>
</div>
</div>


</div>


<section class="contact py-lg-4 py-md-3 py-sm-3 py-3">
</section>

<div class="modal-body">
<h3 class="title text-center mb-lg-5 mb-md-4 mb-sm-4 mb-3">Item Details</h3>
<div class="contact-list-grid" align="center">
<div class=" agile-wls-contact-mid">

<div class="form-group contact-forms" align="justify" >
<form action="#" method="post" enctype="multipart/form-data">
<p>
Category name
</p>
<p>
<select name="cat_name" style="width: 530px; height: 40px;">
<?php
$rs="select cat_name from tbl_category";
$res=mysql_query($rs);
echo'<option>......select category.......</option>';
while($rst=mysql_fetch_array($res))
{
echo'<option value='.$rst['cat_name'].'>'.$rst['cat_name'].'</option>';
}
?>
</select>
</p>
</div>

<div class="form-group contact-forms" align="justify" >
<p>
Subcategory name
</p>
<p>
<select name="sc_name" style="width: 530px; height: 40px;" >

<?php
$rs1="select sc_name from tbl_subcategory";
$res1=mysql_query($rs1);
echo'<option>......select Subcategory.......</option>';
while($rst1=mysql_fetch_array($res1))
{
echo'<option value='.$rst1['sc_name'].'>'.$rst1['sc_name'].'</option>';
}
?>
</select>
</p>
</div>
<div class="form-group contact-forms" align="left" >
<label>Item name</label>
<input type="text" name="item_name" class="form-control" placeholder="Item name"

style="width: 530px; height: 40px;" align="left" required>
</div>
<label>Item Quantity</label>
<input type="text" name="itemquantity" class="form-control" placeholder="Item

quantity" style="width: 530px; height: 40px;" align="left" required>
</div>
<label>Item Rate</label>
<input type="text" name="rate" class="form-control" placeholder="Item rate"

style="width: 530px; height: 40px;" align="left" required>
</div>
<div align="left">
<label> Image</label>
<input type="file" name="txtimg" required>
</div>
</div>
<button type="submit" class="btn btn-block sent-butnn" name="submit" value="submit"
style="width: 400px; height: 40px;">ADD</button>
</div>
</form>
<?php
if(isset($_REQUEST['submit']))
{
$cat_name=$_REQUEST['cat_name'];
$sc_name=$_REQUEST['sc_name'];
$rate=$_REQUEST['rate'];
$item_name=$_REQUEST['item_name'];
$itemquantity=$_REQUEST['itemquantity'];
$folder='pic/';
$file=$folder.basename($_FILES['txtimg']['name']);
move_uploaded_file($_FILES['txtimg']['tmp_name'], $file);
// $target_dir = "pic/";
// $img = $target_dir . basename($_FILES["fileupload"]["name"]);
//
$rs2="select count(*) as cnt from tbl_item where item_name='$item_name'";
$res3=mysql_query($rs2);
$rst4=mysql_fetch_array($res3);
if($rst4['cnt']>0)
{
clr();
echo "<script>alert('Item already added ');</script>";
//echo "alredy added";
}
else
{
$qr="insert into tbl_item(cat_name,sc_name,item_name,img,qty,rate)

values('$cat_name','$sc_name','$item_name','$file','$itemquantity','$rate')";
mysql_query($qr);
//echo $qr;
echo "<script>alert('Item Added successfully');</script>";
clr();
//echo "saved";

}
}
function clr()
{
$cat_name="";
$sc_name="";
$item_name="";
}
?>
</div>
</div>
</div>

</div>
</section>

<section class="sub-below-address py-lg-4 py-md-3 py-sm-3 py-3"></section>


<footer class="py-lg-4 py-md-3 py-sm-3 py-3 text-center">
<div class="copy-agile-right">
<p>
© 2019 Spice Kart | All Rights Reserved </p>

</div>
</footer>


<div class="modal fade" id="exampleModal" tabindex="-1" role="dialog" aria-
labelledby="exampleModalLabel" aria-hidden="true">
<div class="modal-dialog" role="document">
<div class="modal-content">
<div class="modal-header">
<h5 class="modal-title" id="exampleModalLabel">Login</h5>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<div class="modal-body">
<div class="register-form">
<div class="fields-grid">
<div class="styled-input">
<input type="text" placeholder="Your Name" name="Your Name" required="">
</div>
<input type="email" placeholder="Your Email" name="Your Email" required="">
</div>
<input type="password" placeholder="password" name="password" required="">
</div>
<button type="submit" class="btn subscrib-btnn">Login</button>
</div>
</form>
</div>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-secondary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>




<script>
toys.render();

var items, len, i;

}
});
</script>


<script>
}, 900);
});
});
</script>
<script>
var defaults = {
scrollSpeed: 1200,
};
$().UItoTop({
});

});
</script>
</body>
</html>

BIBLIOGRAPHY

Book References:
1. Roger S Pressman, Software Engineering (A Practitioner’s Approach), Seventh
Edition.
2. Programming in php
Web References:
3. www. Functions.com/Mysql
4. www.onlinelibrary.wiley.com/doi/10.1002/qua.21273/full
5. www.google.com
6. www.wikipedia.com
7. www.youtube.com

Spicekarthardcpymain

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Spicekarthardcpymain

Hochgeladen von

Copyright:

Verfügbare Formate

Project Report 2019 SPICE KART

Al-Ameen college edathala 1

1.1 PROJECT OVERVIEW

Al-Ameen college edathala 2

1.2 LITERATURE SURVEY

Certain important objectives to be provided in the system are,

Decrease in the workload.

The system should be user friendly

Minimized processing time

Al-Ameen college edathala 3

Al-Ameen college edathala 4

2.2 PROPOSED SYSTEM:

Give details about a customer’s details.

Give details of the Products and their Price.

password. Further improvement in the system is maintained by providing validation test

the bugs and also improves the efficiency of the system.

Al-Ameen college edathala 5

2.3 FEASIBILITY STUDY

Feasibility study is a procedure that identifies, describes and evaluates

 Does the existing technology sufficient for the suggested one?

Al-Ameen college edathala 6

 The costs conduct a full system investigation.

2.3.4 Behavioral Feasibility

 Is there sufficient support for the users?

2.4.1 Data Modeling

Al-Ameen college edathala 7

Data flow design is concerned with designing a sequence of functional transformations

 A square defines a source (originator) or destination of system data.

 An arrow identifies data flow in motion. It is a pipeline through which information

DATA FLOW DIAGARAM:

Al-Ameen college edathala 8

Al-Ameen college edathala 9

2.4.2Entity Relationship Diagrams

Entity Relationship Diagrams (ERDs) illustrate the logical structure of databases. An

Al-Ameen college edathala 10

Al-Ameen college edathala 11

3.1 INPUT DESIGN

3.1.1 User Interface Design

The interface describes how the website

The SPICE KART is a web based application. Web

3.1.2 Content Design

Content design focuses on two different design tasks, each addressed by

Al-Ameen college edathala 12

3.2 OUTPUT DESIGN

(2)Define the mechanics of achieving the navigation.

The main pages used in the system are,

 Admins home page

Al-Ameen college edathala 13

 Company home page

Al-Ameen college edathala 14

(1) Perform localized processing to generate content and navigation capability in a

(3) Provide sophisticated database query and access,

(4) Establish data interface with external cooperate system.

Al-Ameen college edathala 15

3.3 DATA BASE DESIGN

After designing the input and output the next step is

SPICE KART Tables:

Al-Ameen college edathala 16

Column Type Null Discription

c_fname varchar(20) No Customer name

img varchar(20) No Product image

item_name varchar(20) No Product name

cqty int(20) No Product quantity