A

Project Report
on

OCR OF TEMPLE INSCRIPTIONS AND

TRANSLATIONS IN DEVANAGARI
SCRIPTS.
Submitted in Partial Fulfillment of
the Requirements for the Degree
of

Bachelor of Engineering
in

Information Technology
to

Kavayitri Bahinabai Chaudhari

North Maharashtra University, Jalgaon
Submitted by

Mayur Matsagar
Dhanshri Borse
Snehal Patil
Rushikesh Bhalerao
Jay Chavda
Under the Guidance of

Dr. Pankaj Zope Mr. Kunal Pawar.

DEPARTMENT OF INFORMATION TECHNOLOGY

SSBT’s COLLEGE OF ENGINEERING AND TECHNOLOGY,
BAMBHORI, JALGAON - 425 001 (MS)
2022 - 2023
 SSBT’s COLLEGE OF ENGINEERING AND TECHNOLOGY,
BAMBHORI, JALGAON - 425 001 (MS)
DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE

This is to certify that the project entitled OCR OF TEMPLE INSCRIPTIONS

AND TRANSLATIONS IN DEVANAGARI SCRIPTS. , submitted by

Mayur Matsagar
Dhanshri Borse
Snehal Patil
Rushikesh Bhalerao
Jay Chavda

in partial fulfillment of the degree of Bachelor of Engineering in Information Tech-

nology has been satisfactorily carried out under my guidance as per the requirement
of Kavayitri Bahinabai Chaudhari North Maharashtra University, Jalgaon.

Date: March 23, 2023

Place: Jalgaon

Dr. Pankaj Zope

Mr. Kunal Pawar.
Guide

Dr.Manoj E. Patil Prof.Dr.G.K.Patnik

Head Principal

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) i

Acknowledgements

We would like to express our deep gratitude and sincere thanks to all who helped us in
completing project report successfully. Many thanks to almighty God who gave us the
strength to do. Our sincere thanks to Prof. Dr. G. K. Patnaik, Principal for providing
the facilities to complete the Project report. We would like to express our gratitude and
appreciation to all who gave us the possibility to complete the report. A special thanks to
Dr. Manoj E. Patil, Associate Professor, Head of the Department, whose help, stimulating
suggestions and encouragement, helped us in writing the report. We would also like to thank
Mr.Pankaj Zope and Mr.Kunal Pawar, Associate Professor and Project Guide, who has given
his full effort in guiding us and achieving the goal as well as his encouragement to maintain
the progress in track. I am also sincerely thankful to Mr.Aakash D Waghmare, Assistant
Professor, Incharge of the Project, for his valuable suggestions and guidance. We would also
like to appreciate the guidance given by other supervisor which has improved our presentation
skills by their comments and tips. Last but not the least, We are extremely thankful to our
parents and friends without whom it could not reach its successful completion. Thank You.

Mayur Matsagar
Dhanshri Borse
Snehal Patil
Rushikesh Bhalerao
Jay Chavda

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) ii

Contents

Acknowledgements ii

Abstract 1

1 Introduction 2
1.1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Problem Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5 Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.6 Selection of Life Cycle Model for Development . . . . . . . . . . . . . . . . . 4
1.7 Organization of the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.8 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Project Planning and Management 8

2.1 Feasibility Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.1 Economical Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.2 Operational Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.3 Technical Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Project Scheduling: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 Effort Allocation : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.5 Cost Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.6 Summary : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Analysis 14
3.1 Requirement Collection and Identification : . . . . . . . . . . . . . . . . . . 14
3.1.1 Eliciting Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.2 Analyzing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.3 Recoding Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Software Requirement Specification (SRS) : . . . . . . . . . . . . . . . . . . 15

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) iii

 3.2.1 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.2 Non-Functional Requirements . . . . . . . . . . . . . . . . . . . . . . 15
3.2.3 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.4 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.3 Summary : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4 Design 17
4.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3 UML Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.3.1 Use case Diagram : . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3.2 Class Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3.3 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.3.4 Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.3.5 Deployment Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.3.6 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5 Coding / Implementation 26
5.1 Algorithm/Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2 Software and Hardware for development in detail . . . . . . . . . . . . . . . 26
5.2.1 Hardware Requirement . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2.2 Software Requirement : . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3 Project Modules : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.4 Summary : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6 Testing 28
6.1 Black Box Testing/White Box Testing . . . . . . . . . . . . . . . . . . . . . 28
6.1.1 Black Box Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.1.2 White Box Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2 Manual/Automated Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.3 Test case identification and execution . . . . . . . . . . . . . . . . . . . . . . 30
6.4 Summary : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7 Result and Discussion 31

7.1 Results : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

8 Conclusion and Future Work 34

8.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) iv

 8.2 Future Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

A 35

Bibliography 36

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) v

