PROJECT REPORT

ON
"Le-Epiceria"

A report submitted to Punjabi University, PATIALA in partial

fulfillment of the requirement for the award of DEGREE course in
MASTER OF COMPUTER APPLICATIONS (Session:2018-2020).

Internal Guide Submitted By

Ms. Ekta Garg Ms. Simran Jaidka(6532)
(Asst. prof., Com. Sci. Dept.) MCA-III (6th sem)

S.S.D WOMEN’S INSTITUTE OF TECHNOLOGY, BATHINDA

(Affiliated to Punjabi University, Patiala)
Approved by AICTE, New Delhi
 DECLARATION

I hereby declare that the project entitled “Le-Epiceria” by Simran Jaidka (Rollno.6532) in
fulfillment of requirements for the award of degree of M.C.A(Master Of Computer
Applications), submitted in the department of Computer Applications at S.S.D WOMEN’S
INSTITUTE OF TECHNOLOGY, BATHINDA under PUNJABI UNIVERSITY,PATIALA
.This Project is an authentic record of my own original work carried out under the supervision
of Ms.Ekta Garg(Assistant Prof. in Computer Science Department)

Ms. Simran Jaidka(6532)

Class: MCA-3rd( 6th Sem.)

 PREFACE
In day to day life, we will need to buy lots of goods or products from a shop. It may be food
items, electronic items, house hold items etc etc. Now a days, it is really hard to get some time to
go out and get them by ourselves due to busy life style or lots of works.

This existing system of buying goods has several disadvantages. It requires lots of time to travel
to the particular shop to buy the goods. Since everyone is leading busy life now a days, time
means a lot to everyone. Also there are expenses for travelling from house to shop. More over
the shop from where we would like to buy some thing may not be open 24*7*365. Hence we
have to adjust our time with the shopkeeper’s time or vendor’s time.

In order to solve this, B2C E-Commerce websites have been started. Using these websites, we
can buy goods or products online just by visiting the website and ordering the item online by
making payments online.

The proposed project is Le-Epiceria that helps customers to buy food products online using
internet connection. Purchasing of food products online, user can choose different products based
on categories , online payments , delivery services and hence covering the disadvantages of the
existing system.

In proposed project there is also facility of livechat available through which the users can ask
their queries directly and presently to the owner.
 ACKNOWLEDGEMENT
I take this opportunity to express my deepest gratitude to those who have generously helped me
in providing the valuable knowledge and it is with real pleasure, that i record my indebtedness to
my academic guide, Ms.Ekta Garg (Asst. Prof., Comp. Sci. Dept.) for her counsel and guidance
during the preparation of this project and i also thankful to our Principal Ms.Neeru Garg &
HOD Ms. Manisha Bhatnagar and other staff of S.S.D Women’s Institute Of Technology,
Bathinda.
I would like to take this opportunity to convey my deep sense of gratitude to my External guide
Ms. Kanupriya Aggarwal, for her direction, support and steady motivation. I am extremely
obliged to her for her continuous suggestions, help and cooperation, without which it was
impossible to achieve the success in the work allocated to me.
At the end, I would like to thank all of staff members of Vivarta2Digital Pvt. Ltd. for
providing an excellent and healthy environment during work.
And finally, I would like to thank each and every person who has contributed in any of
the ways in my project.

Ms. Simran Jaidka

Uni.RollNo. 6532
 CERTIFICATE

This is to certify that the website titled “Le-Epiceria” submitted by Ms.

Simran Jaidka , ( Uni.rollno. 6532 ) has been completed successfully in the
academic year 2018-2020 towards the partial fulfillment of MCA-III(6th
semester).

Ms. Manisha Bhatnagar Internal Guide

(College Training Co-Ordinator, Ms. Ekta Garg
H.O.D of Comp. Sci. Dept., (Asst. Prof. Com. Sci. Dept.,
SSDWIT, Bathinda ) SSDWIT, Bathinda)
 ORGANAISATION PROFILE
