PROJECT REPORT

ON
“BOOK STORE”

Submitted in partial fulfillment of the

requirement for the award of the degree of
Bachelor of Computer Application

Submitted To Submitted By
Ms.Alpana Sharma Yash Bindal (09329802017)
Assistant Professor
(Batch: 2017-2020)
Vivekananda Institute of Professional Studies

(Affiliated to Guru Gobind Singh Indraprastha University)

09329802017 Yash Bindal

 CERTIFICATE

This is to certify that I, Yash Bindal of BCA 5th Semester from Vivekananda Institute of
Professional Studies, Delhi has presented this project work entitled “Book Store”, an online
auction website in partial fulfillment of the requirements for the award of the degree of Bachelor
of Computer Applications under my supervision and guidance.

Ms. Alpna Sharma

09329802017 Yash Bindal

 ACKNOWLEDGEMENT

It is our proud privilege to express our profound gratitude to the entire management of
Vivekananda Institute of Professional Studies and teachers of the institute for providing us with
the opportunity to avail the excellent facilities and infrastructure. The knowledge and values
inculcated have proved to be of immense help at the very start of my career. Special thanks to
Hon’ble Founder, Vivekananda Institute of Professional Studies, Delhi for having provided us an
excellent infrastructure at VSIT.

I am grateful to Prof. (Dr.) Supriya Madan (Dean, VSIT), and Ms. Alpna Sharma for their astute
guidance, constant encouragement and sincere support for this project work.

Sincere thanks to all my family members, seniors and friends for their support and assistance
throughout the project.

Yash Bindal

Page No.
Table of Contents

09329802017 Yash Bindal

 1 INTRODUCTION 6

1.1 Objective of the System 7

1.2 Justification and need for the system 7
1.3 Advantage of the system 8
1.4 Previous work or related systems, how they are used. 9

2 REQUIREMENT ANALYSIS 10

2.1 Analysis Study 12

2.2 User Requirements 13
2.3 Discussion with IT Experts 14
2.4 Final Requirements 14

3 DESIGN OF THE SYSTEM 15

3.1 Hardware, Software requirements 17

3.2 System requirements 18
3.3 Detailed System Specification (Module Wise) 19
3.4 ER Diagram of the system 20
3.5 DFDs/Algorithms/Flow Charts 20
21
4 IMPLEMENTATION & CODING
22
4.1 Operating System 26
4.2 Languages 30
4.3 S/W Tools 35
4.4 Coding 38

5 TESTING & TEST RESULTS 42

5.1 Software Testing and Objective of Testing 43

5.2 Sample test data/ Output screen printouts etc. 46

6 CONCLUSION
50
6.1 Conclusion
6.2 Future Scope 50
50

Biblography 51

09329802017 Yash Bindal

 Table of Figures
3 Fig. 3.1 Actor and Use case 17

Fig.3.2 Interaction between user and admin 18

Fig 3.3 ER diagram 19

Fig 3.4 DFD 20

4 Fig 4.1 Member table 21

Fig 4.2 Message Table 22

Fig 4.3 Auction Table 23

Fig 4.4 Home page 28

Fig 4.5 Register Page 34

Fig 4.6 Feedback Page 38

Fig 4.7 Message Page 40

Fig 4.8 Send Messages 41

5 Fig 5.1 Registration Page 46

Fig 5.2 Home page 47

Fig 5.3 Home Page 48

Fig 5.4 Home Page 49

Fig 5.5 Registration Page 50

Chapter 1

09329802017 Yash Bindal

 INTRODUCTION
The goal of this master's project is to design an online bookstore named B-Mart that mainly sells
computer and technical books. The book inventories are stored in MySQL. Customers can access the
bookstore web site through the World Wide Web. Customers will be able to search the database to find
the books they want, check the availability, and place the order to buy the book using their credit cards.

It consists of 2 logins :-

1. User Login
2. Admin Login

