0% found this document useful (0 votes)
103 views40 pages

Voice Based Email System

Voice Based Email System For Blinds This is one of android application. This project used to avoid the traditional typing practices which impossible to visually impaired people. So it is more beneficial to the blinds people for communication. Application will totally controlled by voice.

Uploaded by

Meghana Khuspe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
103 views40 pages

Voice Based Email System

Voice Based Email System For Blinds This is one of android application. This project used to avoid the traditional typing practices which impossible to visually impaired people. So it is more beneficial to the blinds people for communication. Application will totally controlled by voice.

Uploaded by

Meghana Khuspe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 40

VOICE BASED MAILING SYSTEM

FOR BLINDS

A Project Report

Submitted in partial fulfillment of the


requirements for the award of the Degree
of
MASTER OF SCIENCE (INFORMATION TECHNOLOGY)
By

Ms. Meghana Khuspe Seat No. :0103639

Ms. Diksha Sharma Seat No. :0103753

Under the esteemed guidance of

Ms. Seema Vishwakarma


Assistant Professor, Department of Information Technology

DEPARTMENT OF INFORMATION TECHNOLOGY

VIDYALANKAR SCHOOL OF INFORMATION TECHNOLOGY


(Affiliated to University of Mumbai)
MUMBAI, 400 037
MAHARASHTRA
2021 - 2022
VIDYALANKAR SCHOOL OF INFORMATION TECHNOLOGY
(Affiliated to University of Mumbai)
MUMBAI-MAHARASHTRA-400037
DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE
This is to certify that the project entitled, " Voice Based Mailing System For Blinds", is
bonafied work of Ms. Meghana Pandurang Khuspe bearing Application ID:127040
and Ms. Diksha Vinay Sharma bearing Application ID:128235 submitted in partial
fulfilment of the requirements for the award of degree of MASTER OF SCIENCE in
INFORMATION TECHNOLOGY from University of Mumbai.

Internal Guide Coordinator

Internal Examiner External Examiner

Date: College Seal Principal


ABSTRACT

Internet has become one of the basic amenities for day-to-day living. However,
blind people face difficulties in accessing these text materials, also in using any
service provided through internet. We describe the Voicemail system architecture that
can be used by a Blind person to access e-Mails easily and efficiently. The
contribution made by this research has enabled the Blind people to send and receive
Voice Based Mail messages in their language with the help of a Mobile Application.

In the current Email system, they need to type text and then can proceed. But
Blind people cannot access this type of system. Therefore, we came up with our
project as Voice Based mail system for blinds which will help a lot to visually
impaired peoples and also illiterate peoples for sending their mails.
ACKNOWLEDGEMENT
It gives me immense pleasure in expressing my heartfelt thanks to the people who
were part of this project in numerous ways. I owe my thanks to all those who gave endless
support right from the conception of the project idea to its implementation, it would not have
materialized without the help of many.

The dedication, hard work, patience and correct guidance makes any task proficient &
a successful achievement. Intellectual and timely guidance not only helps in trying
productive but also transforms the whole process of learning and implementing into an
enjoyable experience.

With immense gratitude, I would like to convey my special honor and respect to
“Ms. Seema Vishwakarma” (Project Guide) who took keen interest in checking the
minute details of the project work and guided us throughout the same.

A sincere thanks to the non-teaching staff for providing us with the long lab timings
that we could receive along with the books and with all the information we needed for this
project, without which the successful completion of this project would not have been
possible.

Finally, I wish to avail this opportunity & express a sense of gratitude and love to my
friends and my beloved parents for their support, strength and help for everything.

Ms. Meghana P. Khuspe Ms. Diksha Vinay Sharma


DECLARATION
I hereby declare that the project entitled, “Voice Based Mailing System for Blinds” done at
Vidyalankar School of Information Technology, has not been in any case duplicated to
submit to any other universities for the award of any degree. To the best of my knowledge
other than me, no one has submitted to any other university.

The project is done in partial fulfillment of the requirements for the award of degree of
MASTER OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final
semester project as part of our curriculum.

Name and Signature of Students