Vivarta2Digital is a full service digital marketing agency and software development company
based in Tricity, Chandigarh. It help individuals & businesses of all sizes to increase their return
on investment (ROI) by making smarter decisions about how they promote their businesses
online to reach their potential customers.

Online marketing is an investment in your business. Vivarta2Digital is helping to invest

advertising funds wisely and reach digital marketing goals. From Branding to Web
Development, SEO, Social Media and Online Advertising – we can help!

 Name of the Organization: Vivarta2 Digital Pvt. Ltd

 About Company: Vivarta2Digital was founded in 2019.Vivarta2Digital is a full service

digital marketing agency and software development company based in Tricity,
Chandigarh.
 Founder of Vivarta2Digital Pvt. Ltd. is Ms Kanupriya Aggarwal , Who is Gold-
Medalist and an ex-Accenture employee, who has more than a decade’s experience in the
computer & IT industry.

 Address of Organization: Flat No 701, Tower D-8, Maya Garden City, Ambala Road,
Zirakpur, Punjab 140603

 Contact No: 99109 06938

 Services Provided: website Designing And Development, SEO, SMO, SMM, Branding,
Content Marketing, Graphic Design Service.

 Websites:- www.vivarta2digital.com
 STUDENT PROFILE

Name: Ms. Simran Jaidka

Uni.Roll no.: 6532
Course: MCA-III(Sem-6th)
Training: JavaScript, Bootstrap,JQuery,PHP,Responsive
Website Project Name: Le-Epiceria
College: S.S.D. Women’s Institute Of Technology , Bathinda.
 INDEX
S. No. TOPIC PAGE NO.
1 Introduction 1
2 Objective of Project 2
3 System Analysis of Project 3-5
1) Software Requirement
2) Hardware Requirement
4 Scrum Methodology 6-7

5 System Feasibility 8-9

6 System Design 10-11

1) System Design
2) Detailed Design

7 DFD(Data Flow Diagram) 12-16

8 E-R Diagram 17-18
9 Use Case Diagram 19

10 Data Table 20-22

11 Snapshots 23-38
12 System Testing and Implementation 39-44
13 Maintenance 45-46
14 Future 47-48
15 Bibliography and References 49
Introduction
To
Project
INTRODUCTION TO PROJECT
About the project

“Le-Epiceria” is a web based shopping system for an existing shop. The project objective is to

deliver the online shopping application into android platform.

This project is an attempt to provide the advantages of online shopping to customers of a real

shop. It helps buying the products in the shop anywhere through internet by using an android

device & computers. Thus the customer will get the service of online shopping and home

delivery from his favorite shop. This system can be implemented to any shop in the locality or to

multinational branded shops having retail outlet chains.

If shops are providing an online portal where their customers can enjoy easy shopping from

anywhere, the shops won’t be losing any more customers to the trending online shops such as

flipcart or ebay. Since the application is available in the Smartphone it is easily accessible and

always available.

In proposed project there is also facility of livechat available through which the users can ask

their queries directly and presently to the owner.

1
 Objectives of Project
The main objective of the Project on Le-Epiceria is to manage the details of Products,
Customers, Order, Stock. It manages all the information about Grocery, Order , Product . The
project is totally built at the administrative end and thus only the administrator is guaranteed the
access. The purpose of the project is to built an application programme to reduce the manual
work for managing the grocery, Customer, Address, Order. It tracks all the details about the
Order, Stock, Product.

Functionalities provided by Le-Epiceria are given below:

 It allows the customers from the world to view and order food products.
 It provides the full details about the food products and related information about the
product like cost, weight and best before detail etc.
 It provides the facility to customer who wants to buy online food products due to lack of
time and travelling.
 It provides the facility to customers by paying online through Paytm or Orange web
payment system or by cash on delivery.
 It is multilingual website (French, Spanish & English) and provides the facility to
customer to change the language of the website according to their own language.

