Professional Documents
Culture Documents
INTRODUCTION
1.1 OVERVIEW
The main purpose of the project is to develop an application called Non Visual
Search Engine for Visually Challenged is a need for web based application where we provide a
user friendly application for visually impaired people. This application works just like Google
search engine but with a new feature for visually challenged. The data entered anywhere on the
screen is taken into to a textbox with focus in it. So it gives all the results of it in a systematic
manner. When the user clicks the right mouse the first result is read heard. For next result, left
mouse is pressed. In this way the user can listen all the results of the required data.
In the flexibility of the uses the interface has been developed a graphics concept in
mind, associated through a browses interface. The GUI’S at the top level have been categorized
as Administrative user interface and the operational or generic user interface.
The operational or generic user interface helps the users upon the system in transactions
through the existing data and required services. The operational user interface also helps the
ordinary users in managing their own information helps the ordinary users in managing their
own information in a customized manner as per the assisted flexibilities.
2. ANALYSIS
The Word Wide Web has come to take an important part in our lives: it has become
indispensable for finding information, communicating with others, and performing daily tasks
for work, banking, and shopping. Web sites are designed mostly for graphical interaction,
limiting access for an entire community of people with visual disabilities. According to the
WHO’s World Health Report, there are approximately 45 million people without sight
worldwide. These people don’t have proper tool to get the information they want.
• Visually challenged people don’t have proper tool to get the information they want
• Fewer Users – Friendly.
A web based application is needed where we provide a user friendly application for
visually impaired people. This application works just like Google search engine but with a new
feature for visually challenged. The data entered anywhere on the screen is taken into to a
textbox with focus in it. So it gives all the results of it in a systematic manner. When the user
clicks the right mouse the first result is read heard. For next result, left mouse is pressed. In this
way the user can listen all the results of the required data.
3. IMPLEMENTATION
HARDWARE REQUIREMENTS:
The selection of hardware is very important in the existence and proper working of any
software. In the selection of hardware, the size and the capacity requirements are also
important.
Content Description
Min Max
HardDiskDrive 20GB 40GB
RAM 500MB 1GB
SOFTWARE REQUIREMENTS:
The software requirements specification is produces at the culmination of the analysis
tasks. One of the most difficult tasks is that, the selection of the software, once system
requirement is known by determining whether a particular software package fits the
requirements.
Content Description
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Xml;
using net.bing.api;
using SpeechLib;
using System.Data.SqlClient;
s = builder.ToString() + "\n" + s;
title1 = result.Title;
Console.WriteLine();
}
i = 0;
}
if (errors != null)
{
// Iterate over the list of errors and display error details.
Console.WriteLine("Errors:");
Console.WriteLine();
foreach (XmlNode error in errors)
{
foreach (XmlNode detail in error.ChildNodes)
{
Console.WriteLine(detail.Name + ": " + detail.InnerText);
}
Console.WriteLine();
}
}
}
}
protected void btnmail_Click(object sender, EventArgs e)
{
foreach (DataRow dr in dss1.Tables[0].Rows)
{
Response.Cookies["mydes"].Value = dr[r].ToString();
}
Response.Redirect("~/user/usermail.aspx");
}
}
This is the code for connecting to the bing search engine, storing the data content displayed into
the database. Retrieving the result from the database and converting them to speech. The code
also contains mouse click events.
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using SpeechLib;
using System.Net.Mail;
using System.Net;
}
protected void TextBox1_TextChanged(object sender, EventArgs e)
{
sp.Speak(txtto.Text, 0);
btnsend.Focus();
}
}
This code is used for sending the mail to a particular email id entered into the ‘to’ column. The
selected result will be sent as mail to the email id provided.
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Data.SqlClient;
}
void gvfill()
{
da = new SqlDataAdapter("select searchid,searchstring,timestamp,status from
usersearches", con);
ds = new DataSet();
da.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
}
}
This code is used for displaying the search results in a grid.
4. TEST CASES
Testing is one of the most important phases in the software development activity. In
software development life cycle (SDLC), the main aim of testing process is the quality; the
developed software is tested against attaining the required functionality and performance.
During the testing process the software is worked with some particular test cases and
the output of the test cases are analyzed whether the software is working according to the
expectations or not.
The success of the testing process in determining the errors is mostly depends upon the
test case criteria, for testing any software we need to have a description of the expected
behavior of the system and method of determining whether the observed behavior confirmed to
the expected behavior.
LEVELS OF TESTING
Since the errors in the software can be injured at any stage. So, we have to carry out the
testing process at different levels during the development. The basic levels of testing are Unit,
Integration, System and Acceptance Testing.
The Unit Testing is carried out on coding. Here different modules are tested against the
specifications produced during design for the modules. In case of integration testing different
tested modules are combined into sub systems and tested in case of the system testing the full
software is tested and in the next level of testing the system is tested with user requirement
document prepared during SRS.
There are two basic approaches for testing. They are:
FUNCTIONAL TESTING
In Functional Testing test cases are decided solely on the basis of requirements of the
program or module and the internals of the program or modules are not considered for selection
of test cases. This is also called Black Box Testing
STRUCTURAL TESTING
In Structural Testing test cases are generated on actual code of the program or module
to be tested. This is called White Box Testing.
TESTING PROCESS
A number of activities must be performed for testing software. Testing starts with test
plan. Test plan identifies all testing related activities that need to be performed along with the
schedule and guide lines for testing. The plan also specifies the levels of testing that need to be
done, by identifying the different testing units. For each unit specified in the plan first the test
cases and reports are produced. These reports are analyzed.
• TEST PLAN:
o Test plan is a general document for entire project, which defines the scope,
approach to be taken and the personal responsible for different activities of
testing. The inputs for forming test plans are
o Project plan
o Requirements document
o System design
• TEST CASE SPECIFICATION:
Although there is one test plan for entire project test cases have to be specified
separately for each test case. Test case specification gives for each item to be tested. All test
cases and outputs expected for those test cases.
• TEST CASE EXECUTION AND ANALYSIS:
The steps to be performed for executing the test cases are specified in separate
document called test procedure specification. This document specify any specify
requirements that exist for setting the test environment and describes the methods and
formats for reporting the results of testing.
• UNIT TESTING:
Unit testing mainly focused first in the smallest and low level modules,
proceeding one at a time. Bottom-up testing was performed on each module. As developing
a driver program, that tests modules by developed or used. But for the purpose of testing,
modules themselves were used as stubs, to print verification of the actions performed. After
the lower level modules were tested, the modules that in the next higher level those make
use of the lower modules were tested. Each module was tested against required functionally
and test cases were developed to test the boundary values.
• 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. As the
system consists of the number of modules the interfaces to be tested were between the
edges of the two modules. The software tested under this was incremental bottom-up
approach. Bottom-up approach integration strategy was implemented with the following
steps. Low level modules were combined into clusters that perform specific software sub
functions. The clusters were then tested.
• SYSTEM TESTING:
System testing is a series of different tests whose primary purpose is to fully exercise
the computer-based system. It also tests to find discrepancies between the system and its
original objective, current specifications.
5.OUTPUT SCREENS
Search engine
Default Preferences
User preferences
Master Preferences
Action prompt
Logout Screen
6. CONCLUSION
It has been a great pleasure for me to work on this exciting and challenging project.
This project proved good for me as it provided practical knowledge of not only programming in
ASP.NET and C#.NET Frameworks web based application and no some extent Windows
Application but also about all handling procedure related with “Non Visual Search Engine for
Visually Challenged”. It also provides knowledge about the latest technology used in
developing web enabled application and client server technology that will be great demand in
future. This will provide better opportunities and guidance in future in developing projects
independently.
7. FUTURE ENHANCEMENTS
• The entire actions performed by the user are stored in the database i.e the right click and
the left click whenever they are clicked.
• Preference types are given to the user so that he can search it with more ease.
8. REFERENCES
• FOR SQL
• www.msdn.microsoft.com
• FOR ASP.NET
• www.msdn.microsoft.com/net/quickstart/aspplus/default.com
• www.asp.net
• www.fmexpense.com/quickstart/aspplus/default.com
• www.asptoday.com
• www.aspfree.com
• www.4guysfromrolla.com/index.aspx