A Project Report On

A BOOK ZONE
In partial fulfillment for the award of the

degree Of

BACHELOR OF ENGINEERING

In

COMPUTER ENGINEERING

Submitted By

NEHA JHA
(150580107003)

MITTAL CHAUDHARI
(150580107001)

Guided By
Mr. BHAVESH JAIN
[Assistant Professor]

DEPARTMENT OF COMPUTER ENGINEERING

INDRASHIL INSTITUTE OF SCIENCE AND TECHNOLOGY
RAJPUR, KADI
April 2019
 INDRASHIL INSTITUTE OF SCIENCE AND
TECHNOLOGY
(Affiliated to Gujarat Technological University)
Rajpur,Kadi, At &Po:Rajpur, Ta: Kadi, Dist:Mehsana
Website: www.iist.edu.in

CERTIFICATE

This is to certify that the work of User Define Project entitled “A BOOK ZONE” has been
carried out by Neha Jha (150580107003) under my guidance in partial fulfillment for the
degree of Bachelor of Engineering in Computer Engineering 8th Semester at the Department
of Computer Engineering, Indrashil Institute of Science & Technology, Rajpur, Kadi,
Gujarat, during the academic year 2018-19 and her work is satisfactory. This student has
successfully completed User Defined Project under my guidance.

Internal Guide: Head of Department:

Mr. Bhavesh Jain Dr. Prof. Ramesh Prajapati
Assistant Professor, Assistant Professor,
Computer Engineering Department Computer Engineering Department
 INDRASHIL INSTITUTE OF SCIENCE AND
TECHNOLOGY
(Affiliated to Gujarat Technological University)
Rajpur,Kadi, At &Po:Rajpur, Ta: Kadi, Dist:Mehsana
Website: www.iist.edu.in

CERTIFICATE

This is to certify that the work of User Define Project entitled “A BOOK ZONE” has been
carried out by Mittal Chaudhari (150580107001) under my guidance in partial fulfillment
for the degree of Bachelor of Engineering in Computer Engineering 8th Semester at
the Department of Computer Engineering, Indrashil Institute of Science & Technology,
Rajpur, Kadi, Gujarat, during the academic year 2018-19 and her work is satisfactory. This
student has successfully completed User Defined Project under my guidance.

Internal Guide: Head of Department:

Mr. Bhavesh Jain Dr. Prof. Ramesh Prajapati
Assistant Professor, Assistant Professor,
Computer Engineering Department Computer Engineering Department
 GUJARAT TECHNOLOGICAL UNIVERSITY
CERTIFICATE FOR COMPLETION OF ALL ACTIVITIES AT ONLINE PROJECT PORTAL
B.E. SEMESTER VIII, ACADEMIC YEAR 2018-2019
Date of certificate generation : 02 April 2019 (06:15:53)

This is to certify that, Jha Neha Manojkumar ( Enrolment Number -

150580107003 ) working on project entitled with A BOOKZONE from
Computer Engineering department of FACULTY OF ENGINEERING,
SHREE SARASWATI EDU. SANSTHAN GROUP OF
INSTITUTIONS,RAJPUR, KADI had submitted following details at online
project portal.

Periodic Progress Reports (PPR) Completed

Business Model Canvas (Image) Completed

Business Model Canvas (Report) Completed

Patent Drafting Exercise (PDE) Completed

Final Plagiarism Report Completed

Final Project Report Completed

Name of Student : Jha Neha Manojkumar Name of Guide : Mr. BHAVESH M JAIN

Signature of Student : _____________ *Signature of Guide : ________________

Disclaimer :
This is a computer generated copy and does not indicate that your data has been evaluated. This is the receipt that GTU
has received a copy of the data that you have uploaded and submitted as your project work.

*Guide has to sign the certificate, Only if all above activities has been Completed.
 GUJARAT TECHNOLOGICAL UNIVERSITY
CERTIFICATE FOR COMPLETION OF ALL ACTIVITIES AT ONLINE PROJECT PORTAL
B.E. SEMESTER VIII, ACADEMIC YEAR 2018-2019
Date of certificate generation : 02 April 2019 (06:15:18)

This is to certify that, Chaudhari Mittalben Jayantibhai ( Enrolment Number -

150580107001 ) working on project entitled with A BOOKZONE from
Computer Engineering department of FACULTY OF ENGINEERING,
SHREE SARASWATI EDU. SANSTHAN GROUP OF
INSTITUTIONS,RAJPUR, KADI had submitted following details at online
project portal.

Periodic Progress Reports (PPR) Completed

Business Model Canvas (Image) Completed

Business Model Canvas (Report) Completed

Patent Drafting Exercise (PDE) Completed

Final Plagiarism Report Completed

Final Project Report Completed

Name of Student : Chaudhari Mittalben Name of Guide : Mr. BHAVESH M JAIN

Jayantibhai

Signature of Student : _____________ *Signature of Guide : ________________

Disclaimer :
This is a computer generated copy and does not indicate that your data has been evaluated. This is the receipt that GTU
has received a copy of the data that you have uploaded and submitted as your project work.

*Guide has to sign the certificate, Only if all above activities has been Completed.
 ACKNOWLEDGEMENT