EXISTING SYSTEM
The current system for shopping is to visit the shop manually and from the available product
choose the item customer want and buying the item by payment of the price of the item .
Disadvantages are:
1. It is less user-friendly.
2. User must go to shop and select products.
3. It is difficult to identify the required product.
4. It is a time consuming process
5. Not in reach of distant users.

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 system also
recommends a home delivery system for the purchased products. Benefits are:
1. It is more user-friendly.
2. User must not go to shop and select products.
3. It is a time saving process .
4.In reach of large no. of
users.
2
SYSTEM ANALYSIS

3
System Analysis

System analysis is critical to the success of a development project. Requirements must be

documented, actionable, measurable, testable, related to identified program needs or
opportunities, and defined to a level of detail sufficient for system design. Requirements can be
functional and non-functional. It involves obtaining a clear and thorough understanding of the
product to be developed i.e. what is the requirement? What are the solutions? Etc.

Strengths of the System

 No complex Equipment:-The equipment that is used is very simple and no special skills
have to be mastered to be able to operate the system . Therefore, no training is required
for the employees.
 Low Cost:-There is little money spent in maintaining the present system other than
buying the necessary equipment and the ledgers.
 Practicality:-The system is quite stable and can be operated by the people with average
intelligence.
 Efficiency:- I tried to involve accuracy, timeliness and comprehensiveness of the system
output.
 Cost:- It is desirable to aim for the system with a minimum cost subject to th0e condition
that it must satisfy the entire requirement.
 Flexibility:-I have tried that the system should be modified depending on the changing
Needs of the user such modifications should entail extensive reconstructing or recreation
Of software
 Security:-This is very important aspect which I followed in this designing phase and tried
to covers the areas of hardware reliability , feedback procedures and physical security
data.

4
System Requirement Specification

Software Requirements

Component Specification

Operating Systems Minimum Window 7 & above (Windows

8,9,10)
Frontend Tool WordPress

Backend Tool MySQL

Web Browser Chrome,Internet Explorer,Safari,MozilaFirefox

Hardware Requirements

Hardware Requirements
CPU Processor C2D 2.00 GHz minimum

Physical memory (RAM) 512 MB recommended

Virtual memory Double the amount of RAM

Temp disk space Hard disk space 40 GB

5
 Scrum Methodology

What is Scrum Project Management?

There are various methodologies but we use scrum methodology here.

Use Scrum Project Management to Deliver Working Products with More Business Value
Scrum project management is a methodology for managing software delivery that comes under
the broader umbrella of agile project management. It provides a lightweight process framework
that embraces iterative and incremental practices, helping organizations deliver working software
more frequently. Projects progress via a series of iterations called sprints; at the end of each
sprint the team produces a potentially deliverable product increment.

How Does Scrum Project Management Work?

The Scrum approach to project management enables software development organizations to

prioritize the work that matters most and break it down into manageable chunks. Scrum is about
collaborating and communicating both with the people who are doing the work and the people
who need the work done. It’s about delivering often and responding to feedback, increasing
business value by ensuring that customers get what they actually want.

Shifting from traditional project management approaches to Scrum project management requires
an adjustment in terms of the activities that are carried out, the artifacts that are created and the
roles within the project team.

Activities in Scrum Project Management

The main activity in Scrum project management is the Sprint, a time boxed iteration that usually
lasts between 1-4 weeks, with the most common sprint length being 2 weeks.

 Sprint Planning Meeting: At the start of each sprint a planning meeting is held to discuss
the work that is to be done. The product owner and the team meet to discuss the highest-
priority items on the product backlog. Team members figure out how many items they can
commit to and then create a sprint backlog, which is a list of the tasks to complete during
the sprint.
 Daily scrum or daily standup: Each day during the sprint team members share what they
worked on the prior day, will work on today, and identify any impediments. Daily scrums

6
 serve to synchronize the work of team members as they discuss the work of the sprint.
These meetings are time boxed to no more than 15 minutes.
 Sprint Review: At the end of a sprint the team demonstrates the functionality added
