PDF to Audio Convert App

Session (2018-22)

BSSE (Hons)

Submitted By

Name: Ahsan Roll no: 52286-f18

Supervised By

Sir Asif Umar

Department of IT

Hazara University Mansehra

 FINAL APPROVAL

This is to certify that I have read the project report titled “PDF to Audio Convert Android
App” submitted by the following students of BCS 8th semester.

Name Roll No Registration No

Ahsan 52286-f18 15-BCS-F-HU-26

It is my judgment that this project report is of sufficient standard to warrant its acceptance by

the department of Information Technology, Hazara University Mansehra.

COMMITTEE

 External Examiner ____________________________________

 Supervisor ____________________________________

 Head of Department ____________________________________

i
 ACKNOWLEDGEMENT

In the name of ALLAH, the Most Gracious and Most Merciful, all praises to ALLAH for
the strengths and his blessing to me for the completion of the project. I am very thankful to
almighty ALLAH who showers his blessing always on me.

I am deeply grateful to my project supervisor Sir Asif Umar Department of information

technology, who has tendered valuable advices and suggestions for this project. Being truly
without his guidance, support, suggestions and encouragement I would not have been to
complete this project. He was my source of motivation and guidance for the completion of
this project. I am very thankful for his cooperation and guidance.

I am also thankful to the chairman and all the teaching Staff of our department. Their
guidance and suggestions give us the potential to complete our project.

We are also thankful to all our friends who support and encourage us throughout our project.

ii
 PREFACE

The basic objective of this project is to create App which will convert PDF file to audio.
Reading PDF files may cause problem in a professional life. E.g. irritation in eyes or getting
bore while continuous reading. Something new should develop that give comfort to reader.
He doesn't need to watch computer screen for a long period so you are required to develop an
application which convert your PDF file into audio file .Reading need full attention of reader
so reader cannot perform any other task during reading. However through this application, he
can do multitasking. Moreover, visually impaired people may also get benefit from this
application. This application will handle only a PDF File having paragraphs written in
English.

Ahsan

iii
 ABSTRACT

The PDF to Audio Converter project provides an alternative was to access the PDF books for
blind, lazy, readers and others. Using this PDF to Audio Converter the user will be able to
listen to his\her favorite PDF and can do their daily routine. The application can be used to
read any PDF which has English text.

iv
 TABLE OF CONTENTS
CHAPTER 1 INTRODUCTION................................................................................ I

1.1 Project Definition..................................................................................................1

1.2 Features.................................................................................................................1

1.3 Benefits: The prominent benefits of this application are:.....................................2

1.4 Tool used in the Project.........................................................................................3

1.4.1 Java....................................................................................................................3

1.4.2 XML..................................................................................................................3

1.4.3 SQLite......................................................................................................................3

1.3.4 Android Studio.........................................................................................................3

1.5 Scope.....................................................................................................................4

1.6 Feasibility..............................................................................................................4

1.6.1 Operational Feasibility.............................................................................................4

1.6.2 Financial and Economic Feasibility.........................................................................4

1.6.3 Technical Feasibility................................................................................................5

CHAPTER 2 PRESENT SYSTEM.....................................................................................1

2.1 THE PRESENT SYSTEM....................................................................................5

2.2 Following are the Drawback is as follow..............................................................5

2.3 Available Solution for present system..................................................................5

2.3.1 Convert pdf to Audio...............................................................................................5

2.3.2 Time Factor..............................................................................................................6

2.4 Advantages of PDF to Audio Convert..................................................................6

CHAPTER 3 DESIGN OF PROPOSED SYSTEM...............................................................5

3.1 Proposed System...................................................................................................7

3.1.1 Convert pdf to Audio...............................................................................................7

v
 3.1.2 Time factor...............................................................................................................7

3.2 ARCHITECTURE................................................................................................7

3.3 WORK FLOW......................................................................................................8

3.4 Flow Chart.............................................................................................................9

3.5 FLOW CHART...................................................................................................10

3.6 Use Case Diagram...............................................................................................11

3.6.1 Actor......................................................................................................................11

