A

DISSERTATION
ON
“Online Book Store”
UNDERTAKEN AT
SHREE SAI INSTITUTE OF TECHNOLOGY
By

Garima Gharu

SUBMITTED TO
Vikram University, Ujjain
In
Partial fulfilment of the requirement for the Award of the Degree of
Bachelor of computer application (B.C.A)
DEC 2019
GUIDED BY
PROF.AMIT SHARMA

Computer Application Department

SHREE SAI INSTITUTE OF TECHNOLOGY, RATLAM

1
 ACKNOWLEDGEMENT

The Completion of this undertaking could not have been possible without
the participation and assistance of several persons who helped us directly or
indirectly in this project work. We express our heart full and owe a deep sense
of gratitude to my teacher and my faculty guide Prof. Amit Sharma, Shree Sai
Institute of Technology, for their sincere guidance, encouragement, suggestion,
inspired and have contributed immensely to the evolution of our ideas on the
project.

We are extremely thankful to all faculties member of BCA department of

Shree Sai Institute of Technology for their coordination and cooperation and for
their kind guidance and encouragement.

We also thank our friends who have more or less contributed to the
preparation of this project report. We will be always indebted to them.

The study has indeed helped us to explore more knowledgeable avenues

related to my topic and we are sure it will help us in our future.

Thank you

Garima Gharu
BCA (VI SEM)

2
 Certificate of the principal

Date………………..

Project Completion certificate

This is to certify that Garima Gharu , student of BCA (VI semester) of
Shree Sai Institute Of Technology, has successfully completed the
project work entitled “Online Book Store” under the guidance of Prof.
Amit Sharma is a bonafide piece of work carried out at Shree Sai
Institute Of Technology.

The project entitled “Online Book Store” developed by Garima Gharu

in the Shree Sai Institute of Technology and he has done his laboratory
work during the tenure of the project with the guide to complete this
project. All the prescribed certificates are attached after the
completion of all the formalities of the project work as per schedule,
including internal examination.

Place : Ratlam Signature of Principal

Date: Seal of the Institute

3
 Date………………..

Certificate of Attendance

This is to certify that Garima Gharu student of BCA (VI Semester) of

Shree Sai Institute Of Technology, has put at least 200 hours of
laboratory work with the guide to complete this project during the
situated period of the project at Shree Sai Institute Of Technology.

Signature of guide

Place: Ratlam Signature of Principal

Date: Seal of the Institute

4
 DECLARATION

We Garima gharu student of Shree Sai Institute of Technology declare

that the dissertation/project report submitted by us under the
guidance of Prof. Amit Sharma is a bonafide work for Partial fulfilment
of the requirement of the BCA (VI semester) major project work. We
have incorporated all the suggestions provided by our guide time of
time.

We further declare that to the best of our knowledge this dissertation

contains our original work and does not contain any part of any work
which has been submitted for the award of any degree either in this
university or in any other university/Deemed university/Institute etc.
Without proper citation and we will be fully responsible for any
plagiarism found at any stage.

Name & Signature of the guide Name & signature of the student

Prof. Amit Sharma Garima gharu

5
 Date………………..

Dissertation Approval Certificate

This is to certify that that Garima gharu student of BCA (VI semester) of
Shree Sai Institute of Technology, has successfully completed the project
work entitled “Online Book Store” under my guidance. I have regularly assessed
the progress of the work and suggested the correction wherever required. The
student has incorporated all the suggestions provided by me in this dissertation.
This dissertation is bonafide piece of work of the standard of BCA project work
carried out by the student under my supervision. Internal examination has been
completed in my presence and student’s performance was satisfactory and
hence this dissertation is approved for the submission and valuation thereof.

Signature of Guide

Place: Ratlam Signature of Principal

Date: Seal of the Institute

6
 LIST OF CONTENTS

CHAPTER NO. SUBJECT PAGE NO.

Acknowledgement 2

Certificates 4
List of contents 7
1. Introduction 11
1.1 Objective of System 13
1.2 Scope 14
1.3 Existing System 14

1.4 Proposed System 15

2 System development life cycle 16

