A PROJECT REPORT

ON

“NutBut Dry-Fruits”

Prepared by
Maulik Kapupara(RU230696)
Prince Khunt(RU230697)

Under the guidance of

Submitted in
Partial Fulfillment of the Requirements for the Degree of Master of
Computer Application

Submitted at

MAY 2024
DEPARTMENT OF
CSA
RAI SCHOOL OF ENGINEERING SARODA, DHOLKA - 382260 DIST:
AHMEDABAD, GUJARAT

1
 RAI SCHOOL OF ENGINEERING

CERTIFICATE

This is to certify that Mr. Maulik Kapupara of MCA Semester II has

completed his project work titled “NutBut Dry-Fruits” satisfactorily in partial
fulfillment of the requirement of Master of Computer Application degree,
Rai University, Saroda, Ahmedabad in the year 2024.

Internal Guide Head of Department

Prof. Amarjit Prof. Jigar Pandya
Assistant Professor

CSA Department CSA Department

Date: Date:

2
 RAI SCHOOL OF ENGINEERING

CERTIFICATE

This is to certify that Mr. Prince Khunt of MCA Semester II has completed his
project work titled “NutBut Dry-Fruits” satisfactorily in partial fulfillment of
the requirement of Master of Computer Application degree, Rai University,
Saroda, Ahmedabad in the year 2024.

Internal Guide Head of Department

Prof. Amarjit Prof. Jigar Pandya
Assistant Professor

CSA Department CSA Department

Date: Date:

3
 CANDIDATE’S DECLARATION

I hereby declare that, the project report titled “NutBut Dry-Fruits”

submitted towards the partial completion of Project in 2nd semester, of
the Master of Computer Applications in, RSE, Rai University,
Ahmedabad, is an authentic record of my work carried out.

I further declare that the work reported in this project has not been
submitted and will not be submitted, either in part or in full for the award
of any other degree in this institute or any other institute.

Candidate’s Name: Maulik Kapupara

Branch: MCA Candidate’s Signature
Enrollment No: RU230696

Candidate’s Name: Prince Khunt

Branch: MCA Candidate’s Signature
Enrollment No: RU230697

This is to certify that the above statement made by the candidate is

correct to the best of my knowledge.

Signature of
Internal Guide
Prof. Aditya Yadav

4
 AKNOWLEDGEMENT
Apart from the efforts of mine, the success of any project depends largely on the
encouragement and guidelines of many others. I take this opportunity to pen down
and express my gratitude to the people who have been instrumental in the
successful completion of this project.

During this Project, I gained a good experience of real work, which is completely
different from the academics. Moreover, this Project can be considered as the final
step towards achieving the bachelor’s degree. I express my sincere thanks to many
people who have helped me during my training.

I am grateful to my college, RAI SCHOOL OF ENGINEERING, RAI UNIVERSITY for

giving me this wonderful opportunity to undertake this training.

I convey my sincere thanks to Dr. Sailesh Iyer (DEAN, RSE, Rai University), Prof.
Jigar Pandya (HOD, CSA, RSE, Rai University), Prof. Amarjeet (My Internal
Project Guide) for providing me his time, constructive criticism and valuable guidance.
The guidance and support received from all the other faculty members who contributed to
this project, was vital for the success of the project. Besides this, I would like to thank all
those people who helped me in one or the other way.

5
INDEX
NO Particulars Page Number
1 Project Profile 5

2 Introduction/Aims and Objectives 6

3 System Analysis 6

4 Identification Of Need 6

-Preliminary Investigation 6

5 Feasibility Study 9

-Technical Feasibility 9

-Economical Feasibility 9

-Operational Feasibility 10

6 Cost estimation 11

7 Project Analysis 13

Data Dictionary 13

Data Flow Diagram 16

- 0-Level Diagram 18

- 1st Level Diagram 19

- 2nd Level Diagram 21

8 S/W Engineering. Paradigm applied 25