Sr. TITLE Page
No. No.
1. INTRODUCTION
1.1 Background
1.2 Problem statement
1.3 Scope
1.4 Feasibility study
1.5 Objectives
2. Literature review
2.1 Introduction
2.2 Literature review
2.3 Comparative analysis
2.4 Research gap
3. System Design and modelling
3.1 Introduction
3.2 Information requirement gathering and analysis
3.3 System modelling
3.4 Database analysis and modelling
3.5 System diagram
Chapter1:

1. INTRODUCTION

1.1 Background

In the current Email system, they need to type text and then can proceed. But Blind people
cannot access this type of system. Therefore, we came up with our project as Voice based
email system for blinds which will help a lot to visually impaired peoples and also illiterate
peoples for sending their mails.

“Voice Based Email System for Blinds” is one of the best solution for maintaining
communication between visually impaired people. Traditional keyboard typing is difficult to
visually impaired and blind people as they need to be dependent on others for same time.
It’s useful for anyone who finds typing difficulty, painful or impossible. Therefore, we came
up with our project as Voice based email system for blinds which will help lot of people for
sending emails.

The complete system will work on just speech command. Firstly, any user wish to use the
system will register to obtain user name and password by speech.

The complete study of the project in terms of input, processes, output, fields, programs and
procedures. It is a very effective tool for long term planning and trouble shooting. The
primary aim of a technical feasibility study is to remove uncertainty. Since the present value
of a proposed project depends on the probability of its success. Proposed project can be
compatible on every version of windows system.

It refers to the measure of solving problems with the help of a new proposed
system. It helps in taking advantage of the opportunities and fulfils the requirements as
identified during the development of the project. To operate the proposed project no need to
require any technical knowledge.
1.2 Problem statement

 The visually challenged people find it very difficult to utilize this technology because
of the fact that using them requires visual perception. However not all people can use
the internet.

 This is because in order to access the internet you would need to know what is
written on the screen. If that is not visible it is of no use. This makes internet a
completely useless technology for the visually impaired and illiterate people.

 The users of this system don’t need to remember any basic information about
keyboard shortcuts as well as location of the keys. Simple speaking operations are
needed for functions making system easy to use for user of any age group.

 Our system provides location of where user is prompting through voice so that user
doesn’t have to worry about remembering which mouse click operation, he/she wants
to achieve.

 The main objective for his project is that it provides very convenient way
to messaging system using Voice based mail system.
.
1.3 Scope

 For people who can see, e-mailing is not a big deal, but for people who are not
blessed with gift of vision it postures a key concern because of its intersection
with many vocational responsibilities.

 This Voice based email system has great application as it is used by blind people
as they can understand where they are. E.g., whenever cursor moves to any icon on
the website say Register it will sound like “Register Button”.

 There are many screen readers available. But people had to remember mouse clicks.
Rather, this project will reduce this problem as mouse pointer would read out where
he/she lies.

 This system focuses more on user friendliness of all types of persons including
regular persons, visually compromised people as well as illiterate.
1.4 Feasibility study

A feasibility study is an analysis that takes all of a project's relevant factors into account—
including economic, technical, and operational considerations—to ascertain the likelihood of
completing the project successfully. Feasibility study is an assessment of thepracticality of a
proposed project or system.

 Technical feasibility study is the complete study of the project in terms of input,
processes, output, fields, programs and procedures. It is a very effective tool for long
term planning and trouble shooting. The primary aim of a technical feasibility study is
to remove uncertainty. Since the present value of a proposed project depends on the
probability of its success. Proposed project can be compatible on every version of
windows system. Also, it can be adopt any future modification as well as update in the
system.

 Operational feasibility refers to the measure of solving problems with the help of a
new proposed system. It helps in taking advantage of the opportunities and fulfils
the requirements as identified during the development of the project. To operate the
proposed project no need to require any technical knowledge.

 Economic feasibility analysis is the most commonly used method for determining the
efficiency of a new project. It is also known as cost analysis. It helps in identifying
profit against investment expected from a project. Cost and time are the most essential
factors involved in this field of study. Economic feasibility refers to the feasibility of
the considered project to produce economic.
1.5 Objectives

 The main objective for his project is that it provide very convenient way to