List of Tables

2.1 Effort Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

2.2 cost Estimation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) vi

List of Figures

1.1Prototype model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Project Scheduling Chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1 System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Data flow diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
4.3 Use case Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
4.4 Class Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.5 Sequence Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
4.6 Component Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
4.7 Deployment Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
4.8 Activity Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.1 Home Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.2 Translation Result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 32

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) vii

Abstract

Hindi is that the most usually auditory communication in India, with in more than three
hundred million speakers. As there’s no division between the characters of writings writ-
ten in Hindi as there’s in English, the Optical Character Recognition (OCR) frameworks
created for the Hindi language convey a poor recognition rate. During this paper we have
a tendency to propose AN OCR for written Hindi content in Devanagari script content,
utilizing Artificial Neural Network (ANN), that improves its productivity. one in every of
the numerous functions behind the poor recognition rate is mistake in character division.
The closeness of contacting characters within the examined records more entangles the divi-
sion procedure, creating an interesting issue once designing a compelling character division
methodology. Pre-processing, character division, embrace extraction; lastly, grouping and
recognition area unit the important advances that area unit pursued by a general OCR. The
pre-processing tasks thought of inside the paper conversion of gray scaled footage to binary
footage, image rectification, and segmentation of the document´s matter contents into para-
graphs, lines, words, thus at the extent of basic symbols. the basic symbols, obtained as
a result of the essential unit from the segmentation methodology, recognized by the neural
classifier. Neural Network is one in every of the foremost wide used and common techniques
for character recognition downside. This paper discusses the classification and recognition of
written Hindi Vowels and Consonants mistreatment Artificial Neural Networks. The vowels
and consonants in Hindi characters are often divided in to sub teams supported bound vital
characteristics for every cluster, a separate network is meant and trained to acknowledge the
characters that belong to it cluster. Keywords:-Artificial neural Newtwork(ANN)

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 1

Chapter 1

Introduction

Optical Character Recognition (OCR) is an essential task for various applications, and nu-
merous approaches have been considered so far. Recently, the most widely used OCR models
are based on long short term memory-connectionist temporal classification (LSTM-CTC) [1]
or sequence to sequence (seq2seq) models with attention [2], which takes a sequence of slices
(narrow sub-images) as inputs and yields a sequence of recognition results. This approach al-
lows us to build an OCR system without explicit character segmentation. Also, it naturally
learns inter-character correlations by exploiting character-transition statistics. Therefore,
many current open source systems such as Tesseract [3] are based on this LSTM-CTC model
and provide the state-of-the-art performance in English recognition. However, the accuracy
of LSTM-based methods for other languages such as Chinese and Korean are not as high
as English. This is mainly because these kinds of languages have a large number of char-
acters compared to English; Chinese and Korean have thousands of character classes and
there are a huge number of possible cases even if we only consider pairwise combinations.
Therefore, unlike English, explicit character segmentation and individual character recogni-
tion are important for these types of languages. Based on these observations, we propose
a new multi-lingual OCR framework: We develop recognizers for individual languages and
incorporate them into a single framework in a globally optimized way

1.1 Background
Inscriptions are a great source to look back to ancient history and learn from it, discover
truths and may be secrets of life. Apart from the inscriptions in the country, there are
inscriptions in Sri Lanka and South East Asia, where we can find abundant inscriptions
in local languages, Sanskrit and Tamil In recent years, with the development of computer
sciences, computer technology has been applied to comprehensive fields. Language barriers is
one of the most important scenario. The web application has brought major changes all over
the world. We develop a web application which helps in providing the accurate translation

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 2

for the input language.We implement an efficient and user friendly web application. Hence
the application provides a solution through a simple interface which helps to overcome the
time consuming process. The project is completely based on Optical Character Recognition
for multi languages. The utility and main objective of the project is to add automation to
the process in an institution. This is an online based application so it can provide efficiency
to acquire, store and process.

1.2 Motivation
One of the major problems OCR technology can help in solving is extracting data from
structured, unstructured documents, and hand-written documents, making it easy for orga-
nizations to automate the data entry or document digitization tasks. Other problems that
OCR technology helps in solving includes: OCR eliminates the chances of errors in data entry
task that usually arise while per- forming it manually. It helps in the identity verification of
individuals. In the verification process, OCR helps to extract the user information from their
identity document and match it with the one already provided by the user. OCR reduces the
time required to convert manual documents into digital form. In addition to time, the cost
of digitizing the docu- ments also reduces. Aside from all of these benefits, AI-based OCR
also known as intelligent OCR engines have the ability to automatically detect ad extract
the required information and fill-out those details in the digital copy of the document itself.

1.3 Problem Definition