9 S/W & H/W Requirement Specification 25

10 PERTT Chart 26

11 Time Line/GANTT Chart 27

12 Validation Checks /Special Tools 28

Used/Detailed Project scope Explanation
13 Testing 32

14 Implementation 34

6
15 Limitation 35

16 All Screen Layouts & Coding 36

18 Bibliography/References/Glossary 199

7
PROJECT PROFILE
Project NutBut Dry-fruits
Name:
Technology: PHP, mySQL

Front End: HTML, CSS, JavaScript

Back End: PHP (database = nutbut)

Internal Prof. Aditya yadav

Guide:
Submitted Rai University, Ahmedabad
To:
Developed Maulik Kapupara, Prince Khunt
By:

8
INTRODUCTION
 This system is accessed by any user by entering URL of this website in
any browser with the internet.
 Any user can see the websites product.
 Any user can search items by its category like Almonds ,Cashews
Nut ,Pistachios, Walnuts, Raisin, Other Iteams.
 Users can also generate their cart.
 To buy the particular items user needs to register in the website by
providing the email.
 Admin can add, remove, update or see the products.
 Admin can add, remove, update or see the category details of product.
 Admin can add, remove, update or see the Banner.
 Admin can add, remove, update or see the Blogs.
 There are also tables where admin can see the customer's order and its
detail.

SYSTEM ANALYSIS
 This system is all about the converting the shopping system from manual
to online.
 Customer can buy products online after login to the site.
 Admin is adding product to database.
 Admin can edit or delete the products from the database.
 After buying the products are sending to customer’s address that they
have given.

IDENTIFICATION OF NEED
PRILIMINARY INVESTIGATION:
Preliminary investigation is the first phase. In this phase, the system is
investigated. The objective of this phase is to conduct an initial analysis and
findings of the system.

9
The purpose of the preliminary investigation is to evaluate the project requests.
It is not a design study, not does it include the collection of details to completely
describe the business system.
Rather, it is the collecting of information that permits committee members to
evaluate the merits the project request and make an informed judgment about
the feasibility of the proposed project.
I collect the information in this phase through personal interview.
The following is the questionnaire and the answers of the personal interview
that I taken.

Question 1: Which type of application you want to develop?

Answer: Website
Question 2: What will the purpose of this website?
Answer: The main purpose of this website will be that customers can buy dry-
fruits online from this website anywhere and anytime.
Question 3: Do you have any this type of running website?
Answer: No, we have no any this type of running website.
Question 4: Tell me about the functionality that you want in your website?
Answer: There will be must the following functionality that we need in our
website:
- Customers should be able to see dry-fruits category like
Almonds ,Cashews Nut ,Pistachios, Walnuts, Raisin,etc.
- There should be a menus of each category so, customers can easily find
its required products in the minimum time.
- Slider on which we can display our best offers and out new arrival
products.
- Each product must be displayed with its appropriate information like its
name, price, discount etc.
- Customers must be able to add that's items to the cart.
- Without login no any customer can buy the products.
Question 5: Say something about your website design which must be
you want in your system?
Answer: Design should be simple like there were must be,

10
 - A Menus
- A Slider
- There must be menu of a cart system.
- In the bottom we must needs our social account list.
Question 6: Which type of payment method you want in your website?
Answer: Only cash-on-delivery.
Question 7: What is the budget for your website?
Answer: Answer: Rs.10,000 to Rs.12,000
Question 8: How much time-duration in you want to complete this website?
Answer: 2 to 3 month.
Question 9: Please give the title for your website.
Answer: Nut But Dry-Fruits
Question 10: Do you have any logo?
Answer: Yes, we have.

FEASIBILITY STUDY
Feasibility is the measure of how beneficial or practical the development of an
information system will be to an organization.

Feasibility analysis is the process by which feasibility is measured. Feasibility

of a project determines whether it is possible to develop the project.

These are four main factors, which determine the feasibility of the project. They
are discussed as follow.