3.6.2 Association.............................................................................................................11

3.6.3 Use Case................................................................................................................11

3.7 ERD (Entity Relation Diagram)..........................................................................12

3.8 Shared Preferences in Android............................................................................12

3.9 Data types that can be stored in Shared Preferences:..........................................12

3.10 Stored PDF to Audio File..................................................................................13

3.11 Tool used to build the Proposal System............................................................13

CHAPTER 4 TESTING....................................................................................................7

4.1 Introduction.........................................................................................................15

4.2 Test Plan..............................................................................................................15

4.3 Module testing.....................................................................................................15

4.4 Integrated testing.................................................................................................15

4.5 Deployment.........................................................................................................16

4.6 Black-Box Testing...............................................................................................16

4.7 Test Cases............................................................................................................16

CHAPTER 5 REFERENCE MANUAL & SCREEN SHOTS...............................................7

5.1 User Interface Design..........................................................................................18

5.2 Consistency.........................................................................................................18

5.3 Make Sense.........................................................................................................18

vi
 5.4 User Friendly.......................................................................................................18

5.5 Flexibility and Simplicity....................................................................................18

5.6 Efficiency............................................................................................................18

5.7 Front End.............................................................................................................19

5.8 Input Validation...................................................................................................19

5.9 General Page Design...........................................................................................19

5.10 Page Background...............................................................................................19

5.11 Login Area.........................................................................................................19

5.12 Main Page Area.................................................................................................20

5.13 Screen Shots......................................................................................................20

CHAPTER 6 REFERENCES............................................................................................16

Bibliography..............................................................................................................27

vii
 LIST OF FIGURES

Figure 1 Flow chart of Present App.....................................................................................................10

Figure 2 Use case diagram...................................................................................................................11
Figure 3 EDR (Entity Relation Diagram)............................................................................................12
Figure 4 Front Page Registration.........................................................................................................21
Figure 5 Home Login Screen...............................................................................................................22
Figure 6 App Home page.....................................................................................................................23
Figure 7 Upload PDF...........................................................................................................................24
Figure 8 Converting PDF to Audio......................................................................................................25
Figure 9 Listening Audio.....................................................................................................................26

LIST OF TABLES
Table 1 Test Case 1..............................................................................................................................17
Table 2 Test case 2...............................................................................................................................17
Table 3 Test Case 3..............................................................................................................................17

viii
 ABBREVIATIONS
SRS Software Require Specification
PC Personal Computer
APP Application
UML Unified Modeling Language
API Application Programming Interface
IDE Integrated Development Environment
NO Number
UC Use Case
TC Test Case
XML Extensible Mark-up Language
APK Android Package File

ix
 CHAPTER 1
INTRODUCTION
1.1 Project Definition

Reading PDF Files of 100 or more pages may cause problem in a professional life. For-
Example, irritation in eyes or getting bore while continuous reading. Something new should
develop that give comfort to reader. He doesn't need to watch computer screen for a long
period so you are required to develop an application which convert your PDF file into audio
file .Reading need full attention of reader so reader cannot perform any other task during
reading. However through this application, he can do multitasking. Moreover, visually
impaired people may also get benefit from this application. This application will handle only
a PDF File having paragraphs written in English.
In the current busy routine people do not have time to take book an spend time reading it,
instead every one need an alternative access to read the content. If a person is travelling, he\
she cannot read a book, instead of reading they can listen to it. Reading stories or essays or
any text can be arduous however an audio book would make the task easy, by reading the
text. However, an audio reading of text is convenient and do not require much concentration
as reading requires. When a person tends to read a book, it requires to invest his/her time in
reading. Whereas the audio book makes the task easy and user can perform their own task as
well as listening to the audio. In this project, I have implemented a simple pdf to audio
converter using Java (Android App). This App will ask the user to select any pdf file and will
count the pages in the pdf and extract data from the pdf page by page and read the extracted
data to the user after that will be converted into Audio.

1.2 Features
Following are some of the important features

 Registration and login

 User Dashboard

1
  Upload PDF File
 Convert PDF File into Audio
 Listen PDF File