2.1 Introduction of SDLC 18
2.1.1 Phases of SDLC 17
2.1.2 Description of phases 20
2.1.2.1 Analysis of user requirements 20
2.1.2.2 Program design 21
2.1.2.3 Program coding 22
2.1.2.4 Documentation and testing 23
2.1.2.5 Operating and maintaining the system 25
3 Analysis 26
3.1 Requirement analysis 27
3.2 Requirement specification 27

7
3.2.1 Functional requirement 27
3.2.2 Non-functional requirement 28
3.3 Use case analysis 30
3.3.1 Use case diagram 30
3.3.2 Module specification 31
4 Design 34
4.1 System flow diagram 35
4.2 Sequence diagram 36
4.3 Activity diagram 38
4.4 Data flow diagram 40
4.5 E-R diagram 43
5 Implementation 44
5.1 Platform Used 45
5.1.1 Client side 45
5.1.2 Server side 46
5.2 Technology used 47
5.3 Snapshots 50
5.4 Table Structure 55
6 Testing 58

6.1 Testing techniques 59

6.1.1 Unit testing 59

6.1.2 Integration testing 60

6.1.3 System testing 61

8
7 Conclusion 63

7.1 Important features 64

7.2 Advantage 65

7.3 Disadvantage 66

7.4 Conclusion 67

8 Bibliography & references 68

9
 CHAPTER 1

INTRODUCTION

INTRODUCTION

10
1. What is ONLINE BOOK STORE ?
An online book is a resource in book-like form that is only available to read
on the Internet. It differs from the common idea of an e-book, which is usually
available for users to download and read locally on a computer, smartphone or
on an e-reader. "Book-like" means: information is presented in a page format;
pages are normally available to read sequentially (though "flipping" to another
page is possible using a mouse, keyboard or other controllers); and pages are
read passively, with little or no interaction or multimedia. This contrasts with a
text which a user is reading on an interactive Web 2.0 website, which usually
enables the user to click on online links, look up words or keywords online,
etc. "Online" means the content may only be read while the reader is connected
to the Internet. Thus the reader's experience with an online book is similar to
reading a printed book, except that the book is read at a computer and is only
accessible while the reader is online.

Online books are a common resource in virtual learning environments (VLEs).

For example, the Moodle VLE defines an online book in this way. Over the
last few years, there has been an increase of online books that are being used
for notable events or to commemorate the memory of someone. The
fundraising industry often uses online books as a way to fundraise, as online
books are also a way to collect donations and engage with their audience.

 The number of staff required.

11
  Costing information and assumptions.
 When the staff are needed and for how long.
 Any special skills required over and above those that people in the
category would normally be expected to have, as well as the required level
of proficiency and the relative importance of these skills.

Training requirements needed specifically for the project, for example in a

new technology.

 Office and materiel requirements

 Plans for team-building activities. (Motivation management)

The Online Book Store supports staff planning, staff acquisition, allocating
resources to staff, and supervising project specific training activities. A summary
Online Book Store is created for the entire project and managed by the project
manager.

1.1 Objective of Online Book Store

The main objective of the Online Book Store is to manage the details of
Books,Customer,Payment,Delivery,Bills. It manages all the information
about Books, Stock, Bills, Books. The project is totally built at
administrative end and thus only the administrator is guaranteed the
access. The purpose of the project is to built an application program to
reduce the manual work for managing the Books, Customer, Stock,
Payment. It track all the details about the payment,Delivery,Bills.

1.2 What is the Scope of Online Book Store?

This project can be easily implemented under various situations.We can add new
features as and when we require. Reusability is possible as and when require in this
12
project. There is flexibility in all the modules. We can also include online payment
services to this project using PayPal. This will help customers to pay online for
their purchases using Credit/Debit card. There are many features which could be
added to this project for making this project more productive.
1.3 Existing System
The CIS Administration falls short of controlling the employee’sactiv
ities in analyzing his/her strengths and weakness. The decision for appraisal of
assigning next project to the employee or to train him/her to enhance the
skills – where lies with proper projection. He is not provided with the detailed
project information done or to be assigned based on Application / Verticals.