USER LOGIN
It is the basic login interface for any customer or user of the website. It provides the user with the
information of different items added to be auctioned. Also, the user can add his or her item by using the
add auction option on the member home of the website. He can also bid for the already added items for
auction to purchase them as well as can check the status of auction of every item.

ADMIN LOGIN

This login is meant for the manager of the auction website. It gives an overview of all the auctions placed,
who has placed them, highest bid on the items, etc. It also provides the admin with the advantage to cancel
or finalize any auction. It also has a messages section where the admin can receive the messages of its
users and reply to it appropriately.

1.1 OBJECTIVE OF THE SYSTEM

This project will serve the following objectives:-

1. Provides the user with easy and friendly interface

2. Add and maintain record of available products
3. Add and maintain description of products
4. Provides attractive discounts

09329802017 Yash Bindal

 5. Provides a convenient solution for buying books

1.2 JUSTIFICATION AND NEED FOR THE SYSTEM

Nowadays when everyone is so busy and occupied, we all want ease of work. And with the lack of time
arises the need of these kinds of applications that would provide all the facilities to the customer (user),
and the manager/admin at one place. Now, the admin can handle all the items added to the inventory at
one place.

And on the other hand, the user can get the best price to purchase the items from different users sitting at
his home. He also gets to ask queries.

The manager supervises all the purchases which are being made by the users, receive all the feedbacks
and reply to them when he feels necessary. The admin has the right to cancel or finalize any item.

1.3 Advantages of the system

1. Easiness in modification of data: The proposed system provides managing of huge data effectively
and efficiently for efficient results, storing the details of the products, users, etc. in such a way that the
database can be modified.

2. User friendly: The proposed system is user friendly because the retrieval and storing of data is fast and
data is maintained efficiently. Moreover the graphical user interface is provided in the proposed system,
which provides user to deal with the system very easily.

3. Customer Queries: The users of the system are entitled to ask queries about the items that they have
been added.

4. No or very few paperwork: The proposed system either does not require paper work or very few paper
works is required. All the data is feted into the computer immediately and various feedbacks and reports
can be generated through computers. Since all the data is kept in a database no data of the organization
can be destroyed. Moreover work becomes very easy because there is no need to keep data on papers.

5. Support strategic competitive advantage: Proposed system supports strategic competitive

advantages. Since the proposed systems provide easiness in reports generating it will provide strategic
advantages among competitors.

09329802017 Yash Bindal

6. Computer operator control: Computer operator control will be there no errors. Moreover storing and
retrieving of information is easy. So work can be done speedily and in time.

1.4 Previous work or related systems; how they are used.

Before we begin a new system it is important to study the system that will be improved or replaced (if
there is one). We need to analyze how this system uses hardware, software, network and the people
resources to convert data resources, such as transaction data, into information products, . Thus we should
document how the information system activities of input, processing, output, storage and control are
accomplished.

Following are the problems associated with the previous project which led to the creation of the proposed
project:-

1.Inability of modification of data: The managing of huge data effectively and efficiently for efficient
results, storing the details of the products etc. in such a way that the database can be modified as not
possible in the current system.

2.Not user friendly: The existing system is not user friendly because the retrieval and storing of data is
slow and data is not maintained efficiently.

3.Difficulty in reports generating: Either no reports generating in a current system or they are generated
with great difficulty reports take time to generate in the current system.

4.Manual operator control: Manual operator control is there and leads to a lot of chaos and errors.

5.Lot of paperwork: Existing system requires lot of paper work and even a small transaction require
many papers fill. Moreover any unnatural cause (such as fire in the organization) can destroy all data of
the organization. Loss of even a single paper led to difficult situation because all the papers are
interrelated.

6.Inability of sharing the data: Data cannot be shared in the existing system. This means that no two
persons can use the same data in existing system. Also the two departments in an organization cannot
interact with each other without the actual movement of data.

7. No support in decision-making: Existing system does not support managerial decision-making.

09329802017 Yash Bindal

 8.No support in strategic competitive advantage: Existing system does not support strategic