messaging system using Voice based email system.

 Visually impaired people can use very efficiently since there is no need to typing
and Seeing task.

 It will very beneficial for student use for communication like other normal student.
Chapter 2: Literature review
2.1 Introduction

The current system used by the user is simply based on keyboard typing for
communication. Traditional keyboard typing is difficult to visually impaired and
blind people as they need to be dependent on others for same time. It’s useful for
anyone who finds typing difficulty, painful or impossible. Although technology is
already widely available, voice recognition software provides an alternative to
typing on a keyword. According to survey, around 39 million people are blind and
with that some are having low vision, some are above 50 years aged people also
some are illiterate.
2.2 Literature review

This section focuses on the area technologies/ techniques available for visually impaired
peoples.

 Smart guide for blind people this paper focuses the movement of blind person by
warning him/her about any nearby obstacles in order to help him/her during daily
tasks. The instruction will be provided in the form of audio instructions through
the headset and based on real-time situation for both indoor and outdoor
environments.

 The ultrasonic sensors, the system can detect any obstacles These sensors calculate the
distance by comparing the strength of the received signal with the transmitted signal.
It can detect static and moving obstacles, such as crossing people.

 Gesture Design for Visually Impaired People on Mobile Platforms is A Systematic


Literature Review is understand and analyse the gesture design for visually impaired
people on mobile devices and problems faced by them while using eyes-free design
solutions had been analyse. Like if a blind user perform incorrect gesture it may lead
to unwanted output and the user may not know how to revert back the previous
action.

 Kaneet. al. proposed an application named as Slide Rule that uses gestures as its input
and gives audio feedback to blind users to allow them to use smartphones easily.
Slide Rule incorporates multi-touch interactions on mobile phone touchscreens. How
error occurs while using the application. The results concluded that difficulty was
experienced mostly when number of fingers used and the number of strokes is to be
performed.

 Text reader for Visually impaired person paper proposes an inexpensive mobile
application which is designed for the visually impaired person. For read or write,
blind person uses Braille’s system.

 This mobile application is able to capture the image of printed material with a
mobile camera. The captured image is then converted to text by using image-to-text
conversion in Optical Character

 Recognition (OCR) framework. Finally, the text will be read out into speech format
using text-to-speech conversion in Text to Speech (TTS) framework.

 Mobile Vision as Assistive Technology for the Blind: An Experimental Study


The paper focuses on a specific mobile vision task: detection of “landmarks” in the
environment, along with mechanisms to guide a person to-wards a detected landmark
without sight. Discovery and guidance components of this task. for example the blind
person visiting an office building, looking to find the office of Dr.
A.B. He or she may walk through the corridor (while using a white cane or a
dog guide for mobility), using the camera phone to explore the walls in search
of a tag with the desired information. The vision algorithm implemented in the camera
phone can be programmed to identify tags and read the text in each tag.

2.3 Comparative Analysis:

 There are many technologies that have been developed different systems to help
the visually impaired people in their daily lives.

 Smart guide for blind people focuses the movement of blind person by warning
him/her about any nearby obstacles in order to help him/her during daily tasks It
consist of A 9V battery is used to run the system, where the voltage will be converted
down to 5V using the voltage regulator. The brain of the system is the PIC
microcontroller 16F877 receive the input data and process it in order to give the
relevant instructions to the vibrator and the audio chip. The input of the system
comes from ultrasonic sensors that measure the distance of the surrounding obstacles
and then supplies the stream of real-time data to the PIC microcontroller. three
ultrasonic sensors are used, one for the front detection and the other two for the left
and right detection.

 Text reader for Visually impaired person is a mobile application which is designed
for the visually impaired person. For read or write, blind person uses Braille’s system
which is less compared to visually able people. Following is the process,
The taken image act as input and image is processed system using OCR image is
converted to text, then the obtained text is converted in speech using TTS module.

 Voice based Email system, We describe the Voicemail system architecture that can be
used by a Blind person to access e-Mails easily and efficiently. This research will
enabled the Blind people to send and receive voice based e-Mail messages in their
language with the help of a Mobile Application. This will enable the visually
impaired to carry their daily task easily.