No volume of words are sufficient to express gratitude towards my internal guide, Prof. Bhavesh
Jain, Computer Engineering Department, IIST, Kadi, who has been very considerate and
cooperative and guided whole-heartedly. He has been a continuous source of motivation,
encouragement and kind support for preparing this project report. He shared with me all the
innovative ideas to do the research in a right direction and in an organized manner.

We are also thankful to Dr. Prof. Ramesh Prajapati, Head of Computer Engineering Department
for providing all the facilities and harmonious environment for learning. We would also like to
thank all the respected faculty members for their invaluable help and cooperation during Project
Report.

I
 ABSTRACT

This project is to create that type of book zone in which students or anyone who have old book,
which is no more in use, then rather giving it to the waste, one can click photo of that book and
can sell any type of book in our website. One can sell story books, comics, novels, academic
books, competitive books and get money.

One has to first register them on this website and login for selling or buying books. One can
search boos by book name, author name, nearby area, edition etc. Using nearby area one can get
the book from the nearest place rather than going to the long distance area. If someone has not
put any book which one desire to by than our comparison option will help you to find the
cheapest price books from the 10 best websites of online book sharing. User can do both online
as well as cash on delivery payment.

There will be a chat portal as well. If one does not want to buy any book then he/she can view
the website. There will be feedback also. So, if anyone has suggestions or complaints regarding
to our website then one can write to us.

II
 List of Figures

Figure Number Description Page No

Figure 2.2.1 Spiral Model 11
Figure 3.1 E-R Diagram 14
Figure 3.2.1 Level-0 Data Flow Diagram 15
Figure 3.2.2 Level-1 Data Flow Diagram 16
Figure 3.2.3 Level-2 Data Flow Diagram 17
Figure 3.3.1 Use case Diagram 18
Figure 3.4.1 Sequence Diagram 19
Figure 3.5.1 Activity Diagram For Admin 20
Figure 3.5.2 Activity Diagram For User 21
Figure 3.6.1 Class Diagram 22
Figure 4.1.1 System Flow Diagram 23
Figure 4.1.2 System Flow Chart 24

III
 List of Table

Table Number Description Page No

Table 4.1 Role Table 25
Table 4.2 Admin Table 25
Table 4.3 Advertise Table 26
Table 4.4 User Table 26
Table 4.5 Category Table 26
Table 4.6 Sub Category Table 27
Table 4.7 Company Information Table 27
Table 4.8 Query Table 28
Table 4.9 Book Table 28
Table 4.10 Brand Table 29
Table 4.11 Log Table 29
Table 4.12 Subject Wise Table 30

IV
 Symbols and Abbreviations
For E-R (Entity Relationship) Diagram & Class Diagram:

Symbol Description

Entity

Operation

Attribute

Relationship between attribute and operation

Class name and attribute

For DFD (Data Flow Diagram):

Symbol Description

System name

Data store

Data flow

Entity

Operation

V
For Use case Diagram:

Symbol Description

Attribute

Relationship

Actor

For Activity Diagram:

Symbol Description

Start point

End point

Condition

flow

Operation

Fork

VI
For Sequence Diagram:

Symbol Description

Object

Transient object

Send request
________ Accept request

Abbreviations:

Name Full Form

ER Entity Relationship
DFD Data Flow Diagram
SDLC Software Development Life Cycle
R.T.I. Right To Information

VII
 Contents
Acknowledgement I
Abstract II
List of Figures III
List of Table IV
Symbols And Abbreviations V
Contents VIII
Chapter 1 Introduction 1
1.1 Project Detail 1
1.1.1 Project Profile 1
1.1.2 Project Definition 1
1.2 Purpose 1
1.3 Scope 2
1.4 Objective 2
1.5 Technology and Literature Review 2
Chapter 2 About The System 4
2.1 System Requirement Specification 4
2.2 Feasibility Study 4
2.3 Project Planning 5
2.3.1 Project Development Approach 5
Chapter 3 Analysis 8
3.1 E-R Diagram 8
3.2 Data Flow Diagram 9
3.3 Use Case Diagram 12
3.4 Sequence Diagram 13
3.5 Activity Diagram 14
3.6 Class Diagram 16
Chapter 4 Design 17
4.1 System Flow Diagram 17
4.2 Data Dictionary 19
4.3 User Interface 30
Chapter 5 Implementation 34
5.1 Implementation Environment 34
5.2 Program/Module Specification 35
5.3 Security Features 36
5.4 Coding Standards 36
Chapter 6 Testing 38
6.1 Testing Plan 39
6.2 Testing Strategy 41
6.3 Testing Method 40
Conclusion & References 47

VIII
IX
A BOOK ZONE INTRODUCTION

Chapter 1: Introduction
1.1 Project Details

1.1.1 Project Profile

Title A BOOK ZONE

Project Type UDP
Team Size 02
Neha Jha (150580107003)
Team Member
Mittal Chaudhari (150580107001)
Front End Java
Back End MySQL
Internal Guide Mr. Bhavesh Jain
Operating System Windows 7

1.1.2 Project Definition:

To Buy and Sell any type of books online which can save time and money both rather
Then going to the book store and find the books.