1.3.1 Drawbacksof Existing System

 Need of extra manual effort.

 It used to take much time to find any book
 Not very much accurate.
 Danger of losing the files in some cases

In the existing system all the information of a employee or client proceed manually
and it has to maintain the record of the entire activity involved in manual system.
Searching the property was done by the persons own self from the organization or
through internet sites there was a limitation of matching choice of their property. In
these cases the time was very essential. So to solving this problem stock of
problems can be listed in the existing system.

The definition of our problem lies in manual system and a fully automated system.

Manual system: The system is very time consuming and lazy. This system is more
prone to errors and sometimes the approach to various problems is unstructured.

Technical system: With the advent of latest technology if we do not update our
system then our business result in losses gradually with time. The technical

13
systems contains the tools of latest trend i.e. computers printers, fax, Internet etc.
The systems with this technology are very fast, accurate, user-friendly and reliable.

1.4 Proposed System

The proposed system provides facilities to access the book system from anywhere
in the community. The customer can visit the site and purchase the book according
to their requirements. The main advantage of the system is that all transactions can
be done through a common network. Many features of e-commerce have been
implemented here. Thus making it more economical.
The existing system has certain limitations than a web based system. In order to
wipe out those limitations in the computerized system, we introduced a web based
system. This will be able to meet all the requirements of the user. The proposed
system will be able to implement easily. In this system there is no need of keeping
files or records by the administrator. He can keep the records in the computer
system itself and can be shared among networks. The user is able to acces all the
information at any point of time.
Almas online book store provides a user friendly interface and performs operations
according to the user’s request. Almas allows the user to view any type of books
available ,searching for a particular book based on name ,author ,language,
publication etc..and the user can also purchase books based on his/her requirement.
Inorder to purchase a particular book, the user should have an account. The user
can register directly to our site by filling an online registration form. After
registration, the user can log in to the site by using the username and password
created during registration. Only the registered user have the permission to
purchase books from Almas online book store.

14
 CHAPTER 2

SYSTEM DEVELOPMENT

LIFE CYCLE

15
SYSTEM DEVELOPMENT LIFE CYCLE

2.1 SYSTEM DEVELOPMENT LIFE CYCLE

Software Development Life Cycle consists of details steps and activities which
describes how to design , develop , maintain , replace , alter , enhance , test or even
launch a software . The activities can be broken down into a very detail level but at
the same time they can be grouped into five ( 5 ) core categories : Plan , Design ,
Develop , Test and Deploy . It is a graphic representation which displays a typical
Software Development Life Cycle.

2.1.1 Phases of SDLC

System Analysis

System Design

Coding

System Testing

System Implementation

System Maintenance.

16
2.1.2 System Development Life Cycle

SDLC is a process which defines the various stages involved in the development of
software for delivering a high-quality product. SDLC stages cover the complete
life cycle of a software i.e. from inception to retirement of the product.

Adhering to the SDLC process leads to the development of the software in a

systematic and disciplined manner

A software has to be developed and a team is divided to work on a feature of the

product and is allowed to work as they want. One of the developers decides to
design first whereas the other decides to code first and the other on the
documentation part.

This will lead to project failure because of which it is necessary to have a good
knowledge and understanding among the team members to deliver an expected
product.

Purpose of SDLC is to deliver a high-quality product which is as per the

customer’s requirement.

SDLC has defined its phases as, Requirement gathering, Designing, Coding,
Testing, and Maintenance. It is important to adhere to the phases to provide the
Product in a systematic manner.

17
 A GENERIC SYSTEM DEVELOPMENT LIFE CYCLE

18
2.1.2.1 Analysis of user requirements

The Analysis Phase is where the project lifecycle begins. The Analysis Phase is
where you break down the deliverables in the high-level Project Charter into the
more detailed business requirements. The Analysis Phase is also the part of the
project where you identify the overall direction that the project will take through
the creation of the project strategy documents.

Gathering requirements is the main attraction of the Analysis Phase. The process of
gathering requirements is usually more than simply asking the users what they
need and writing their answers down. Depending on the complexity of the
application, the process for gathering requirements has a clearly defined process of
its own. This process consists of a group of repeatable processes that utilize certain
techniques to capture, document, communicate, and manage requirements.