competitive advantages.

Chapter 2

REQUIREMENT ANALYSIS
Before we begin a new system it is important to study the system that will be improved or replaced (if
there is one).We need to analyze how this system uses hardware, software, network and the people
resources to convert data resources, such as transaction data, into information products, such as reports
and displays. Thus we should document how the information system activities of input, processing, output,
storage and control are accomplished.

2.1 ANALYSIS STUDY

1. Open Communication Environment:

It provides a good way of communication between the user (customer) and the admin of the system. The potential
customer gets to see a wide variety of products available to him. He may order the products which he

09329802017 Yash Bindal

 desires to buy and also can ask queries which leads to an healthy communication between the user and the
manager.
2. Lower Installation Charges:
We neither require any high configuration systems for smooth running of server program, nor do we require any
high configuration systems for smooth running of a client program. This application is designed with an
ease to support any ordinary system having a internet connection. At the server the charges are only for
setting up the LAN connections but not the systems.
3. Secured and Reliable:
The messages that travel across the LAN are enclosed in the form of TCP packets which are a secured form of
data transfer that is most widely used across the globe. So the private sessions would be done in a secured
form without a third party interface.
4. Simple to use and Easy to Understand:
The coding of this application is a tedious job. But the client and server modules are enclosed in servlet and jsp
pages. The user only needs a web browser to start interpreting the coding done in these pages.
5. Platform Independent
Since the project is done completely in java, it also executes main properties of language. The given application
is platform independent. So the client systems may have vista, Linux, Mac or any other operating system,
but they can connect to server easily without any dependencies of OS.

2.2 Feasibility Study

All projects are feasible if they have unlimited resources and infinite time. But the development of
software is plagued by the scarcity of resources and difficult delivery rates. It is necessary and prudent to
evaluate the feasibility of a project at the earliest possible time. The three considerations are involved in
the feasibility analysis.

2.3 Technical Feasibility

Technical feasibility centers on the existing mobile system (hardware, software…etc) and to what extent it can
support the proposed addition if the budget is a serious constraint, then the project is judged not feasible. The
technical feasibilities are important role in my project because here I am using PHP & MySQL. It requires XAMPP
to develop this application. An easily available software and easy to use.

09329802017 Yash Bindal

2.4 Economical Feasibility
This procedure is to determine the benefits and savings that are expected from a candidate system and
compare with cost. If benefits outweigh cost then the decision is made to design and implement the system.
Otherwise further justification or alterations in proposed systems that have to be made if it is having a
change of being approved. This is an ongoing effort that improves any feasibility costs spent on this project
because here I am using open source environments.

2.5 Operational Feasibility

People are inherently resistant to change and mobiles have been known to facilitate change. There is no
need of technical background is required to work on the application. All the information needed can be
seen on just one click.

2.2 USER REQUIREMENTS

The system provides the user with ease of ordering books over the internet. The user merely require a web browser
to explore the system and start placing orders. The user might also give the feedback about the product. All this can
be done using an internet connection and a web browser installed in user’s system. The system specifications that
a user may want are as follows:

1. It should be easy to understand

2. Must be interactive
3. Should provide a good user interface
4. Security should be maintained
5. Redundancy must be controlled

Inquiry Form/Interviews
Q) What kind of system?

A) A fast and reliable system

Q) User satisfaction from the content?

The content is to be self explanatory and user could easily understand it

09329802017 Yash Bindal

Q) Data security?

Data should be in encrypted format so that no third party could access the user credentials.

Q) Using of system

A system that is easy to use and with less complications.

Q) What kind of interface?

A more user oriented interface that is basically designed for the users only

Q) Trustworthiness of the user credentials?

Since the user is providing of its credentials to the application so its rights to use needs to be of the user
i.e. without user permissions it cannot be exchanged or changed

2.3 Discussion with IT experts

