Project Proposal

PROJECT PROPOSAL
BCSP- 064
ON
ONLINE GROCERY SHOPPING SYSTEM

“A WEBSITE FOR OUR SOCIETY’S EASE”
By
Name: NAZIA
Enrollment No: 168490578

Under Guidance
Of
Ms. Juveria
Bachelor of Computer Applications (BCA)
Indira Gandhi National Open University, MaidanGarhi,

New Delhi – 110068.
ONLINE GROCERY
SHOPPING SYSTEM
ACKNOWLEDGEMENT
Here we gladly present this project report on “ONLINE GROCERY
SHOPPING SYSTEM” as part of the 5th semester BCA . At this time of
submitting this report we use this opportunity to mention those people
who with us along the work. We take this occasion to thank God,
almighty for blessing us with his grace and taking our endeavor to a
successful culmination. We extend our sincere and heartfelt thanks to
our esteemed guide, Ms. Juveria for providing us with the right
guidance and advice at the crucial junctures and for showing us the
right way. We would like to thank the other faculty members also, at
this occasion. Last but not the least; we would like to thank friends for
the support and encouragement they have given us during the course
of our work.
168490578
Page 2
Content page
TABLE OF CONTENTS
1. TITLE OF PROJECT:- ...............................................................................................................................4
2. INTRODUCTION:- ....................................................................................................................................4
3. PROJECT OBJECTIVE:- ...........................................................................................................................5
4. PROJECT CATEGORY:- ...........................................................................................................................6
4.1 EXISTING SYSTEM:……………………………………………………………………………………………………7
4.2 PROPOSED SYSTEM:………………………………………………………………………………………………….7
4.3 NEED: .......................................................................................................................................................7
5. SYSTEM ANALYSIS:-...............................................................................................................................8
6. DATA FLOW DIAGRAM ...................................................................................................................9
ENTITY RELATIONSHIP DIAGRAM: .................................................................................................... 18
7. A COMPLETE STRUCTURE:- .............................................................................................................. 19
7.1 DESCRIPTION OF MODULE:.......................................................................................................... 19
8. LIST of TABLES: ............................................................................................................................ 21
10. TESTING TO BE USED:- ............................................................................................................. 26
11. REPORT GENERATION:- ............................................................................................................. 30
12. TOOLS, DATABASE, HARDWARE AND SOFTWARE REQUIREMENTS: ............................... 30
Derby Server Feature .............................................................................................................................. 32
Ease of installation, deployment, and use ...................................................................................... 32
Scalability ..................................................................................................................................................... 32
Data warehousing ..................................................................................................................................... 32
System integration with other server software ............................................................................ 32
13. Hardware and Software Requirement....................................................................................... 35
A. Hardware Requirement ................................................................................................................. 36
168490578
Page 3
B. Software Requirements ...................................................................................................................... 36

14. Are you doing this project for industry or organization..?? ............................................. 37
15. Future scope and further enhancement:- ............................................................................... 38
16. References:- ........................................................................................................................................... 38
1. TITLE OF PROJECT:-
ONLINE GROCERY SHOPPING

SYSTEM
2. INTRODUCTION:-
“Online Grocery Shopping System” 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 the shop of the things we
want. The order can be placed online through Internet. The payment, the
168490578
Page 4
confirmation of purchasing; we can do everything we want. Now we can think that

how the days have been changed with time. People had to stand in rows to wait
there terms to buy a particular thing from a popular shop. But what is happening
now a day’s; we can extremely surprise that those things can be available on the
door-step in few hours.
People had to suffer the rush of the market when they went for shopping.
They used to think hundred times to buy anything having the sufficient money for
shopping. The problem was the rush; the quarrel at the time of buying the things.
But the advancement of technology brought the new way for shopping. The way of
shopping was completely changed with the coming of Internet to place their order
on any popular shop or shopping-mall for the thing they want to buy. Now they
can place their order from the home.
This project entitled “Online Grocery Shopping System” 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 online for any article.
3. PROJECT OBJECTIVE:-
Today the Internet and its boom have created a new economic scenario that only
stresses on the classical concept of the “product” but also on the modern concept
of “service”. It is this level of service that dictates whether a commercial venture
will succeed or not in the market. To provide a high accessibility of service we will
design the online shopping website, so that potential customers need not go to a
physical shop to buy products or services.
There are several objective of this website are following given bellows:
 This site gives all the information about the e-shopping to provide better
