Gujarat Technological University

Chandkheda, Ahmedabad

Sanjaybhai Rajguru College of Engineering

A Summer Internship project Report on

“Online bookstore”
Under the subject Summer Internship (3170001)
B.E. Semester VII
INFORMATION TECHNOLOGY ENGINEERING

Submitted By
Parmar Nikita jayantibhai (190363116018)
Academic Year
(2021-2022)

i
1

CERTIFICATE
This is to certify that the project report has been
satisfactorily completed by Nikita parmar (190363116018)
under my guidance in the fulfillment of the course Summer
Internship (3170001) work during the academic year 2021-
2022.

signature
1
 Acknowledgement

We have taken efforts in this project. However, it would not have been possible
without the kind support and help of many individuals and organizations. We
would like to extend our sincere thanks to all of them.
 ABSTRACT

The project is an authentication system that validates user for accessing the system only when they
input correct password. The project involves three levels of user authentication. There are varieties
of password systems available, many of which have failed due to bot attacks while few have
sustained it but to a limit. In short, almost all the passwords available today can be broken to a
limit. Hence this project is aimed to achieve the highest security in authenticating
users.It contains three authentication phases having three different kinds of password system. The
password difficulty increases with each level. Users have to input correct password for successful
login. Users would be given privilege to set passwords according to their wish. The project
comprises of text password i.e. pass phrase, image based password and OTP password for the three
levels respectively. This way there would be negligible chances of bot or anyone to crack passwords
even if they havecracked the first level or second level, it would be impossible to crackthe third
one. Hence while creating the technology the emphasis was put on the use of innovative and
nontraditional methods. Many users find the most widespread text-based password systems
unfriendly, so in the case of three level password we tried creating a simple user interface and
providing users with the best possible comfort in solving password
List of table

 Data Dictionary

 Estimations

 Scheduling
List of figures
 Data Flow Diagram

 Design
 System design
 Data design

 Testing
 Flow graph

 snapshot

.
 Table of Contents
Problem Statement ...................................................................................................
Process Model..........................................................................................................
1. Software Requirement Specification ......................................................
1.1 Overall Description ............................................................................
1.1.1 Product Functions ..........................................................................
1.1.2 User Characteristics .......................................................................
1.1.3 General Constraints .......................................................................
1.1.4 Assumptions and Dependencies.....................................................
1.2 External Interface Requirements .........................................................
1.2.1 User Interfaces...............................................................................
1.2.2 Hardware Interfaces.......................................................................
1.2.3 Software Interfaces ........................................................................
1.3 Functional Requirements ....................................................................
1.3.1 FR 1 .............................................................................. .
1.3.2 FR 2 .............................................................................. .
1.3.3 FR n .............................................................................. .
1.4 Performance Requirement ..................................................................
1.5 Design Constraints .............................................................................
1.6 Data Flow Diagram ............................................................................
1.7 Data Dictionary ..................................................................................
2. Estimations ............................................................................................
2.1 Function Points ...................................................................................
2.2 Efforts ................................................................................................
3. Scheduling .............................................................................................
4. Risk Management ..................................................................................
5. Design ...................................................................................................
5.1 System Design ....................................................................................
5.2 Data Design ........................................................................................
6. Coding ...................................................................................................
7. Testing...................................................................................................
8. References .............................................................................................
Problem Statement

The software to be designed is for a book store that wishes to go online.It is to be developed to
improve the efficiency for customer.

The important features to be developed includes:

 Login/Registration module require customer to login into the system or he can

create an account if he not yet have one.
 Order module require customer to enter the book detailed that he/she wants to buy.
 Book detail(s) module allows the system to keep book information in detailed by
name,genre etc.
 Stock management will tell about the quantity of books left in store.
 Payment module allows the customer to online payment like paytm and credit/debit
cards or cash on delivery.
 Delivery and tracking module gives the information about tracking and by whom it is
delivered.
 User feedback module.
Process Model
We choose Waterfall model due to following reasons:

 This model is choose because our requirements are very well known, clear and fixed.
 Product definition is stable.
 There are no ambiguous requirements in our project.
 The project is short.
 This model is simple and easy to understand and use.
 It is easy to manage due to the rigidity of the model – each phase has specific