1.2 Purpose
A Book Zone is an initiative called online buying and selling books system. The main goal of
this website is that there are so many students who are belonging from the rural areas at which
they cannot find their academics books and they have to go the city area for buying the books.
So, our website will solve this problem and students can buy or sell book on our website, can
compare price, search different types of books.

This website provides the facilities to select category, tracking of order, give feedback, track
orders can pay online as well as offline too.

1
A BOOK ZONE INTRODUCTION

1.3 Scope
 Delivered on schedule within budget.
 Be easy to use.
 Have a good user interface.
 It satisfies all the user requirements.
 It will save time as well as money.

1.4 Objectives
The main objective of the project on A Book Zone is to manage the details of Books, Stock, Customer,
Order, and Payment. It manages all the information about Books, Bill, and Payment. The project is totally
built at administrative end and thus only the administrator is guaranteed the access. The purpose of the
project is to build a website program to reduce the manual work for managing the books, stock, and bill.
Customer. It tracks all the details about the Customer, Order and Payment.

1.5 Technology and Literature Review

Technology:
Project Title A BOOK ZONE
Front End JAVA
Back End MySQL
Operation System Windows 7,8,10
Project Duration 1 year
Supporting Tools Net beans IDE

2
 A BOOK ZONE INTRODUCTION

Literature Review:

Application Important
S.No Offered By Updated Problems
Title Significance
In this website In this website user can
India Book India
1 July 2018 user can view all only buy books they can’t
Store bookstore
type of books. sell their books.
In this website
In this website user can only
user can see all
Books Shubham September buy books, it not provide
2 information which
Wagon Jain 2018 user ratings and
ever they want to
comparison of prices.
buy.
In this website use
Online Online February can get books in In this website user can’t get
3
Book Store Bookstore 2018 different all academic books.
languages.

3
A BOOK ZONE ABOUT THE SYSTEM

Chapter 2: About the System

2.1 System Requirement Specification:
2.1.1 Hardware Requirements:

 Processor : 250 MHz

 Hard disk : 256 GB Min
 RAM : 2 GB Min
 Others : If any Applicable

2.1.2 Software Requirements:

 Frontend : Java
 Backend : MySQL

2.2 Feasibility Study:

Feasibility study involves research relating to the different aspects that go into
developing software. It begins with marketing analysis in terms of the need to develop
the software, the industry or organization for whom the system is developed, the cost
that will go into the software development process and will the product be welcomed in
the market and why.

This type of the study includes three more aspects like as follows:

 Technical Feasibility
 Time scheduled Feasibility
 Operational Feasibility

Technical Feasibility:

Technical Feasibility deals with finding out whether technology to implement the
system is currently available or the resources currently being used should be upgraded.
A BOOK ZONE technically feasible if the system meets the hardware and software
requirement specified in the “System Requirements”.

10
A BOOK ZONE ABOUT THE SYSTEM

Time Scheduled Feasibility:

Projects are initiated with specific deadline. We need to evaluate whether the deadline
are mandatory or desirable. Time is one of the critical factors in the development of any
system but this kind of feasibility is hardly perfect in any system.

We have been asked to complete the project within the working days of the organization
having period of 10 months approximation. So we have managed to complete the
project Documentation and analysis part before given deadline. In the project planning
section we elaborated our ideas to develop the system within the given period. Hence, it
is feasible to develop a system in predetermined time interval.

Operational Feasibility:

Any project proposed can be beneficial only if it satisfies the organization requirement.

2.3 Project Planning

2.2.1 Project Development Approach:
We are using following Spiral Model in my project.

Diagram of Spiral model:

Fig 2.2.1

11
A BOOK ZONE ABOUT THE SYSTEM

The spiral model is similar to the incremental model, with more emphasis placed on risk
analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and
Evaluation. A software project repeatedly passes through these phases in iterations
(called Spirals in this model). The baseline spiral, starting in the planning phase,
requirements is gathered and risk is assessed. Each subsequent spiral builds on the
baseline spiral.

Requirements are gathered during the planning phase. In the risk analysis phase, a
process is undertaken to identify risk and alternate solutions. A prototype is produced at
the end of the risk analysis phase. Software is produced in the engineering phase, along
with testing at the end of the phase. The evaluation phase allows the customer to
evaluate the output of the project to date before the project continues to the next spiral.

This model tries to combine the advantages of both the waterfall model and the rapid
prototyping model. Note the way in which there is a continual process of re-evaluation.

 Advantages of Spiral Model:

 High amount of risk analysis hence, avoidance of Risk is enhanced.

 Good for large and mission-critical projects.

 Strong approval and documentation control.

 Additional Functionality can be added at a later date.

 Software is produced early in the software lifecycle.

 Disadvantages of Spiral Model:

 Can be a costly model to use.

 Risk analysis requires highly specific expertise.

 Project’s success is highly dependent on the risk analysis phase.

 Doesn’t work well for smaller projects.

 When to Use Spiral Model:

 When costs and risk evaluation is important.

 For medium to high-risk projects.

 Long-term project commitment unwise because of potential changes to

12
A BOOK ZONE ABOUT THE SYSTEM