19
2.1.2.2 Program design

Based on the user requirements and the detailed analysis of a new system, the new
system must be designed. This is the phase of system designing. It is the most
crucial phase in the development of a system. The logical system design arrived at
as a result of system analysis and is converted into physical system design. In the
design phase the SDLC process continues to move from the what questions of the
analysis phase to the how . The logical design produced during the analysis is
turned into a physical design - a detailed description of what is needed to solve
original problem. Input, output, databases, forms, codification schemes and
processing specifications are drawn up in detail. In the design stage, the
programming language and the hardware and software platform in which the new
system will run are also decided. Data structure, control process, equipment source,
workload and limitation of the system, Interface, documentation, training,
procedures of using the system, taking backups and staffing requirement are
decided at this stage.

There are several tools and techniques used for describing the system design of the
system. These tools and techniques are: Flowchart, Data flow diagram (DFD), Data
dictionary, Structured English, Decision table and Decision tree which will be
discussed in detailed in the next lesson.

20
2.1.2.3 Program coding

The system design needs to be implemented to make it a workable system. his

demands the coding of design into computer language, i.e., programming language.
This is also called the programming phase in which the programmer converts the
program specifications into computer instructions, which we refer to as programs.
It is an important stage where the defined procedures are transformed into control
specifications by the help of a computer language. The programs coordinate the
data movements and control the entire process in a system. A well written code
reduces the testing and maintenance effort. It is generally felt that the programs
must be modular in nature. This helps in fast development, maintenance and future
changes, if required. Programming tools like compilers, interpreters and language
like c, c++, and java etc., are used for coding .with respect to the type of
application. The right programming language should be chosen.

21
2.1.2.4 Documentation and testing

The documentation of the program fulfils two main objectives. The first is to
provide a technical reference to facilitate ongoing maintenance and development of
the software itself. The second is to provide user documentation, i.e. a set of
instructions that inform the user about the features of the software and how to use
them. Before actually implementing the new system into operations, a test run of
the system is done removing all the bugs, if any. It is an important phase of a
successful system. After codifying the whole programs of the system, a test plan
should be developed and run on a given set of test data. The output of the test run
should match the expected results. Sometimes, system testing is considered as a
part of implementation process.

Using the test data following test run are carried out:

 Program test
 System test

Program test : When the programs have been coded and compiled and brought to
working conditions, they must be individually tested with the prepared test data.
All verification and validation be checked and any undesirable happening must be
noted and debugged (error corrected).

System Test : After carrying out the program test for each of the programs of the
system and errors removed, then system test is done. At this stage the test is done
on actual data. The complete system is executed on the actual data. At each stage
of the execution, the results or output of the system is analyzed. During the result
analysis, it may be found that the outputs are not matching the expected output of

22
the system. In such case, the errors in the particular programs are identified and are
fixed and further tested for the expected output. All independent modules be
brought together and all the interfaces to be tested between multiple modules, the
whole set of software is tested to establish that all modules work together correctly
as an application or system or package.

When it is ensured that the system is running error-free, the users are called with
their own actual data so that the system could be shown running as per their
requirements.

23
2.1.2.5 Operating and maintaining the system

Maintenance is necessary to eliminate errors in the system during its working life
and to tune the system to any variations in its working environments. It must meet
the scope of any future enhancement, future functionality and any other added
functional features to cope up with the latest future needs. It has been seen that
there are always some errors found in the systems that must be noted and
corrected. It also means the review of the system from time to time. The review of
the system is done for:

•knowing the full capabilities of the system

•knowing the required changes or the additional requirements

•studying the performance.

If a major change to a system is needed, a new project may have to be set up to

carry out the change. The new project will then proceed through all the above life
cycle phases.

24
 CHAPTER 3

ANALYSIS

25
3.1 REQUIREMENT ANALYSIS

In systems engineering and software engineering, requirements analysis focuses on