service for the customer.
 It provides the facility to the customers who want to shop online due to
lack of time.
 It provides facility to the customers to payment by the cash and cheque
and DD also.
 It’s provides the full details about the product and related information
about the product like cost, size etc.
 With the help of it we can save the time and money also.
168490578
Page 5
 It provides the remote shopping by the cash, or DD, or Debit card also
 It provides better security and good delivery service to the customer.
4. PROJECT CATEGORY:-
We have several alternative suggestions about the project category like:

Desktop Application, Web-based Application, OOPs application, Networking,
RDBMS etc.
Out of available one we have opted Web based application based on client server
architecture.
The proposed system falls into the category of Multimedia. A web based system
has two
types of pages one is static web pages and another are dynamic webpages, which
are saved
on web server and can be seen by sending request to webserver through HTTP
protocol.
Static web pages: - Static web pages are easy to spot sometimes we can
pick them
out by just looking at the content of the page. The content (text, images,
hyperlinks,
and so on) and appearance of static web pages is always the same regardless of
who
visits the page, or how and when they arrive at the page, or any other factors.
Dynamic web pages: - The dynamic web pages are web pages, which we
can
Interact like a time is shown on the page or we are sending information through
web
Form ,online chat, sending mail on net etc all the action this action performed with
the
Help of dynamic web pages.
Web Server: - Web server are software that manage web pages and make
them available to client browser via local network or over the internet. In the case
of
The Internet, the web server and browser are usually on two different machines,
Possibly many miles apart. However, in a local situation you can set up machine
that
runs the web server software, and then use a browser on the same machine to
look at
its web pages.
168490578
Page 6
4.1 Existing System:

 In the existing system all the transactions, dealings of products,
purchasing of products were done manually which is time consuming.
 Reports are prepared manually as when needed. Maintaining of reports is
very tedious task.
 To buy any product user has to collection information about it either by
visiting the shop or asking people which is the better one.
 There is no computer for handling payments. All calculations are
performed manually which may not be accurate always. Maintaining the
record is really a tedious task.
4.2 Proposed System:

In the proposed system customer need not go to the shop for buying the
products. He can order the product he wish to buy through the
application in his Smartphone. The shop owner will be admin of the
system. Shop owner can appoint moderators who will help owner in
managing the customers and product orders. The system also
recommends a home delivery system for the purchased products.
4.3 NEED:
I have designed the given proposed system in the JSP and oracle to automate the
process.
The following steps that give the detailed information of the need of proposed
system are:
Performance: During past several decades, the records are supposed to be
manually handled for all activities. The manual handling of the record is time
consuming and highly prone to error. To improve the performance of the
Company's file system, the computerized system is to be undertaken. The
computerized project is fully computerized and user friendly even that any of the
members can see the report and status of the company's file system.
Efficiency: The basic need of this website is efficiency. The website should
be
efficient so that whenever a new user submits his/her details the website is
updated automatically. This record will be useful for other users instantly.
168490578
Page 7
-8-
Control: The complete control of the project is under the hands of authorized
person who has the password to access this project and illegal access is not
supposed to deal with. All the control is under the administrator and the other
members have the rights to just see the records not to change any transaction or
entry.
Security: Security is the main criteria for the proposed system. Since illegal
access may corrupt the database. So security has to be given in this project.
5. SYSTEM ANALYSIS:-
A system analysis is a separation of a substance into parts for study and their
implementation and detailed examination. Before designing any system it is
important that the nature of the business and the way it currently operates are
clearly understood. The detailed examination provides the specific data
required during designing in order to ensure that all the client's requirements are
fulfilled. The investigation or the study conducted during the analysis phase is
largely based on the feasibility study. Rather it would not be wrong to say that the
analysis and feasibility phases overlap. High-level analysis begins during the
feasibility study. Though analysis is represented as one phase of the system
development life cycle (SDLC), this is not true. Analysis begins with system
initialization and continues until its maintenance. Even after successful
implementation of the system, analysis may play its role for periodic maintenance
and up gradation of the system.
DESIGN OBJECTIVES AND CONSTRAINTS
 Flexible –
