A PROJECT REPORT ON

“STICKCART” Online Grocery

Submitted by:
Shantanu Sharma - 145453000
Poonam sharma-151480983
Arun-151480905
Veru -151480905

MCA-Semester-IV

Project Coordinator:
Mrs. Monika Sharma
 INDIRA GANDHI NATIONAL OPEN UNIVERSITY (IGNOU)

ACKNOWLEDGEMENT

We would like to express our deepest appreciation to all those who provided us the
possibility to complete this report. A special gratitude we give to our
project coordinator, Mrs. Monika, whose contribution in stimulating suggestions
and encouragement helped us to coordinate our project especially in writing this
report.

Furthermore we would also like to acknowledge with much appreciation the crucial
role of the staff of IGNOU, who gave the permission to use all required equipment
and the necessary materials to complete the task “STICKCART”. I have to
appreciate the guidance given by other supervisor as well as the panels especially in
our project presentation that has improved our presentation skills thanks to their
comment and advices.
CONTENTS

1. INTRODUCTION
1.1 OVERVIEW OF PROJECT.

2. SYSTEM STUDY
2.1 PROBLEM DEFINITION
2.2 SOFTWARE REQUIREMENTS
2.3 HARDWARE REQUIREMENTS

3. CONCEPTS & TECHNIQUES

4. SYSTEM ANALYSIS

5. DESIGN SPECIFICATION
5.1 TABLES
5.2 CONTEXT DIAGRAM
5.3 DATAFLOW DIAGRAMS

6. SYSTEM SPECIFICATION

7. SCREENS

8. RESULTS AND ADVANTAGES

9. CONCLUSION

10. BIBLIOGRAPHY
 INTRODUCTION
“StickCart” (Online Grocery Ordering)
The Project entitled "STICKCART" is a web-based project which is made for
remote shopping or shopping through Internet. As the technology is being
advanced, the way of life is changing accordance. Now a day’s we can place
order for anything from our home. There is no need to go to the shop for the
things we want. The order can be placed online through Internet. The payment,
the confirmation of purchasing; we can everything we want. Now we can think
that how the days have been changed with time. People had to stand in rows to
buy a particular thing from a popular shop. But what is happening now a day’s;
all those things are available to our door-steps within few hours.

This project entitled “StickCart” is an implementation of the above

description. It means, it implements the E-shopping or in other word shopping
through Internet. It lets the user to place their order online for any grocery items.

The primary features of the project entitled "STICKCART" are high

accuracy, design flexibility and easy availability. And also it uses database
tables Representing entities and relationships between entities.

OVERVIEW OF STICKCART
The central concept of the application is to allow the customer to shop virtually using the
Internet, allow customers and seller to buy/sale the grocery items of their desire from the
online store. The information pertaining to the products are stores on an RDBMS at the
server side (store). The Server process the customers and the items are shipped to the
address submitted by them.
 The application is designed into a module for the customers who wish to buy
the articles.

The end user of this product is a departmental store where the application is
hosted on the web and the administrator maintains the database. The
application which is deployed at the customer database, the details of the items
are brought forward from the database for the customer view based on the
selection through the menu and the database of all the products are updated at
the end of each transaction.

Data entry into the application can be done through various screens
designed for various levels of users. Once the authorized personnel feed the
relevant data into the system, several reports could be generated as per the
security.
SYSTEM STUDY
 PROBLEM DEFINITION

To develop a web-based application to improve the service to the customers in

"STICKCART".

GOALS FOR THE SYSTEM AND THE

PROJECT

The system is capable of maintaining details of various customers, products and

storing all the day to day transactions such as COD(CASH ON DELIVERY).

CONSTRAINTS ON THE
 SYSTEM AND THE PROJECT

STICKCART is developed in PHP7 using Java as front end and it could

run only on Java 5.4 and onward versions.

HARDWARE AND SOFTWARE

SOFTWARE REQUIREMENT SPECIFICATION