the tasks that determine the needs or conditions to meet the new or altered product
or project, taking account of the possibly conflicting requirements of the
various stakeholders, analyzing, documenting, validating and managing software
or system requirements.

Requirements analysis is critical to the success or failure of a systems or software

project. The requirements should be documented, actionable, measurable, testable,
traceable, related to identified business needs or opportunities, and defined to a
level of detail sufficient for system design.

Requirements analysis can be a long and tiring process during which many delicate
psychological skills are involved. Large systems may confront analysts with
hundreds or thousands of system requirements. New systems change the
environment and relationships between people, so it is important to identify all the
stakeholders, take into account all their needs and ensure they understand the
implications of the new systems. Analysts can employ several techniques to elicit
the requirements from the customer. These may include the development of
scenarios (represented as user stories in agile methods), the identification of use
cases, the use of workplace observation or ethnography, holding interviews,
or focus groups (more aptly named in this context as requirements workshops, or
requirements review sessions) and creating requirements lists. Prototyping may be
used to develop an example system that can be demonstrated to stakeholders.
Where necessary, the analyst will employ a combination of these methods to
establish the exact requirements of the stakeholders, so that a system that meets the
26
business needs is produced. Requirements quality can be improved through these
and other methods

3.2 REQUIREMENT SPECIFICATION

A software requirements specification (SRS) is a description of a software system to

be developed. It lays out functional and non-functional requirements, and may
include a set of use cases that describe user interactions that the software must
provide.
In order to fully understand one’s project, it is very important that they come up
with a SRS listing out their requirements, how are they going to meet it and how
will they complete the project. It helps the team to save upon their time as they are
able to comprehend how are going to go about the project. Doing this also enables
the team to find out about the limitations and risks early on.

3.2.1 Functional Requirements

In software engineering, a functional requirement defines a system or its

component. It describes the functions a software must perform. A function is
nothing but inputs, its behavior, and outputs. It can be a calculation, data
manipulation, business process, user interaction, or any other specific functionality
which defines what function a system is likely to perform.

Functional software requirements help you to capture the intended behavior of the
system. This behavior may be expressed as functions, services or tasks or which
system is required to perform.

27
3.2.2 Non Functional Requirements

A non-functional requirement defines the quality attribute of a software system.

They represent a set of standards used to judge the specific operation of a system.
Example, how fast does the website load?

A non-functional requirement is essential to ensure the usability and effectiveness

of the entire software system. Failing to meet non-functional requirements can
result in systems that fail to satisfy user needs.

Non-functional Requirements allows you to impose constraints or restrictions on

the design of the system across the various agile backlogs. Example, the site should
load in 3 seconds when the number of simultaneous users are > 10000. Description
of non-functional requirements is just as critical as a functional requirement.

The non-functional requirements in our project are:

 Time :-
The project should be completed within the stipulated time period.

 Cost :-
The cost involved in making the project should be less.

 Usability :-
This requirement is present, as this system will interact with user.

 Reliability :-
This system must be highly robust.
28
3.3 Use Case ANALYSIS

 use case

29
3.4 Module Specification
This project contains four main modules:

 Home Module
 Admin Module
 User Module
 Books Module

 Home Module:
It contains the details of the company.
 Admin Module:

Admin module consists of following options. They are

o User Registration:

This module is used to register the details of the new Admin user .Admin
user creation is created to the particular Admin.

o Username: This module is used to get the username for the website.
o Password: It Contains The Password of the userId.
o First Name & Last Name: It contains the user Amin Name And his/her
Surname.
o Address: It Contains the address of the user.
o PhoneNo: It Contains the Phone No. Of the user Admin
o Email: It Contains the user Admin Email Id For two factor Authentication
o Salary Detail: It is used to view all the salary details of the Admin’s and
also used to give the other allowances and deductions.
o Send and Receive Message: It is used to send and receive message from the
user.
o View: It is used to view the Company profile, user profile,Admin profile,
salary detail, attendance detail.

30
 User Module:

The user creation consists of following options. They are

o Username: This module is used to get the username for the website.

31
o Password: It Contains The Password of the userId.

o First Name & Last Name: It contains the user Amin Name And his/her
Surname.