There are lakhs of inscriptions that are scattered throughout the length and breadth of our
Great Nation. These inscriptions were usually found on the walls of the Heritage sites like
Forts. Temples and other ancient structures, so that people in that era could access them.
A common man is deprived of this great knowledge, which if deciphered into understandable
script can shed light into lot of crucial aspects for the mankind.

1.4 Scope
The scope of this product Optical character Recognition of temple inscription is to provide an
efficient and enhanced software tool for the users to perform inscription document image anal-
ysis, document processing by reading and recognizing the characters in research, academic,
governmental and business organizations that are having large pool of document.Irrespective
of he size of documents and the type of characters in documents, the product is recognizing
them, searching them and processing them faster according to the needs of the environment.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 3

1.5 Objective
The objective of this product is to develop a responsive and accountable attitude among all
the users in order to maintain a historical data as it is. Many of the inscriptions are couched in
extravagant language, but when the information gained from inscriptions can be corroborated
with information from other sources such as still existing monuments or ruins, inscriptions
provide insight into world’s dynastic history that otherwise lacks contemporary historical
records. Digital archiving of these images is necessary for conservation and accessibility. The
major challenges of digitization of such images are blurred edges of the text and minimum
distinction between text and nontext parts.

• To Maintain the historical data as it is.

• Information of OCR can be readable with high degree of accuracy. Flatbed scanners
are very accurate and may produce reasonably top quality images.

• Processing of OCR information is fast. Large quantities of text are often input quickly.
is cheaper than paying someone amount to manually enter great deal of text data.
Moreover it takes less time to convert within the electronic form.

• To co-ordinate between students and Departments / Sections to redress the grievances.

• To reduce paperwork.

• Reduced operational time.

• Increased accuracy and reliability.

• Reducing human efforts.

• Easy maintains of Data.

1.6 Selection of Life Cycle Model for Development

The four basic process activities of specification, development, validation and evolution are
organized differently in different development processes. In the prototype model, they are
organized in sequence, while in incremental development they are interleaved. Software
Development Life Cycle (SDLC) is a process used by the software industry to design, develop
and test high quality software. The SDLC aims to produce a high quality software that meets
or exceeds customer expectations, reaches completion within times and cost estimates.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 4

 Figure 1.1:Prototype Model

The Prototyping Model is one of the most popularly used Software Development Life Cycle
Models (SDLC models).This model is used when the customers do not know the exact project
requirements beforehand. In this model, a prototype of the end product is first developed,
tested and refined as per customer feedback repeatedly till a final acceptable prototype is
achieved which forms the basis for developing the final product. The Prototyping Model is
one of the most popularly used Software Development Life Cycle Models (SDLC models).This
model is used when the customers do not know the exact project requirements beforehand.
In this model, a prototype of the end product is first developed, tested and refined as per
customer feedback repeatedly till a final acceptable prototype is achieved which forms the
basis for developing the final product.

• Requirement Analysis: A prototyping model starts with requirement analysis. In

this phase, the requirements of the system are defined in detail. During the process,
the users of the system are interviewedto know what their expectation from the system.

• System Design: Prototyping is the process of building a model of a system. In terms

of an information system, prototypes are employed to help system designers build an
information system that intuitive and easy to manipulate for end users.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 5

 • Implementation: A prototype is a partial implementation of a product expressed
either logically or physically with all external interfaces presented (Kan, 2003). It must
be producible with significantly effort than the planned product

• Integration and Testing: The objective of this phase is to perform system integra-
tion testing of the developed system. The systems integration test function is to ensure
that the developed systems meet all the technical requirements with the components
and subsystems integrated.

• Maintenance: The maintenance phase of the SDLC occurs after the product is in
full operation. Main- tenance of software can include software upgrades, repairs, and
fixes of the software if it breaks. Software applications often need to be upgraded or
integrated with new systems the customer deploys.

1.7 Organization of the report

Chapter 1: Entitled as Introduction describes the details about Background, Problem Def-
inition, Scope and Objective of the project, Identification of Software Development Process
Model and Organization of report.
Chapter 2:: Entitled as Project Planning and Management consists of details about the
Mod- elling of Grievance System, Feasibility Study, Risk Analysis, Project Scheduling and
Cost Estimation of the project.
Chapter 3: Entitled as Analysis describes in detail, the Requirement Collection and Identi-
fication, H/w and S/w Requirements, Functional and Non-Functional Requirements and a
Software Requirements Specification (SRS).
Chapter 4: Includes design about System Architecture, Data Flow Diagram and various
UML Diagrams.
Chapter 5: Consists of coding and implementation phases of the application.
Chapter 6: Briefs about various types of testing phases against which the application is
tested.
Chapter 7: Describes the results or the outputs of application and also discussion about
Advantages as well as disadvantages of proposed system.
Chapter 8: Provides the conclusion and future work which can be done on the topic.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 6