Creating an IT project for a beginner can at times become a challenging task. So, the discussion with the
veterans in the field of IT becomes an important task which might lead to some great benefits for the
developer. Some IT developers might consider it as an time wasting process but, they would be missing
out on a very important lesson ignoring this step. The people who are in the IT field for a long time knows
the mindset of the user pretty well and might help in giving some important pointers which in turn would
help in improvement of the project. Following were the outcome of the discussion held with our IT experts:

1. Proper validations were proposed

2. User friendly template was taken
3. Security Checks were performed
4. More functionality was added

So, it was a very eventful and important step taken in the development of the project which leads to some
interesting improvements in the project.

2.4 Final Requirements

User Oriented: A system should be more user friendly not of the technical point of view

09329802017 Yash Bindal

Better GUI: All the elements used in the system should be of interactive in nature that is its look and feel
is not so boring that the user could get bored while using it.

Reliability: The system should be reliable and fast in processing

Data security: Access to the organizational data is not to be granted to any unknown person which is not
a part of the transaction

Confidentiality: Whatever the user is providing to the organization ,the user has the full rights to modify
it and it could be not be accessed/modified without users permission

Better Management of information: All the information should be managed that is the flow of the
information is to be in right track

Presentation: The content that is to be presented to the user is to be presented in such a way that is self
explanatory to the user and he/she is satisfied with the data.

09329802017 Yash Bindal

 Chapter 3

DESIGN OF THE SYSTEM

3. Software requirements

Platform Platform Independent

The Operating System Windows 7
Framework PHP, Apache Tomcat Server
Front-End Tool Google Chrome
Back-End Tool MySQL

3.1.1 Hardware Requirements

Processor Intel Pentium IV 2.9 GHz Other

RAM Minimum 2 GB

Graphics Integrated graphics card

Hard Disk Minimum 50 GB

3.2 System Requirements

To know the detailed system requirements an SRS has to be prepared. Software requirement specification
abbreviated as SRS is a means of translating the idea of files into a formal document. The main features
of SRS include:
● Establishing the basis for an agreement between the client and the developer.

09329802017 Yash Bindal

 ● Producing a reference for validation of the final product. SRS assist clients in determining if the
software meets the requirements.
Mainly there are six requirements which an SRS must satisfy.

(a) It should specify the external behavior.

(b) It should specify the constraints.

(c) It should be easy to change.

(d) It should be a reference tool.

(e) It should record throughout the lifecycle.

(f) It should have the capacity of expectation of an undesired event.

Usually we come across four types of requirement specification

(a) User Interface Requirements

(b) Database Requirements

(c) Functional Requirements

(d) Non-Functional Requirements

3.2.1 User Interface Requirements

The user of the proposed system requires that the developed software should be user friendly, have security
access, and ensure the privacy of the administrator and produce results in timely manner. The users are
not frequently exposed to the reservation system, so the system interface to the user must be simple and
understandable. The web pages must be user-friendly and must be in an easy-to-use style. The user must
be able to easily switch among various I/O screens. The product is well designed so that it can be used
easily by the users who are novices to the system.

3.2.2 Database Requirements

09329802017 Yash Bindal

The database should be designed in such a way that it enhances the efficient searching , reservation and
manipulation of all the information associated. For instance all general information regarding an item
attribute should be stored in a particular table.

The database should be organized in such a way that it helps in searching and reserving various essential
summaries needed for users.

3.2.3 Functional Requirements

The various functional requirements of the system can be summarized as:-

(a) A home page that is user friendly and ambiguous.

(b) It is easy to look for the desired information.

(c) User can easily do reservation.

3.2.4 Non-Functional Requirements

Non-functional requirements define the system properties and constraints that arise through user needs,
because of the budgeted constraints or organizational policies, or because of the need for interoperability
with other software or due to the external factors such as safety regulations privacy registrations and so
on.

Design Requirements

The main objectives of input design are:

(a) Controlling the amount of input

(b) Keeping the process simple.

(c) The best thing in the input design is to achieve all the objectives mentioned in the simplest manner
possible.