economic priorities.

 Users are unsure of their needs.

 Requirements are complex.

 New product line.

 Significant changes are expected (research and exploration).

13
A BOOK ZONE ANALYSIS

Chapter 3: Analysis
3.1 E-R Diagram:
Data models are tools used in analysis to describe the data requirements and
assumptions in the system from a top-down perspective. They also set the stage for the
design of databases later on in the SDLC.

There are three basic elements in ER models:-

 Entities are the "things" about which we seek information.

 Attributes are the data we collect about the entities.

 Relationships provide the structure needed to draw information from multiple

entities.



 

Fig 3.1 E-R Diagram

14
A BOOK ZONE ANALYSIS

3.2 Data Flow Diagram:

Data flow diagram (DFD) was introduced by de Marco (1978) and GaneSarson (1979)
is an important tool used by system analyst.
A Data Flow Diagram models a System by using external entities from which A Data
Flows to a process, which transform the data and creates output data Flow Which goes
to other processes or external entity or data store.
A Stored data may also flow to processes as input. The Main merit of DFD is that it can
provide an overview of what data system would process. What transactions of data are
done? What data are store. Which stored data are used? Where the result flows?
The graphical representation of the system makes it good communication tool between a
user and system analyst on the one hand and a system Designer on the other.
In practice, DFD are used for representing logical processing of data. It is however
useful to evolve a logical DFD after first developing a physical DFD which shoes a
person’s performing various operations performing operations.

15
A BOOK ZONE ANALYSIS

3.2.1 0-Level Data Flow Diagram:

Fig 3.2.1 0-Level DFD

3.2.2 1-Level Data Flow Diagram:

Fig 3.2.2 1 LEVEL DFD

16
A BOOK ZONE ANALYSIS

3.2.3 2-Level Data Flow Diagram:

Fig 3.2.3 2 LEVEL DFD

3.3 Use Case Diagram:

Actors:
An Actor is a role that a user plays with respect to the system. There is only one actor in
above figure i.e. user. There can be many users in the given system, but as far as the
system is concerned, they all play the same role. Actors carry out use cases. A single
actor may perform many use cases; conversely, a use case may have several actors
performing it.

17
A BOOK ZONE ANALYSIS

Use Case Relationships:

In addition to the links among actors and use cases, we can show several kinds of
relationships between use cases.
The include relationship occurs when you have a chunk of behavior that is similar
across more than one use case and you don’t want to keep copying the description of
that behavior.
You can also use case generalization when you have one use case that is similar to
another use case but does a bit more. In effect, this gives us another way of capturing
alternative scenarios.
A third relationship, which we have shown is called extend. Essentially, this is similar to
generalization but with more rules to it.

3.3.1 Use case Diagram for User:

Fig 3.3.1 Use case Diagram for User

18
A BOOK ZONE ANALYSIS

3.4 Sequence Diagram:

A Sequence diagram is an interaction diagram that shows how processes operate with
one another and in what order. It is constructing of a Message Sequence Chart.

A sequence diagram shows object interactions arranged in time sequence.

Sequence diagram is the most common kind of interaction diagram, which focuses on
the message interchange between a numbers of lifelines.

3.4.1 Sequence Diagram for Admin:

3.4.1 Sequence Diagram for Admin

3.5 Activity Diagram:

An Activity diagram is another important diagram in UML to describe dynamic aspects
of the system. Activity diagram is basically a flow chart to represent the flow from one
activity to another activity.

19
A BOOK ZONE ANALYSIS

The Activity can be described as an operation of the system so the control flow is drawn
from one operation to another. Activity diagrams are graphical representations of
workflows of stepwise activities and actions with support for choice.

3.5.1 Activity Diagram for Admin:

3.5.1 Activity Diagram for Admin

20
A BOOK ZONE ANALYSIS

3.5.2 Activity Diagram for User:

3.5.2 Activity Diagram for User

3.6 Class Diagram:

A class diagram is a type of static structure diagram that describes the structure of a
system by showing the system’s classes, their attributes, operations (or methods), and
the relationship among object.

Class diagram is not only used for visualizing, describing and documenting different
aspects of a system but also for constructing executable code of the software
application.

21
A BOOK ZONE ANALYSIS

3.6.1 Class Diagram:

3.6.1 Class Diagram

22
A BOOK ZONE DESIGN

Chapter 4: Design
4.1.1 System Flow Diagram

Fig 4.1.1 System Flow Diagram

23
A BOOK ZONE DESIGN

Fig 4.1.2 System Flow Chart

24
A BOOK ZONE DESIGN

4.2.1 Data Dictionary:

A database system provides two types of languages: - One to specify the database
schema and the other to express database queries a duplets.

A database schema is specified by set of definitions expressed by Data Definition

Language (DDL). The result of compilation of DDL statement is set of tables that are
stored in a special file called data-dictionary or data -directory.

A data dictionary is a file that contains metadata – that is data about data. This file
consulted before actual data are read or modified in database system.

Table 4.1: Role Table

Column Name Data Type Size Constraints

Role_id int 11 Primary Key
Role_type varchar 30 Unique Key
Active_flag varchar 1 Not Null
Created_date datetime Not Null
Updated_date datetime Not Null
Admin_id int 11 Foreign Key