during the sprint. The goal of this meeting is to get feedback from the product owner and
any users or other stakeholders who have been invited to the review.
 Sprint Retrospective: At the end of each sprint the team participates in a retrospective
meeting to reflect on the sprint that is ending and identify opportunities to improve in the
new sprint.

Artifacts in Scrum Project Management

Scrum Project Management requires very few artifacts, concentrating instead on delivering
software that produces business value. The main artifacts in Scrum are:

 Product Backlog: This is a complete list of the functionality that remains to be added to
the product. The product backlog is prioritized by the product owner so that the team
always works on the most valuable features first.
 Sprint Backlog: This is a prioritized list of tasks the team needs to complete during the
sprint.
 Burndown charts: These are used to show the amount of work remaining in a sprint and
provide an effective way to determine at a glance whether a sprint is on schedule to have
all planned work finished.

7
FEASIBILITY
STUDY OF
PROJECT

8
FEASIBILITY STUDY
Preliminary investigation examine project feasibility, the likelihood the system will be useful to
the organization. The main objective of the feasibility study is to test the Technical, Operational
and Economical feasibility for adding new modules and debugging old running system.
Feasibility study is the process of determination of whether or not a project is worth doing.
Feasibility analysis is completed in three phases:
1. Technical feasibility
2. Economical feasibility
3. Operational feasibility

Technical feasibility
Technical feasibility determines whether the work for the project can be done with the existing
equipment, software technology and available personnel. Technical feasibility is concerned with
specifying equipment and software that will satisfy the user requirement. Le-Epiceria is
technically feasible as the technical requirements are completely available in the present
scenario.

The technical requirements for Le-Epeceria are:

 Front-End – WordPress

 Database- MYSQL

Economic Feasibility
 Economic analysis is the most frequently used method for evaluating the effectiveness of
a carpooling system.

 The system being developed is economic with respect to Company’s point of view.

 The driver who is sharing his available seats get a fare amount of share from all the
passengers for his fuel and other expenses.

 The passengers also share their fare with other passengers which makes their journey
economic and hassle-free.

Operational Feasibility

 The system working is quite easy to use and learn due to its simple but
attractive interface. User requires no special training for operating the system.

9
SYSTEM
DESIGN

10
SYSTEM DESIGN

System design is the process of defining the architecture, modules, interface, and data for a
system to satisfy specified requirement. System design could be seen as the application of system
theory to product development.

The primary objective of the design is to deliver the requirements as specified in the feasibility
report. These are the some of the objectives, which I kept in mind:-

 Practicality: The system is quite stable and can be operated by the people with
average intelligence.
 Efficiency: I tried to involve accuracy, timeliness and comprehensiveness of the
system output.
 Cost: It is desirable to aim for the system with a minimum cost subject to the
condition that it must satisfy the entire requirement.
 Flexibility: I have tried that the system should be modifiable depending on the
changing needs of the user. Such modifications should entail extensive
reconstructing or recreation of software. It should also be portable to different
computer systems.
 Security: This is very important aspect which I followed in this designing phase
and tried to covers the areas of hardware reliability, fallback procedures, and physical
security of data.

DETAILED DESIGN

The detail design phase involves completing the product’s design. The design team works
toward completion of the specification for the product and its subassemblies, product
element, and manufacturing processes. Like the other phases of product development ,detail
design is an iterative process. Design trade-offs are made as the design team learns more
about the impact of design decisions on the performance, reliability and cost of the
product.The design team obtains more information about how to manufacture
components,subassemblies, and the product, product’s design requirements.

11
DFD(Data Flow Diagram)

DFD
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modelling its process aspects. Often they are a preliminary step used to
create an overview of the system which can later be elaborated. DFDs can also be used for the
visualization of data processing (structured design).
A DFD shows what kinds of data will be input to and output from the system, where the data
will come from and go to, and where the data will be stored. It does not show information about
the timing of processes, or information about whether processes will operate in sequence or in
parallel (which is shown on a flowchart).