1.3 Benefits: The prominent benefits of this application are:

 Save time

 Easily Listen Audio

 Benefits to People who has eye sight problem.

 Easier to old persons, patient, families

 Do multi-tasking with listen audio.

2
1.4 Tool used in the Project

1.4.1 Java

Java is a popular programming language, created in 1995. It is owned by Oracle, and

more than 3 billion devices run Java. It is used for: Mobile applications (especially
Android apps) Desktop applications. It is a simple programming language. Java
makes writing, compiling, and debugging programming easy. It helps to create
reusable code and modular programs. Java is a class-based, object-oriented
programming language and is designed to have as few implementation dependencies
as possible.

1.4.2 XML

Extensible Mark-up Language or XML: A mark-up language created as a standard

way to encode data in internet-based applications. Android applications use XML
to create layout files. Unlike HTML, XML is case-sensitive, requires each tag be
closed, and preserves whitespace.

1.4.3 SQLite

SQLite is an open source SQL database that stores data to a text file on a device.
Android comes in with built in SQLite database implementation. SQLite supports all
the relational database features. In order to access this database, you don't need to
establish any kind of connections for it like JDBC,ODBC etc.

1.3.4 Android Studio

It's the most basic tool for Android developers. Created by Google in 2013, it has
pretty much become the standard software for Android Developers. It's a great tool
because it has the support of Google as well as a large community of developers.

3
1.5 Scope

The proposed system is helping those peoples who have eye sight problem or getting bore
when learning pdf files. This App will help those peoples and easily can listen audio
instead of learning PDF Files. Users doesn't need to watch computer screen for a long
period so you are required to develop an application which convert your PDF file into
audio file .Reading need full attention of reader so reader cannot perform any other task
during reading. However through this application, he can do multitasking. Moreover,
visually impaired people may also get benefit from this application. This application will
handle only a PDF File having paragraphs written in English.

1.6 Feasibility

In feasibility study will determine whether the project should go ahead. The people
carrying out the study will take into account labor and material costs.

1.6.1 Operational Feasibility

Operational feasibility is an evaluation to determine whether the system is

operationally acceptable or not. It is also determining how the proposed
system will fit with current operational system and how will operator use the
proposed system. In the perspective of Operational feasibility this system does
not requires any high experience person to manage it and use it. So, this
website is operationally feasible.

1.6.2 Financial and Economic Feasibility

Financial feasibility is the analysis of a project's cost and revenue with the
Organization and determined that the organization is satisfied or not in term of
financial power. In the perspective of the financial feasibility this system is
very feasible. The cost and superiority of this system make it economically
feasible. The project will be a good investment of the organization. How much
spend on the website the organization will easily offer for it.

4
1.6.3 Technical Feasibility

Technical feasibility is attainability of a system using currently existing

technology. Technical feasibility means the required technology or resources
are available or not in terms of manpower and equipment’s. The project is
fully feasible as in the perspective of technical feasibility. The system does not
require any extra ordinary hardware. It runs on any condition of PC having
windows XP and windows 7 Window 8, 10. The technical feasibility
guaranties accuracy. So, the website is technically feasible because the
required hardware and equipment’s is available in the market.

5
 Chapter 2
Present System
2.1 THE PRESENT SYSTEM

The Blind and Dyslexic people would find it difficult to read, to support those people
different computer solutions have provided many alternative ways to convert text to audio.
Readings of a book are stored on tapes. Consortium and standardized in 2002 by the National
Information Standards Organization (NISO). The DTB standard describes how multimedia
information, such as audio files, text files and images are composed to create an audio book.
Many other solutions are to convert PDF files to MP3 players using third party applications
or web applications. Peoples have problem to read 100 of pages, it may create problem for
example, Getting peoples bore during reading, or irritation in eyes with continues reading.
He doesn't need to watch Mobile or Computer screen for a long period so you are required to
develop an application which converts your PDF file into audio file.

2.2 Following are the Drawback is as follow

 Eye sight problem

 Getting bore When reading Books

2.3 Available Solution for present system

2.3.1 Convert pdf to Audio