Table 4.2: Admin Table

Column Name Data Type Size Constraints

Admin_id int 11 Primary Key
Admin_name varchar 50 Not Null
Admin_Email varchar 50 Unique
Admin_Mobile bigint 10 Unique
Admin_Password varchar 16 Not Null
Created_date datetime Not Null
Updated_date datetime
Status varchar 1 Not Null
Active_Flag varchar 1 Not Null
Foreign Key
Role_id int 11 (Reference From
Admin_Tbl)

25
A BOOK ZONE DESIGN

Table 4.3: Advertise Table

Column Name Data Type Size Constraints

Advertise_id int 11 Primary Key
Company_name varchar 60 Not Null
Advertise_image text Not Null
Advertise_url text Not Null
Created_date datetime Not Null
Starting_date datetime Not Null
Ending_date datetime Not Null

Table 4.4: User Table

Column Name Data Type Size Constraints

User_id int 11 Primary Key
User_name varchar 50 Not Null
User_email varchar 50 Unique
User_mobile varchar 13 Unique
User_password varchar 16 Not Null
Active_flag varchar 1 Not Null
Status varchar 1 Not Null
Registration_date datetime 11 Not Null
Updated_date datetime Not Null
Foreign Key
Role_id int (reference from
role_tbl)

Table 4.5: Category Table

Column Name Data Type Size Constraints

Category_id int 11 Primary Key
Category_name varchar 30 Unique
Active_flag varchar y

26
A BOOK ZONE DESIGN

Table 4.6: Sub-Category Table

Column Name Data Type Size Constraints

Sub_Category_id int 11 Primary Key
Sub_Category_name varchar 30 Unique
Active_flag varchar 1
Foreign Key
Category_id int 11 (reference from
category_tbl)

Table 4.7: Company_Info Table

Column Name Data Type Size Constraints

Company_id int 11 Primary Key
Company_name varchar 50 Not Null
Logo text Not Null
Address text Not Null
Contact_info_one varchar 13
Contact_info_two varchar 13
Active_flag varchar 1 Not Null
Url_one text
Url_two text
Url_three text
Foreign Key
Admin_id int 11 (Reference From
Admin_Tbl)

27
A BOOK ZONE DESIGN

Table 4.8: Query Table

Column Name Data Type Size Constraints

Query_id int 11 Primary Key
Query_title varchar 50 Not Null
Query text Not Null
Answer text
Name varchar 50 Not Null
Email varchar 50 Not Null
Mobile varchar 13 Not Null
Status varchar 1 Not Null
Created_date datetime Not Null
Updated_date datetime
Foreign Key
(Reference From
Admin_id int 11
Admin_Tbl
)Null Allow

Table 4.9: Book Table

Column Name Data Type Size Constraints

Book_id int 11 Primary Key
Book_name varchar 50 Unique
Book_serial_no varchar 10 Unique
Book_description text
Foreign Key
Subject_wise_id int 11 (Reference From
Subject_Wise_Id)
Foreign Key
Brand_id int 11 (Reference From
Brand_Tbl )
Book_id int 11 Unique

28
A BOOK ZONE DESIGN

Table 4.10: Brand Table

Column Name Data Type Size Constraints

Brand_id int 11 Primary Key
Brand_name varchar 50 Unique
Brand_Active_flag varchar 1 Not Null
Brand_Created_date datetime Not Null
Brand_Updated_date datetime Null Allow
Foreign Key
Created_Admin_id int 11 (Reference From
Admin_Tbl )
Foreign Key
(Reference From
Updated_Admin_id int 11
Admin_Tbl
)Null Allow

Table 4.11: Log-in Table

Column Name Data Type Size Constraints

Log_id int 11 Primary Key
User_Agent text Not Null
Ip_Address varchar 15 Not Null
Operating_System varchar 10 Not Null
Mac_Address varchar 17 Not Null
Login_Time datetime Not Null
Logout_Time datetime Not Null
Foreign Key
(Reference From
User_id int 11
User_Tbl) Null
Allow
Foreign Key
(Reference From
Admin_id int 11
Admin_Tbl
)Null Allow

29
A BOOK ZONE DESIGN

Table 4.12: Subject-Wise Table

Column Name Data Type Size Constraints

Subject_Wise_id int 11 Primary Key
Subject_Name varchar 30 Unique
Subject_Active_Flag varchar 1 Not Null
Created_Date datetime Not Null
Updated_Date datetime Null Allow
Foreign Key
Sub_Category_id int 11 (Reference From
Subcategory_Tbl)
Foreign Key
Created_Admin_id int 11 (Reference From
Admin_Tbl )
Foreign Key
Updated_Admin_id int 11 (Reference From
Admin_Tbl )

4.3 User Interface:

Home Registration Page

30
A BOOK ZONE DESIGN

Profile Submit Ad

Book Advertisement Footer

31
A BOOK ZONE DESIGN

Advertisement 1 Advertisement 2

Advertisement 3 Advertisement 4

32
A BOOK ZONE DESIGN

Added Posts List of Ads

33
A BOOK ZONE IMPLEMENTATION