2.4 Research Gap:


 After exploring different technologies we are implementing Voice based email
system for visually impaired person. The visually challenged people find it very
difficult to utilize this technology because of the fact that using them requires visual
perception. However not all people can use the internet.
 This is because in order to access the internet you would need to know what is
written on the screen. If that is not visible it is of no use. This makes internet a
completely useless technology for the visually impaired and illiterate people. The
users of this system don’t need to remember any basic information about keyboard
shortcuts as well as location of the keys.
 Simple speaking operations are needed for functions making system easy to use
for user of any age group. Our system provides location of where user is
prompting
through voice so that user doesn’t have to worry about remembering which mouse
click operation he/she wants to achieve or which gesture he/she needs to perform for
any operation.

Chapter 3:
System Design and modelling
3.1 Introduction

“Voice Based Email System for Blinds” is one of the best solutions for maintaining
communication between visually impaired people. Traditional keyboard typing is difficult to
visually impaired and blind people as they need to be dependent on others for same time.
It’s useful for anyone who finds typing difficulty, painful or impossible. Therefore, we came
up with our project as Voice based email system for blinds which will help lot of people for
sending emails. The complete system will work on just speech command. Firstly, any user
wish to use the system will register to obtain user name and password by speech.
3.2 Information requirement gathering and analysis

 Requirement Analysis is the initial phase of every software project management


lifecycle. Aim of project Voice based email system for blinds is that system which is
the very user friendly to the visually impaired person. So main requirement of the
proposed system is that user no need to handle that system using any visualization or
typing using keyboard. The system will be handle using voice only. Also, user wants
the confirmation for their input, so system will provide feedback for input.

 After deciding requirement, next phase is we have predefined the software or system
design. In proposed system, user first register themselves in system using username
and password. Then, when user wants to use the system, they have login it in system
and they proceed further. User can send, receive as well delete the mails.

 For better implementation, while designing the system we have divide the system into
units so that it can be very easier to build the system. After implementing every unit
or modules, we have to integrate that module for overall system. After implementing
whole system, we have to test unit by unit sequentially. This is called as System
Testing. It is more beneficial for detecting and solving errors.

 It maintains every communication message that store in the system which can be
helpful for future use. The messages that are sent by user, it will store in Sent and the
messages that are receive by user are store in Inbox. New messages can be created by
using Compose. Also unwanted messages can be deleted in Trash. In this way, system
can be maintained.
3.3 System modelling

 Basic Modules:

 Admin:

o Admin logs in the system and validates admin username and password. It
alerts the valid or invalid username and password notification.

o Admin register in the system for future use. Only registered admin can
access the use of system.

o The person who wants to access the system, they must be registered and can
become admin. After registering first time, for next time they just have to
login themselves in system.

o So that system will identified the user and provide access, otherwise denied.

 User:

o User also wants to register in system so that they can access the use of system.

o Admin and user are the two person can communicate with each other.

o When we use the system that time we will become admin and other will user.

 Compose:

o When user wants to send the message to other user , that time compose used .

o In Compose, user has to type Username and then main message .

o After completion of above, user has to say ‘send’.

 Inbox:

o User Will Hear the messages in Inbox


3.4 Database Analysis and Modelling

 Database Design:
Our system maintains a database for user validation and storing mails of the user. There
are a total of five tables. The Inbox, Sent-Mail schemas will store all mails of the
respective service that belongs to that particular user.

 Database Table:

Registration Table

Sr.No. Field Data type Null Key Default

1 Username Varchar (20) No Primary Key <null>


2 FullName Varchar (20) No <null>
3 Age Integer (20) No <null>
5 Password Varchar (20) No <null>
6 Confirm Varchar (20) No <null>
password

Inbox Table

Sr.No. Field Data Type Null Key Default


1 Username Varchar (20) No <null>
2 mail Varchar (20) No <null>

Message Table

Sr.no. Field Data Type Null Key Default


1 id Varchar (20) No Primary key <null>
2 To Varchar (20) No <null>
3 Message Varchar (20) No <null>
4 sender Varchar (20) No <null>
5 Receiver Varchar (20) No <null>