We create an Application which will convert pdf file to audio then Users can
easily listen pdf instead of reading pdf, Peoples can get bore when read
something, instead we build an App where User can easily Listen and get
work done.

6
 2.3.2 Time Factor

When you read something it will take lots of time as well, so in App user can easily
listen and it will not take too much time, because we know that when we read
something it is taking time, instead in App User can easily listen as well as do multi-
tasking as well.

2.4 Advantages of PDF to Audio Convert

PDF to audio converter project provides an alternative way to access the PDF Books
for blind, lazy, readers and others. Using PDF to Audio converter the user will be able
to listen to his/her favorite PDF and can do their daily routine. The application can be
used to read any PDF which will convert English Text into Audio.

7
 Chapter 3
Design of Proposed System
3.1 Proposed System

In this current busy routine people do not find time to read a book, or to convert the PDF file
into MP3 player using third party applications or web application. In this system I am
developing an application using Java to convert the PDF file into audio format and read out to
the user. The application is more used friendly as it not requires any audio file or MP3 player.
The user will have to select the PDF file which user wants to listen.

Following are some of the important reasons why Food delivery on running train is
important.

3.1.1 Convert pdf to Audio

We create an Application which will convert pdf file to audio then Users can easily
listen pdf instead of reading pdf, Peoples can get bore when read something, instead
we build an App where User can easily Listen and get work done.

3.1.2 Time factor

When you read something it will take lots of time as well, so in App user can easily
listen and it will not take too much time, because we know that When we read
something It is taking time, instead in App User can easily listen as well as do multi-
tasking as well.

3.2 ARCHITECTURE

PDF to Audio Converter is a Android application contains play, pause (buttons) and label to
display text which allows the user to select the PDF files and the user has to click on the play

8
button in order to extract text from PDF file and will read the text. The application has been
developed in a way that the until the speaker read’s out the extracted text the player cannot be
paused. The App is also, provided with a label to display the text, the text will only be
displayed only after reading the extracted text.

3.3 WORK FLOW

 In this PDF to Audio Converter the user needs to select any PDF file from the desired
location.
 After selecting the PDF file, the user needs to click Convert button.
 If the PDF file contains page numbers, the PDF file will be extracted..
 The extracted text will be then read.
 Now, after reading the text the text will be converted into audio.

9
3.4 Flow Chart

A flowchart is a diagram that depicts a process, system or computer algorithm. They are
widely used in multiple fields to document, study, plan, improve and communicate often
complex processes in clear, easy-to-understand diagrams. Flowcharts, sometimes spelled as
flow charts, use rectangles, ovals, diamonds and potentially numerous other shapes to define
the type of step, along with connecting arrows to define flow and sequence. They can range
from simple, hand-drawn charts to comprehensive computer-drawn diagrams depicting
multiple steps and routes. If we consider all the various forms of flowcharts, they are one of
the most common diagrams on the planet, used by both technical and non-technical people in
numerous fields. Flowcharts are sometimes called by more specialized names such as process
flow chart Process Map, Functional Flowchart, Business Process Mapping, Business Process
Modeling and Notation (BPMN), or Process Flow Diagram (PFD). They are related to other
popular diagrams, such as Data Flow Diagrams (DFDs) and Unified Modeling Language

(UML) Activity Diagrams.

10
3.5 FLOW CHART

SELECT PDF

If pdf has
greater than 7 If pdf has less than or equal to 7
thousand thousand characters
characters
Less than 7
thousand

Greater than 7
thousand
Read extracted text

Pdf will not be converted.

Convert to audio mp3

Exit
Exit

Figure 1 Flow chart of Present App

11
3.6 Use Case Diagram

3.6.1 Actor

An actor in use case modeling specifies, A role played by user or any other system
object that interact with the subject.

3.6.2 Association

A relationship between classes of objects that allows one object instance to cause
another to perform an action on its behalf.

3.6.3 Use Case

A use case is a methodology used in system analysis to identify, clarify and organize
system requirements.

Figure 2 Use case diagram

12
13
3.7 ERD (Entity Relation Diagram)

Figure 3 EDR (Entity Relation Diagram)