o Address: It Contains the address of the user.

o PhoneNo: It Contains the Phone No. Of the user Admin

o Email: It Contains the user Admin Email Id For two factor Authentication

o Book: It contains the details of the books

CHAPTER 4
32
 DESIGN

4.1 System Flow Diagram

A System Flow Diagram (SFD) shows the relationships between the major
components in the system. It is a systematic representation of an algorithm or a
process. The steps in a process are shown with symbolic shapes, and the flow of the
process is indicated with arrows connecting the symbols.
In order to improve a process, it is first necessary to understand its operation in
detail. Describing this in text lacks the clarity of a pictorial diagram, where
individual steps are more easily seen. The flowchart is a simple mapping tool that
33
 shows the sequence of actions within a process, in a form that is easy to read and
communicate. The mapping of ‘what follows what’ is shown with arrows between
sequential action boxes, as in the illustration. This also shows the boxes for process
start and end points of which there are normally one each.
Processes become more complex when decisions must be made on which, out of an
alternative set of actions, must be taken. The decision is shown in a flowchart as a
diamond shaped box containing a simple question to which the answer is yes or no.

SYSTEM FLOW DIAGRAM

4.2 Sequence Diagram

34
 Select Role

Enter Email id and

Password

SEQUNCE DIG. Admin

Details
 SEQUENCE DIAGRAM FOR EMPLOYEE :-
valid?

4.3Activity Diagram
 Activity Diagram For Login
Welcome Screen

Welcome
35 message

Invalid Login
Message
 Enter username

Available
Activity diagram Login.
Yes

No
 Activity Log for Registration

Enter new and Confirm password

36
 Activity Diagram For registration

4.4 Data Flow Diagram (DFD):-

37
A data flow diagram (DFD) illustrates how data is processed by a system in terms
of inputs and outputs. As its name indicates its focus is on the flow of information,
where data comes from, where it goes and how it gets stored.

A DFD is a graphical representation of flow of data through information system.

DFD can be used to visualize a data processing.

The result is a series of diagrams that represent the business activities in a way that
is clear and easy to communicate. A business model comprises one or more data
flow diagrams (also known as business process diagrams). Initially a context
diagram is drawn, which is a simple representation of the entire system under
investigation.

 DFD Components:
 Entities: -Entities are source and destination of information data.
Entities are represented by rectangles with their respective names.
 Process: -Activities and action takes on the data are represented by
circle or Round- edge rectangles.
 Data Storage:- It can either be represented as a rectangle with absence
of both smaller sides or as an open-sided rectangle with only one side
missing
 Data Flow: -Movement of data is shown by pointed arrows. Data
movement is shown from the base of arrow as its source towards head
of the arrow as destination.

Context Level DFD

38
 DFD (Data Flow Diagram)

39
 First Level DFD

4.5 ER-Diagram

40
ER Model is represented by means of an ER diagram. Any object, for example,
entities, attributes of an entity, relationship sets, and attributes of relationships sets,
can be represented with the help of an ER diagram.

ER-Diagram

41
 CHAPTER 5

IMPLEMENTATION

42
 Implementation

5.1 IMPLEMENTATION

A crucial phase in the system life cycle is the successful implementation of the new
system design. Implementation simply means converting a new system design into
operation. This involves creating computer compatible files, training the operating
staff and installing hardware terminals, and telecommunication network before the
system is up and running.

In system implementation, user training is crucial for minimizing resistance to

change and giving the new system a chance to prove its worth. Training aids such
as user-friendly manuals, a data dictionary and job performance aids that
communicate information about the new system and help screens. Provide the user
with a good start on the new system.

43
5.2 PLATFORM USED
5.2.1 Client Side:
Hardware Requirements:-

Processor : Pentium 4 or any other higher versions

Hard Disk : Minimum 2 GB Required

Ram : Minimum 256 MB Required

Monitor : Any

Software Requirements:-

Operating System : Windows 7

Language : Java

Front End : java,Html,Jsp,Netbeans IDE

Browser : Any Browse

44
5.2.2 Server Side:
Hardware Requirements:-