As the software developed is by using different technologies, so there are certain requirements
to be fulfilled in order to execute this software package in order to increase the efficiency of the
project and minimize the problems related to this project.
Some of the requirements are:-
1. Supported Architecture
1.1. x86.
1.2. x64.

2. Software Requirements
2.1. All Supporting Operating System Open Source And Platform Independent
Source.
2.2. NetBeans IDE (And You Have To Use Different IDE For PHP).
2.3. MySQL 5.7 Community Server (GPL).
2.4 PHP Version 7.0.1 RC1 Non- Thread Zip.
2.5 Internet Explorer 11 Or Latest (Chrome, Opera, Mozilla, Firefox).
3. Hardware Requirements
3.1. Pentium 3 Processor And Above More Higher.
3.2. RAM (512 MB or More).
3.3. Minimum Support Browser – Internet Explorer 11 Or Other Latest Browser.
DATABASE TABLES
SYSTEM SPECIFICATION
SYSTEM SPECIFICATION

The application STICKCART was designed into a module, For the

customers who wish to buy the articles.

BUSSINESS PROCESS MODEL

The end-user of this product is a departmental store where the

application is hosted on the web and the administrator maintains the
database. The application which is deployed at the departmental stores will
automate the customer details that are appended to the customers database,
the details of the items are brought forward from the database for the
customers view based on the selection through the menu and the database of
all the products are updated at the end of each transaction.

Data entry into the application can be done through various screens
designed for various levels of users. Once the authorized personnel feed
relevant data into the system, several reports could be generated as per the
security.

If the customer wants to buy the product he wants to enter into the
shopping chart. He selects the desired product, after that he enter in to the
order form he fills the order form. After filling order form merchant
shipped the product to address specified by the Customer.

The central concept of the application is to allow the Customer to

shop virtually using the Internet and allow customers to buy the items and
articles of their desire form the store. The information pertaining to the
products are stored on an RDBMS at the server side (store). The Server
processes the customer's request and the items are shipped to the address
submitted by them.

HTML is a formal set of specifications used to define information,

which can be added to the content of a document as an aid processing. The
purpose of HTML is to specify how the text should be processed. The
purpose of a browser becomes to act as a presentation engine, to interpret
HTML & display the contents in appropriate manner.

Within Hyper text there will be an indication of the start and end of
the paragraph, there will be no explicit instructions about the size, fonts,
color, etc., It will contain the basic information about the link but no
specifications about how to display the highlight the link. It left to the
browser how information should be displayed.

The importance of HTML lies with Internet because one doesn’t

know about the end user since there are different user types on the NET. If
HTML would be a language having instructions about the colors, sizes &
fonts it would be subjected to a specific environment> Secondly as the
number of users grow day by day one should think of minimizing the amount
of information to be passed from one system to the other. Hence HTML
would contain plan ext. file would occupy less space than any other graphics
file but, having the addresses of those locations.

If hypertext one must send information for displaying the text and these
instructions are embedded in the text itself.

SYSTEM DESIGN
Design of software involves conceiving, planning out and specifying
the externally observable characteristics of the software product. We have
data design, architectural design and user interface design in the design
process. These are explained in the following section. The goal of design
process is to provide a blue print for implementation, testing and
maintenance activities.

DATA DESIGN:

The primary activity during data design is to select logical

representations of data objects identified during requirement analysis and
software analysis. A data dictionary explicitly represents the relationships
among data objects and the constrains on the elements of the data structure.
A data dictionary should be established and used to define both data and
program design.

FEASIBILITY STUDY:

Feasibility study is conducted once the problem is clearly understood.

Feasibility study is a high level capsule version of the entire system analysis
and design process. The objective is to determine quickly at a minimum
expense how to solve a problem. The purpose of feasibility is not to solve
the problem but to determine if the problem is worth solving. The system
has been tested for feasibility in the following points.

1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.

1. Technical Feasibility: -