(1) Technical Feasibility:

The main aim of technical feasibility study is to determine whether it is

possible to develop the proposed system.

Can only be evaluated after the technical issues are resolved issues. The
present technologies available and study the technical requirements and
their availability in the organization & the technical equipments
availability in market.

So, in this project technical requirement is:

11
 Hardware: A computer with

- 1 GB RAM

- 500 MB Hard disk

- Intel core processor

Software: - Any editor

- Any Browser

- MySql

The above both technical requirements can be fulfil. So system is

technically feasible.

(2) Economical Feasibility:

To measure the cost-effectiveness of a project or solution. Which is often

called cost-benefit analysis.

The economic feasibly takes into consideration the financial matters

regarding the proposed system. The organization measures the cost
effectiveness of the proposed system. The economical feasibility of the
proposed system is as under budget of a company or not! This is checked in
economical feasibility.

As the requirement there is must be the cost of the following things.

- Development Cost : Rs.7000

- Light Bill : Rs. 2000
- Software : Rs. 1500
- Other : Rs. 1500
--------------
Rs.12,000

So, it is also possible.

(3) Operational Feasibility:

Operational feasibility studies also look at how a project plan meets the
criteria specified during the system development requirements analysis phase.

12
 The operation feasibility deals with the matter whether the proposed
system fulfills the requirement of the organization. This feasibility determines
whether the proposed system covers all the aspects of the current system &
gives an extra facility which is not in current system.

As, the requirement there is no any old system or this system can be used
by any computer basic knowledge person. So, it is also feasible.

COST ESTIMATION
There are many methods available to get the size of the project. I have use two
methods to estimate the size of the project. Those methods are LOC (Line of
Code) and FP (Function Point). With these both methods I can get approximate
size of the project.
There are two methods available in "Software Engineering" to get the
approximate cost of the project. These methods are COCOMO (Constructive
Cost Model) and Empirical method. With these both methods I can get
approximate cost of the project.
I have gone through LOC method to get the approximate size of this software
project and COCOMO method to gate the approximate cost of the software
project.
Here I have done all the calculations to get the approximate size and cost of this
website project
LOC:
Code For Best Most Likely Worst
Design 2000 2100 2200
Database 1000 1400 1500
Coding 4000 5000 5700

13
 Total 7000 8500 9400

LOC (24900/3) = 8000

KLOC 8000/1000=8
COCOMO METHOD
E=2.4+(KLOC)8
=2.4+(1.82)8
2.4+14.56
E = 16.96 perMonth
T = 2.5+(E) 0.38
2.5+(1.696)0.38
T = 3.144
Cost estimate is as given below working time.
3Month = 90days
Expensive & Cot Estimation
Computer rent 4000
Light Bill 2000
Database design & Creation 1000
Coding 5000
12,000
Then the approximate cost of this website will be about 12,000/- RS.

14
PROJECT ANALYSIS
DATA DICTIONARY:
Project goals are converted into the defined system functions that the
organization intends to develop.
Data Dictionary set of information describing the contents, format, and structure
of a database and the relationship between its elements, used to control access to
and manipulate of the database.
Database: nutbut
Table: adminusers
Description: This table will stores the detail of the admin.
Field Name Data type Constraint Description
ID Int(11) Auto Store the unique ID
Increment
USERNAME Varchar(255) Not null Store the username
PASSWORD Varchar(255) Not null Password of admin
EMAIL Varchar(255) Not null Store the email of user

Table: customer
Description: This table will stores the detail of the order of product.
Field Name Data type Constraint Description
ID Int(11) Auto Store the unique ID
Increment
FIRST NAME Varchar(255) Not null Store the user first name
LAST NAME Varchar(255) Not null Store the user last name
EMAIL Varchar(255) Not null Store the user email id
ADDRESS Varchar(300) Not null Store the user address
CITY Varchar(255) Not null Store the user city name
PHONENUMBER Varchar(255) Not null Store the user phone
number
PRODUCT ID Int(12) Not null Store the product id from