User Table
UserId

UserFirstName
userLastName
UserMobile
userEmail
userPassword

3.8 Shared Preferences in Android.

A Shared Preferences object points to a file containing key-value pairs and provides simple
methods to read and write them. Each Shared Preferences file is managed by the framework
and can be private or shared. This page shows you how to use the Shared Preferences APIs to
store and retrieve simple values.

3.9 Data types that can be stored in Shared Preferences:

 Boolean
 Int
 Long
 Float
 String
 stringSet
 Custom data structure

14
3.10 Stored PDF to Audio File.

We will save all the converted audio files in mobile phone directory.

App will automatically create this directory in any phone that has this “APP”.

DIR

Files/pdftoaud/

So all the converted files stored inside Files/pdftoaud folders.

3.11 Tool used to build the Proposal System.

In proposed System we will have lots of Tool to build the projects. In order to talk about the
project we will build Mobile App. We will use Technologies used in mobile app
development.

Tool Description
JAVA Java is a popular programming language,
created in 1995. It is owned by Oracle, and
more than 3 billion devices run Java. It is
used for: Mobile applications (especially
Android apps) Desktop applications. It is a
simple programming language. Java makes
writing, compiling, and debugging
programming easy. It helps to create
reusable code and modular programs. Java
is a class-based, object-oriented
programming language and is designed to
have as few implementation dependencies
as possible.

15
XML Extensible Mark-up Language or XML: A
mark-up language created as a standard
way to encode data in internet-based
applications. Android applications use
XML to create layout files. Unlike HTML,
XML is case-sensitive, requires each tag be
closed, and preserves whitespace.

SQLite SQLite is a open source SQL database

that stores data to a text file on a device.
Android comes in with built in SQLite
database implementation. SQLite supports
all the relational database features. In order
to access this database, you don't need to
establish any kind of connections for it like
JDBC, ODBC etc.

Android Studio It's the most basic tool for Android

developers. Created by Google in 2013, it
has pretty much become the standard
software for Android Developers. It's a
great tool because it has the support of
Google as well as a large community of
developers.

16
Chapter 4
Testing
4.1 Introduction

Testing is to check the working of the application that is it working in the desire way that we
want or not. It is an important phase in development it is also use to check the errors and bugs
in the application if any exits due to texting programmers are able to remove them from the
application.

4.2 Test Plan

Testing plan of Ambulance Tracking comprises of the following steps.

1) Module testing

2) Integrated testing

3) Deployment

4) Black-Box testing

4.3 Module testing

We made the PDF to Audio Converter which has login/register module, Select pdf module,
and convert to audio module, than listen audio file module.

4.4 Integrated testing

Then we combine all the modules together and then tested them. We combined all the main
modules and tested them as a whole like one application.

16
4.5 Deployment

We deployed this project on Android Phone (APK file)

4.6 Black-Box Testing

A strategy in which a software component is treated like an opaque box is called Black box
testing. In this testing strategy tests case designers’ focus on determining how well the
component conforms to the published requirements for the component, instead of worrying
about the implementation details.

Black box testing focuses on the functional requirement of the software. This testing strategy
enables us to derive sets of input conditions that willfully exercise all functional requirements
for a program. Black box testing is necessary and alternative to white box testing. Rather, it is
a complementary approach that is likely to uncover a different class of errors than white box
testing method. For the present system we have used Black Box Testing strategy.

Black box testing used to find following errors:

 Incorrect or missing functions.

 Interface errors.

 Performance errors.

 Initializing and termination errors.

4.7 Test Cases

Test cases are specifications of the inputs to the test and the expected output from the system.
The following test cases are used for this project.

17
Table 1 Test Case 1

Test Number 1

Test Name Reg/login

Actor User

Inputs Username and password

Explanation When I click on Submit button the form submitted successfully.

Result Form submitted successfully.

Table 2 Test case 2

Test Number 2

Test Name Upload PDF

Actor User

Inputs User select pdf file

Explanation When user select pdf It will convert pdf to Audio

Result Request Submitted.

18
Table 3 Test Case 3