1.8 Summary
In the chapter all the details about problem definition, motivation, scope, objective of the
project and selection of software development model are included. In the next chapter,
description about the Project Planning and Management is provided.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 7

Chapter 2

Project Planning and Management

The chapter includes details regarding Feasibility study, Risk Analysis, Project Scheduling,
Effort Allocation and Cost Estimation as well as a short summary. Section 2.1 includes
details regarding feasibility that includes Operating, Economical and Technical feasibility.
Details regarding Risk Analysis like Commercial risks, Design risks and other risks as well
are discussed in Section 2.2. Section 2.3 provides explanation about Project Scheduling while
section 2.4 describes the effort allocation i.e effort taken by each group member. Section 2.5
provides information about cost estimation of the project.

• Modeling of VedAnuvad:

The modeling of proposed SGS requires a completely automated system, thus helping the
user retrieve the information as soon as possible. The backup plans are provided in the form
of the database helping avoiding data in case of catastrophic situations. Hence, the system
is reliable to perform in adverse situations. The system is scalable and can be expanded
and customized to meet the needs of the firms for which it will be implemented. Moreover,
the system provides a user-friendly interface with a realistic view. The system provides
search facilities to search a specific entry matching in the database, and this system consists
of an auditor as a supreme body to monitor the entire system’s performance. The system
consists of an administrator and a collector within whom the tasks can even be passed at
the time of encountering someone not proficient in handling the given task, and thus the
system works smoothly without further delays. Victim’s authentication is done beforehand
in order to avoid the nuisance which might arise in the manual system. The aim of the
proposed GRS (prototype in Fig. 2) is to address the issues present in the current system,
implement validation techniques (with respective stakeholders, as shown in Fig. 3) that will
help reduce the margin of error in operations, providing adequate data backup facilities in
order to ensure system restart even after a calamity and ensures consistency. It is a foolproof
system that simulates and replaces the present manual system.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 8

2.1 Feasibility Study
Feasibility study examines how beneficial is the project economically, technically and opera-
tionally. The student grievance system is truly feasible project and satisfies all the conditions
described below.

2.1.1 Economical Feasibility

The project can be regarded as economically feasible because the organization possesses the
computer system with them, so there is no need of bearing any cost on resources needed for
the development of system.

2.1.2 Operational Feasibility

People are inherently resistant to change and computer has been known to facilitate changes.
An estimate should be made of how strong the user is likely to move towards the develop-
ment of computerized system. These are various levels of users in order to ensure proper
authentication and authorization and security of sensitive data of the organization. proposed
project is beneficial only if it can be turned into information systems that will meet the or-
ganizations operating requirements.Simply stated, this test of feasibility asks if the system
will work when it is developed and installed.Are there major barriers to Implementation?
feasible based on the following:

• Is there sufficient support for the project from management from users? If the current
system is well liked and used to the extent that persons will not be able to see reasons
for change, there may be resistance.

• Are the current business methods acceptable to the user? If they are not, Users may
welcome a change that will bring about a more operational and useful systems.

• Have the users been involved in the planning and development of the project?

• early involvement reduces the chances of resistance to the system and in general and
increase the likelihood of successful project.

2.1.3 Technical Feasibility

The criteria for technical feasibility of student grievance system are:-

• Route Discovery:- Route discovery mechanism is discussed below. The steps for
route discovery are as follows:

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 9

 • Easy to use:- The users were assumed to normal ordinary people having knowledge
of simple computer operation for the user and basic knowledge of database operations
for the student grievance cell administrator, so ease of use is a very essential factor if
we want to get the problem solved quickly.

• Reliability:-As tables are used for storing data, so reliability is maintained as exact
data is retrieved.

• Portabi-lity:- The project can easily run on any computer machine.

• Serviceability:- This project try to provide maximum possible services to user.

In our project technical feasibility is considered up to a great extent. The website is build
using Html, CSS, Java Script which is freely available. Thus the problem of non-availability
of software does not appear. The backend of the system PHP and MY SQL which is freeware
database. Proposed system has the capacity to hold the data. It also provides data security
by password protecting.

2.2 Analysis
Taking decision on an uncertain event or situation may or may not be successful, which
is what risk is about. Risk management not only prevents organizations from entering
a dangerous and uncertain territory, which could lead to a catastrophic failures, but also
ensure the development and growth of the business. The depth and clarity with which a risk
is defined is critical for risk management. In an event where an organization has a low risk
situation at hand and decides to postpone rather than resolve the issue involved for financial
or other reasons, the risk may eventually become a threat of moderate to high level and this
could prove to be disastrous for management.

• Commercial Risks:

Following are some commercial risks identified in the project:

