Document Reader
Document Reader
Abstract
The Application is built using Vb.Net; Our Application is used to read the
multiple documents such as pdf file, word file, text file and rtf file,
The Application can be used to view multiple documents, It uses the Text to
Speech Engine for Reading the particular document that is being uploaded
by the user, The User can Select different speech readers such as male and
female, The user has also control over the volume and the rate of the speech
function of our application,
The User can pause the speaker from reading the given (uploaded) file, the
user can select the particular text that he/she want the application to read,
When the Speaker Reads the Text from the uploaded file that particular text
or word gets highlighted
The application Aims to Read/View Multiple document with some special
features such as STOP, PAUSE, VOLUME, RATE OF SPEECH, selection of
voice(MALE/FEMALE)
Operating Environment
.NET Framework
Visual Studio 2008
HARDWARE REQUIREMENTS:
SOFTWARE REQUIREMENTS:
Application Uses
API for Text-to-Speech
Applications can control text-to-speech (TTS) using interopspeechlib.dll Component Object
Model (COM) interface. Once an application has created an object, the application only needs a
call to generate speech output from some text data. In addition, this interface also provides
several methods for changing voice and synthesis properties such as speaking rate output
volume and changing the current speaking voice
Special SAPI controls can also be inserted along with the input text to change real-time
synthesis properties like voice, pitch, word emphasis, speaking rate and volume. This synthesis
markup sapi.xsd, using standard XML format, is a simple but powerful way to customize the
TTS speech, independent of the specific engine or voice currently in use.
This method can operate either synchronously (return only when completely finished speaking)
or asynchronously (return immediately and speak as a background process).
Technology Used
VB.NET:
Visual Studio .NET is now built on top of the .NET Framework. The .NET Framework takes
application development to viewing the Internet as your new operating system. Your applications
will no longer recognize hardware as a boundary limitation. This is an evolution of the Windows
DNA model. This new framework is built on open Internet protocols for a standardized
interoperability between platforms and programming languages. The .NET Framework will also
allow the creation of new types of applications. Applications will now run using the Common
Language Runtime (CLR). All .NET applications will use this same runtime environment, which
allows your Visual Basic applications to run on equal ground with other languages.
The CLR allows Visual Basic to provide inheritance and free threading, whose absence created
two glaring limitations to Visual Basic Applications. Visual Basic .NET is object-oriented.
Everything is now an object, and every object is inherited from a standard base class.
Another benefit of the CLR is a common type system, which means that all programming
languages share the same types. This greatly increases interoperability between languages.
The Internet has entered a new phase. First, it was used to display static Web pages. Businesses
soon found that this did not help them significantly. Next, the Internet evolved to dynamic
content and allowing electronic commerce. The next step is to move towards complete
applications running on the Internet. Visual Basic .NET promotes these new Web applications.
Web services allow objects to be located anywhere on the Internet and to be called from any
application across the Internet (no more trying to get DCOM configured). Of course, extending
applications across the Internet will increase security risks. The .NET Framework has many
security features built-in to it to protect your applications.
Type safety is now enforced. This prevents code from accessing memory locations that it does
not have authorization to access. This allows you to define how your objects are accessed. Before
code is run, it is verified to be type-safe. If it is not type-safe, it will only run if your security
policies allow for it.
Microsoft has added significant new functionality to make developers work more effectively,
without requiring them to learn entirely new ways of doing their jobs.
If you have seen earlier versions of Visual Basic, the IDE for VB.NET will look very familiar.
But if you have also worked with InterDev in the past, even more of the new interface will be old
hat. That is because the new IDE used for VB.NET has integrated the best ideas from both
environments to provide a more effective way of getting work done.
Advantages of VB.NET
Build Robust Windows-based Applications:
With new Windows Forms, developers using Visual Basic.Net can build Windows-based
applications that leverage the rich user interface features available in the Windows operating
system. All the rapid application development (RAD) tools that developers have come to expect
from Microsoft are found in Visual Basic .NET, including drag-and-drop design and code behind
forms. In addition, new features such as automatic control resizing eliminate the need for
complex resize code. New controls such as the in-place menu editor deliver visual authoring of
menus directly within the Windows Forms Designer. Combined with greater application
responsiveness, as well as simplified localization and accessibility, these new features in
Windows Forms make Visual Basic .NET the choice for today's Visual Basic developers.
Resolve Deployment and Versioning Issues Seamlessly:
Visual Basic .NET delivers the answer to all of your application setup and maintenance
problems. With Visual Basic .NET, issues with Component Object Model (COM) registration
and DLL overwrites are relics of the past. Side-by-side versioning prevents the overwriting and
corruption of existing components and applications.
XCOPY deployment enables Windows-based applications to be deployed to client machines
simply by copying files into the desired application directory. In addition, the auto-downloading
of applications for Windows makes the deployment of rich Windows-based applications as easy
as deploying a Web page.
statement and tag completion for HTML documents. In addition, separation of HTML markup
and code enable more efficient team-based development.
Improved Coding:
You can code faster and more effectively. A multitude of enhancements to the code editor,
including enhanced IntelliSense, smart listing of code for greater readability and a background
compiler
for
real-time
notification
of
syntax
errors
transforms
into
Requirement Analysis
FEASIBILITY STUDY
The very first phase in any system developing life cycle is preliminary
investigation. The feasibility study is a major part of this phase. A measure of how
beneficial or practical the development of any information system would be to the
organization is the feasibility study.
The feasibility of the development software can be studied in terms of the
following aspects:
1. Operational Feasibility.
2. Technical Feasibility.
3. Economical feasibility.
OPERATIONAL FEASIBILITY
The site will reduce the time consumed to maintain manual records and is not
tiresome and cumbersome to maintain the records. Hence operational feasibility is
assured.
TECHNICAL FEASIBILITY
ECONOMICAL FEASIBILTY
Once the hardware and software requirements get fulfilled, there is no need
for the user of our system to spend for any additional overhead.
For the user, the web site will be economically feasible in the following
aspects:
The web site will reduce a lot of paper work. Hence the cost will be
reduced.
Our web site will reduce the time that is wasted in manual processes.
The storage and handling problems of the registers will be solved.
Accordingly the model which we choose should be suitable for the project as the
software process model changes the cost of the project also changes because the
steps in each software process model varies.
This software is build using the waterfall mode. This model suggests work
cascading from step to step like a series of waterfalls. It consists of the
following steps in the following manner
Waterfall model:
Analysis Phase
Design Phase
Coding Phase
Testing Phase
Analysis Phase:
The objective of design is to determine how the problem will be solved. During design the
analysts focus shifts from the logical to the physical. Data elements are grouped to form
physical data structures, screens, reports, files and databases.
Coding Phase:
The system is created during this phase. Programs are coded, debugged, documented, and tested.
New hardware is selected and ordered. Procedures are written and tested. End-user
documentation is prepared. Databases and files are initialized. Users are trained.
Testing Phase:
Once the system is developed, it is tested to ensure that it does what it was designed to do. After
the system passes its final test and any remaining problems are corrected, the system is
implemented and released to the user.
Technical Requirements