Processor : Dual core or any other higher versions

Hard Disk : Minimum 40 GB or higher

RAM : Minimum 256 MB Required

Monitor : Any

Software Requirements:-

Operating System : Windows 10

Language : JRE, JDK

Software : MS SQl (Back End)

Browser : Any Browse

Web Server : Glassfish Server 4.1

45
5.2 TECHNOLOGY USED:

 JSP as Front End:

Java Server Page (JSP) is a technology that helps software developers create
dynamically generated web pages based on HTML, XML, or other document
type. Released in 1999 by Sun Microsystems, JSP is similar to PHP and ASP,
but it uses the Java programming language.

To deploy and run Java Server Pages, a compatible web server with a servlet
container, such as Apache Tomcat or Jetty, is required

 Why JSP?
 Performance is significantly better because JSP allows embedding
Dynamic Elements in HTML Pages itself instead of having a separate
CGI files.
JSP are always compiled before it’s processed by the server unlike CGI/Perl
which requires the server to load an interpreter and the target script each time
the page is requested.

 NETBEANS IDE :
46
  Best Support for Latest Java Technologies
Netbeans IDE is the official IDE for Java 8. With its editors, code
analyzers, and converters, you can quickly and smoothly upgrade
your applications to use new Java 8 language constructs, such as
lambdas, functional operations, and method references.
 Fast & Smart Code Editing
An IDE is much more than a text editor. The Netbeans Editor indents
lines, matches words and brackets, and highlights source code
syntactically and semantically. It lets you easily refractor code, with a
range of handy and powerful tools, while it also provides code
templates, coding tips, and code generators.

 Easy & Efficient Project Management

Keeping a clean overview of large application, with thousands of
folders and files, and millions of lines of code, is a daunting task.
Netbeans IDE provide different views of your data, from multiple
project windows to helpful tools for setting up your applications and
managing them efficiently, letting you drill down into your data
quickly and easily, while giving you versioning tools via Subversion,
Git integration out the box.

 Glassfish Sever as Server:

GlassFish is a Java application server project created by Sun Microsystems

that allows many developers to generate enterprise technologies that are
convenient and scalable, as well as additional services that can be installed

47
based on preference. It is a free, dual-licensed software under the GNU
General Public License (GPL) and the Common Development and
Distribution License (CDDL). GlassFish was acquired by Oracle in 2010.

SNAPSHOTS

48
 Home Page:

49
 I. User Log In

50
Admin Log In

51
Register

52
53
 Table Structure

Admin Registration Table

54
 User Registration Table

55
 Books Data Table

56
 CHAPTER 6

TESTING

Testing

57
Software testing is a critical phase of software quality assurance. It indicates the
ultimate review of specification, design and code generation. Once source code has
been generated, software must be tested to uncover and correct maximum possible
errors, before being delivered. Testing emphasizes on a set of methods for the
creation of test cases that fulfil overall testing objectives.
The primary objectives of software testing are as follows:
1. Testing is a process of executing a program to find an error in it.
2. A good test case should have a high probability of finding an as-yet-
undiscovered error.
3. A test case will be considered successful if it uncovers an as-yet-
undiscovered error.

6.1 TESTING TECHNIQUE

6.1.1 UNIT TESTING:-

unit testing is a level of software testing where individual units/ components of a
software are tested. The purpose is to validate that each unit of the software
performs as designed. A unit is the smallest testable part of any software. It usually
has one or a few inputs and usually a single output. In procedural programming, a
unit may be an individual program, function, procedure, etc. In object-oriented
programming, the smallest unit is a method, which may belong to a base/ super
class, abstract class or derived/ child class. (Some treat a module of an application
as a unit. This is to be discouraged as there will probably be many individual units
within that module.) Unit testing frameworks, drivers, stubs, and mock/ fake
objects are used to assist in unit testing.

58
6.1.2 INTEGRATION TESTING:

Integration testing is a level of software testing where individual units are