deliverable and a review process.
 In this model phases are processed and completed one at a time. Phases do not overlap.
 Waterfall model works well for smaller projects where requirements are very well
understood
 1.software requirement specification

Administrator can see the daily sell of the books,can also see the feedback given by the
customers.Administrator maintains the deliveries.

Supplier can use the system to see the product,their prices and quantity available profit and lose.

1.1.1 General Constraints

 The interface will be in English only.

 The system is working for single server.

 GUI features available.

1.1.2 Assumptions and Dependencies

The product does require back-end database server MySQL for storing the

username and Password for different types of user of the system.

ASSUMPTIO
NS:  User must be trained for basic computer functionality.

 User must have basic knowledge of English.

 The system must be able to respond to database software

within reasonable time

1.2 External Interface Requirements

1.2.1 User Interfaces

User of the system will be provided with the Graphical user

interface,there is no Command line interface for any function.

1.2.2 Hardware Interfaces

Hardware requirement will be same for the both the parties which are follows:

 Processor- Pentium I or above.

 Ram 128MB or above.

1.2.3 Software Interfaces

Software required to make for working of our online bookstore is:

 Operating system: Windows XP/Vista/7 or later version, Linux OS which
supports Networking.

Java development tool kit….

1.3 Functional Requirements.
The system must provide following functionality:

1.3.1 Order

This module basically deals with the order of the books. It accepts book name , retrieve book
details, calculate price based on selected book. After it payment process start then the book is
delivered to the customer .

1.3.2 Cancellation

Once the order of book has done, it can be cancelled or seen by this module. It accepts order ID
verifies it with the database. On successful confirmation by the customer it can cancel the order.
Further, it will update the bookstore database and the payment gateway to issue refund.

1.3.3 Search

This module retrieves the details of the books. It accepts book name or subject and course name
and then retrieves the details of the particular book or all the books from particular subject or
course name.

1.4 Performance Requirement

1. Any number of users can access the system at any time and maintain speed at maximum.

2. Server will be working whole 24x7 times.

3. Security

4. Reliability

5. Portability

1.5 Design Constraints

 This Software can be installed on Personal Computers, Tablets or Smart phones.
 For security reasons, Login Id & Password must be provided.
 1.6 Data Flow Diagram
DFD LEVEL 0:

CUSTOM lLogin/registra SUPPLIER

ER tion

order

book details stock availability

Payment delivery &tracking

feedback ONLINE BOOKSTORE

DFD LEVEL 1:

Books

cost

Available
Generate
book details
order id and
total cost

Retrive&
display

cost

Available feedback Gener-

Book books order
Information ate Bill
Details User Details
and payment

Customer Order ID
Order id & cost

Update
feedback database
Acknowledgement Order id

Cancell-
ation
CUSTOMER RECORDS
 DFD LEVEL 2:

CHECK
AVAILABI
ORDERED
LITY OF
CUSTOMER BOOKS
BOOKS

STOCKS
AVAILABILITY
BOOK
DATABASE

COLLECTI
NG
INFORMA
TIO ON
CUSTOMER INFORMATION

CUSTOMER RECORDS

PAYMENT
MODE
PAYMEN
T
UPDAT
E COST
DATAB DELIV
ASE PAYMENT ERY

ONLINE
PAYMENT
PAYMENT
CUSTOMER
1.7 Data Dictionary

TABLE 1:

S.no. data Description

1 Customer info.

User name

login id

Userid

Password

2 Registration info

Fname +Mname+Lastname

Date of birth

Address

Phone number

Gender

E-mail id

3 Book Details

Book id

Book name

Author

Publishor

Price

Subject

4 order

Order ID
 Total cost

Product details

Payment Details

2 Estimations
 Function Points

GRAD
E
VALU
E
1 Does the system require reliable backup and recovery? 5

2 Are specialized data communications required to transfer information to or 4

from the application?

3 Are there distributed processing functions? 4