DFD Symbols

 A square defines a source or destination of system data.

 An arrow line identifies the data flow or data in motion. It is a pipeline through which
information flows.

 A circle or bubble represents a process transform incoming data flow in to outgoing

data flow.

 A horizontal line represents data stored or data at rest or a temporary rest repository of
data.
 An open rectangle refers to the database storage

12
 LEVEL 0

View
Guest/User/Admin Le-Epiceria

Request for view reply

Le-Epiceria db

LEVEL 1(Guest)
View/search or add product to cart/

Guest Visit Le Epiceria

Le-Epiceria db

13
 LEVEL 1(user)
View/search/ add product to cart / Cancel order/
purchase items
User Visit Le Epiceria

Le-Epiceria db

LEVEL 1(admin)

Admin Login Check Valid Admin Update

Database
Authentication

Changes made to database changes saved

Le-Epiceria db

14
LEVEL 2(Guest/User)

Visit Le Epiceria
Guest/User

View/select

Category Choose Category

View/select product

product Choose Product

After Select product then add to cart

Add to Cart
addcart
create account/login/registration

Account Creation
user/customer

buy product

Buy Product

15
LEVEL 2(admin)

authenticate
Admin Le Epiceria

View
Insert data
Add/Update Category
category
reply

Insert data

product Add/Update
reply Product

check cart
request for view
View Cart
addcart
reply
view/select order
request for view

order View order

reply

confirm/cancel order
request for confirm
/cancel order
Confirm/cancel order
order
reply

dispatch order
order Dispatch order
reply

deliver product

Deliver product

16
ER Diagram
ER diagram

An entity-relationship diagram, or ERD, is a chart that visually represents the relationship

between database entities. ERDs model an organization’s data storage requirements with three
main components: entities, attributes, and relationships.
Symbols used in ER Diagram
Entities:- An entity is an object with a distinct set of properties that is easily identified.

A weak entity is an entity that must defined by a foreign key relationship with another entity as
it cannot be uniquely identified by its own attributes alone.

Attributes:- An attribute is a property of an entity that differentiates it from other entities and
provides information about the entity.

A multivalued attribute can have more than one value. For example, an employee entity can
have multiple skill values.

Relationship:- A relationship is a crucial part of the design of database which represent the
link between different entities.

17
 Le Epiceria

Cust.Id 1 1

UserId
Belongs Manages
Name

M 1 User Name
Email Id
Customer/User
Admin
Address
1 Password

UserName
1 Deliver 1

Password
Reserve
Products In M Manages

Product id
Product id
1 M
P_Name
P_Name
Shopping Cart Products
P_Price
Total Price
1 M
P_Quantity P_Category
Purchase To Buy

1 P_Quantity

1
Registration or
Login

Email Id
Password

User Name
18
Use Case Diagram
A use case diagram at its simplest is a representation of user’s interaction with the system that
shows the relationship between user and the different use cases in which the user is involved A
use case diagram can identify the different types of users of a system and the different use cases .

Login/Register

New account
creation/SignUp

User
View FoodStore Details

View Categories /
Products

Add/delete categories
/products

Add/Remove Products
to/from cart
Guest
Order products
Or View Orders

Track order current

Status

Manage or Reject
Orders

Manage Customer/
Product database

19
DATABASE

20
Admin Table:

Field Name Datatype Constant

User_name varchar Primary key

User_password varchar Notnull

Users /customers Login Table:

Field Name Datatype Constant

Id Int Primary key

Name varchar Notnull
Email varchar Notnull

User/Customers Table:

Field Name Datatype Constant

Id Int Primary key

Name varchar Notnull
Email varchar Notnull
Phone no. Int Not null
Address varchar Not null
City varchar Not null
State varchar Not null
Country varchar Not null
Postcode Int Not null

21
Product Table:

Field Name Datatype Constant

Id Int Primary key

Name varchar Notnull
Category varchar Notnull
Price Int Not null
Quantity Int Not null