Chapter 5: Implementation
5.1 Implementation Environment:
Java is a set of computer software and specifications developed by James Gosling at Sun
Microsystems, which was later acquired by the Oracle Corporation, that provides a system
for developing application software and deploying it in a cross-platform computing
environment. Java is used in a wide variety of computing platforms from embedded devices
and mobile phones to enterprise servers and supercomputers. Java applets, which are less
common than standalone Java applications, were commonly run in secure, sandboxed
environments to provide many features of native applications through being embedded in
HTML pages. It's still possible to run Java in web browsers after most of them having
dropped support for Java's VM.

5.1.1 Program/Module Specification:

Various functional modules that can be implemented by the project will be –

 Login Module
 Registration Module
 Submit Ads
 Advance Search
 Recommended Ads
 Chat Portal

5.1.2 Login Module:

Users can enter their username and password and if it is correct user can enter in the
website and use it.
5.1.3 Registration Module:

User can create profile by entering their personal and professional detail in the
registration page and become a registered user. Registered user can use all the
functionality of their part.

5.1.4 Submit Ads:

User can submit ads of any books in different categories for selling with full details
& description of that book with desired price.

34
A BOOK ZONE IMPLEMENTATION

5.1.5 Advance Search:

User can search books by book name, author name, nearby area, price range, and
different categories.
5.1.6 Recommended Ads:

By recent searches of books by any user they can see recommended books so they
easily find the books they want.
5.1.7 Chat Portal:

User can do chat with buyer and seller according to books selling or buying and they
get necessary information to get books.

5.2 Security Features:

Security-neutral code does nothing explicit with the security system. It runs with whatever
permissions it receives. Although applications that fail to catch security exceptions
associated with protected operations (such as using files, networking, and so on) can result
in an unhandled exception, security-neutral code still takes advantage of the Java security
technologies.
A security-neutral library has special characteristics that you should understand. Suppose
your library provides API elements that use files or call unmanaged code; if your code does
not have the corresponding permission, it will not run as described. However, even if the
code has the permission, any application code that calls it must have the same permission in
order to work. If the calling code does not have the right permission, a Security Exception
appears as a result of the code access security stack walk.
A security-neutral library has special characteristics that you should understand. Suppose
your library provides API elements that use files or call unmanaged code; if your code does
not have the corresponding permission, it will not run as described. However, even if the
code has the permission, any application code that calls it must have the same permission in
order to work. If the calling code does not have the right permission, a Security Exception
appears as a result of the code access security stack walk.

35
A BOOK ZONE IMPLEMENTATION

5.2.1 Application Code That Is Not a Reusable Component:

If your code is part of an application that will not be called by other code, security is simple
and special coding might not be required. However, remember that malicious code can call
your code. While code access security might stop malicious code from accessing resources,
such code could still read values of your fields or properties that might contain sensitive
information.

Additionally, if your code accepts user input from the Internet or other unreliable sources,
you must be careful about malicious input.

5.2.2 Managed Wrapper to Native Code Implementation:

Typically in this scenario, some useful functionality is implemented in native code that you
want to make available to managed code. Managed wrappers are easy to write using either
platform invokes or COM interrupt. However, if you do this, callers of your wrappers must
have unmanaged code rights in order to succeed. Under default policy, this means that code
downloaded from an intranet or the Internet will not work with the wrappers.

Instead of giving all applications that use these wrappers unmanaged code rights, it is better
to give these rights only to the wrapper code. If the underlying functionality exposes no
resources and the implementation is likewise safe, the wrapper only needs to assert its rights,
which enables any code to call through it. When resources are involved, security coding
should be the same as the library code case described in the next section. Because the
wrapper is potentially exposing callers to these resources, careful verification of the safety
of the native code is necessary and is the wrapper’s responsibility.

5.2.3 Library Code That Exposes Protected Resources:

This is the most powerful and hence potentially dangerous (if done incorrectly) approach for
security coding: Your library serves as an interface for other code to access certain
resources that are not otherwise available, just as the classes of the .NET Framework
enforce permissions for the resources they use. Wherever you expose a resource, your code
must first demand the permission appropriate to the resource (that is, it must perform a
security check) and then typically assert its rights to perform the actual operation.

36
A BOOK ZONE IMPLEMENTATION

5.3 Coding Standards:

5.3.1 Purpose of Coding Standards and Best Practices:
Best practices are a set of informal rules that the software development community has
learned over time to improve the quality of applications and simplify their maintenance.
They can be broken into many levels based on the coding language, the platform, the target
environment and so forth. Using best practices for a given situation greatly reduces the
probability of introducing errors into your applications, regardless of which software
development model is being used to create that application. There are coding standards that
originated from the intensive study of industry experts who analyzed how bugs were
generated when code was written and correlated these bugs to specific coding practices.

37
A BOOK ZONE TESTING

Chapter 6: Testing
6.1 Testing Plan:

Testing is the process carried out on software to detect the differences between its behavior and
the desired behavior as stipulated by the requirements specifications. Testing is advantageous in
several ways. Firstly, the defects found help in the process of making the software reliable.

Secondly, even if the defects found are not corrected, testing gives an idea as to how reliable
the software is. Thirdly, over time, the record of defects found reveals the most common kinds
of defects, which can be used for developing appropriate preventive measures such as training,
proper design and reviewing.