• Risk: Privacy Security also possess significant challenges that the IT industry. The
privacy of data for every user is must and everyone want that security in the Due to
inconsistencies in augmented reality programming, oversight, and negligence, there is.

• A legitimate chance of getting into trouble without meaning to do so.

• Risk: These elements are driving attention from reality which may cause a less clear
or improper information getting from this portal.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 10

 • Risk: At the moment, the majority of websites are one trick that can do big attack or
confusion between this other websites, thing which can be done without their assistance
with the same level of effectiveness.

• Design/Engineering Risks:

• Risk: Errors and design assumptions. Action to be taken: Use the expertise by project
coordinators.

• Other Risks:

• Risk: Co-ordination.

• Action to be taken: Give hundred percent by project coordinators.

2.3 Project Scheduling:

The section specifies the project scheduling of the project. Software project scheduling is an
activity that distributes estimated effort across the planned project duration by allocating
the effort to specific software engineering task. In the phase, we are identifying all the major
software engineering activities and the product function to which they are applicable. As
the linear sequential model have been selected for developing the project, the work is divided
according to the phases of the model. As a group of four members working on the project,
the project is scheduled accordingly. If the project development goes as per the planned
schedule, the project schedule defines the task and that must be tracked and controlled as
progress.

Figure 2.1: Project Scheduling Chart

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 11

2.4 Effort Allocation :
Each of the software project estimation techniques leads to an estimate of work units re-
quired for completion of the software development. The characteristics of each project task
dictate the distribution of efforts. There are four members in the project and there are four
phases such as Project Planning,Requirement Gathering, Analysis, Design.

Table 2.2 Effort Allocation

2.5 Cost Estimation

Cost estimation in project management is the process of forecasting the cost and other
resources needed to complete a project within a defined scope. Cost estimation accounts
for each element required for the project and calculate a total amount that determines a
project’s budget. If a project cost management system such as a software tool is used, and it
encompasses all the units of project controls, it would not be possible to ignore the execution
changes after the budget is baselined from the estimate data. This is because as the data is
the same, the inherent software structure forces any changes to be flushed out and be clearly
differentiated from the baseline. Therefore, the cost estimate will also be updated with the
changes during execution, which will keep the estimate dynamic and accurate

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 12

 Table 2.3 Cost Estimation

2.6 Summary :
In the chapter, all the details related to Project Planning and Management are mentioned.
In the next chapter, all the details regarding the requirements gathering and analysis are
presented.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 13

Chapter 3

Analysis

The chapter describes everything related to the requirement gathering and further analysis
such as hardware, software, functional and non-functional requirements. Also it has the
software requirements specification that provides complete description of the requirements of
the system. Section 3.1 describes requirement collection and identification. All the hardware
and software requirements are discussed in Section 3.2. Section 3.3 describes the functional
and non-functional requirements of the system to be developed. Section 3.4 describes the
Software Requirements Specification (SRS)

3.1 Requirement Collection and Identification :

In system engineering and software engineering, requirements analysis focuses on the tasks
that determine the needs or conditions to meet the new or altered product or project, taking
account of the possibly conflicting requirements of the various stakeholders, analyzing, doc-
umenting, validating and managing software or system requirements. The main objective
here is to understand the existing system thoroughly and check the feasibility requirements.
Requirements Analysis includes three types of activities:

3.1.1 Eliciting Requirements

The all information required for this process (E.g. the project charter or definition), Business
process documentation, and stakeholder interviews. Sometimes it is also called requirements
gathering or requirements discovery.

3.1.2 Analyzing Requirements

To analyze the every part of project and Determining Whether the stated requirements are
clear, complete, consistent and unambiguous, and resolving any apparent conflicts between
the analyzing phase.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 14

3.1.3 Recoding Requirements
Requirements may be documented in various forms where all information is provided, usu-
ally including a summary list and may include natural-language documents, use cases, user
stories, process specifications and a variety of s models including data models.

3.2 Software Requirement Specification (SRS) :

A software requirements specification (SRS) is a document requirement activity that captures
complete description about how the system is expected to perform. To provide proper and
correct documentation information for clarifying every information in detail. It is usually
signed off at the end of requirements engineering phase. The quality characteristics of SRS
must be according to the given guidelines:

• Correctness

• Completeness

• Consistency

• unambiguous

• Modifiability

• Verifiability

• Traceability

3.2.1 Functional Requirements

It deals with the functionalities required from the system which are as follows. The re-
quirement that where needed for this project and website and all the functionalities that
are required to help satisfy the main goal of the project are included within the functional
requirements. The interface is very user-friendly and easily understandable. The main aim
to solve the issues related to language barriers.It will preserve the historical data as it is.

3.2.2 Non-Functional Requirements