Order Table:

Field Name Datatype Constant

Id Int Primary key

Date Int Notnull
Email Varchar Notnull
Product_name Varchar Notnull
Product_qty Int Notnull
Pickedup location Varchar Notnull
Subtotal Int Not null
Payment method Varchar Not null
Total Int Notnull

22
SNAPSHOTS

23
HOMEPAGE:

24
25
26
ABOUTUS PAGE:

27
WEEKLY-SPECIAL PAGE:

28
SHOP PAGE:

29
PRODUCT CATERGORY PAGE:

30
SINGLE PRODUCT PAGE:

31
CART PAGE:

32
CHECKOUT PAGE:

33
34
ORDER-DETAILS PAGE:

35
CONTACT US PAGE:

36
USER-ACCOUNT PAGE:

37
USER ORDERVIEW:

38
TESTING

39
TESTING
Software testing is a process of running with intent of finding errors in software. Software testing
assures the quality of software and represents final review of other phases of software like
specification, design, code generation etc.

Testing Objectives
The main objective of testing is to uncover a host of errors, systematically and with minimum
effort and time. Stating formally, we can say,

 Testing is a process of executing a program with the intent of finding an error.

 A successful test is one that uncovers an as yet undiscovered error.
 A good test case is one that has a high probability of finding error, if it exists. The tests
are inadequate to detect possibly present errors.
 The software more or less confirms to the quality and reliable standards.

LEVELS OF TESTING
The two levels of Testing are
 Unit Testing
 System Testing

Unit Testing
Unit testing emphasizes the verification effort on the smallest unit of software design i.e.; a
software component or module. Unit testing is a dynamic method for verification, where
program is actually compiled and executed. Unit testing is performed in parallel with the coding
phase. Unit testing tests units or modules not the whole software.

I have tested each view/module of the application individually. As the modules were built up
testing was carried out simultaneously, tracking out each and every kind of input and checking
the corresponding output until module is working correctly.

The functionality of the modules was also tested as separate units. Each of the three
modules was tested as separate units. In each module all the functionalities were tested in
isolation.

1. In the Shop Products Module when a product has been added to cart it has been made sure that
if the item already exists in the shopping cart then the quantity is increased by one else a new
item is created in the shopping cart. Also the state of the system after a product has been dragged
in to the shopping cart is same as the state of the system if it was added by clicking the add to
cart button. Also it has been ensured that all the images of the products displayed in the shop
products page are drag gable and have the product property so that they can be dropped in the
cart area.

2. In the Product Description Module it has been tested that all the images are displayed properly.
Users can add review and the as soon as a user adds a review it is updated in the view customer

40
review tab. It has been checked to see if the whole page refreshes or a partial page update
happens when a user writes a review.

3. In the Cart Details it has been tested that when a user edits a quantity or removes a product
from the cart, the total price is updated accordingly. It has been checked to see if the whole page
refreshes or a partial page update happens when a user edits the cart.

Integration Testing
In integration testing a system consisting of different modules is tested for problems arising from
component interaction. Integration testing should be developed from the system specification.
Firstly, a minimum configuration must be integrated and tested.
In my project I have done integration testing in a bottom up fashion i.e. in this project I have
started construction and testing with atomic modules. After unit testing the modules are
integrated one by one and then tested the system for problems arising from component
interaction.

Validation Testing
It provides final assurances that software meets all functional, behavioral & performance
requirement. Black box testing techniques are used.
There are three main components
- Validation test criteria (no. in place of no. & char in place of char)
- Configuration review (to ensure the completeness of s/w configuration.)
- Alpha & Beta testing-Alpha testing is done at developer’s site i.e. at home & Beta testing once
it is deployed.
Test Cases- I have used a number of test cases for testing the product. There were different cases
for which different inputs were used to check whether desired output is produced or not.
1. Addition of a new product to the cart should create a new row in the shopping cart.
2. Addition of an existing product to the cart has to update the quantity of the
product. 3.Any changes to items in the cart have to update the summary correctly.
4. Because same page is inserting data into more than one table in the database atomicity of the
transaction is tested.
5. The state of the system after a product has been dragged in to the cart should be same as the
state of the system if the same product is added to the cart by clicking a button.