The project entitles "Project Monitoring System" is technically

feasibility because of the below mentioned feature. The project was
developed in PHP which Graphical User Interface.

It provides the high level of reliability, availability and compatibility.

All these make PHP an appropriate language for this project. Thus the
existing software PHP is a powerful language.

2. Economical Feasibility: -

The computerized system will help in automate the selection leading

the profits and details of the organization. With this software, the machine
and manpower utilization are expected to go up by 80-90% approximately.
The costs incurred of not creating the system are set to be great, because
precious time can be wanted by manually.

3. Operational Feasibility:

In this project, the management will know the details of each project
where he may be presented and the data will be maintained as decentralized
and if any inquires for that particular contract can be known as per their
requirements and necessaries.

Implementation:

Implementation is the stage where the theoretical design is turned

into a working system. The most crucial stage in achieving a new successful
system and in giving confidence on the new system for the users that it will
work efficiently and effectively.

The system can be implemented only after thorough testing is done and if it
is found to work according to the specification.

It involves careful planning, investigation of the current system and its

constraints on implementation, design of methods to achieve the change
over and an evaluation of change over methods a part from planning. Two
major tasks of preparing the implementation are education and training of
the users and testing of the system.

The more complex the system being implemented, the more involved will
be the systems analysis and design effort required just for implementation.

The implementation phase comprises of several activities. The required

hardware and software acquisition is carried out. The system may require
some software to be developed. For this, programs are written and tested.
The user then changes over to his new fully tested system and the old system
is discontinued.
TESTING:
The testing phase is an important part of software development. It is the
process of finding errors and missing operations and also a complete
verification to determine whether the objectives are met and the user
requirements are satisfied.

Software testing is carried out in three steps:

The first includes unit testing, where in each module is tested to

provide its correctness, validity and also determine any missing operations
and to verify whether the objectives have been met. Errors are noted down
and corrected immediately. Unit testing is the important and major part of
the project. So errors are rectified easily in particular module and program
clarity is increased. In this project entire system is divided into several
modules and is developed individually. So unit testing is conducted to
individual modules.

The second step includes Integration testing. It need not be the case,
the software whose modules when run individually and showing perfect
results, will also show perfect results when run as a whole. The individual
modules are clipped under this major module and tested again and verified
the results. This is due to poor interfacing, which may results in data being
lost across an interface. A module can have inadvertent, adverse effect on
any other or on the global data structures, causing serious problems.

The final step involves validation and testing which determines which
the software functions as the user expected. Here also some modifications
were. In the completion of the project it is satisfied fully by the end user.

Maintenance and Enhancement

AS the number of computer based systems, grieve libraries of computer

software began to expand. In house developed projects produced tones of
thousand soft program source statements. Software products purchased
from the outside added hundreds of thousands of new statements. A dark
cloud appeared on the horizon. All of these programs, all of those source
statements-had to be corrected when false were detected, modified as user
requirements changed, or adapted to new hardware that was purchased.
These activities were collectively called software Maintenance.
 The maintenance phase focuses on change that is associated with error
correction, adaptations required as the software's environment evolves, and
changes due to enhancements brought about by changing customer
requirements. Four types of changes are encountered during the
maintenance phase.

Correction
Adaptation
Enhancement
Prevention

Correction:
Even with the best quality assurance activities is lightly that the
customer will uncover defects in the software. Corrective maintenance
changes the software to correct defects.
Maintenance is a set of software Engineering activities that occur
after software has been delivered to the customer and put into operation.
Software configuration management is a set of tracking and control
activities that began when a software project begins and terminates only
when the software is taken out of the operation.

We may define maintenance by describing four activities that are

undertaken after a program is released for use:

Corrective Maintenance
Adaptive Maintenance
Perfective Maintenance or Enhancement
Preventive maintenance or reengineering

Only about 20 percent of all maintenance work are spent "fixing

mistakes". The remaining 80 percent are spent adapting existing systems to
changes in their external environment, making enhancements requested by
users, and reengineering an application for use.