15
 cart item table
USER ID Int(12) Not null Store the user id from cart
item table
PRODUCT Varchar(255) Not null Store the product image
IMAGE from cart item table
PRODUCT Varchar(255) Not null Store the product quantity
QUANTITY from cart item table

Table: category
Description: This table will stores the different type of items category.
Field Name Data type Constraint Description
ID Int(11) Auto Store the unique ID
Increment
CATEGORY Varchar(255) Not null Store the category name
NAME
CATEGORY Varchar(255) Not null Store the images of
IMAGE category

Table: product
Description: This table will stores the detail of the product.
Field Name Data type Constraint Description
ID Int(11) Auto Store the unique ID
Increment
CATEGORY ID Varchar(255) Not null Store the category id from
category table
PRODUCT NAME Varchar(255) Not null Store the product name
DESCRIPTION Text Not null Store the description of
product
PRICE int(11) Not null Store the product price
SPECIAL PRICE Varchar(255) Not null Store the product special
price
PRODUCT Varchar(255) Not null Store the product of
IMAGE image

Table: cart item

Description: This table will be uses for the cart system.
Field Name Data type Constraint Description

16
 ID Int(11) Auto Increment Store the unique ID
USER ID Varchar(255 Not null Store the user ID
)
PRODUCT ID Int(11) Not null Store the product
ID
PRODUCT IMAGE Varchar(255 Not null Store the product
) Image
PRODUCT PRICE Varchar(255 Not null Store the product
) price
PRODUCT Varchar(255 Not null Store the product of
QUANTITY ) quantity
PRODUCT IMAGE Varchar(255 Not null Store the product
) ID
TOTAL Varchar(255 Not null Store the product
) price title

Table: blog
Description: This table will stores the detail of the blog.
Field Name Data type Constraint Description
ID Int(11) Auto Increment Store the unique ID
BLOG TITLE Varchar(255) Not null Store the blog title
BLOG Text Not null Store the blog
DISCRIPTION discription
BLOG IMAGE Varchar(255) Not null Store the blog image
BLOG date Date Not null Store the blog date

Table: Add Banner

Description: This table will be uses for the customer order tracking history.
Field Name Data type Constraint Description
ID Int(11) Auto Increment Store the unique ID
SLIDER TITLE Varchar(255) Not null Store the slider title
SLIDER IMAGE Varchar(255) Not null Store the slider image

Table: users
Description: This table will store the whole user entered login in website.

17
 Field Name Data type Constraint Description
ID Int(12) Auto Store the unique ID
Increment
USER NAME Varchar(255) Not null Store the user name
EMAIL Varchar(255) Not null Store the user email id
PASSWORD Varchar(50) Not null Store the user password

DATA FLOW DIAGRAM:

A data flow diagram (DFD) is a graphical representation of the "flow" of the
data through an information system, modeling its process aspects.
It's easy to understand the flow of data through systems with the right data flow
diagram software. This guide provides everything you need to know about data
flow diagrams, including definitions, history, and symbols and notations.
The data-flow diagram is part of the structured-analysis modeling tools. When using
UML, the activity diagram typically takes over the role of the data-flow diagram.
DFD is a graphical view of all system processes and transactions. With the DFD
an End-User also can easily understand the system in a short time
It may be used as a communication tool between a system analyst and any
person who plays a part in the order that acts as a starting point for redesigning
a system.
Thus DFD is a necessary phase while developing software.
DFD use a number of symbols to represent system. Most data flow modeling
methods use four kinds of symbols these symbols are used to represent four
kinds of system components.
1- Processes
2- Data stores
3- Data flows
4- External entities
Explanation of main symbols which are used in data flow diagram is given

18
1) This shape is used in data flow diagram for
represent a particular Database.

2) This shape is used in data flow diagram for

represent a input/output process.

3) This arrow shape is used in data flow