There are Quality Requirements that stimulate how well a software/websites does work it
has to do. The different browsers platforms are available to visit the websites like chrome,
Mozilla Firefox,etc. Performance of the number of terminals to be supported is dependent
on the server that will be used at the time of deployment.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 15

 The proposed system will thereby provide service and it can be monitored on a basis
where a server dependent performance will be mapped on time, when the websites will be
run successfully.

3.2.3 Hardware Requirements

Here, no requirements of hardware in this project. Only every user need a browser and active
internet connection.

1. Operating System: Any

2. RAM: 4GB or above

3. Processor: intel i3/AMD Ryzen 3000 or above

4. HDD/SSD: Any

3.2.4 Software Requirements

Software Requirement deal with denting software resource requirement and prerequisites that
need to visit the website to provide optimal functioning of an websites software. The website
is reactive as very compatible to every screen like pc/mobile/tablets. These Requirements
or pre-requisites are generally included in the software installation package and need to be
visit separately before the software is installed.

1. Operating System: Windows, linux.

2. Front End: HTML,CSS, JS.

3. Back End: Python, Django.

4. Libraries: NLTK, Numpy, Pandas, Pytesseract.

3.3 Summary :
In the chapter, Analysis was presented which included the hardware and software require-
ments, functional and non-functional requirements and the software requirements specifica-
tion (SRS) as well to give detail information about above points. In the next chapter, Design
is described along with various UML diagrams.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 16

Chapter 4

Design

System design provides the understanding and procedural details necessary for implement-
ing the system. Design is an activity concerned with making major decisions, often of a
structural nature.Software design is the rest of the three technical activities: designs, coding
and tests which are required to build and verify the software. Section 4.1 describes the Sys-
tem Architecture which includes. Description about the Data Flow Diagram is provided in
Section 4.2. Section 4.3 describes various UML diagrams related to the architecture. Section
4.4 provides a short summary.

4.1 System Architecture

Figure 4.1:System Architecture

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 17

4.2 Data Flow Diagram
A data flow diagram is a flowchart can help to visualize the data pipeline of a system user can
trace happens to the data as it moves between components. It is a great to find redundancies
and optimize the speed and responsiveness of software. A DFD is often used as a preliminary
step to create an overview of the system going into great detail, it can later be elaborated.
DFDs are used for the visualization of data processing (structured design). A DFD show
kind of information input to and output from the system, the data will advance through the
system, and it the data will be stored. It represented information of process timing processes
will operate in sequence or in parallel, unlike a traditional structured flowchart which focuses
on control flow, or a UML activity workflow diagram, which presents both control and data,
flows as unified model. A data flow diagram can dive into progressively more detail by using
levels and layers, zeroing in on a particular piece. DFD levels are numbered 0 or 1, and
occasionally go to even Level 3 or beyond. The necessary level of detail depends on the
scope of what you are trying to accomplish.

• DFD Diagram

• Student will choose the domain in which he/she has problem and raise Complain about
the issues he finds.

• Teacher has to login through his login id and can view the complaints that has been
raised by the students.

• Later, the teachers can view the complaint details and takes further actions required
accordingly. Each complaint will have a definite time limit associated with it.

• Later, the teachers can view the complaint details and takes further actions required
accordingly. Each complaint will have a definite time limit associated with it.

• Firstly the complaint will issued to class teacher when the time limit gets over and the
teacher takes no action then the same complaint gets promoted to HOD and he/she also
takes no action then it will be promoted to Principal wherein a message is forwarded
to through the system. This makes it easier for the teachers to recognize that the
complaint is come from the Grievance System.

• The student gets the notification whether the complaint is IN PROCESS or it has been
CLOSED by the teachers ON Dashboard.

• Student needs to check the complaint status whereas a teacher needs to check the
complaint regularly to see whether new complaint has been filed or not.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 18

 Figure 4.2: Data flow Diagram

4.3 UML Diagrams

Unified Modeling language (UML) is a standardized modeling language enabling developers
to specify, visualize, construct and document artifacts of a software system. Thus, UML
makes these artifacts scalable, secure and robust in execution. UML is an important aspect
involved in object-oriented software development. It uses graphic notation to create visual
models of software systems.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 19

4.3.1 Use case Diagram :
A Use Case diagram shows the interaction between the system and entities external to the
system. These entities are called actors which have specific role in the system. The figure
shows the use case diagram for proposed system. Purpose of Use Case Diagram is to know
or show functionality of the system.

Figure 4.3:Use Case Diagram Betweem Admin and User

4.3.2 Class Diagram:

A Class diagram is used to represent the static view of the system. It mainly uses classes,
interfaces and their relationships. The Figure shows the class diagram for proposed system.
Purpose of Class Diagram is to show structural aspects of the system.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 20

 Figure 4.4:Class Diagram

4.3.3 Sequence Diagram