combined and tested as a group. The purpose of this level of testing is to expose
faults in the interaction between integrated units. Test drivers and test stubs are
used to assist in Integration Testing.
Integration testing is a phase of software testing in which individual software
modules are combined and tested as a group. It follows unit testing and precedes
system testing. The major objective of integration testing is to tackle the problem
of interfacing i.e. putting all the acceptable imprecision (view) may be magnified
to unacceptable levels; global data structure can cause problems and to truncate
this list of problems we use integration testing.
Integration testing is a systematic technique for constructing the program structure
while at the same time conducting tests to uncover errors associated with
interfacing. The objective is to take unit tested components and build a program
structure that has been dictated by the design.
Integration testing strategy used is Bottom-Up Integration Testing. In it all the
bottom or low level modules, procedures or functions are integrated and then
tested. After the integration testing of lower level integrated modules, the next
level of modules will be formed and can be used for integration testing. This
approach is helpful only when all or most of the modules of the same development
level are ready.

59
6.1.3 SYSTEM TESTING:

System Testing is a level of software testing where a

complete and integrated software is tested. The purpose of
this test is to evaluate the system’s compliance with the
specified requirements.

6.1.4 ACCEPTANCE TESTING:

Acceptance testing is a level of software testing where a system is tested for

acceptability. The purpose of this test is to evaluate the system’s compliance with
the business requirements and assess whether it is acceptable for delivery.

60
 Testing

61
 CHAPTER 7

CONCLUSION

CONCLUSION

7.1 IMPORTANT FEATURE

 The system should have a login .
 The Admin should have all the type of authority.

62
  The system is very useful for the companies or builders that can post
properties and admin can monitors records of all of them.
 Performance evaluation.
 Employee scheduling.
 Salary Structure & Attendance management.
 Recruiting & Applicant tracking.
 Learning management.
 Payroll management.
 Analytics & Reporting.
 E-Test.

7.2 ADVANTAGES

 GUI:
The proposed system provides better graphical user interface.
 Search:
Searching for desired Job become easy and efficient.
 Increase work Speed:
Due to automation of some part of the system work speed will increase.
 Less Paperwork:
For the proposed system less paper work is required.
 Reduce Error:
Due to computerized there are less possibilities of error.
 Economical:
Due to minimal errors and work delay proposed system can be
economically to the company.

63
 7.3 DISADVANTAGE AND LIMITATIONS
There are few limitations in this web application which are following:

1. As with most online transactions, you need a lot of trust to use online
bookstores. Because you cannot see and touch the books you are buying, you
cannot guarantee that what you saw on the website is what will be delivered to
you.
2. When you buy books online, you don’t receive any personalized service.
This may not be much of a deterrent for most, but some people enjoy having direct
access to a store rep for answering questions or for assistance in their browsing
efforts.
3. By choosing to buy books online, you are also choosing to accept the risks
of fraud. Fraud is a big problem plaguing transactions across the internet. While
you can always take measures to protect your finances, there is no way to
completely remove fraud from the equation.
4. Though the actual books purchased from an online store may be cheaper,
you oftentimes have to deal with high shipping costs.
5. Returns are very problematic when you buy books online. The return
policies of online stores can make the process either impossible or more costly than
you are willing to accept.

64
7.4 CONCLUSION
The switch from written books being from bookstores to being
ordered online or even just digital copies has had profound effects
on the
industry including bookstores and libraries and the general people
of the
world. The positives include easy access for everyone and cheaper
0books along with saving natural resources. The negatives however
are much greater and cannot be ignored. Some of the negatives
include the loss of jobs and businesses through the
digitalization of books, the loom threat of Google books, as well as
losing a
sense of our past. Books have played such a large role in human
history that it
is bitter sweet to be replacing them. To me, it seems that e-books,
Google books, and online retailers are the future and that the future
is good. But, if you look past all the conveniences and look at the
people being affected by this then it becomes clear that this is not a
future that I want.

65
 CHAPTER 8

BIBLIOGRAPHY

AND

REFERENCES

66
8.1 Websites referred

 www.slideshare.net
 www.youtube.com
 www.javaTpoint.com
 www.tutorialspoint.com
 www.w3schools.com
 www.stackoverflow.com

1. Search Engine

 www.google.com

67