diagram represent a particular process.

4) This shape is used in data flow diagram for

represent a particular process

19
So, the following is the data Flow Diagram of my project.

1) 0-Level

users

Request Response

nutbut

Request Response

admin

20
2) 1-Level-Client (Data flow diagram)

21
3) 1-Level-Admin (Data Flow Diagram)

22
4) 2-Level-Client (Data Flow Diagram)

23
5) 2-Level-Admin (Data Flow Diagram)

24
S/W Engineering Paradigm:
System Development Life Cycle is process of development of software. There
are some steps to follow to create a system.
In SDLC steps follows requirement gathering. In Requirement gathering
questionnaire, personal interview etc. are the method for gathering information.
Analysis phase includes creating Software Requirement Specification and
analyze the gathered data.
In design phase, design of Software application i.e. database design and GUI
design have to be prepared.
In coding phase coding is done of different modules and forms. In testing phase,
the different type of testing is done like integration testing, unit testing, system
testing and at last the created website is implemented and maintained.
Following are the different Life Cycle Model example.
 Waterfall model
 Iterative waterfall model
 Prototyping model
 Evolutionary model
 Spiral model
 R.A.D. model (Rapid Application Development)
I am following Waterfall Model following is diagrammatic representation of
different phase of waterfall model.
WATERFALL MODEL
Requirement Gathering and analysis :-
All Possible requirements of the system to be developed are captured
in this phase and documented in a requirement specific doc.
System Design :-
The requirement specifications from first phase are studied in this
phase and the system design is prepared.
This system design helps in specifying hardware and system
requirements and helps in defining the overall system architecture.

25
Implementation :-
With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.
Integration and Testing :-
All the Units Develops in the Implementation phase are integrated
into a system after testing of each unit post integration the entire system is
tested for any faults and failures.
Deployment Of system :-
Once the functional and non-functional testing is done the product is
deployed in the customer environment or released into the market.
Maintenance :-
There are some issues which commune in the environment to fix
those issue patches are released also to enhance the product some better version
are released.

H/W REQUIREMENT SPECIFICATION

26
  10 GB Hard Disk
 500 MB RAM
 Monitor / Laptop
 CPU
 Mouse
S/W REQUIREMENT SPECIFICATION
 Any Operating System
 MySql
 Any Editor

PERT Chart
PERT (Project Evaluation and Review Technique) charts consist of a network
of boxes and arrows.
A PERT chart, sometimes called a PERT diagram, is a project management tool
used to schedule, organize and coordinate tasks within a project.
He boxes represent activities and the arrows represent task dependencies. PERT
charts are a more sophisticated form of activity chart.
The boxes of PERT charts are usually annotated with the pessimistic, likely, and
optimistic estimates for every task.
PERT charts provide project managers with an estimation of the minimum
amount of time needed to complete a project.
There are thus not one but many critical paths, depending on the permutations
of the estimates for each task. This makes analysis of critical path show by
using shaded boxes. The PERT chart representation of the MIS problem of
show follows.

27
GANTT CHART
A Gantt chart is a special type of bar chart where each bar represents an activity.
The bars are drawn along a time line. The length of each bar is proportional to
the duration of time planned for the corresponding activity.
No. Task Name Start Finish Duration
1 Requirement 10-08-2021 19-08-2021 9 days
Gathering
2. System analysis 20-08-2021 24-08-2021 4 days
3. Client module design 25-08-2021 31-08-2021 1 weak
4. Database design 1-09-2021 5-09-2021 5 days
5. Admin Module design 6-09-2021 12-09-2021 1 weak
6. Coding 13-09-2021 27-09-2021 15 days
7. Testing 28-09-2021 5-10-2021 8 days
8. Implementation 6-10-2021 9-10-2021 3 days
9. Documentation 10-10-2021 12-10-2021 2 days

In order to estimate the time durations for various activities, usually managers
let the engineers themselves estimate the time for an activity they might be
assigned to. However, some managers prefer to estimate the time for various
activities themselves.