A diagram that shows the existence of Objects over time , and the Messages that pass be-
tween those Objects over time to carry out some behaviour. A sequence diagram simply
depicts interaction between objects in a sequential order i.e. the order in which these inter-
actions take place. We can also use the terms event diagrams or event scenarios to refer to
a sequence diagram.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 21

 Figure 4.5:Sequence Diagram

4.3.4 Component Diagram

Component diagram is UML structure diagram which shows component and dependencies
between the component. Model diagrams allow to show different views of a system, for
example, as multi-layered (aka multi-tiered) application - multi-layered application model.
Following component diagram shows the components of the proposed system, hierarchy of
components and their relationships with each other.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 22

 Figure 4.6:Component Diagram

4.3.5 Deployment Diagram

Deployment Diagram is a type of diagram that specifies the physical hardware on which
the software system will execute. It also determines how the software is deployed on the
underlying hardware. It maps software pieces of a system to the device that are going to
execute it.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 23

 Figure 4.7:Deployment Diagram

4.3.6 Activity Diagram

The activity diagram is used to demonstrate the flow of control within the system rather
than the implementation. It models the concurrent and sequential activities. The activity
diagram helps in envisioning the workflow from one activity to another. It put emphasis on
the condition of flow and the order in which it occurs.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 24

 Figure 4.8:Activity Diagram

4.4 Summary
In the chapter, design and system architecture 4.1,Data Flow Diagram 4.2 is described with
UML diagram 4.3,Use case diagram 4.3.1 and class diagram 4.3.2.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 25

Chapter 5

Coding / Implementation

Important phase in system development is the successful implementation of the new system
design. Implementation includes all those activities that take place to convert from the old
system to the new system.
This chapter mainly contains following sections: Section 5.1 Algorithm /Steps 5.2 de-
scribed Software and Hardware Requirements in details. Section 5.3 described the project
modules and Section 5.4 described Summary.

5.1 Algorithm/Steps
1. Input image.

2. Preprocessing : Skew correlation algorithm.

3. Segmentation : Multipass correlation algorithm.

4. Feature extraction : Machine learning algorithm.

5. Classification : Support vector machine algorithm.

6. Output.

5.2 Software and Hardware for development in detail

Following are the Requirement of Hardware assets which are most necessary for Developing
as well as Handling the webside :

5.2.1 Hardware Requirement

Here, no requirements of hardware in this project. Only every user need a browser and active
internet connection.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 26

 1. Operating System: Any.

2. RAM: 4GB or above.

3. Processor: intel i3/AMD Ryzen 3000 or above.

4. HDD/SSD: Any.

5.2.2 Software Requirement :

Software Requirement deal with denting software resource requirement and prerequisites that
need to visit the website to provide optimal functioning of an websites software. The website
is reactive as very compatible to every screen like pc/mobile/tablets. These Requirements
or pre-requisites are generally included in the software installation package and need to be
visit separately before the software is installed.

• Operating System: Windows, linux.

• Front End: HTML,CSS, JS.

• Back End: Python, Django.

• Libraries: NLTK, Numpy, Pandas, Pytesseract.

5.3 Project Modules :

We follow the divide and conquer theory, so divide the overall problem into more manageable
parts and develop each part or module separately. When all modules are ready, integrate
all the modules into one system. In this phase, briefly describe all the modules and the
functionality of these modules.

5.4 Summary :
In this chapter, describe the Implementation details, Hardware and software requirements
in details, Modules of project and summary are presented. In the next chapter, Testing and
Test cases are presented.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 27

Chapter 6

Testing

Testing goes side by side with the implementation is aimed at ensuring the system works
accurately before the live operation is performed. The common view of testing held by the
user is to ensure they are no errors in a program. Testing usually means the process of
executing a program with explicit intention of handling errors. It depends on the process
and the associated stakeholders of the project.
The chapter mainly contains following sections:- Section 6.1 describes the Black Box
Testing. And the White Box Testing is described in the Section 6.2. Summery of the
chapter is described in the section 6.3.

6.1 Black Box Testing/White Box Testing

6.1.1 Black Box Testing
Black Box testing also known as Behavioral Testing, is a software testing method in which
the internal structure/design/implementation of the item being tested is not known to the
tester. Tests can be functional or non-functional, though usually functional. The method is
named so because the software program, in the eyes of the tester, is like a black box; inside
which one cannot see. such method attempts to find errors in the following categories:
The goal of the technique is to find issues in the following categories:

1. Incorrectly implemented Dialog flow causing vulnerabilities.

2. Errors in connecting to the database.

3. Errors in data structures.

4. Behavioral issues.

After the Successful Testing it was found that :

1. There is no incorrectly implemented Dialog flow causing vulnerabilities.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 28

 2. Application is connecting to the database Successfully each time.