The main objectives of output design are:

(a) Identifying the specific outputs.

09329802017 Yash Bindal

(b) Creating reports for displaying and storing information.

The primary goal of the system analysis is to improve the efficiency of the existing system. For that the
study of specification of the requirements is very essential. For the development of the new system, a
preliminary survey of the existing system will be conducted. Investigation done whether the upgradation
of the system into an application program could solve the problems and eradicate the inefficiency of the
existing system

3.3 Detailed System Specification (Module Wise)

The proposed system consists of mainly 6 important modules and various other sub modules. The main 6
modules of the system are as follows

1 Create Account-this module is used by the customer to get himself/herself registered to the website.
The customer has to provide some basic information regarding him to get registered to the website. The
information to be provided by the customer for getting himself registered is: name, contact, address,
password and email. Once the user is registered he is ready to use the functionalities present in the website.

2 Login-Once a user has been registered to the website, he is free to use the services offered to him by
logging into his account using appropriate details. The proposed website accepts two kinds of logins which
are as follows:

User Login: it is the basic normal login for any customer of the website. The user enters his username
and password to login.

Admin Login: this is the login portal made especially for admin(s) of the website. It allows the admin to
gain access to privileged root user powers.

3 Feedback/Query: user can give their feedback or ask a query or suggestions which could help in overall
quality of the product.

4 Messages: user can send or/and receive messages to and from other users that can be thought of as a
chat messenger, as well as to the admin.

3.3 THE USE CASE APPROACH

A use case is a set of scenarios that describe an interaction between a user and a system.

09329802017 Yash Bindal

A use case diagram displays the relationship among actors and use cases. The two main components of a
use case diagram are use cases and actors.

USE CASE

Fig. 3.1 Actor and Usecase

An actor is represents a user or another system that will interact with the system you are modelling.

A use case is an external view of the system that represents some action the user might perform in order
to complete a task.

LOGIN
LOG IN

LOG OUT

BOOKS MANAGES

BOOKS
ADMIN
User CATEGORIES

Fig.3.2 Interaction between user and admin

09329802017 Yash Bindal

In The above diagram there are 2 actors or users who use the system. These two users are as follows:

1. User-The customer is allowed to login to the system, logout of it, add items to auction, bid for
the items added to the website to purchase and view the status of his bookings.

2. Admin-The admin can also login and logout of the system. Other than that the admin of the
system manages all the auctions and can cancel/finalize the item for the auction.

3.4 ER DIAGRAM
Entity – Relationship model (ER model) in software engineering is an abstract way to describe a database.
This article refers to the techniques proposed in Peter Chen's 1976 paper. However, variants of the idea
existed previously, and have been devised subsequently such as super type and subtype data entities and
commonality relationships.
ID
ADDS ITEMS

ADDS
SENDS & RECEIVES

SENDS

FEEDBACK MESSAGES

RECIEVES SENDS & RECEIVES MANAGE

09329802017 Yash Bindal

 ADMIN
NAME

PASSWOR
D

Fig 3.3 ER diagram

In The above diagram shows the entity relationship. An Entity Relationship Diagram (ERD) is a visual
representation of different data using conventions that describe how these data are related to each other.
For example, the elements writer, novel, and consumer may be described using ER diagram. In the
diagram, the elements inside rectangles are called entities while the items inside diamonds denote the
relationships between entities. This ER diagram tutorial for beginners covers most things related to ER
diagram

Chapter 4

IMPLEMENTATION AND CODING

USER TABLE

09329802017 Yash Bindal

 Fig. 4.1 User table

This fig shows the table which is said to be a User table. It contains the data about the members who are
user in the bookstore website. It contains eleven fields name ,email ,password.

CONTACT TABLE

09329802017 Yash Bindal

 Fig 4.2 Contact Table

This fig shows the table which is said to be a Contact table. It contains the data about all the messages
who are user in the auction website. It contains sender, email, message.. This table also contains
feedback those are send by the user and it is send to admin.

