LAKSHMI NARAIN COLLEGE OF TECHNOLOGY
INDORE
GYMCFGlG
MAJCF FFCJECT'
CM
CLcLL CcVlL:lrc
DEPARTMENT O NORMATON TECHNOOGY ENGNEERNG
SESSON zo11-zo1z
SUBMTTED TO: SUBMTTED BY:
ER. BHARAT PRAJAPAT YOGTA GUNJA(o8zoTo81o8)
SHEA VNCHURKAR(OO2OlTOO'OCO)
VlMAY VEFMA (OO2OlTOO'O74)
Approval Signatures
Dr. Manish Shrivastav Dr. D. 1. Mitra
Shefali Vinchurkar Yogita Gunjal
Vinay Verma Er. Bharat Prajapat
Approved by: Principal Approved by: HOD
Prepared by: Team Member Prepared by: Team Member
Reviewed by: Project Guide Prepared by: Project Guide
%able of Contents
1. Project Overview...............1
1.1Purpose, Scope, and Objectives......................1
1.2Assumption and Constraints...........................2
1.3Project Deliverables...............................2
1.4Schedule and Budget Summary.........................2
1.5Evolution oI the plan.................................2
Enception ellobaration
1.6 ReIerences....................................2
1.7DeIinitions and Acronyms.................................3
. Project Organization...............4
2.1External InterIaces................................................4
2.2Internal Structures.................................................4
2.3Role and Responsibilities.......................................4
. Managerial Process Plans.............5
3.1Start-up Plan...................................................5
3.1.1 Estimates.........................5
3.1.2 StaIIing...........................5
3.1.3 Resource Acquisition.....................5
3.2Work Plan....................................................6
3.2.1 Work Breakdown Structure....................6
3.2.2 Schedule Allocation.......................7
3.2.3 Resource Allocation.......................7
3.2.4 Budget Allocation.......................7
3.3Project Tracking Plan.................................................8
3.3.1 Requirements Managements......................8
3.3.2 Schedule Control ........................8
3.3.3 Budget Control.........................8
3.3.4 Quality Control...........................9
3.3.5 Reporting...........................9
3.3.6 Project Metrics.........................9
3.4Risk Management Plan..................................................9
3.5Project closeout Plan...............................................10
4. Supporting Process Plans..............11
4.1Process Model.................................................11
4.2Methods, Tools and Techniques.........................11
4.3InIrastructure.................................11
4.4Product Acceptance................................12
5. Supporting Process Plan................1
5.1ConIiguration Management............................................13
5.2VeriIication Management...............................................13
V model validation
5.3Documentation...............................................................14
5.4Quality Assurance..........................................................14
Iso 9.26
EIIiciency
Maintainabilti
Portability
------
5.5Reviews and Audits.......................................................14
5.6Problem Resolution........................................................15
5.7Process Improvement.....................................................15
1. Project Overview
1.1 Purpose, Scope and Objective
ln many offlces we save our daLa on flles le on papers lL becomes very dlfflculL Lask Lo preserve Lhese papers for long
perlod and we have Lo Lake care of Lhese papers So lf we use any Lechnlque Lo mlnlmlze Lhe efforLs behlnd Lhe
preservlng flles Lhen we wlll converL Lhls daLa on papers or flle lnLo dlglLal form 1hen lL wlll become very comforLable Lo
reLrleve access daLa So Lhls ls one of Lhe purposes of CharacLer 8ecognlLlon SysLem le Lo auLomaLlcally converL Lhe
handwrlLLen daLa on paper lnLo dlglLal form
The Scope oI CharacLer 8ecognlLlon SysLem ls
1he maln use of Lhls appllcaLlon ls ln Lhe fleld of educaLlon and research ln several case we work on copy and paper
because everyLhlng on compuLer ls noL easy buL Lhe noLes on paper are very hard for dlsLrlbuLlon so we converL Lhe
hard copy ln sofL copy wlLh some exLra addlLlon of sLandard fonLs Lo lncrease Lhe readablllLy and efflclenL sLorage
ln Louch screen devlces as an lnpuL mechanlsm we can use CC8
lL can be also use for learnlng purpose
lL can be use for audlLlng documenLaLlon purpose ln lndusLrles
?
The objectives oI the proposed soItware is
'Developing a system that helps in recogni:ing a character presented to it. This system uses the concept of
optical character recognition and neural networks to recogni:e a handwritten paper and convert it into digital
form so it can be easily readable, storable and accessible by any one at anytime.`
1. Assumption and Constraints
1) &ser must have primary knowledge oI computer.
2) Black `n` White image may result in loss oI character inIormation.
3) Colour image documents may not guarantee expected perIormance rates.
4) Some image Iormats like BMP do not have clear resolution.
5) The input character must not be too deviate Irom the standard shape.
6) It can only recognise English characters.
1. Schedule Summary
Scheduling oI a soItware project does not diIIer greatly Irom scheduling oI any multitask engineering eIIort.
ThereIore, generalized project scheduling tools and techniques can be applied with little modiIication Ior
soItware projects.
Time required in diIIerent phase oI project:
1|me L|ne Chart 1
1.4 Evolution of the plan
In our daily liIe we make handwritten documents Ior various purposes like Ior handwritten notes, Ior giving
presentations, Ior keeping records etc, here we have to arrange this physical documents Ior a long time
according to our need . It is very diIIicult to store and access them. By considering this thing we thought to
make soItware which will convert these handwritten documents into digital Iorm so that we can modiIy and
store it. For this we searched number oI websites and Iinally we got to know the importance oI such soItware.
1.5 References
1.5.1 In Reference book
4 ava 2 Complete ReIerence
4 SoItware Engineering, A Practitioner`s Approach
4 !ava neural neLworks (!eff PeaLon)
[Link] Documentation and resources
4 [Link]
4 [Link]
4 [Link]
4 [Link]
Definition and acronyms:
1AVA:
!ava ls an ob[ecL orlenLed language developed by sun MlcrosysLems Lhe [ava language was deslgned Lo be small slmple
and porLable across plaLforms and operaLlng sysLems boLh aL Lhe source and aL Lhe blnary level whlch means LhaL [ava
programs (appleLs and appllcaLlons) can run on any machlne LhaL has Lhe [ava vlrLual machlne)
CC8
t|ca| Character kecogn|t|on or Ck ls a Lechnology LhaL enables you Lo converL dlfferenL Lypes of documenLs such
as scanned paper documenLs ul flles or lmages capLured by a dlglLal camera lnLo edlLable and searchable daLa
nu8AL nL1WC8k
A neural neLwork ls a sofLware (or hardware) slmulaLlon of a blologlcal braln 1he purpose of a neural neLwork ls Lo
|earn to recogn|ze atterns ln your daLa Cnce Lhe neural neLwork has been Lralned on samples of your daLa lL can
make red|ct|ons by deLecLlng slmllar paLLerns ln fuLure daLa SofLware LhaL learns ls Lruly ArLlflclal lnLelllgence
neural neLworks are a branch of Lhe fleld known as Art|f|c|a| Inte|||gence CLher branches lnclude Case 8ased
8easonlng LxperL SysLems and CeneLlc AlgorlLhms 8elaLed flelds lnclude Classlcal SLaLlsLlcs luzzy Loglc and Chaos
1heory A neural neLwork can be consldered as a black box LhaL ls able Lo predlcL an ouLpuL paLLern when lL recognlzes a
glven lnpuL paLLern 1he neural neLwork musL flrsL be Lralned by havlng lL process a large number of lnpuL paLLerns and
showlng lL whaL ouLpuL resulLed from each lnpuL paLLern Cnce Lralned Lhe neural neLwork ls able Lo recognlze
slmllarlLles when presenLed wlLh a new lnpuL paLLern resulLlng ln a predlcLed ouLpuL paLLern
. Project Organization
.1 Hardware Interfaces :-
(a) Monitor screen- The soItware shall display inIormation to the user via the
monitor screen.
(b) Mouse- The soItware shall interact with the movement oI the mouse and the
mouse butons. The mouse shall activate imput and output, command buttons
and select options Irom menus.
(c) eyboard- The soItware shall interact with the keystrokes oI the keyboard. The
keyboard will input data into the active areas oI the G&I.
(d)Flat-Bed Scanner Optional]- The soItware senses the input Irom the scanner and provide the user to save
the scanned document in a user speciIied Iormat.
(e)Camera- The Camera image can also be used Ior capturing Documents.
. Software Interfaces
(a) Net Beans 7.0
(b)Neuroph Studio.
. Role and Responsibility
The organi:ation of a team depends on its size and the Iamiliarity oI members with one another. For
larger, newly Iormed teams it may help to assign more concrete roles to members. More inIormal roles may
work well Ior smaller teams. Depending on a team's speciIic circumstances, some members can even alternate
positions on a regular basis.
The team members Ior the proposed system are:
1) Pushpendra singh bais
2) Shailesh prajapati
3) Sandeep patel
4) Pavan sharma
. Managerial Process Plans
.1 Start-up Plan
Estimates:-
The estimates oI the project depend on the type oI project, time taken to complete the
project and at last the number oI manpower required to complete it.
Resource Acquisition:-
The resource acquisition depends on the project modules. Hence the allocation oI resource
is done by our college.
. Project %racking Plan
This points covers number oI things like Requirements Managements, Schedule Control and Quality
Control. Here all this points are important requirement management is very important thing Ior the user as
well as project which we want to deploy, in deployment project has system requirement and staII has
resource requirement.
Schedule control means to divide the time Ior the completion oI project, this management is very
important not because it is necessary to complete the project on time.
Budget control and quality is one oI the most important requirements oI user, hence to satisIy the user a
programmer should keep both these things in mind.
. Risk Management Plan
This point is most important Ior either user or developer perspective because risks are in both side. From
developer side it is important to have data security.
.4 Project closeout Plan
Time to complete the project is one oI the most important things, because it may be harmIul Irom both side
in cost and etc.
4. Supporting Process Plans
4.1 Process Model:-Several models exist to streamline the development process. Each one has its pros and
cons, and it's up to the development team to adopt the most appropriate one Ior the project. Sometimes a
combination oI the models may be more suitable.
The waterfall model is a sequential design process, oIten used in soItware development processes , in which
progress is seen as Ilowing steadily downwards (like a waterIall ) through the phases oI Conception, Initiation,
Analysis , Design, Construction, Testing , Production/Implementation and Maintenance .
This is in Iact the way the term has generally been used in writing about soItware developmentas a way to
criticize a commonly used soItware practice. The waterIall model is a systematic and sequential approach to
soItware development that begins at the system level and progresses through Iollowing phases:
kequ|rement Ana|ys|s ln Lhls phase of our pro[ecL Lhe requlremenLs of Lhe sysLem are analyzed
whlch enables Lo undersLand Lhe naLure of Lhe sofLware Lo be bullL 1he lnformaLlon domaln requlred
funcLlon behavlor performance and lnLerfaces are sLudled
es|gnln Lhls phase we had Lo declde Lhe daLa sLrucLure sofLware archlLecLure lnLerface deLalls of
Lhe pro[ecL 1hen Lhls deslgn ls LranslaLed lnLo codlng ln Lhe nexL sLep
Cod|n1he deslgn was LranslaLed lnLo machlne readable form ln Lhls sLep
1est|ngln Lhls phase new componenLs LhaL ls whlch are noL Lhe reusable ones and lnLerfaces of Lhe
sysLem had Lo be LesLed
,a|ntenance 1he phase ln whlch Lhe modules are updaLed or changed accordlng Lo requlremenL of
Lhe cllenL
The unmodiIied "waterIall model". Progress Ilows Irom the top to the bottom, like a waterIall.
42 Why Used Ior these ro[ect
We selecL Lhls model for our pro[ecL [usL only because lL ls easy Lo undersLand and Lhe phases of SuLC are
very much famlllar for Lhe programmer lL ls Llnearly SequenLlal model because lLs phases work one by one
accordlng Lo lLs sequences
5. Supporting Process Plan
5.1 Configuration Management
ConIiguration management is the important part oI any project, it very important to know conIiguration oI
the system or requirements i.e. memory requirement database and internet connection etc.
5. Verification Management
Security is one oI the most important issue in any soItware and website, hence it is important to do the
veriIication management to make our product secured.
5. "uality Assurance
ow cost and best quality is the requirement oI all the clients, security and perIormance are the things which
helps to make the product oI good quality
5.4 Review and Audits
Review and Audits applies to all projects documents, soItware conduct speciIic reviews and audits that
need is deIined by the project and quality plans. Also applies to the audit oI the quality management system.
It provides deIinition and uniIorm requirements to enable project staII to perIorm the necessary reviews and
audits oI products and processes.