Test Number 3

Test Name Listen PDF

Actor User

Inputs User click on any converted file in App

Explanation When user Click on any file in App will start audio and user can listen PDF.

Result Successfully Done.

19
 Chapter 5
Reference Manual & Screen Shots
5.1 User Interface Design

It is particularly important first to design how the system will look and respond to user be
before designing the website structure. The most critical and creative aspect of development
is to design the user interface. User interface design determines how the system will look for
the user from the outside. The basic design principles, considered the user interface design,
are the following.

5.2 Consistency

Consistency is the ability of user to predict that the software is going to do in each situation
based on the experience with the product. It means to provide the sets of behavior in the
response to user actions and generalize knowledge about one aspect of the system to other
aspects.

5.3 Make Sense

Good user interface gives user clues about what to do next in each situation. It means to
provide clear and obvious ways for the user to get something done.

5.4 User Friendly

To make the system user friendly, right level and right kind of response should be given to
user against each user action with an input device. Lack of proper feedback can be a big
problem when nothing appears to have happened. In design of many project proper and
immediate feedback is provide at different stages to make the system user friendly.

5.5 Flexibility and Simplicity

It means that system should be so simple and flexible that user is able to concentrate on
getting the task at hand done with a minimum of distraction. The system is also making
simple by redundancy.

5.6 Efficiency

Efficiency is an important feature in the designing user interface in efficient application

minimize the number of steps require to perform in operation and provide users with
shortcuts. My system requires minimum options and choices to improve efficiency.

20
5.7 Front End

In application used by the silent to access database engines or to present information to the
user is called frond end. My front-end tools are available in market. We have selected
macromedia dream weaver as a front end to access databases, because the dream weaver is
the fastest and easiest way to develop web application for windows.

Forms served as a window used to customize the interface of application. Controls, graphics
and pictures are added to the form to create a desired look. Forms are the foundation for
creating interface of an application. Forms can be used to add windows and dialog boxes to
application. Forms are container for other controls and objects.

Forms provide the data gathering functionality to the webpage. It is very useful if the web site
is used to advertised and sell products. Forms can automatically submit data collected in its
controls to a web server.

5.8 Input Validation

Input validation is a proactive process, it happens while data is being entered. It is the process
of checking the data entered by the user before that data is stored to the database. If an error
occurs from the user, then it should simply display meaningful display message

5.9 General Page Design

The web pages, of which the entire website is comprised of, have been designed in such a
way to streamline the page vs. information flow, so that the visitor may feel easy to navigate
through the website, yet comfortable with page layout. I have designed a page template, on
the basis of which all the other pages are presented on the visitor’s browser.

The web page is designed to best fit on a 1024*768 pixels resolution, but if it is viewed on a
800*600 pixels resolution, only the background will shrink, while the page size remain the
same at the center. This flexibility has been maintained because a considerable number of
visitors use 800*600 pixels resolution on their screen.

The various parts of the front end are explained as follows.

5.10 Page Background

This section contains light color.

5.11 Login Area

These are containing links to Admin area, User area, and vehicles.

21
5.12 Main Page Area

This section will contain the actual contents of the web page. It would elongate enough to
accommodate the contents.

5.13 Screen Shots.

Following are the screen shots of my Project.

22
Figure 4 Front Page Registration

23
Figure 5 Home Login Screen

24
Figure 6 App Home page

25
Figure 7 Upload PDF

26
Figure 8 Converting PDF to Audio

27
Figure 9 Listening Audio

28
Chapter 6 References
Bibliography

[1] Google, "Google.com," [Online]. Available: https://www.google.com. [Accessed sunday june

2022].

[2] Vikipedia, "Vikipedia.org," [Online]. Available: https://www.vikipedia.org. [Accessed sunday

june 2022].

[3] G. Search,
"https://www.irjmets.com/uploadedfiles/paper/volume2/issue_12._december_2020/5297/
1628083212.pdf," [Online]. Available:
https://www.irjmets.com/uploadedfiles/paper/volume2/issue_12._december_2020/5297/1
628083212.pdf. [Accessed sunday june 2022].

29