6.1.1 The Need of Testing:

No matter how good a programmer is, no application will ever be one hundred percent correct.
Testing was important to us in order to ensure that the application works as efficient as possible
and conforms to the needs of the system. Testing was carried out throughout the development
of the application, not just the application has been developed, as at this stage it took a great
deal of effort to fix any bugs or design problems that were occurred.

The completion of the application is achieved only after it has been thoroughly tested. Though
this gives a feel that project is completed, there cannot be any project without going through
this stage. Hence in this stage it is decided whether the project can undergo the real time
environment execution without any breakdowns, therefore a package can be rejected even at
this stage.

Regardless of which strategies the analysis follows, there are preferred practices to ensure the
testing is useful. The levels of tested and types of test data, combined with testing libraries are
important accepts of the actual test process. Among the various testing practices or strategies
that are following by analysis.

38
A BOOK ZONE TESTING

6.2 Project Strategy:

When our application was configured and customized in the system, the test was observed that
this configuration or customization does not cause any improper processing or violation. The
following care was taken when the application was developed at the local machine. The
interface may have something not proper, which can be tested by this checklist:
 Number of input parameter equal to number of argument?
 Parameter and argument attributes match?
 Number of arguments transmitted to called forms equal to number of parameters?
 Attributes of arguments transmitted to called forms to attributes of parameters?
 Number attributes and order of arguments to built-in functions correct?
 The local data structures for a form are common source of errors. The following types
of errors should be searched for.
 Improper or inconsistent typing
 Erroneous initialization or default values
 Incorrect (misspelled or truncated) variables names
 Inconsistent data types
 Underflow, overflow and addressing exception
 As far as unit testing is concerned we did it at the time of coding in an informal but
extensive way, so as to reduce number of problems arising out of incorrect syntax,
incorrect variable, function names etc.
 Close the database connection when not required.
 Care was taken to check for any infinite loop that exists in code before executing the
code.
 Checked all input systems and all functionality it's working properly.
 The database connections were checked and each time the database connection
was opened it was ensured that the connection was closed within finally block to
optimize the database performance.



39
A BOOK ZONE TESTING

Figure 6.2
6.3 Testing Methods:
6.3.1 White-Box Testing:
Also known as glass box, structural, clear box and open box testing. A software testing is
a technique whereby explicit knowledge of the internal workings of the items being
tested is 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; it means that he must be completely
aware that or particular input a particular output must be obtained.

The main benefit of this type of testing is Tester can see if the program diverges from
its intended goal. This test concentrates on the examination of the code rather than the
specification. We have included three different forms of white box testing.

 Statement Coverage Criterion:

This is the simplest coverage criterion. We are checking in it that each statement of the
program was executed “at least once”.

40
A BOOK ZONE TESTING

 Branch Coverage Criterion:

An improvement over statement is Branch Coverage. In that we are running a series of

test to ensure that all branches are tested at least once.

 Path Coverage Criterion:

There are many errors which were not detected by statement or branch testing. The
reason is that some errors are related to some combination of branches and it may be not
check in other test. We are checking in this test is all path of programs are executed or
not.

6.3.2 Black-Box Testing:

Black-box and white-box are test design methods. Black-box test design treats the
system as a "black- box", so it doesn't explicitly use knowledge of the internal structure.
Black-box test design is usually described as focusing on testing functional
requirements. Also know as behavioral, functional, opaque-box, and closed-box.

Black Box Testing was helpful us to find error such as:

 Interface error.
 Incorrect or missing functions.
 Errors in data structures or external database access.
 Performance Errors.
 Initialization and termination errors.

I have also done Boundary value analysis by applying different size of digits. Example:
The password strength must be.

 Unit Testing:

Unit testing is a method of testing the correctness of a particular module of source code.
The idea is to write test cases for every non-trivial function or method in the module so
that each test case is separate from the others if possible. The developers mostly do this
type of testing. In this method of testing we test all individual components to ensure that

41
A BOOK ZONE TESTING

they operate correctly. Each component is tested independently without other system
components.

 Integration Testing:

It is the phase of software testing in which individual software modules we are combined
and tested as a group. It follows unit testing and precedes system testing. The purpose of
Integration testing is to verify functional, performance and reliability requirements placed
on major design items. It takes as its input modules that have been checked out by unit
testing, groups them in larger aggregates, applies tests defined in an Integration test plan
to those aggregates, and delivers as its output the integrated system ready for system
testing.

 Module Testing:
A module is composed of various programs related to that module. Module testing is
done to check the module functionality and interaction between units within a Module.

 Alpha Testing:
At the development site, the customer conducts a alpha test under the natural settings to
record the errors and usage problems.
 Beta Testing:
At the customer site, the end-user conducts the "live" application test in customer
environment to encounter the problems to be modified before product release.
 System Testing:
As the s/w is to be integrated with other system elements, system testing focuses on
validating the system integration by:

 Recovery Testing: To assure proper recovery.

 Security Testing: To protect the improper penetration
 Stress Testing: To confront the program with abnormal resources such as
 Quantity, frequency or volume.
 Performance Testing: The run-time performance of S/W in