09329802017 Yash Bindal

4.1 OPERATING SYSTEM

Platform Independent: Since the project is done completely in java, it also executes main properties of
language. The chat application is platform independent. So the client systems may have vista, Linux, Mac
or any other operating system, but they can connect to server easily without any dependencies of OS.

4.2 Languages used

PHP

Chapter 5

09329802017 Yash Bindal

 TESTING & TEST RESULTS

5.1 SOFTWARE TESTING

Software testing is a critical element of software quality assurance and represents the ultimate review of
specification design and coding. Testing is an exposure of a system to trial input to see whether software
meets correct output. Testing cannot be determined whether software meets user’s needs, only whether it
appears to confirm to requirements. Testing can show that a system is free of errors, only that it contains
error. Testing finds errors, it does not correct errors. Software success is a quality product, on time and
within cost. Through testing can reveal critical mistakes. Testing should therefore,

Validate Performance

Detects Errors

Identify Inconsistencies

5.2 Test Objective

● There is strong evidence that effective requirement management leads to overall project cost
savings. The three primary reasons for this are,
● Requirement errors typically cost well over 10 times more to repair than other errors.
● Requirement errors typically comprise over 40% of all errors in a software project.
● Small reduction in the number of requirement errors pays big dividend in avoided rework costs
and schedule delays.
● System are not designed as entire systems nor are they tested as single systems the analyst must
perform both unit and system testing. For this different level testing are use:

5.2.1 Unit Testing

In unit testing Module is tested separately and the programmer simultaneously along with the coding of
the module performs it.

In unit testing the analyst tests the programs making up a system. For this reason, unit testing is sometime
called program testing. Unit testing gives stress on modules independently of one another, to find errors.

09329802017 Yash Bindal

This helps the tester in detecting errors in coding and logic that are contained within that module alone.
The errors resulting from the interaction between modules are initially avoided.

Unit testing can be performed from the bottom up, Starting with smallest and lowest-level modules and
proceeding one at a time., for each module in Bottom-up testing a short program is used to execute the
module and provides the needed data, so that the module is asked to perform the way it will when
embedded within the larger system.

5.2.2 System Testing

This is performed after the system is put together. The system is tested against the system requirement to
check if all the requirements are met and if the system performs of specify by the requirements.

Testing is an important function to the success of the system. System testing makes a logical assumption
that if all the parts of the system are correct, the goal will be successfully activated. Another reason for
system testing is its utility as a user-oriented vehicle before implementation.

The function of testing is to detect the defects in the Software. The main goal testing is to uncover
requirement, design and coding errors in the programs. The types of testing are discussed below:

5.2.3 MODULE TESTING

Module tests are typically dynamic white-box tests. This requires the execution of the software or parts of
the software. The software can be executed in the target system, an emulator, simulator or any other
suitable test environment.
The focus of the tests is:
● Set up of regression tests. This means the test environment once set up for a function can be re-
used to check its performance e.g. after maintenance.
● Coverage of the relevant state of the art test methods like equivalence class building, boundary
value analysis and condition coverage are used.

5.2.3 INTEGRATION TESTING

“If they all work individually, they should work when we put them together.” The problem of course is
“putting them together “. This can be done in two ways:

09329802017 Yash Bindal

 1. Top down integration: Modules are integrated by moving downwards through the control
hierarchy, beginning with main control module are incorporated into the structure in either a depth
first or breadth first manner.
2. Bottom up integration: It begins with construction and testing with atomic modules i.e. modules
at the lowest level of the program structure. Because modules are integrated from the bottom up,
processing required for the modules subordinate to a given level is always available and the need
of stubs is eliminated.

5.2.4 BLACK-BOX TESTING