Deleting and Updating Table

Sr.No. Field Data Type Null Key Default


1 Firstname Varchar (20) No <null>
2 Last name Varchar (20) No <null>
3 Email Id Varchar (20) No Primary key <null>
4 Contact no. Int (20) No <null>
5 Date of birth Varchar (20) No <null>
 Data Integrity and constraints:

 Referring the centralization of information about the management of system making


it well secure is the first thing as the accuracy and the consistency of data been safely
store.
 According to the system being design, there is the genuine need of validity of the
registered user’s data and their privacy integrity. In addition, phone numbers provided
must be numeric making it sure that number should not exceed more than ten numbers
and specifying that the current details is mandatory with an asterisk mark for the
following.
 The other will be that the password mode will be in hidden format and safe along
with the characters being type will be in capital.
3.5 System Diagram
Use case Diagram:

A Use case diagram at its simplest is a representation of a user’s interaction with the system
that shows the relationship between the user and the different use cases in which the user is
involved.

Use case diagram represents the Email system. There are six use cases such as view mail,
send mail, receive mail, manage mail, parameters and manage all accounts. There are two
actors i.e., USER and ADMINISTRATOR. The send mail use case includes parameters
such as sender, receiver and data.
Chapter 4: Methodology
4.1 Introduction

“Voice Based Email System for Blinds” is one of the best solutions for maintaining
communication between visually impaired people. Traditional keyboard typing is difficult to
visually impaired and blind people as they need to be dependent on others for same time. It’s
useful for anyone who finds typing difficulty, painful or impossible. Therefore, we came up
with our project as Voice based email system for blinds which will help lot of people for
sending emails. The complete system will work on just speech command. Firstly, any user wish
to use the system will register to obtain user name and password by speech.

4.2 Flow Chart of proposed methodology

4.3 Description of methodology used

The following section presents the complete set of functional and non-functional requirement.
Functional requirement of client listed first, according to their relationship to the overall system. The
non-functional requirements that pertain to security to the interface, human interaction, maintenance are
subsequently presented. With the underline software system taking responsibility for user’s operation
throughout its lifecycle, not only its accuracy ensured, but all the actions are logged in a database for
analysis an accuracy of client.
Following are the tools that we are using for this proposed system.
 Android Studio
 SQLite
 SPEECH-TO-TEXT google api
 TEXT-TO-SPEECH gogle api

Chapter 5 : Results, Analysis and Discussion

 After Launching Software LOGIN Form appear.


 If username is correct and password is wrong.

 If both username and password are correct.


 REGISTRATION Form appear like.
 When all textboxes are filled and data is correct.
 COMPOSE Form appear like.
 If receiver’s username is not exists in database.
 When message sent successfully.
 INBOX Form appear like.
 CALL or PHONE DIAL page appear like
 Registration Database Table
 Message Database Table

Chapter 6 :Implementation And Testing


package com.example.vbesfb;

import android.content.ActivityNotFoundException;
import android.content.Context;
import android.content.SharedPreferences;
import android.database.Cursor;
import android.database.sqlite.SQLiteDatabase;
import android.os.Bundle;
import android.app.Activity;
import android.content.Intent;
import android.os.Handler;
import android.speech.RecognizerIntent;
import android.speech.tts.TextToSpeech;
import android.speech.tts.TextToSpeech.OnInitListener;
import android.view.View;
import android.widget.Button;
import android.widget.EditText;
import android.widget.ImageButton;
import android.widget.Toast;

import java.util.ArrayList;

enum RegistrationField1 {
USER_NAME, PASSWORD;
}

public class LoginActivity extends Activity implements OnInitListener {


protected static final int RESULT_SPEECH_TO_TEXT = 1;
protected static final int RESULT_TEXT_TO_SPEECH = 2;
public static final String MY_PREFERENCE="com.example.vbesfb";
public static final String IS_LOGGED_IN ="isLoggedIn";
public static final String FROM_USER_ID ="fromUserId";

SharedPreferences sharedPreferences;
EditText userName, password;
RegistrationField1 enumRegistrationField1;
Button Submit, Register;
ImageButton btnSpeak1;
TextToSpeech tts;
DataBaseHelper mydb;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_login);