Testing Done in our System

The best testing is to test each subsystem separately as we have done in our project. It is best to
test a system during the implementation stage in form of small sub steps rather then large chunks.
We have tested each module separately i.e. have completed unit testing first and system testing
was done after combining /linking all different Modules with different menus and thorough
testing was done. Once each lowest level unit has been tested, units are combined with related
units and retested in combination. These proceeds hierarchically bottom-up until the entire system
is tested as a whole. Hence we have used the Top Up approach for testing our system

41
IMPLEMENTATION

42
IMPLEMENTATION
System implementation is the stage when the user has thoroughly tested the system and approves
all the features provided by the system. The various tests are performed and the system is
approved only after all the requirements are met and the user is satisfied.

Implementation is the process of having systems personnel check out and put new equipment
into use, train users, install the new application and construct any files of data needed to use it.
This phase is less creative than system design.

The implementation of the web based or LAN based networked project has some extra steps at
the time of implementation. We need to configure the system according the requirement of the
software.

For the project we need to install and configure Xamp server 3.0.6, database server, and the
deployment directory for the project.

ASPECTS OF IMPLEMENTATION
The two aspects of implementation are:
• Training Personnel

• Conversion Procedures

Training
Even well designed and technically elegant systems can succeed or fail because of the way they
are used. Therefore, the quality of the training received by the personnel involved with the
system in
various ways helps or hinders, and may even prevent, the successful implementation of an
information system
Conversion
Conversion is the process of changing from the old system to the new system. There are two
methods of handling systems conversion:

• Parallel Run
• Immediate cut-off

43
Parallel Run
In this approach, the old system and the new system are used simultaneously for some period of
time so that the performance of the new system can be monitored and compared with that of the
old system. Also in case of failureof the new system, the user can fall back on the old system.
The risk of this approach is that the user may never want to shift to new system.

Immediate cut-off
In this method, the use of the old system ceases as soon as the new system is implemented and
bought in to palace. The old system becomes redundant from the day of implementation of the
new system. There is the high risk involved in this approach if the new system is not tested
rigorously.

This is because of the fact that if the new system fails, then there will not be anything to fall back
upon. The advantage of this approach is that both the systems need not be used simultaneously.

44
MAINTENANCE

45
Maintenance
Once the Application that is Installed on the System. it Enters the Maintenance Phase. All
system need maintenance. Maintenance is required because there are often some residual errors
remaining in the system that must be removed as they are discovered Maintenance involves
understanding the effects of the change, making the changes to both the code and the
documents, testing the new parts and retesting the old parts that were not changed .Maintenance
is mainly of two types:

 Corrective Maintenance.

 Adaptive Maintenance.

Corrective Maintenance: Almost all software that is developed has residual errors or bugs in
them. Many of these Surfaces only after the system have been on operation, sometimes for a
long time. These errors once discovered need to be removed, leading to the software to be
change. This is Called Corrective Maintenance.

Adaptive Maintenance: Even without a bugs, Software Frequently undergoes change. the
software often must be upgraded and enhanced to include more features and provide more
services This requires modification of the Software. This type of Maintenance is known as the
Adaptive Maintenance.

46
FUTURESCOPE

47
Future Scope
The following things can be done in future.
 The Online payment system through E-cards will work in future.
 Coupon system also will be in work in future,with the help of coupon system
customers can apply coupon on different products and get the benefit upon prices .
 The users could subscribe for price alerts which would enable them to receive
messages when price for products fall below a particular level.

48
Bibliography
 Learning MYSQL & Javascript with Jquery ,CSS & HTML5
 Learn PHP , Bootstrap ,MySQL

Catalogues
 Training sessions conducted by company itself.

References :
www.w3schools.com

49
50
51