Date post: | 26-Oct-2014 |
Category: |
Documents |
Upload: | krishanapatel57 |
View: | 45 times |
Download: | 1 times |
PC ACCESS FOR VISUALLY IMPAIRED
2012
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page ii
PC ACCESS FOR VISUALLY IMPAIRED
A PROJECT REPORT
Submitted by
PATEL NISHANT G.
PADHIYAR SAGAR N.
NARIGARA MANHAR N
In fulfillment for the award of the degree
Of
BACHELOR OF ENGINEERING
in
Information Technology
Om Shanti Engineering College, Rajkot
Gujarat Technological University, Ahmedabad
May 2012
Om Shanti Engineering College
Information Technology
2012
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page iii
CERTIFICATE
Date: 17-5-12
This is to certify that the dissertation entitled “PC ACCESS FOR
VISUALLY IMPAIRED” has been carried out by PATEL NISHANT G. ,
PADHIYAR SAGAR N. and NARIGRA MANHAR N. under my guidance in
fulfillment of the degree of Bachelor of Engineering in INFORMATION
TECHNOLOGY (8th
Semester) of Gujarat Technological University,
Ahmedabad during the academic year 2011-12.
Guides: Vekaria Daxa V.
Head of the Department
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page iv
Candidate’s Declaration
We Nishant G Patel, Manhar N Narigara, Sagar N Padhiyar bearing hereby certify that
the Project Report entitled “PC ACCESS FOR VISUALLY IMPAIRED”, under the
guidance of Prof. DAXA V VEKARIA, Om Shanti engineering college, Rajkot, is submitted
in partial fulfillment of the requirements for the Award of the Degree of Bachelor of
Engineering in Information Technology.
This is a record of bonafide work carried out by me and the results embodied in this Project
Report has not been produced / copied from any source. The results embodied in this Project
Report have not been submitted to any other University or Institute for the Award of any
other Degree or Diploma.
Patel Nishant G. (080360116032)
Narigara Manhar N. (080360116028)
Padhiyar Sagar N. (080360116030)
Department of Information Technology,
Om Shanti Engineering College,
Rajkot – 360020.
Date: 17-5-12
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page v
Acknowledgement I would like to thank Prof. Daxa V Vekaria for her invaluable support,
encouragement and guidance, without which my B.E. Project would
have been an exercise in futility.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page vi
Abstract
Nowadays blind people can also use computer, for them “Software for visually impaired”
(SVI) is used, a software which works with speech, which converts your computer into a
talking computer. It reads out all the matter that is on the computer‟s screen.
Currently visually impaired persons are using JAWS (Job Access With Speech), developed
by Microsoft. While using JAWS blind people having problem of locating and mapping of
controls in VB. We have taken this problem as an IDP from Shree V.D.Parekh Andh
Mahilavikas Gruh, Dhebarbhai Road, Rajkot. The model that will be used in the project is an
Incremental Model.
Introduction
SOFTWARE FOR VISUALLY IMPAIRED (SVI) version 1.0 is software program which
works with speech, which converts your computer into a talking computer. It reads out all the
matter that is on the computer‟s screen.
This allows blind and visually impaired users to read the screen with a text-to-speech output.
This software is specifically designed for visually impaired society. The effectiveness of the
SVI in assisting visually impaired people in learning and working or other factors.
Problem Definition / Motivation
Currently visually impaired persons are using JAWS (Job Access With Speech), developed
by Microsoft. While using JAWS blind people having problem of locating and mapping of
controls in VB. As shown in fig-2. SVI provides facility to overcome this problem.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page vii
Fig-1: problem in JAWS software
Motivation
We had motivated to doing this project from Shree V.D.Parekh Andh Mahilavikas Gruh,
Dhebarbhai Road, Rajkot. This organization is not having that much fund to spend on
software like SVI. So we are taking this problem as our IDP from this organization to help
them.
Scope
This application is specifically designed for educational institutions, public libraries, and
organizations whose sole purpose is to better the lives of the visually impaired.
Preliminary Work
JAWS software is available in market. JAWS is scripting programming software. JAWS is a
screen reader software program for visually impaired users produced by the blind and low
vision group at freedom scientific of st.petersburg, Florida, USA.
Its purpose is to make personal computer using Microsoft windows accessible to blind and
visually impaired users. It accomplishes this by providing the user with access to the
information displayed on the screen via text-to-speech. JAWS is a powerful software
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page viii
program designed to work with a speech synthesizer to improve the productivity level of
visually impaired employees, students and the casual user.
In JAWS some problem is being occurs when they are learning VB6, visually impaired
people suffering problem of locating and mapping controls in VB form, as solution we are
providing in SVI according to coordinates of components position. When control moving on
screen then sound out come as moving control, as an ex. One button on screen user moving
button one pixel to left direction and label of button is „bt1‟, then computer speak out “bt1
moving one pixel to left direction”.
One another problem in JAWS is language, JAWS available in 15 different languages, but
not in all Indian languages, so 15 million Indian people of blind community suffering in them
life. So we will provide our software in Hindi, Gujarati, Tamil and more other languages in
future.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page ix
LIST OF FIGURES:
1. PROBLEM IN JAWS SOFTWARE…………………….………….…….….……..vii
2. PROCESS MODEL……………………………………………………….......……..6
3. PROJECT DEVELOPMENTAPPROCH…………………………………………….8
4. PROBLEM AND WEAKNESS OF CURRENT SYSTEM……………..….………22
5. CLASS DIAGRAM……………………………………………………..….……….27
6. USECASE DIAGRAM………………………………………………….….……....28
7. SEQUENCE DIAGRAM ……………………….……………………….….………29
8. LEVELOF TESTING……………………………………………………….………52
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page x
LIST OF TABLES:
1. MILESTONES AND DELIVERABLES…………….……………………………10
2. ROLES AND RESPONSIBILITIES……………………………………..………....11
3. PROJECT SCHEDULING…………………………………………………………12
4. ROLES AND RESPONSIBILITIES…………………………………………….…12
5. PROJECT SCHEDULING…………………………………………………………13
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page xi
TABLE OF CONTENTS
TITLE PAGE NO
Candidate’s declaration ……………………………………..…….…………..ii
Certificate …………………………….…………………………..…………...iv
Acknowledgement…………………..………………………..………..…….....v
Abstract ……………………………………………………………..………....vi
List of Figures……………………………………………………..…………....ix
List of Tables………………………………………………………..…………..x
Table of Contents……………………………………………………………… vii
CHAPTER-1 Introduction (page 1 starts)
1.0 Introduction
1.1 Project Summary 02
1.2 Purpose 02
1.3 Scope 02
1.4 Objective 03
1.5 Literature survey 03
1.6 Document Conventions 04
CHAPTER-2 Project Management (page 5 starts)
2.0 Project Management 06
2.1 Project Planning 06
2.1.1 Project Development Approach and Justification 08
2.1.2 Project Plan 10
2.1.3 Milestones and Deliverables 10
2.1.4 Roles and Responsibilities 11
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page xii
2.2 Project Scheduling 12
2.3 Risk Management 14
2.3.1 Risk Identification 14
2.3.2 Risk Analysis 14
2.3.3Risk planning 14
CHAPTER-3 System Requirements Study (page 15 starts)
3.0 System Requirements Study 15
3.1 User Characteristics 16
3.2 Hardware and Software Requirements 16
3.2.1 Software interfaces 17
3.3 Constraints 18
3.3.1 Regulatory Policies 18
3.3.2Parallel Operations 18
3.3.3 Reliability Requirements 18
3.3.4 Safety and Security Consideration 19
3.4 Assumptions and Dependencies 19
CHAPTER-4 System Analysis (page 20 starts)
4.0 System Analysis 20
4.1 study of current system 21
4.2 requirement of system 21
4.3 Feasibility Study 22
4.4 requirement validation 22
4.5 features of new system 22
4.6 key features 23
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page xiii
4.7 Class Diagram 25
4.8 use case diagram 26
4.9 Sequence and Diagram 27
CHAPTER-5 Coding (page 28 starts)
5.1 Leading screen 29
5.2 Home screen 29
5.3 Utility menu screen 30
5.4 option menu screen 30
5.5 help menu screen 31
5.6 text file reader 31
5.7 text file converter 32
CHAPTER-6 Testing (pagef 35 starts)
6.0 Testing 36
6.1 Testing Plan 36
6.2 Testing Strategy 37
6.3 Testing Methods 38
6.4 Test Cases 40
CHAPTER-7 Limitation and Future Enhancement (page 41 starts)
7.0 Limitation and Future Enhancement 42
CHAPTER-8 Conclusion and Discussion (page 43 starts)
8.0 Conclusion and Discussion 44
CHAPTER-9 References (page 45 starts)
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 1
1. Introduction
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 2
1.0 INTRODUCTION
1.1 Project Summary
SOFTWARE FOR VISUALLY IMPAIRED (SVI) is software program which works with
speech, which converts your computer into a talking computer. It reads out all the matter that
is on the computer‟s screen.
However, while there is a range of technologies that are available, there is little known about:
The kinds of technologies being used by visually-impaired people, the effectiveness of those
technologies in assisting visually-impaired people in learning and working or other factors
that help for visually impaired people in learning, working or living.
1.2 Purpose
This application is Specifically designed for educational institutions, public libraries, and
organizations whose sole purpose is to better the lives of the visually impaired. the
application is design for the blind and visually impaired people who are suffering in the life.
The system also compare with other system and other technologies to prove this application.
1.3 Scope
The scope of this project is to enable the users to ease the use of computer. The motive of
developing this application is to provide a service to visually impaired society for them
confident future
1.4 Objective
The objective of this project is to help the people who are blind and visually impaired and to
make them confident in them life. The research project was to identify and analyse
technologies that aid the blind and visually impaired in educational preparation for work, and
in employment. The research also aimed at identifying strategies that either assist or aid
employed blind and visually impaired workers in developing their skills to participate at
higher levels in their current employment positions. As well, the research aimed to provide
conclusions and recommendations that would inform the development of better education
mechanisms for the blind and visually impaired.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 3
1.5 Literature Survey
1.5.1 Blind people in India
India is now home to the world‟s largest number of blind people. Of the 37 million
people across the globe who are blind, over 15 million are from India. For them, the
world of personal computers, office automation and the Internet offers mixed
blessings. That world wasn't designed for them, but with the right assistive
technology, they can take part in it. When everything works well, they have access to
an ocean of information vastly greater than anything previously available to the blind.
But pitfalls and maddening frustrations are a constant reality.
1.5.2 Screen Reader
Blind computer users mainly rely upon screen-reader software, which describes the
activity on the screen and reads the text in the various windows, explained Gayle
Yarnell, owner of Adaptive Technology Consulting Inc. in Amesbury, Mass. Yarnell
is blind.
Screen readers cost between $500 and $1,000, although there are also freeware screen
readers. (Windows XP and Vista come with a screen reader called Narrator, but even
Microsoft Corp. says it's not powerful enough for serious use.).
We had motivated to doing this project from Shree V.D.Parekh Andh Mahilavikas
Gruh. Dhebarbhai Road, Rajkot. This organization is not having that much fund to
spend on software like SVI. So we are taking this problem as our IDP from this
organization to help them.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 4
1.6 Document Conventions
Here is not any tough or strict standard but good format for the REPORT. Here all
sentences and words have its own priority.
The header will follow the size 18 bold and the sub header will follow the size 14
bold. The detail of this REPORT means the detail of the sub header will follow the
size 12 times roman.
It also uses capital lettered words to highlight key words.
The important sentences are written with the size 12 bold and words are written with
the underline to highlight the user requirement.
The document has tried to maintain a priority of requirements, short forms for some
commonly abbreviated terms.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 5
2. Project Management
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 6
2.0 PROJECT MANAGEMENT
2.1 PROJECT PLANNING
Process Model
Fig 2 Process Model
The prototyping diagram begins with requirements gathering. Developer and customer meet
and define the overall objectives for the software, identify whatever requirement are known,
and outline areas where further definition is mandatory. A quick design then occurs. The
quick design focuses on a representation of those aspects of the software that will be visible
to the customer/user (e.g. input approaches and output formats). The quick design leads to the
construction of a prototype. The prototype is evaluated by the customer/user and is used to
define requirement for the software to be develop. Iteration occurs, as the prototype is tune to
satisfy the needs of the customer, at the same time enabling the developer to better
understand what needs to be done.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 7
Ideally, the prototype servers as a mechanism for identifying software requirements. If a
working prototype is built, the developers attempt to make use of existing programs
fragments or apply tools (e.g. reports generators, window managers, etc…) that enable
working programs to be generated quickly
.
Project planning process starts with an assessment of the constraints affecting the project:
- Identify objectives
- Determine information Requirements
- Analyze System Needs
- Designing
- Documentation
- Development
- Testing
- Deployment
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 8
2.1.1 Project Development Approach and Justification
Waterfall Model
The waterfall model is a model which was developed for software development; that is to
create software. It is called as such because the model develops systematically from one
phase to other in a downward fashion, like a waterfall.
Fig.3 Project development approach
Waterfall Model Phases
Given below are the various phases of waterfall model. Although, the phase name may differ
for every software organization, the basic implementation steps remain the same
Analysis and Software Definition
this is the first phase of waterfall model which includes a meeting with the customer to
understand his requirements. This is the most crucial phase as any misinterpretation at this
stage may give rise to validation issues later. The software definition must be detailed and
accurate with no ambiguities. It is very important to understand the customer requirements
and expectations so that the end product meets his specifications.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 9
System Design
the customer requirements are broken down into logical modules for the ease of
implementation. Hardware and software requirements for every module are identified and
designed accordingly. Also the inter relation between the various logical modules is
established at this stage. Algorithms and diagrams defining the scope and objective of each
logical model are developed. In short, this phase lays a fundamental for actual programming
and implementation.
System Implementation
this is the software process in which actual coding takes place. A software program is written
based upon the algorithm designed in the system design phase. A piece of code is written for
every module and checked for the output.
System testing
The programmatically implemented software module is tested for the correct output. Bugs,
errors are removed at this stage. In the process of software testing, a series of tests and test
cases are performed to check the module for bugs, faults and other errors. Erroneous codes
are rewritten and tested again until desired output is achieved.
System Deployment and Maintenance
this is the final phase of the waterfall model, in which the completed software product is
handed over to the client after alpha, beta testing. After the software has been deployed on the
client site, it is the duty of the software development team to undertake routine maintenance
activities by visiting the client site. If the customer suggests changes or enhancements the
software process has to be followed all over again right from the first phase i.e requirement
analysis
Thus, the project requires the fulfillment of one phase, before proceeding to the next.
Therefore if there is a fault in this software it will be detected during one of the initial phases
and will be sealed off for correction.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 10
A lot of emphasis is laid on paperwork in this method as compared to the newer methods.
When new workers enter the project, it is easier for them to carry on the work from where it
had been left. The newer methods don‟t document their developmental process which makes
it difficult for a newer member of the team to understand what step is going to follow next.
The Waterfall Model is a straight forward method and lets one know easily what stage is in
progress.
The Waterfall method is also well known amongst the software developers therefore it is easy
to use. It is easier to develop various software through this method in short span of time.The
inter-dependence of waterfall model phases may lead to developmental issues, if a systematic
approach is not followed at each step. However, in spite of these shortcomings, waterfall
model is adopted all across the world.
2.1.2 Project Plan:
The key to a successful project is in planning which is the first thing we do when undertaking
a project. The value of project planning results in saving money, time and many problems.
Learning Project Technologies: 2 Week
Requirement Gathering and Design: 2 Week
Implementation: 4 Weeks
Testing: 1 Week
Documentation: 2 Weeks
2.1.3 Milestone And Deliverables:
Name of deliverables Target release date
Project plan document 21/2/2011
Requirement specification 15/3/2011
Design specification 10/4/2011
System implementation 25/4/2011
Test plan 30/4/2011
Table 1. Milestones and Deliverables
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 11
2.1.4 Roles And Responsibilities:
RESPONSIBILITIES MEMBER
Analysis Patel Nishant, padhiyar sagar, & manhar narigara
Analysis Review Patel Nishant, padhiyar sagar, & manhar narigara
Design Patel Nishant, padhiyar sagar, & manhar narigara
Design Review Patel Nishant, padhiyar sagar, & manhar narigara
Coding Patel Nishant, padhiyar sagar, & manhar narigara
Front-site Design Patel Nishant, padhiyar sagar, & manhar narigara
Design Review Patel Nishant, padhiyar sagar, & manhar narigara
Testing Patel Nishant, padhiyar sagar, & manhar narigara
Documentation Patel Nishant, padhiyar sagar, & manhar narigara
Table 2: Roles and Responsibilities
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 12
2.2 Project Scheduling:
Sr. No. Phase Duration
1 Project Selection
2 Preliminary Study 18th
july-20th
july
3 Thesis Writing 25th
july-29th
july
4 Project Model Selection 30th
july-1th
Aug.
5 SRS Preparation 2th
Aug.-6th
Aug
7 Synopsis writing 7th
Aug.-11th
Aug.
8 Data Diagrams Preparation 12th
Aug.-25th
Aug.
10 Database Design 1th
Sep.-20th
Sep.
11 Data Flow Analysis 21th
Sep.-10th
Oct.
12 Creating Pages From Design 11th
Oct.-30th
Oct.
13 System Coding 15th
Jan. - 30th
Mar.
14 System Testing and Implementation 1th
Feb. - 15th
Mar.
Table 3: project scheduling
Roles and Responsibilities
Table 5: Roles and Responsibilities
Name of the person Roles and responsibilities
Patel Nishant g.
Narigara manhar n.
Padhiyar sagar n
Developer
Designer
Tester
Analyzer
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 13
2.2 Project Scheduling
Table 6: Project Scheduling
Software life cycle phase Completion
date/duration
System Analysis: Problem definition and
description.
3 weeks
Hardware Software requirements 2 weeks
Constraints/Goals of implementation 1 week
Requirement gathering 1 week
Requirement analysis 1 week
Requirement specification 1 week
System Design: Use case diagram 2 days
User interface design 5 days
Sequence diagram 3 days
Class diagram 2 days
GUI form design 2 weeks
Coding Standard Conversion 1 week
Coding 1 week
Testing and deployment 10 days
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 14
2.3 Risk Management
There can be many risks that jeopardize the software system and therefore solution is to be
found to provide security and to protect the software from those risks. Otherwise it can cause
the problem in future.
2.3.1 Risk Identification
Some types of risks that can harm our software system are:
Voice should be clear
Word pronunciation should be clear
Developing the wrong functions and properties
Poor system maintainability
2.3.2 Risk Analysis
If voice is not clear then user cant listen properly so that time is wasted in
recovering or reinstallation of software.
There are dictionary manager that will find proper word.
Physical calamities can completely destroy the whole system.
2.3.3 Risk Planning
There are dictionary management is for finding a proper word, if proper word is
not found then on-line help is there.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 15
3.0 System Requirements
Study
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 16
3.1 USER CHARACTERISTICS: It is about types of the users who are dealing with the system Assumptions:
- In general it has been assumed that the user has complete knowledge of the System
that means user is not a native user.
- Any data entered by him/her will be valid. To make the software as user friendly as
possible but at the same time keeping in minds user requirements.
3.1.1 USER:
The users of the system are members who want to be part of our system & want to be
connected to their callings by tracking him/her self.
3.2 Hardware and Software Requirements:
3.2.1 Hardware Interfaces:
3.2.1.2 Client Configuration:
Configuration:
- Pentium – IV or Higher
- 450 MHz Processor or higher
- 512 MB RAM or higher
- 80 GB HDD or higher
- Super VGA Monitors (800*600)
Operating System: Microsoft Windows XP and Microsoft Windows 7 or other
higher versions
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 17
3.2.2 Software Interfaces:
3.2.2.1 Development Side tool
Visual Studio 2010
Natural Language processing tool kit
Digital signal processing tool
Back End Tools
- Documentation Tools
- MS Visio 2007
- Microsoft Word 2007
Operating System
- Microsoft Windows XP and Microsoft Windows 7 or other higher
versions.
Visual Studio 2010
Visual Studio is a complete set of development tools for building ASP.NET
Web applications, XML Web Services, desktop applications, and mobile
applications. Visual Basic, Visual C++, Visual C#, and Visual J# all use the
same integrated development environment (IDE), which allows them to share
tools and facilitates in the creation of mixed-language solutions. In addition,
these languages leverage the functionality of the .NET Framework, which
provides access to key technologies that simplify the development of ASP Web
applications and XML Web Services.
Natural Processing Tool kit
Natural Language Processing is a theoretically motivated range of
computational techniques for analyzing and representing naturally occurring
texts at one or more levels of linguistic analysis for the purpose of achieving
human-like language processing for a range of tasks or applications.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 18
The goal of NLP as stated above is “to accomplish human-like language
processing”. The choice of the word „processing‟ is very deliberate, and should
not be replaced with „understanding‟. For although the field of NLP was
originally referred to as Natural Language Understanding (NLU) in the early
days of AI, it is well agreed today that while the goal of NLP is true NLU, that
goal has not yet been accomplished.
A full NLU System would be able to:
1. Paraphrase an input text
2. Translate the text into another language
3. Answer questions about the contents of the text
4. Draw inferences from the text
3.3 Constraints:
3.3.1 Regulatory Policies:
All the access rights to access the project is provided to all the users depending on
their user type that is given by the administrator.
3.3.2 Parallel Operations:
This system can be used by administrator as well as user at the same time.
Administrator can keep watch on users who is tracking someone.
3.3.3 Reliability Requirements:
The main reliability requirement is the validation used. Without proper validation the
system does not allow to enter that value into the database. For eg. In the email id, the user
cannot enter any dummy value, the validation checks that whether there is „@‟ or „.‟ symbol
in that. Also any null value is not allowed in place of compulsory fields.
The System allows no proxy authentication while any login and has a fixed session period
after which the session of a single login will automatically expire. Moreover the system
allows no dual login that is logging in to the system with same credentials from different
machines or systems at the same time
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 19
3.3.4 Safety and Security Consideration:
If there is extensive damage to a wide portion of the database due to catastrophic failure,
such as a disk crash, the recovery method restores a past copy of the database that was backed
up to archival storage (typically tape) and reconstructs a more current state by redoing the
operations of committed transactions from the backed up to the time of failure. Another
safety requirement in our project is for authenticated access of the data. So, we have to
provide the user‟s privilege as per requirement.
Better security option is provided with User name & Password. Unauthorized persons
cannot access to the system.
It should take a timely backup of all the data at some safe location for safety purpose.
The data safety of the data is very much concerned as all the processing are depend on
the data which is stored in our database.
Restrict communications between some areas of the program.
Later version of the software will incorporate encryption techniques in the
user/license authentication process.
Communication of sensitive data should be encrypted.
3.4 Assumptions and Dependency:
Full working of mobile tracking system is dependent on the availability of GPS or
Bluetooth connection.
Assumptions:
In general it has been assumed that the user has complete knowledge of the System
that means user is not a native user.
Any data entered by him/her will be valid. To make the software as user friendly as
possible but at the same time keeping in minds user requirements.
Dependencies:
It depends that the one should follow the international standards for the generating the
User ID & should fill the related information in the proper format.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 20
4.0 System Analysis
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 21
4.0 System analysis
4.1 Study of Current System
Currently visually impaired persons are using JAWS (Job Access With
Speech), developed by Microsoft. JAWS is based upon a whole new approach to
talking computers - that of designing software with the priorities of the blind user in
mind. Yet, the sighted trainer or supervisor has not been forgotten, since JAWS offers
both audible and visual flexibility.
4.2 Requirements of System
The software is not breakdown suddenly in any disaster like power failure.
The development of software is based on the object oriented model.
The timeline of this software must be in our mind.
The performance of the function and every module must be well.
At every step the output of the one phase is the input of the other phase
and it will be reliable and accurate.
The risk factor must be taken at initial step for better performance of the
software.
The individual function the performance will be well.For login to the
software password and user name will be matched to the password and
name.
The overall performance of the software will reliable and enable the user
to work efficiently.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 22
4.3 Feasibility Study
4.4.1 Does the system contribute to the overall objectives of the organization?
ANS: Yes, The system contributes the overall objectives of the organization.
4.4.2 Can the system be implemented using the current technology and within
the given cost and schedule constraints?
ANS: No, we are going to use totally new technology. The current system is
using VB technology.
4.4.3 Can the system be integrated with other system which are
already in place?
ANS: No, we are going to replace the existing system with new system.
4.4 Requirements Validation
There will be proper security regarding to the accessing of application. The
external security can be provided by given the login authentication. There is also the
facility that the user can lock his private data. The whole software is secure from the
outside accessing.
4.5 Features of New System
The research also aimed at identifying strategies that either assist or aid
employed blind and visually impaired workers in developing their skills to participate
at higher levels in their current employment positions. As well, the research aimed to
provide conclusions and recommendations that would inform the development of
better education mechanisms for the blind and visually impaired. It includes the use of
additional software which allows the visually impaired a way to arrange all the
components used in PC through voice recognition systems. This project is expected to
provide visually impaired an easy access computer.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 23
4.6 Key Features
Independent Installation
SVI has an interactive talking installation. The Visually Challenged can install
our software easily & independently without sighted assistance.
In-Built Training Tutorials
SVI has built-in Basic Training Tutorials in DAISY format with text and audio
Instruction to help beginners to understand how to navigate the Windows
environment with SVI.
Indian Accent Voice
SVI provides a choice of different voices, which includes English, Hindi, and
Gujarati etc.
Hot Key Help
Press INSERT+H to get instant help for the SVI hot keys or Windows short
cut keys available in the current dialog window. All keyboard control is
same as JAWS.
Screen Sensitive Help
Press INSERT+F1 to hear a description of the current focus or position you
are in and also SVI prompts you with guidance of what to do Next i.e. If you
are a beginner or learning computers and get stuck or do not know what to do,
by pressing INSERT + F1 in the keyboard, SVI software shows you the way.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 24
Access Key Announcement
SVI helps you to operate the computer at a faster pace by letting the user
customize the announcement of the access keys (the underlined letters
used as shortcuts) for performing various functions. This helps the user
quickly navigate and activate the controls and menus.
Keyboard Help
In SVI when you press INSERT+1 you enter Keyboard Help mode where
when any key is pressed you hear its name and a description of its function
with a brief synopsis. This is very useful in teaching the keyboard to the
blind.
Easy Speech Guided Self-Installation by the Blind
SVI has a very simple talking installation that enables the blind to install the
software themselves. Just insert the CD into the CD-ROM drive and in a
few minutes, SVI for Windows will install on your computer. Not only will
the installation be easier, but also right from the moment it starts, your
computer will talk.
The installation is interactive; giving you the information you need,
immediately, verbally, without having to second-guess the installation
process.
Flexibility in Use
The design accommodates a wide range of individual preferences and
abilities.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 25
4.7 Class Diagram
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 26
4.8 System Activity
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 27
4.9 Sequence Diagram
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 28
5.0 Coding
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 29
5.1 Loading screen
5.2 Home screen
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 30
5.3 Utility menu screen
5.4 Option menu screen
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 31
5.5 Help menu screen
5.6 Text file reader
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 32
5.7 Text file converter
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 33
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 34
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 35
6.0 Testing
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 36
Software testing is an important technique for assessing the quality of a software
product. Software testing is the process of analyzing a software item to detect the differences
between existing and required conditions (that is, bugs) and to evaluate the features of the
software item. Software testing is an activity that should be done throughout the whole
development process.
Software testing is one of the “verification and validation,” or V&V, software practices.
Verification is the process of evaluating a system or component to determine whether
the products of a given development phase satisfy the conditions imposed at the start of that
phase. Verification activities include testing and reviews.
Validation is the process of evaluating a system or component during or at the end of
the development process to determine whether it satisfies specified requirements. At the end
of development validation activities are used to evaluate whether the features that have been
built into the software satisfy the customer requirements and are traceable to customer
requirements. Through verification, we make sure the product behaves the way we want it to.
Through validation, we check to make sure that somewhere in the process a mistake hasn‟t
been made such that the product build is not what the customer asked for; validation always
involves comparison against requirements.
6.1 TESTING PLAN
The testing sub-process includes the following activities in a phase dependent manner:
i. Create Test Plans.
i. Create Test Specifications.
ii. Review Test Plans and Test Specifications.
iii. Conduct tests according to the Test Specifications, and log the defects.
iv. Fix defects, if any.
v. When defects are fixed continue from activity.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 37
6.2 TESTING STRATEGY:
Black box testing should make use of randomly generated inputs (only a test range
should be specified by the tester), to eliminate any guess work by the tester as to the methods
of the function.
- Data outside of the specified input range should be tested to check the robustness
of the program.
- Boundary cases should be tested (top and bottom of specified range) to make sure the
highest and lowest allowable inputs produce proper output.
- The number zero should be tested when numerical data is to be input.
- Stress testing should be performed (try to overload the program with inputs to see
where it reaches its maximum capacity), especially with real time systems.
- Test monitoring tools should be used whenever possible to track which tests have
already been performed and the outputs of these tests to avoid repetition and to aid in
the software maintenance.
- Other functional testing techniques include: transaction testing, syntax testing, domain
testing, logic testing, and state testing.
- Finite state machine models can be used as a guide to design functional tests.
LEVELS OF TESTING:
Unit Testing: To detect error from each software component individually.
Integration testing: Interacting components are verified & the interface errors are
detected.
System testing: All the system elements forming the system is tested as a hole.
Acceptance testing: in this testing phase concluded to ensure that the software works
correctly in user‟s working environment.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 38
FIG 14: Level of Testing
6.3 TESTING METHODS:
There are mainly two strategies are there.
1) Static Testing
2) Dynamic Testing
3) Black Box Testing
4) White Box Testing
1. STATIC TESTING:-
The Verification activities fall into the category of Static Testing. During static testing,
you have a checklist to check whether the work you are doing is going as per the set
standards of the organization. These standards can be for Coding, Integrating and
Deployment. Reviews, Inspection's and Walkthrough's are static testing methodologies.
2. DYNAMIC TESTING:-
Dynamic Testing involves working with the software, giving input values and checking
if the output is as expected. These are the Validation activities. Unit Tests, Integration
Tests, System Tests and Acceptance Tests are few of the Dynamic Testing
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 39
methodologies. As we go further, let us understand the various Test Life Cycle's and get
to know the Testing Terminologies. To understand more of software testing, various
methodologies, tools and techniques.
3. BLACK BOX TESTING:-
Black Box Testing is testing without knowledge of the internal workings of the item
being tested. For example, when black box testing is applied to software engineering, the
tester would only know the legal inputs and what the expected outputs should be, but not
how the program actually arrives at those outputs. It is because of this that black box
testing can be considered testing with respect to the specifications, no other knowledge of
the program is necessary. For this reason, the tester and the programmer can be
independent of one another, avoiding programmer bias toward his own work. For this
testing, test groups are often used. Also, due to the nature of black box testing, the test
planning can begin as soon as the specifications are written.
This strategy has some advantage like it is more effective on larger units of code than
glass box testing, tester needs no knowledge of implementation, including specific
programming languages, tester and programmer are independent of each other, tests are
done from a user's point of view, will help to expose any ambiguities or inconsistencies in
the specifications, test cases can be designed as soon as the specifications are complete.
4. WHITE BOX TESTING:-
White box testing strategy deals with the internal logic and structure of the code. White
box testing is also called as glass, structural, open box or clears box testing. The tests
written based on the white box testing strategy incorporate coverage of the code written,
branches, paths, statements and internal logic of the code etc. In order to implement white
box testing, the tester has to deal with the code and hence is needed to possess knowledge
of coding and logic i.e. internal working of the code. White box test also needs the tester
to look into the code and find out which unit/statement/chunk of the code is
malfunctioning.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 40
6.4 TEST CASES:
In software engineering, the most common definition of a test case is a set of conditions or
variables under which a tester will determine if a requirement or use case upon an application
is partially or fully satisfied. It may take many test cases to determine that a requirement is
fully satisfied. In order to fully test that all the requirements of an application are met, there
must be at least one test case for each requirement unless a requirement has sub requirements.
In that situation, each sub requirement must have at least one test case. This is frequently
done using a Traceability matrix.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 41
7.0 Limitation and Future
Enhancement
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 42
7.1 LIMITATION
The person who is illiterate cannot use this system.
User must have basic knowledge about computer.
7.2 FUTURE ENHANCEMENT
We can give advertise of other features in our system.
For normal users who do not aware of English it may be possible to use Integration
of languages like Hindi, Gujarati etc.
This system currently working within software, we will going to go develop this
software for PC.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 43
8.0 Conclusion and
Discussion
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 44
8.0 CONCLUSION AND DISCUSION
The real problem of blindness is not the loss of eyesight; the problem is the misunderstanding
and lack of information that exist. If a blind person has proper training and opportunity,
blindness can be reduced to a physical nuisance.
We are developing this software for approximately 45% of individuals with severe visual
impairment or blindness has a high school diploma, compared to 80% of fully sighted
individuals. This software will be freely available in market, our main goal to develop this
software for blind community who are not affort to buy comparatively available other
software.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 45
References
1. Anupam Basu, Debasish Sen , Shiraj Sen and Soumen Chakraborty “An Indian
Language Speech Synthesizer –Techniques and Applications”, INDIAN
INSTITUTE OF TECHNOLOGY, KHARAGPUR 721302, DECEMBER 17-
19, 2003.
2. Halimah Badioze Zaman, David Kennedy, Choo W.O., Azlina Ahmad And
Aidanismah Yahya, “Voice Recognition Browser for the Visually Impaired
Learners (Mg Sys VISI)”, Department of Information Science Universiti
Kebangsaan Malaysia Bangi,43600, Selangor MALAYSIA.
3. http://www.ntlk.org
4. http://www.freedomscientific.com
5. http://www.webaim.org
6. http://www.docstoc.com
7. Uirá Kulesza and Dilma M. Silva, “Reengineering of the JAWS Web Server
Design using Aspect-Oriented Programming”, Computer Science Department
University of São Paulo, BRAZIL.
PC ACCESS FOR VISUAL IMPAIRED
OMSEC_IT Page 46
SPECIMEN
PC Access For Visually Impaired
A PROJECT REPORT
Submitted by
Nishant Patel
(080360116032)
Sagar padhiyar
(080360116030)
Manhar narigara
(080360116028)
In fulfillment for the award of the degree
Of
BACHELOR OF ENGINEERING
In
Information Technology
Sanjayraj Education Zone
Om Shanti Engineering College,Rajkot
2012
Gujarat Technological University, Ahmedabad
DECEMBER 2012