sharedPreferences=getSharedPreferences(MY_PREFERENCE,
Context.MODE_PRIVATE);
boolean isLogin = sharedPreferences.getBoolean(IS_LOGGED_IN,false);
if(isLogin)
{
startActivity(new Intent(LoginActivity.this, InboxActivity.class));
finish();
}

mydb = new DataBaseHelper(this);

userName = (EditText) findViewById(R.id.txtUserName);

password = (EditText) findViewById(R.id.txtpassword);

btnSpeak1 = (ImageButton) findViewById(R.id.btnSpeak);


Submit = (Button) findViewById(R.id.submit);
Register = (Button) findViewById(R.id.register);

Intent i = new Intent();


i.setAction(TextToSpeech.Engine.ACTION_CHECK_TTS_DATA);
startActivityForResult(i, RESULT_TEXT_TO_SPEECH);

btnSpeak1.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
initSpeaker();
}
});

userName.setOnFocusChangeListener(new View.OnFocusChangeListener() {
@Override
public void onFocusChange(View v, boolean hasFocus) {
if (hasFocus) {
tts.speak("Enter user name", TextToSpeech.QUEUE_FLUSH, null);
enumRegistrationField1 = RegistrationField1.USER_NAME;
initSpeaker();
}
}
});

password.setOnFocusChangeListener(new View.OnFocusChangeListener() {
@Override
public void onFocusChange(View v, boolean hasFocus) {
if (hasFocus) {
tts.speak("Enter passcode", TextToSpeech.QUEUE_FLUSH, null);
enumRegistrationField1 = RegistrationField1.PASSWORD;
initSpeaker();

}
}
});

Submit.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
loginUser();
}
});
}

@Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
super.onActivityResult(requestCode, resultCode, data);
if (requestCode == RESULT_TEXT_TO_SPEECH) {
if (resultCode == TextToSpeech.Engine.CHECK_VOICE_DATA_PASS) {
tts = new TextToSpeech(this, this);
} else {
Intent i = new Intent();
i.setAction(TextToSpeech.Engine.ACTION_INSTALL_TTS_DATA);
startActivity(i);
}
} else {

if (resultCode == RESULT_OK && null != data) {

ArrayList<String> text = data


.getStringArrayListExtra(RecognizerIntent.EXTRA_RESULTS);
switch (enumRegistrationField1) {
case USER_NAME:
userName.setText(text.get(0));
password.requestFocus();
break;

case PASSWORD:
password.setText(text.get(0));
loginUser();
break;
}
}
}
}

@Override
public void onInit(int status) {
if (status == TextToSpeech.SUCCESS) {
tts.speak("Welcome to Login Page.", TextToSpeech.QUEUE_FLUSH, null);
new Handler().postDelayed(new Runnable() {
@Override
public void run() {
userName.requestFocus();
}
}, 4000);
}

if (status == TextToSpeech.ERROR) {
Toast.makeText(getApplicationContext(), "Device is not Compatible",
Toast.LENGTH_SHORT).show();
}
}

private void initSpeaker() {


new Handler().postDelayed(new Runnable() {
@Override
public void run() {
Intent intent = new
Intent(RecognizerIntent.ACTION_RECOGNIZE_SPEECH);
intent.putExtra(RecognizerIntent.EXTRA_LANGUAGE_MODEL, "en-US");
try {
startActivityForResult(intent, RESULT_SPEECH_TO_TEXT);
} catch (ActivityNotFoundException a) {
Toast.makeText(getApplicationContext(),
"Opps! Your device doesn't support Speech to Text",
Toast.LENGTH_SHORT).show();
}
}
}, 1000);
}