28
Many managers believe that an aggressive schedule motivates the engineers to
do a job better and faster.
However, careful aspects, but also cause schedule compromise on intangible
quality aspects, but also cause schedule delays.
A good way to achieve accuracy without creating problems is to let people set
their own schedules.
We can see that one engineer can do the database design and then code the
database design whereas another engineer and design the GUI part, code the
GUI part, and still have time left for writing the user manual. Thus, Gantt charts
are very useful in scheduling resources

VALIDATION CHECKS
TEST CASES:
A Test case is a set of conditions or variable under which a tester will determine
whether a system satisfy requirement or works correctly.
In software engineering, a test case is a specification of the inputs, execution
conditions, testing procedure, and expected results that define a single test to be
executed to achieve a particular software testing objective, such as to exercise a
particular program path or to verify compliance with a specific requirement.
The process of developing test case can also helps to find the problem in
requirement or design of an application.
A formal written test case is characterized by a known input and by an expected
output, which is worked out before the test is executed.
A test case can have the following elements, not however that normally a test
management tool is used by companies by the tool used.

Test Suit ID: The ID of the test suit, to which this test case belongs.
Test Case ID: The ID of the test case.
Expected Result: The expected result of the test.

29
Actual Result: The actual result of the test, to filled after executing the test
case.
Created By: The name of the author of the test case.
Executed By: The name of the person who executing the test cases.
Pass/Fail: The result in "Pass" or "Fail" according to the test, when the
expected result and the actual result is same then the result is "pass" else result
is "fail".
Remark: Any comment on the test case or test execution.
I create following some test case which is expected by me.

Test Suite Id : 1 Description :

Test Case Id : 1 This test case will checks the
Create By : Kapupara Maulik validation functionality on the
Executed By : Kapupara Maulik login form.
Tas Task Executed Actual Pass / Remark
k No Result Result Fail
1 Enter valid email id Login Login Pass -
and password Successfully success
2 Enter invalid email “Invalid Generating Pass -
id and password email id or “invalid
password” email id or
Massage password
will
generate.
3 Click on login An error Generating Pass -
button without message will an error
providing any generate message
value
4 Enter a valid email “Invalid Generating Pass -
id and password email id or “invalid
but in case password” email id or
sensitive Will password “.
generate.

30
5 Provide an “Invalid Generating Pass -
incorrect email id email id or “invalid
and password password” email id or
Will password “.
generate.
6 Provide a correct An error Generating Pass -
email id or message will an error
incorrect password generate message

7 Provide blank An error Generating Pass -

email id and blank message will an error
password generate message

Test Suite Id : 1 Description :

Test Case Id : 2 This test case will checks the
Create By : Kapupara Maulik validation functionality on the
Executed By : Kapupara Maulik registration form.
Tas Task Executed Actual Pass / Remark
k No Result Result Fail
1 Enter string in String will String is not Pass -
mobile field not allowed. allowing
2 Enter more than 10 Only 10 Only 10 Pass -
digit in mobile digit willdigit
field. allowed. allowing
3 Enter password in Allow the Allowing Pass -
string and number password the
both. password.
4 Remain all field Require Generating Pass -
blank and submit. field require field
message will message.
generate

31
Test Suite Id : 1 Description :
Test Case Id : 3 This test case will checks the
Create By : Kapupara Maulik validation functionality of cart
Executed By : Kapupara Maulik system.
Tas Task Executed Actual Pass / Remark
k No Result Result Fail
1 If user will not Redirect to Redirected Pass -
logged in and login page. to login
clicked on cart page.
2 User visit cart No items Cart is Pass -
without login should be empty. No
displayed. item is
displaying
3 User login and visit If user has No item is Pass -
cart. added any displaying
item then it
displayed.
4 On product page Item should Item is Pass -
clicking on “add to be added to added to
cart” cart cart.
5 Changing the The total Total is Pass -
quantity of item. should be changing
changed
according to
item
quantity
6 Clicking on remove Item will Item is Pass -
check box remove from removed
cart. from cart
and total is
changed.