3. No errors found in data structures.

4. Application has no behavioral issues.

6.1.2 White Box Testing

White box testing is testing of a software solution’s internal structure, design, and coding. In
this type of testing, the code is visible to the tester. It focuses primarily on verifying the flow
of inputs and outputs through the application, improving design and usability, strengthening
security. White box testing is also known as Clear Box testing, Open Box testing, Structural
testing, Transparent Box testing, Code-Based testing, and Glass Box testing.

1. Internal security holes

2. Broken or poorly structured paths in the coding processes

3. The flow of specific inputs through the code

4. Expected output

5. The functionality of conditional loops

6. Testing of each statement, object, and function on an individual basis

After Completion of Testing it was found that,

1. No internal security holes.

2. No broken or poorly structured paths found in the coding processes.

3. The flow of specific inputs through the code is working seamlessly.

4. For Every process Application is generating expected output.

5. conditional loops are functioning properly.

6. Testing of each statement, object, and function on an individual basis done successfully
with expected outputs.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 29

6.2 Manual/Automated Testing
Review requirements, specifications, user documentation, help files, and other project doc-
umentation to understand the system and assure quality of the products and automated tests
to be developed. Develop manual testcases based on requirements and then convert them
to automation Develop automation standards and processes Documenting design decisions
and ensuring adherence. As a Senior QA Engineer, you’ll work with open source tools to
automate testing Responsible for defining manual and automated testing strategy/standards
and the design of resilient automated test components and test programs.

6.3 Test case identification and execution

Test Case is the set of inputs along with the expected output and actual output some
additional information.

6.4 Summary :
In this Chapter, Testing of the project is described. In the next Chapter, Result of the
project s and Discussion about the project is described.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 30

Chapter 7

Result and Discussion

Result is a thing that is caused or produced by something else and also called as the con-
sequences and outcomes. Discussion is the action or process of talking about something in
order to reach a decision or to exchange ideas.
The organization of this Chapter is as follows. Section 7.1 represents the Result of the
Project. Discussion is described in Section 7.2. Finally, the last section 7.3 represents
Summary of this chapter.

7.1 Results :
Now here are the snapshot of Translation in Devanagari Scripts. In this section, we are
discussing through some of the snapshot of project.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 31

 Figure 7.1 :Home Page

Figure 7.1 shows the Home page as well as the first part which user has to be faced .It
also contains the VedAnuved upload Files and choose language which translate it.

Figure 7.2 : Translation Result

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 32

 Figure 7.2 shows the user interface , From where users will be able to see the file and see
the output result.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 33

Chapter 8

Conclusion and Future Work

8.1 Conclusion
• This work attempted at creating a universally applicable OCR system integrated with
audio output for ancient Maharashtra script.

• By using a CNN and Image Recognition techniques, an operable system was designed
for modern and ancient Maharashtra.

• The difference in the style of the ancient Maharashtra scripts from the modern Maha-
rashtra script posed as a challenge to execute the task efficiently .

• Multiple samples of ancient inscriptions from some historical temples were taken as
case studies to implement the developed methodology. An acceptable accuracy rate of
77.7was attained for these samples.

8.2 Future Scope

• What does the future hold for OCR? Given enough entrepreneurial designers and
sufficient research and development dollars, OCR can become a powerful tool for future
data entry applications. However, the limited availability of funds in a capital-short
environment could restrict the growth of this technology. But, given the proper impetus
and encouragement, a lot of benefits can be provided by the OCR system. They are

• We are trying to integrate speech to text and make in more efficient for users. 3.The
recognition of new font characters by the system is very easy and quick. 4.We are
trying to increase the accuracy near about 8013/16

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 34

Appendix A

Application is very simple to use . User have only emmulator. There is no any requirement
to any other installation process.

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 35

Bibliography

1. https://www.google.com/url?sa=tsource=webrct=jurl=https://www.irjet.net /archive/V8/i5/V
AOvVaw02qI 5konedx

2. https://www.geeksforgeeks.org/software-engineering-prototyping-model/

3. https://www.researchgate.net/publication/324621040AP prototype f or G rievance

R edressal S ystem

4. https://costmanagement.eu/blog-article/what-is-cost estimation-we-explain-it-to-you-
in- 4-steps

5. https://www.slideshare.net/miteshpatel414/complaint- management-system

6. https://www.chegg.com/homework-help/questions-and-answers/student-complaint-managemen
system-scms-scenario-student-actor-enters-details-order-regis- q26132437

7. https://creately.com/diagram/example/i1acnwpa1/grievance-redressal-system-

8. https://qdoc.tips/complaint-management-system-ppt-pdf-free.html

SSBT’s College of Engineering and Technology, Bambhori, Jalgaon (MS) 36