The design would enable future requirements of the organization to be
incorporated without much difficulty. Often the organizational needs and
objectives change over time and hence such a design enables the system to reflect
these changes.
• Maintainable -
168490578
Page 8
A good design is easy to maintain and this reduces the client's maintenance cost,
which usually represents a proportion of the lifetime of the system.
• Portable -
A client for whom the software was developed may wish to change the hardware
on which the system run. A good design is portable - in other words it is capable of
being transferred from one machine environment to another with minimum
amount of effort.
• Easy to use -
With increasing number of general users having exposure to computers and access
to websites, expectations of computer applications in term of their ease of use are
also increasing. A good design will result in a system which is `user - friendly' -
easy to understand, not difficult to learn how to use and straightforward to
operate.
• Reliable -
The system designed must be secure against human error, deliberate misuse or
machine failure, and which the data will be stored without corruption.
6. DATA FLOW DIAGRAM
Analysis refers to the process of examining a business situation with intent of

improving it through better procedures and methods.
The analysis model achieves three primary objectives: -
1. To describe the requirements of the customer.
2. To establish a basis for the creation of a software design.
3. To define a set of requirements that can be validated once software is built.
DFD LEVEL ‘0’:-
168490578
Page 9
Admin Side DFD 1st Level:-
168490578
Page 10
2nd Level Admin DFD-(3.0):-
168490578
Page 11
168490578
Page 12
168490578
Page 13
1st Level User Side DFD:-
168490578
Page 14
2nd Level User DFD-(4.0):-
168490578
Page 15
2nd Level User DFD-(5.0):-
168490578
Page 16
168490578
Page 17
ENTITY RELATIONSHIP DIAGRAM:
168490578
Page 18
7. A COMPLETE STRUCTURE:-
7.1 DESCRIPTION OF MODULE:
The system after careful analysis has been identified to be presented with the
following modules and roles.
The modules involved are:
 Administrator
 Users
1. Admin module:
The administrator is the super user of this application. Only admin have access
into this admin page. Admin may be the owner of the shop. The administrator has
all the information about all the users and about all products.
This module is divided into different sub-modules.
1. Manage Items
2. Manage Users
3. Manage Orders.
4. Manage Category
5. Manage Report
Manage items
 Add Products
The shopping cart project contains different kind of products. The products
can be classified into different categories by name. Admin can add new
products into the existing system with all its details including an image.
168490578
Page 19
 Delete Products
Administrator can delete the products based on the stock of that particular
product.
 Search products
Admin will have a list view of all the existing products. He can also search
for a particular product by name.
Manage user:
 View Users
The admin will have a list view of all the users registered in the system.
Admin can view all the details of each user in the list except password.
 Add Users
Admin has privileges to add a user directly by providing the details.
 Delete &Block Users

Administrator has a right to delete or block a user. The default status of a
new user registered is set as blocked. The admin must accept the new user
by unblocking him.
Manage orders:
 View Order
Administrator can view the Orders which is generated by the users. He can
verify the details of the purchase.
 Delete order
Admin can delete order from the orders list when the product is taken for
delivery.
Manage Category:
The admin manages the category of the items.
Manage Report:
The administrator manages the report of items, payment, order etc.
168490578
Page 20
2. User module:
User is a visitor, who visit the site and buy something from our website by making
online payment.
 Registration
A new user will have to register in the system by providing essential details
in order to view the products in the system. The admin must accept a new
user by unblocking him.
 Login
A user must login with his user name and password to the system after
registration.
 View Products
User can view the list of products based on their names after successful
login. A detailed description of a particular product with product name,
products details, product image, price can be viewed by users.
 Search Product
Users can search for a particular product in the list by name.
 Add to cart
The user can add the desired product into his cart by clicking add to cart
option on the product. He can view his cart by clicking on the cart button. All
products added by cart can be viewed in the cart. User can remove an item
from the cart by clicking remove
 Submit Cart
After confirming the items in the cart the user can submit the cart by
providing a delivery address.On successful submitting the cart will become
empty.
8. LIST of TABLES:
168490578
Page 21
1. Category Table:
Attributes Type Nulls Key Extra
C_id Int No Primary
C_Name Varchar(50) Yes
2. Item Table:
I_id Int No Primary
I_name Varchar(50) Yes
I_details Varchar(500) Yes
Price Float Yes
Image Varchar Yes
Qty Int Yes
Add_qty Int Yes
C_name Varchar(50) Yes
Entry_date datetime Yes
3. Feedback Table:
Attributes Type Nulls key Extra
F_id Int No primary
168490578
Page 22
U_name Varchar(30) Yes
Message Varchar(500) Yes
Entry_date datetime yes
4. Admin Table:
I_id Int No Primary
Username Varchar(30) Yes
password Varchar(30) Yes
5. Order table:
O_id Varchar(50) No Primary
I_name Varchar(50) Yes
Qty Int Yes
Price Float Yes
Tprice float Yes
Status Int Yes
Entry_date Datetime Yes
168490578
Page 23
Image Varchar(500) Yes
6. User Table:
U_id int No Primary
Name Varchar(50) Yes
Last_name Varchar(50) Yes
Address Varchar(500) Yes
City Varchar(50) Yes
Pincode Varchar(50) Yes
Mobile_No Varchar(50) Yes
Email Varchar(50) Yes
Password Varchar(50) Yes
Entry_date Datetime Yes
7. Payment Table:
P_id Int No Primary
168490578
Page 24
Amount Float Yes
Type Varchar(50) Yes
Bank Varchar(50) Yes
Branch Varchar(50) Yes
Card_no Varchar(50) Yes
Cvv Int Yes
Entry_date datetime yes
8. Process logic of module:-
168490578
Page 25
9. TESTING TO BE USED:-
Software testing is an investigation conducted to provide stakeholders with
information about the quality of the product or service under test. [1] Software
testing can also provide an objective, independent view of the software to allow
the business to appreciate and understand the risks of software implementation.
Test techniques include, but are not limited to, the process of executing a program
or application with the intent of findings of the bugs (errors or other defects).
Software testing can be stated as the process of validating and verifying that a
computer program/application/product:
 meets the requirements that guided its design and development,

 works as expected,
168490578
Page 26
 can be implemented with the same characteristics,

 and satisfies the needs of stakeholders.
Software testing, depending on the testing method employed, can be implemented
at any time in the development process. Traditionally most of the test effort occurs
after the requirements have been defined and the coding process has been
completed, but in the Agile approaches most of the test effort is on-going. As
such, the methodology of the test is governed by the chosen software
development methodology.
Different software development models will focus the test effort at different points
in the development process. Newer development models, such as Agile, often
employ test-driven development and place an increased portion of the testing in
the hands of the developer, before it reaches a formal team of testers. In a more
traditional model, most of the test execution occurs after the requirements have
been defined and the coding process has been completed.
Testing methods:-
Static vs. dynamic testing:
There are many approaches to software testing. Reviews, walkthroughs,

or inspections are referred to as static testing, whereas actually executing
programmed code with a given set of test cases is referred to as dynamic testing.
Static testing can be omitted, and unfortunately in practice often is. Dynamic
testing takes place when the program itself is used. Dynamic testing may begin
before the program is 100% complete in order to test particular sections of code
and are applied to discrete functions or modules. Typical techniques for this are
either using stubs/drivers or execution from a debugger environment.
The box approach:
168490578
Page 27
Software testing methods are traditionally divided into white- and black-box
testing. These two approaches are used to describe the point of view that a test
engineer takes when designing test cases.
White-Box testing:
White-box testing (also known as clear box testing, glass box

testing, transparent box testing, and structural testing) tests internal
structures or workings of a program, as opposed to the functionality exposed to
the end-user. In white-box testing an internal perspective of the system, as well
as programming skills, are used to design test cases. The tester chooses inputs to
exercise paths through the code and determine the appropriate outputs. This is
analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT).
While white-box testing can be applied at the unit, integration and system levels of
the software testing process, it is usually done at the unit level. It can test paths
within a unit, paths between units during integration, and between subsystems
during a system–level test. Though this method of test design can uncover many
errors or problems, it might not detect unimplemented parts of the specification or
missing requirements.
Techniques used in white-box testing include:
 API testing (application programming interface) - testing of the application

using public and private APIs
 Code coverage - creating tests to satisfy some criteria of code coverage
(e.g., the test designer can create tests to cause all statements in the
program to be executed at least once)
 Fault injection methods - intentionally introducing faults to gauge the
efficacy of testing strategies
 Mutation testing methods
 Static testing methods
Code coverage tools can evaluate the completeness of a test suite that was
created with any method, including black-box testing. This allows the software
team to examine parts of a system that are rarely tested and ensures that the
most important function points have been tested.[21] Code coverage as a software
metric can be reported as a percentage for:
 Function coverage, which reports on functions executed
168490578
Page 28
 Statement coverage, which reports on the number of lines executed to

complete the test
100% statement coverage ensures that all code paths, or branches (in terms
of control flow) are executed at least once. This is helpful in ensuring correct
functionality, but not sufficient since the same code may process different inputs
correctly or incorrectly.
Black-box testing:
Black box diagram
Black-box testing treats the software as a "black box", examining functionality

without any knowledge of internal implementation. The tester is only aware of
what the software is supposed to do, not how it does it. Black-box testing methods
include: equivalence partitioning, boundary value analysis, all-pairs testing, state
transition tables, decision table testing, fuzz testing, model-based testing, use
case testing, exploratory testing and specification-based testing.
Specification-based testing aims to test the functionality of software according

to the applicable requirements. This level of testing usually requires thorough test
cases to be provided to the tester, who then can simply verify that for a given
input, the output value (or behavior), either "is" or "is not" the same as the
expected value specified in the test case. Test cases are built around specifications
and requirements, i.e., what the application is supposed to do. It uses external
descriptions of the software, including specifications, requirements, and designs to
derive test cases. These tests can be functional or non-functional, though usually
functional.
Specification-based testing may be necessary to assure correct functionality, but it

is insufficient to guard against complex or high-risk situations.
One advantage of the black box technique is that no programming knowledge is

required. Whatever biases the programmers may have had, the tester likely has a
different set and may emphasize different areas of functionality. On the other
168490578
Page 29
hand, black-box testing has been said to be "like a walk in a dark labyrinth without
a flashlight." Because they do not examine the source code, there are situations
when a tester writes many test cases to check something that could have been
tested by only one test case, or leaves some parts of the program untested.
This method of test can be applied to all levels of software

testing: unit, integration, system and acceptance. It typically comprises most if
not all testing at higher levels, but can also dominate unit testing as well.
10. REPORT GENERATION:-

From above modules different reports are generated. Reports that can be
generated :
 User Reports: Gives the user details.
 Item Report: Give item details.
 Oder Report: Give the details of order.
 Payment report: Give details of the payments.
11. TOOLS, DATABASE, HARDWARE AND SOFTWARE

REQUIREMENTS:
 Tool’s platform
Software Requirements
 Front End : HTML, CSS and JSP programming.
 Back End : derby.
 Frame Work : Net Beans 7.4
168490578
Page 30
 Reason of selection of Tools/Platforms (Software

Requirement)
Features of Java
The prime reason behind creation of Java was to bring portability and
security feature into a computer language. Beside these two major features,
there were many other features that played an important role in moulding
out the final form of this outstanding language. Java is easy to learn and its
syntax is quite simple, clean and easy to understand. The confusing and
ambiguous concepts of C++ are either left out in Java or they have been re-
implemented in a cleaner way. In java everything is Object which has some
data and behavior. Java can be easily extended as it is based on Object
Model. Java makes an effort to eliminate error prone codes by emphasizing
mainly on compile time error checking and runtime checking. But the main
areas which Java improved were Memory Management and mishandled
Exceptions by introducing automatic Garbage Collector and Exception
Handling. Unlike other programming languages such as C, C++ etc which
are compiled into platform specific machines. Java is guaranteed to be
write-once, run-anywhere language.
On compilation Java program is compiled into byte code. This byte code is
platform independent and can be run on any machine, plus this byte code
format also provide security. Any machine with Java Runtime Environment
can run Java Programs. When it comes to security, Java is always the first
choice. With java secure features it enable us to develop virus free, temper
free system. Java program always runs in Java runtime environment with
almost null interaction with system OS, hence it is more secure.
168490578
Page 31
Derby server
Apache Derby (previously distributed as IBM Cloudscape) is a relational

database management system (RDBMS) developed by the Apache Software
Foundation that can be embedded in Java programs and used for online
transaction processing. It has a 3.5 MB disk-space footprint.
Apache Derby is developed as an open source project under the Apache 2.0
license. Oracle distributes the same binaries under the name Java DB.
Derby Server Feature
Apache Derby, an Apache DB subproject, is an open source relational

database implemented entirely in Java and available under the Apache
License, Version 2.0.
Ease of installation, deployment, and use

Derby Server includes a set of administrative and development tools that improve your
ability to install, deploy, manage, and use Derby Server across several sites.
Scalability
The same database engine can be used across platforms ranging from laptop computers
running Microsoft Windows® 95/98 to large, multiprocessor servers running Microsoft
Windows NT®, Enterprise Edition.
Data warehousing
Derby Server includes tools for extracting and analyzing summary data for online
analytical processing. Derby Server also includes tools for visually designing databases
and analyzing data using English-based questions.
System integration with other server software

Derby Server integrates with e-mail, the Internet, and Windows.
Databases:
A database in Microsoft derby Server consists of a collection of tables that

contain data, and other objects, such as views, indexes, stored
procedures, and triggers, defined to support activities performed with the
data. The data stored in a database is usually related to a particular
subject or process, such as inventory information for a manufacturing
warehouse.
168490578
Page 32
Derby Server can support many databases, and each database can store either
interrelated data or data unrelated to that in the other databases. For example, a
server can have one database that stores personnel data and another that stores
product-related data. Alternatively, one database can store current customer order
data, and another; related database can store historical customer orders that are
used for yearly reporting. Before you create a database, it is important to
understand the parts of a database and how to design these parts to ensure that
the database performs well after it is implemented.
Entity Integrity Constraint:

Entity Integrity Constraints are of two types:
 Unique Constraints
 Primary Key Constraints
The unique constraints designate a column or a group of columns as a

unique key. The constraint allows only unique values to be stored in the
column derby Server rejects duplication of records when the unique key
constraint is used.
The primary key constraint is similar to the unique key constraint. The primary
key constraint just like the former avoids duplication of values. Its needs it best
felt when a relation has to be set between tables, because in addition to prevent
in duplication it also does not allow null values.
Referential Integrity Constraint:
The Referential Integrity Constraint enforces relationship between tables. It
designates a column or a combination of columns as a foreign key. The foreign
key establishes a relationship with a specified primary or unique key in another
table, called the referenced key. In this relationship, the table containing the
foreign key is called a child table and the table containing the referenced key is
called the parent table.
[
168490578
Page 33
Database
A database is similar to a data file in that it is a storage place for data. Like a data
file, a database does not present information directly to a user; the user runs an
application that accesses data from the database and presents it to the user in an
understandable format.
A database typically has two components: the files holding the physical database
and the database management system (DBMS) software that applications use to
access data. The DBMS is responsible for enforcing the database structure,
including:
 Maintaining the relationships between data in the database.
 Ensuring that data is stored correctly and that the rules defining data
relationships are not violated.
 Recovering all data to a point of known consistency in case of system

failures.
Net Beans
Net Beans IDE is the official IDE for Java 8. With its editors, code analyzers, and
converters, you can quickly and smoothly upgrade your applications to use new
Java 8 language constructs, such as lambdas, functional operations, and method
references. Batch analyzers and converters are provided to search through
multiple applications at the same time, matching patterns for conversion to new
Java 8 language constructs. With its constantly improving Java Editor, many rich
features and an extensive range of tools, templates and samples, Net Beans IDE
sets the standard for developing with cutting edge technologies out of the box.
168490578
Page 34
Net Beans IDE is a free, open source, integrated development environment (IDE)
that enables you to develop desktop, mobile and web applications. The IDE
supports application development in various languages, including Java, HTML5,
PHP and C++. The IDE provides integrated support for the complete development
cycle, from project creation through debugging, profiling and deployment. The IDE
runs on Windows, Linux, Mac OS X, and other UNIX-based systems.
The IDE provides comprehensive support for JDK 7 technologies and the most
recent Java enhancements. It is the first IDE that provides support for JDK 7, Java
EE 7, and Java FX 2. The IDE fully supports Java EE using the latest standards for
Java, XML, Web services, and SQL and fully supports the Glass Fish Server, the
reference implementation of Java EE.
Client/server
As explained in the "Embedded Derby" section, an application can embed Derby,

which means that the Derby engine runs in the same JVM as the application.
However, an application can also access a Derby database using the more familiar
client/server mode. This is achieved via a framework that embeds Derby and
handles database requests from applications, including applications running in
different JVMs on the same machine or on remote machines. The Derby Network
Server is such a framework. It embeds Derby and manages requests from network
clients.
12. Hardware and Software Requirement
168490578
Page 35
A. Hardware Requirement
Standalone Platform Network Platform
H/W Component PC Requirement Server
Requirement
CPU Pentium IV Core2 dual
CPU Speed 2.1 GHZ 3.0 GHZ
RAM 1 GB 1 GB
Hard Disk Capacity 40 GB 80 GB
Display VGA VGA
Network Upgradeable Yes Yes
DVD-drive 52x Writable 52x Writable
Keyboard Multimedia Multimedia
Mouse Optical Optical
B. Software Requirements
Standalone Platform Network Platform
168490578
Page 36
S/W Component PC Requirement Server Requirement
Operating System Windows XP Windows 2008 Server
Programming Language None Net beans
Back-End None Derby
Browser IE 6.0 or above IE 6.0 or above
Package Msoffice2007 Msoffice2007
Web Server None Glass Fish 4.0
Scripting Java Script
Interface HTML, CSS
13. Are you doing this project for industry or

organization..??
NO, we are not doing this project for any industry or any organization. This
project is developed for Academic purpose. It was developed at college
campus for the fulfillment of summer training under supervision of faculty.
Regarding this internship, we had gain lots of knowledge about making

website.
168490578
Page 37
14. Future scope and further enhancement:-
This website is designed to a stand-alone, single user system. It is

proposed to make the multiuser system.
15. References:-
http://www.slideshare.net/ieeexploreprojects/academic-
project
http://www.w3schools.com
http://www.draw.io
http://www.erdplus.com
168490578
Page 38

Project Proposal

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Proposal

Uploaded by

Copyright:

Available Formats

PROJECT PROPOSAL

ONLINE GROCERY SHOPPING SYSTEM

Enrollment No: 168490578

Indira Gandhi National Open University, MaidanGarhi,

B. Software Requirements ...................................................................................................................... 36

ONLINE GROCERY SHOPPING

“Online Grocery Shopping System” is a web–based project which is made for

confirmation of purchasing; we can do everything we want. Now we can think that

This project entitled “Online Grocery Shopping System” is an implementation

We have several alternative suggestions about the project category like:

4.1 Existing System:

4.2 Proposed System:

DESIGN OBJECTIVES AND CONSTRAINTS

6. DATA FLOW DIAGRAM

Analysis refers to the process of examining a business situation with intent of

DFD LEVEL ‘0’:-

Admin Side DFD 1st Level:-

2nd Level Admin DFD-(3.0):-

2nd Level Admin DFD-(4.0):-

2nd Level Admin DFD-(5.0):-

1st Level User Side DFD:-

2nd Level User DFD-(4.0):-

2nd Level User DFD-(5.0):-

ENTITY RELATIONSHIP DIAGRAM:

7.1 DESCRIPTION OF MODULE:

The modules involved are:

This module is divided into different sub-modules.

 Delete &Block Users

Attributes Type Nulls Key Extra

C_id Int No Primary

C_Name Varchar(50) Yes

Attributes Type Nulls Key Extra

I_id Int No Primary

I_name Varchar(50) Yes

I_details Varchar(500) Yes

Price Float Yes

Image Varchar Yes

Qty Int Yes

Add_qty Int Yes

C_name Varchar(50) Yes

Entry_date datetime Yes

F_id Int No primary

U_name Varchar(30) Yes

Message Varchar(500) Yes

Entry_date datetime yes

I_id Int No Primary

Username Varchar(30) Yes

password Varchar(30) Yes

Attributes Type Nulls Key Extra

O_id Varchar(50) No Primary

U_name Varchar(50) Yes

I_name Varchar(50) Yes

Qty Int Yes

Price Float Yes

Tprice float Yes

Status Int Yes

Entry_date Datetime Yes

Image Varchar(500) Yes

Attributes Type Nulls Key Extra

U_id int No Primary

Name Varchar(50) Yes

Last_name Varchar(50) Yes

Address Varchar(500) Yes

City Varchar(50) Yes