public void loginUser() {


SQLiteDatabase db = mydb.getReadableDatabase();
String strUserName = userName.getText().toString().trim();
String strPassword = password.getText().toString().trim();
if (strPassword.isEmpty() || strUserName.isEmpty()) {
Toast.makeText(this,"Invalid Username or password.",
Toast.LENGTH_SHORT).show();
tts.speak("Please make sure you entered both username and password. ",
TextToSpeech.QUEUE_FLUSH, null);
this.userName.requestFocus();
} else {
Cursor c = db.rawQuery(
"Select * from " +
DataBaseHelper.REGISTRATION_TABLE_NAME
+ " where " + DataBaseHelper.UserName
+ " = '" + strUserName + "'", null);
if (c != null) {

if (c.getCount() > 0) {
if (c.moveToFirst()) {
String loginUsername =
c.getString(c.getColumnIndexOrThrow(DataBaseHelper.UserName));
String loginPassword =
c.getString(c.getColumnIndexOrThrow(DataBaseHelper.Password));
final long userId =
c.getLong(c.getColumnIndexOrThrow(DataBaseHelper.Id));

if(loginUsername.equals(strUserName) &&
loginPassword.equals(strPassword)){
Toast.makeText(this,"Successfully Logged in.",
Toast.LENGTH_SHORT).show();
tts.speak("you have successfully logged in.",
TextToSpeech.QUEUE_FLUSH, null);

new Handler().postDelayed(new Runnable() {


@Override
public void run() {
Intent intent = new Intent(LoginActivity.this,
InboxActivity.class);
startActivity(intent);

SharedPreferences.Editor editor =
sharedPreferences.edit();
editor.putBoolean(IS_LOGGED_IN,true);
editor.putLong(FROM_USER_ID, userId);
editor.commit();

finish();
}
}, 3000);
}
else
{
Toast.makeText(this,"Username or password mismatched",
Toast.LENGTH_SHORT).show();
tts.speak("OOps! User name or password not matched.",
TextToSpeech.QUEUE_FLUSH, null);
new Handler().postDelayed(new Runnable() {
@Override
public void run() {
clearText();
userName.requestFocus();
}
}, 3000);

}
}

} else {

Toast.makeText(this,"Not registered with us.",


Toast.LENGTH_SHORT).show();
tts.speak("OOps! You have not register with us. we are redirect
you on registration page.", TextToSpeech.QUEUE_FLUSH, null);

new Handler().postDelayed(new Runnable() {


@Override
public void run() {
Intent i = new Intent(LoginActivity.this,
RegistrationActivity.class);
startActivity(i);

finish();

}
}, 4000);

}
}
}
}

private void clearText() {


userName.setText("");
password.setText("");
}
}

Chapter 6: CONCLUSION

 Conclusion
In the existing system, the communication through messaging are done by typical keyboard typing
which is impossible to the Blind people. But in Proposed system, this drawback of typical is
eliminated completely.
Existing system includes following points:
 Typical keyboard Typing.
 User interface by touching screen is more.
 System feedback through seeing only which is useless to blind people.

The aim to proposed system is to develop a system for blind people convenience. The proposed
system can overcome all the limitation of existing system.
Proposed system includes following points:
 Avoid traditional keyboard typing
 System feedback is provided using voice for blind people
 Not only messages but calling also done.
 All Instructions are given to the user in the form of voice
 More convenient to the blind people
 Totally handled by voice
At the end, it is concluded that we have made effort on following points:
 A description of the background and context of the project and its relation to work
already done in the area.
 The description of Purpose, Scope and Applicability.
 We define the problem on which we are working in the project.
 We describe the requirement Specifications of the system and the actions that can be
done these things.
 We understand the problem domain and produce a model of the system by which
describe operations that can be performed on the system.
 Finally the system is implemented and tested according to the test cases.

 Limitation of System
Although I have put my best efforts to make the software flexible, easy to operate but limitations
cannot be ruled out even by me.
List of Limitation which is available in the VOICE BASED EMAIL SYSTEM FOR BLINDS:
If any people having bad pronunciation, then this app is useless for them.
It takes all noises in crowed.

 System Maintenance
The softare will definitely undergo change once it is delivered to the customer.There can be many
reasons for this change to occur. Change could because of some unexpected input values to the
system. The software should be developed to accommodate change that could happen during post
implementation period.

 References
 https://www.tutorialpoint.com/android
 https://www.geeksforgeeks.org
 https://www.java-samples.com

You might also like