Test Suite Id : 1 Description :

Test Case Id : 4 This test case will checks the
Create By : Kapupara Maulik validation functionality of
Executed By : Kapupara Maulik checkout process.
Tas Task Executed Actual Pass / Remark
k No Result Result Fail
1 Id user is logged in User will Redirected Pass -

32
 and clicked on redirected to to address
checkout delivery detail page.
address
detail page.
2 Clicking on Items will Message is Pass -
continue on after ordered and Displayed
providing delivery display
detail message the
order is
successfully
order

TESTING
UNIT TESTING
Unit Testing is a software testing technique by means of which individual units
of software.
Unit testing is under taken when a module has been coded and successfully
reviewed.
There are some methods for unit testing are as follows:
1)Black Box Testing
- Equivalence class partition
- Boundary value analysis
2) White Box testing
- Statement coverage
- Branch coverage
- Condition coverage
- Path Coverage
- Linearly independent path

33
- Dataflow based testing
- Mutation testing

INTEGRATING TESTING
The primary objective of the integration testing is to test the module interface in
order to ensure that there are no error in parameter passing when one module
invokes another module.
During integration plan specify the steps and the order in which module are
combine to realize the full system.
After each integration test the practical is tested.
Following are the integration testing method & approaches :
 Big band approach
 Top down approach
 Bottom up approach
 Mixed approach

SYSTEM TESTING
In the system testing the whole application is tested and the error and possibility
is carried out in it.
Following are the method& approaches of the system testing.
 Alpha Testing
 Beta Testing
 Acceptance Testing
Testing is a process of executing a program with the intent of finding an error.
A good test case is one that as a high probability of finding an yet in discovered
error.
A successful test is one that uncovers a yet undiscovered error.

34
Software testing is a critical element of software quantity assurance and
representation, design and coding.
The increasing visibility of software as a system element and the attendant
"cost" associated with a software failure are motivating forces for well-planned,
through testing.
It is not unusual for a software development organization to expend between 30
to 40 percent of total project effort on testing. In the extreme, testing of human-
rated software can cost three times as much as all other software engineering
activities combined.
There are several testing technique but I have been focused to White Box
testing technique. As well as this software is concerns I have test all the
required testing of the testing.

IMPLEMETAION
A Software implementation method is a systematically structured approach to
effectively integrated a software based services or component into workflow of
an organization structure or an individual end-user.
There are four method to implementation.
1. 1.Direct Cutover
2. 2.Parallel running
3. 3.Phased
4. 4.Pilot
I have used parallel running to implement my software.
Parallel Running :
Parallel running is one of the ways to change from an existing system to a new
one. This conversion takes place as the technology of the old one.
The phrase parallel running can refer to the process of changing a fragment of
business information technology operation to a new or to the technique applied

35
by the human resources departments in which the existing staff stay on board
during the transition to a new staff.
It is one of the strategies for system implementation in which both the old and
new system are running side by side until the users are certain that the new
system has no problems. After a period of time, when the system is proved to be
working correctly, the old system will be removed completely and users will
depend solely o the new system.

OLD SYSTEM

NEW SYSTEM

The old and new system are doing the same processing and operating side by
side.

LIMITATION
Most of software project have some limitation, it is not perfect in all way.
Limitation of this software is describe below:
 In this website online payment is not available.
 There is not facility to filter the items.
 All the products are displaying in the one page, i.e. there is no pagination.
 User cannot save their product to buy later.

These limitations can be solved by working on the project of more than the
period allocated for the project.

BIBLIOGRAPHY
There are some study materials which is used by me to develop my project
which are as below:

36
Website:
- www.tutorialspoint.com
- www.stackoverflow.com
- www.w3schools.com

Thank You

37