4 Is performance critical? 2

5 Will the system run in an existing, heavily utilized operational 3

environment?

6 Does the system require on-line data entry? 4

7 Does the on-line data entry require the input transaction to be built over 4
multiple screens or operations?

8 Are the ILFs updated online? 4

9 Are the inputs, outputs, files, or inquiries complex? 2

10 Is the internal processing complex? 4

11 Is the code designed to be reusable? 3

12 Are conversions and installations included in the design? 3

13 Is the system designed for multiple installations in different 1

organizations?

14 Is the application design to facilitate change and for ease of use by the 5
user?

Estimation of Complexity Weighing Factors

VALUE ADJUSTMENT FACTORS, Σfi= 48

MEASUREM OPT LIKE PESS EST. WEIGHNI FP

ENT LY COU NG COU
PARAMETER NT FACTOR NT
Number of external inputs 2 4 6 4 4 16

Number of external 2 3 6 3 5 15
outputs
Number of 1 1 4 1 4 4
external inquiries

Number of internal 1 2 3 2 10 20
logical files

Number of 1 1 3 1 7 7
external interfaces

Count total 62

COMPUTING FUNCTION POINTS:

FP = COUNT TOTAL * (0.65 + 0.01 * Σfi)

= 62 * (0.65+ 0.01 * 48)

= 70.06
 2.1 Efforts

The average productivity for this kind of system =6.5 FP/pm

Considering the labour rate=Rs. 8000

Cost per FP = 1230

Total efforts = FP (calculated) / average productivity

= 70.06 /6.5

=10.778 person months

Total cost for the project = Total efforts * labour rate

= 10.778 * 8000

= Rs. 86224

3. Scheduling
3.1 Schedule table

WORK TASKS SCHEDULE

1. IDENTIFY NEEDS AND BENEFITS
Meet with concerned members Week 1
Identify needs and project constraints Week 1
Establish problem statement Week 2
Milestone Week 2

2. REQUIREMENT ANALYSIS
Detailed discussion of the project Week 3
Creating Data flow Diagram Week 4
Data Dictionary Week 5
Milestone Week 5

3. PROJECT MANAGEMENT
Computing F.P. and Effort Week 5
Schedule table Week 6
Risk table Week 7
Timeline Chart Week 8
Milestone Week 8

4. DESIGN ENGINEERING
Architectural Design Week 8
Data Design Week 9
Pseudo Code Week 9
Milestone Week 10

5. TESTING Week 12

Refinement:

Subcondition1: Certain check points are recorded in the system periodically

Sub condition 2:As a part of check-pointing ,after every update in the database, checkpoints are
updated which states that the database is updated correctly till that point.

Mitigation/Monitoring:

1. A copy of all the databases must be maintained side by side on a different system. Also, it
must be updated simultaneously.

2. A recovery tool must be designed which could recover the database according to the check
points.

Management

A special team is allocated for the recovery of the database as soon as possible. The secondary
databases which were maintained as a copy must be made primary so that the working of the
software is not affected.
from
 4. Design

5.1 System Design

ONLINE
BOOKSTORE

GENERATE
BILL

RETRIEVE BOOK TOTAL COST DELIVERY & CANCELLATION

INFORMATION CALCULATION TRACKING ORDER

DISPLAY
TOTAL COST
DELIVERY TO
OF THE BOOK CUSTOMER

TAKE CUSTOMER GENERATE

DETAILS AND BILL AND
PAYMENT ORDER ID
ORDER DISPLAY DETAILS TAKE ACKNOWL-
BOOK OF BOOK ORDER ID EDGEMEN

5.2 Data Design

ER-Diagram:-

from
 B_name
subject
Name Email_id b_id

M N aurthor
Customer Search Books

Publisher
1
Phone
Add. Course name

Phone

Order

Comments
N Mode
Transaction_id

1
Delivery& 1 Generate
Payment
tracking bill

1
N
Order_ID
Bill
status

S_name
Status of order Transactipon_id Mode

from
 Customer
Email_id Name Mobile Address

Book
Book_name Book_id Publisher Author Price