Integrated System.

42
A BOOK ZONE TESTING

6.4 Testing Cases:

A test case has a component that describes an input, action or event and an expected response,
to determine if a feature of an application is working correctly. A test case is a set of conditions
or variables under which it is determined if a requirement or use case is partially or fully
satisfied. And so, in order to determine if the system created and implemented satisfied the
previously-defined requirements or not, the following test cases were used: Purpose, Required
Input and Expected Output.

6.4.1 Required Inputs and Expected Results:

TEST CASE ID: TC_Reg_01 NAME: Login

TESTING STRATAGY: Black Box and White Box Testing

PURPOSE: Checking the authenticity of the user.

INPUT: Email, password

TEST DATA: cust_email, cust_password

EXPECTED O/P: If username and password are correct then user is

allowed to enter in to the system and if not then
he/she is again asked to enter the username and
password

UNBEHAVIOURABLE O/P: N.A.

STEPS: After user enters user name and password it is going to be verified with database
and allows user to access system if both matches correctly.

Table 6.4.1 Log-in

43
A BOOK ZONE TESTING

TEST CASE ID: TC_Login_02 NAME: User Rights

TESTING STRATAGY: Black Box and White Box Testing

PURPOSE: Checking the authenticity of the user.

INPUT: Username, password

TEST DATA: cust_username, cust_password

EXPECTED O/P: User privileges are allocated according to user

group.
UNBEHAVIOURABLE O/P: N.A.

STEPS:

• After user enters user name and password it is going to be verified with database
• It matches user name and password and get his user privileges
• As per assigned privileges relevant action will be enabled

Table 6.4.2 User Rights

TEST CASE ID: TC_GEN_01 NAME: Compare Validation

[For comparing Date format]

TESTING STRATAGY: Black Box and White Box Testing
PURPOSE: Validating date with date format
INPUT: Input name of all web pages
TEST DATA: Dates, Application
EXPECTED O/P: Validation occurs
UNBEHAVIOURABLE O/P: N.A.
STEPS :
After user fills up the date or website format in textbox and if the validation is not
correct the user is asked to again enter the correct value.

Table 6.4.3 Data Validation

44
A BOOK ZONE TESTING

TEST CASE ID:TC_GEN_02 NAME: Email Validation

[[email protected]]
TESTING STRATAGY: Black Box and White Box Testing
PURPOSE: Validating Email addresses and allow users to
enter in a proper format
INPUT: Email address
TEST DATA: Email
EXPECTED O/P: Validation occurs
UNBEHAVIOURABLE O/P: N.A.
STEPS :

• When any submit button is pressed and if the validation is not correct, system
won’t allow user to proceed further, ask to enter the correct email_id again.

Table 6.4.4 Email Validation

TEST CASE ID:TC_GEN_03 NAME: Required Validation

TESTING STRATAGY: Black Box and White Box Testing

PURPOSE: Validating input data in component. It should not be
null.
INPUT: Require field of all web pages
TEST DATA: Email_id, password, firstname,Dates, Price
EXPECTED O/P: Validation occurs
UNBEHAVIOURABLE O/P: N.A.
STEPS :
1. In case of each and every entry mostly at the end of form when use processes submit
button then length of each and every field is going to be checked
2. In case of required field if it is get less than 1 then alert will be displayed which indicates
that particular field should not be empty and won’t allow to proceed before filling up
that field

Table 6.4.5 Required Field Validation

45
A BOOK ZONE TESTING

TEST CASE ID:TC_AV_04 NAME: Edit Profile

TESTING STRATAGY: Black Box and White Box Testing

PURPOSE: Whenever any user wants change his/her information

and selected previous information should be placed
automatically in relevant textbox

INPUT: Selection of user for updating

TEST DATA: Respective Id of user is passed

EXPECTED O/P: Existing name of the selected item

UNBEHAVIOURABLE O/P: Exception Occurs: no output will be displayed

STEPS :

• Whenever user selects user then their respective Ids are passed.
• And from database, then from already placed data its new data should be stored in some
variable then all the information is placed in relevant textbox.
• Updated category is then reviewed.

Table 6.4.6 Update

46
A BOOK ZONE

Conclusion
Thus, the proposed system for book sharing will provide a platform for all students to give and
take books through a more efficient and streamlined manner. The system incorporates a number
of techniques to further increase the process of sharing books. By automating the book searching
process with the help of computer assistance a lot of precious time and effort of the students will
be saved. The proposed system will thus be much more efficient than the current offline process
and will be a huge help to all students.

47
A BOOK ZONE

References:

 Prathamesh Muzumdar ,The University of Texas at Arlington ‘Online Book Sharing

System - A new trend in textbook sales management for services marketing’ Journal of
Management and Marketing Research (2009)

 Carbaugh, R., & Ghosh, K. (2005). Are college textbooks priced fairly? Challenge, 48
(5), 95-112
 Bakos, J. Y. (1997). Reducing buyer search costs: Implications for electronic
marketplaces. Management Science 43(12) 1613-1630.

 Wargo, John M. PhoneGap Essentials: Building Cross-Platform Mobile Apps. Addison-

Wesley, 2012.

48