ADAPTATION:

Over time, the original environment (E>G., CPU, operating system,

business rules, external product characteristics) for which the software was
developed is likely to change. Adaptive maintenance results in modification
to the software to accommodate change to its external environment.
ENHANCEMENT:

As software is used, the customer/user will recognize additional

functions that will provide benefit. Perceptive maintenance extends the
software beyond its original function requirements.

PREVENTION:

Computer software deteriorates due to change, and because of this,

preventive maintenance, often called software re engineering, must be
conducted to enable the software to serve the needs of its end users. In
essence, preventive maintenance makes changes to computer programs so
that they can be more easily corrected, adapted, and enhanced. Software
configuration management (SCM) is an umbrella activity that is applied
throughout the software process. SCM activities are developed to

Identify change.
Control chug.

Ensure that change is being properly implemented.

Report change to others that may have an interest.
DATAFLOW DIAGRAMS

CONTEXT DIAGRAM

Product details

Enhance
Update Product Customer
Merchant
Order
Delete

Customer Details
FIRST LEVEL DATA FLOW DIAGRAM FOR MARCHANT LOGIN TO
ENHANCE STORES

Merchant Details

Stores Enhance
Merchant stores

Store Details

FIRST LEVEL DATA FLOW DIAGRAM FOR MARCHANT LOGIN TO

ENHANCE STORES
 Merchant Details

Delete
Stores Or
Merchant
Update

Updated store
Details

FIRST LEVEL DATAFLOW DIAGRAM FOR CUSTOMER PROCESSING

ON PRODUCTS

Product details

Customer Product
Product Customer
name type
Details

Amount Payable
SECOND LEVEL DATA FLOW DIAGRAM FOR BILL SHIPMENT

Product details

Products Bill Bill

Customer
Order Processing Shipment

Address
Shipment Specified by
Address the Customer
 PROJECT SCREEN

HOME Page:
PRODUCT Page:

Add Edit Product:

LOGIN-SIGNUP PAGE :

Add Cart Page

 RESULTS AND ADVANTAGES
INTERPRETATION OF THE RESULT

The system has been implemented and tested successfully. It meets

the information
Requirements specified to the great extent. Although the system has been
designed keeping the
Present and future requirements in mind and made very flexible. There are
limitations of the
System. Proper consideration has been given for a wide range of new
enhancements in
The future, through out the development of system. The system is
developed user friendly.

In future, if it is required to generate reports other than provided by the

system, it can be simply
Achieved by a separate module to the main menu without affecting the
design of the system.
ADVANTAGES

 It simplifies the operation.

 It avoids a lot of manual work.
 Every Transaction is obtained and processed immediately.
 Avoids errors by avoiding the manual work.
User friendly screen to enter the data and Enquire the database tables.
 Online help messages available to the operating system.
 User can easily access the system without much experience.
 Provide Hardware and software securities.
 Portable and flexible for further extension.
CONCLUSION
CONCLUSION

The central concept of the application is to allow the customer to shop

virtually using the Internet and allow customers to buy the items and articles
of their desire from the store. The information pertaining to the products are
stores on an RDBMS at the server side (store). The Server process the
customers and the items are shipped to the address submitted by them.
The application was designed into two modules first Os for the
customers who wish to buy the Prducts. Second is for the storekeepers who
maintains and updates the information pertaining to the products and those of
the customers?
The end user of this product is a departmental store where the application
is hosted on the web and the administrator maintains the database. The
application which is deployed at the customer database, the details of the
items are brought forward from the database for the customer view based on
the selection through the menu and the database of all the products are
updated at the end of each transaction.

Data entry into the application can be done through various screens
designed for various levels of users. Once the authorized personnel feed the
relevant data into the system, several reports could be generated as per the
requirements.
This system offers information relevant to the user accessing the
application thus avoiding unnecessary overloading and at the same time
maintaining the security.