Black-box testing is a method of software testing that tests the functionality of an application as opposed
to its internal structures or workings.
The system is tested just to assure whether it is meeting all the expectations or requirements from it, tester
is not concerned with the internal logic of the module or system to be tested. Some inputs are given to
system and it is observed whether the system is working as per the client’s requirements or not or
according to the requirements specified in SRS document. Specific knowledge of the application's
code/internal structure and programming knowledge in general is not required.
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. The test designer
selects valid and invalid inputs and determines the correct output. There is no knowledge of the test object's
internal structure. This method of test can be applied to all levels of software
testing: unit, integration, functional, system and acceptance. It typically comprises most if not all testing
at higher levels, but can also dominate unit testing as well. Black box testing or functional testing is used
to check that the outputs of a program, given certain inputs, conform to the functional specification of the
program. The term black box indicates that the tester does not examine the internal implementation of the
program being executed

5.2.5 WHITE-BOX TESTING

A software testing technique where by explicit knowledge of the internal workings of the item being tested
are used to select the test data. Unlike black box testing, white box testing uses specific knowledge of
programming code to examine outputs. The test is accurate only if the tester knows what the program is
supposed to do. He or she can then see if the program diverges from its intended goal. White box testing
does not account for errors caused by omission, and all visible code must also be readable.

09329802017 Yash Bindal

Contrary to black-box testing, software is viewed as a white-box, or glass-box in white-box testing, as the
structure and flow of the software under test are visible to the tester. Testing plans are made according to
the details of the software implementation, such as programming language, logic, and styles. Test cases
are derived from the program structure. White-box testing is also called glass-box testing, logic-driven
testing or design-based testing. There are many techniques available in white-box testing, because the
problem of intractability is eased by specific knowledge and attention on the structure of the software
under test.

5.2.6 VALIDATION TESTING

TEST CASES
Field Value Valid/Invalid Result
Contact Null Invalid Fill all the fields
Confirm Wrong Invalid Passwords do not match
password
Password Wrong Invalid Please enter a valid id and
password
Name Null Invalid Fill all the fields
OUTPUTS
Contact=Null

09329802017 Yash Bindal

 Fig. 5.1 Registration Page

This fig. shows the validation of the mandatory fields. All the fields are mandatory to be filled, this the
validation for the fields when a user is registering himself on this particular website.

Password=Do not match

Fig. 5.2 Home page

This fig. shows the validation of password do not match. This means if the password is not matched with
the previous one then it will produce this error. A user must match ot fulfilled this validation to login
himself successfully.
Username/Password=wrong

09329802017 Yash Bindal

 Fig. 5.3 Home Page

This fig. shows the validation of not fulfilling the right id and password. A user must entered the right id
and password.

09329802017 Yash Bindal

 Name=Null

Fig. 4.5 Registration page

This fig. shows the validation of the mandatory fields. All the fields are mandatory to be filled, this the
validation for the fields when a user is registering himself on this particular website.

Chapter 6

CONCLUSION

6.1CONCLUSION

09329802017 Yash Bindal

Now a day’s there is a big demand of different types of applications, which is because IT has become the
main part of our New World. There is a big need of different applications. People want application for
every specific task from work to entertainment. We have developed the Java application “GO Grab it”
which works easy on any given web browser.

The application has been tested on platform of java and found to be working as per the given criteria. It
can be safely concluded that the application possesses a highly efficient UI system and is working properly
and meeting to all the requirements of the user. The application gives the user maximum flexibility in the
types of touch and other device movements.

6.2 FUTURE SCOPE

Every project whether large or small has some limitations no matter however diligently developed. In
some cases limitations is small while in other cases they may be broad also. The new system has got some
limitations. Major areas where modifications can be done are as follows:

● Our system is not online so further it can be improved.

● The security is limited so some additional arrangement could be made to provide more security to
the system.
● There is no provision of complain handling so further it can be added.

BIBLOGRAPHY
● http://www.w3schools.com
● http:// www .stackoverflow.com
● http://wikipedia.com

09329802017 Yash Bindal

● Java The Complete Reference, by Herbert Schildt

09329802017 Yash Bindal