Generate Bill
Order_id Name Book_name Total_cost Address

Payment
Order_id Transaction_id Mode

from
 1. Coding

Int a,found=0;(1)
Char b_name[30],subject[30],author[30];
Void Search( ) (2)
{
cout<<”\n (1) SEARCH BY BOOK NAME :”;
cout<<”\n (2) SEARCH BY SUBJECT & AUTHOR :”; (3)
cin>>a;
if(a==1) (4)
{
gets(b_name); (5)
while(!ifile.eof() && found==0) (6)
{
ifile.read((char*)&S1,sizeof(detail)); (7)
if(strcmp(b_name,S1.book_name)==0) (8)
found=1; (9)
}
}
else (10)
{
gets(subject); (11)
gets(author);
while(!ifile.eof()) (12)
{
ifile.read((char*)&S1,sizeof(detail)); (13)
if(strcmp(subject,S1.subject)==0&&strcmp(author,S1. author)==0) (14)
print(s1); (15)
}
}
} (16)

from
 2. Testing
7.1 Flow graph

4 10

5 11

6 12

7 13

8 14

9
15

16

Paths:

from
 Path 1: 1 2 3 4 5 6 16

Path 2: 1 2 3 4 5 6 7 8 6….

Path 3: 1 2 3 4 5 6 7 8 9 6…

Path 4 : 1 2 3 10 11 12 16

Path 5: 1 2 3 10 11 12 13 14 12…

Path 6: 1 2 3 10 11 12 13 14 15 12…

7.2 Cyclomatic Complexity

Using Regions: -

Number of regions = 6
Therefore, cyclomatic complexity = 6

Using Edges & Nodes: -

Number of Edges (E) = 20

Number of Nodes (N) =16
V (G) = E – N + 2
=20 – 16 + 2
=6
Therefore, cyclomatic complexity = 6

Using Predicate Nodes: -

No. Of predicate Nodes (P) =5

V (G) = P+1
=5+1
=6
Therefore, cyclomatic complexity = 6

7.3 Test cases

Test Case 1: P1:

from
 When the user enters, ‘Y’(to the Ques. that whether he knows the book

name). Then the User enters the book name. ,

Program enters in while loop but the file does not exist or is

empty. & it exits

Test Case 2: P3:

When the user enters , ‘Y’(to the Ques. that whether he knows the book name.).

Then the User enters the book name.

Then program enters in while loop, searches the whole file & the corresponding book name is found. &

it exits

Test Case 3:P2:

When the user enters, ‘Y’(to the Ques. that whether he knows the book name).

Then the User enters the book name.

Then program enters in while loop, searches the whole file but the corresponding book name is not
found .

& it exits

Test Case 4:P4:

When the user enters ‘N’(to the Ques. that whether he knows the book name.)

Then the user enters the subject and course name.

Program enters in while loop but the file does not exist or is empty.

& it exits.

Test Case 5:P5:

When the user enters ‘N’ (to the Ques. that whether he knows the book name)

from
Then the user enters the subject and course name.

Then program enters in while loop, searches the whole file but the corresponding set of subject
andcourse name is not found.

& it exits.

Test case 6: P6:

When the user enters ‘N’(to the Ques. that whether he knows the book

name)Then the user enters the subject and course name.

Then program enters in while loop , searches the whole file & the corresponding sets of subject
andcourse name is found.

& it exits.
SNAPSHOTS

Figure 1. snapshot 1

Figure 2. Snapshot 2
Figure 3. Snapshot 3

Figure 4 . Snpshot 4
Figure 5. Snapshot 5

Figure 6 . Snapshot 6
Figure 7. Snapshot 7

Figure 8. Snapshot 8
Figure 9 .Snapshot 9

Figure 10 . Snapshot 10
Figure 11 . Snapshot 11

Figure 12 . Snapshot 12
Figure 13 . Snapshot 13

Figure 14. Snapshot 14

Figure 15. Snapshot 15

Figure 16. Snapshot 16

Figure 17. Snapshot 17

Figure 18. Snapshot 18

Figure 19 . Snapshot 19