Академический Документы
Профессиональный Документы
Культура Документы
]
Handwriting Classification
Version <1.0>
16-5-2O16
HIST0RY
DATE VERS10N EXPLANATION AUTH0RS
16-5-2O16 <1.O> Initial Version of Document FARWA NADEEM
TALAYA FARASAT
AYESHA ASHRAF
2UseCases........................................................................................................................................................2
2.1 ACT0RS...........................................................................................................................................2
2.2 USE CASES(LIST)..........................................................................................................................3
2.3 DIAGRAMS................................................................................................................................ ...4
2.4 USE CASES........................................................................................................................ ............9
3DesignOverview...........................................................................................................................................16
3.1 System Architecture........................................................................................................................27
3.2 System Interfaces............................................................................................................................30
3.3 Constraints and Assumptions..........................................................................................................35
4SystemObjectModel.....................................................................................................................................36
4.1 Introduction.....................................................................................................................................36
4.2 Subsystems......................................................................................................................................36
4.3 Subsystem Interfaces.......................................................................................................................36
50bjectDescriptions.......................................................................................................................................37
5.1 0bjects................................................................................................................... .........................37
60bjectC0llaboration............................................................................................................................. .........40
6.1 0bject Collab0ration Diagram........................................................................................................40
7Dynamic M0del.............................................................................................................................................41
7.1 Sequence Diagrams.........................................................................................................................41
7.2 State Diagrams................................................................................................................................47
8Non-functionalRequirements........................................................................................................................48
8.1 Performance Requirements.............................................................................................................48
8.2 Design Constraints..........................................................................................................................48
9SupplementaryDocumentation.....................................................................................................................48
1.Introduction
The application is developed for the classification of various hand written documents. We use
different machine learning techniques for achieving the target.
1.1Purpose
This project is mainly developed for the classification of different hand written samples. Our
main purpose is to identify the author or writer of the document .This project is developed for
this purpose.
Manually this work takes a lot of time and of course effort so our main target is to make a
efficient and reliable system to control crimes in courts. This system is also used in banks and
in businesses for the authentication of documents. Reliability is our main focus during making
a system. It is used in different places like in crime control agencies for investigation purposes.
Plagiarism can be controlled and Copy rights are promoted with the help of that system.
1.2 Scope
The scope of this system is vast as it is used for investigation purposes in many areas like
hospitals where the prescription authenticity is required. It is a type of biometric system
which is basically developed for authentication purposes. These type of systems are used for
crime control purposes and for verification in many areas or fields. It can be online as well
as offline.
1.4 Refernces
Software requirements specification (SRS) of hand written identification using image
processing techniques.
Intr0duction
Ussecase
Design 0verview
System 0bject model
0bject descriptions
0bject c0llaborations
Dynamic model
N0n functional requirements
Supplymentary d0cumentation
2 USE-CASES
2.1 ACT0RS
2.1.1 Writer
Writer are the users in Handwriting classification that provide or write a content by hand
and repeat this process to provide enough samples for application to learn it which will
be further used for unknown writing classification Writer can be any person some major
types are written bellow
Teacher
Student
Criminal
Author
Poet
Additional Inf0rmation: Writer is the only user on which this application is
based on in fact for which this application is designed because they will provide
the sample they will input it
.
Its basically not the writer .It is the End user of application who will gather the
samples from Writer train the system and get the Result from application and
perform some action on the basis of classification results.
DESCRIPTI0N BRIEFLY
This is basically for the insertion of sample. Then these samples are successfully stored in the memory for fute
utilizations.
Goal:
● The successful Insertion of New sample by some writer and system identify the sample
Success Measurement:
● The Sample is generated and inserted in system and now will be used for future classification
Precondition:
● Writer must first be registered in System before submitting the sample to recognize it later.
● DATASETS must be completed so that the data must be appropriate and sufficient.
TR1GERS
● The time arrives when samples are successfully inserted
USECASE
EVEVT
DESCRIPTION
EVENTS FL0W
1. A writer is first registered in system to be used further
2. Samples from that writer are gathered and Entered
3. Writer can view or remove the inserted samples
4. Once this process is repeated for all writers then classification is initiated by providing unknown
content
Assumptions
1. It is assumed that Writer will write the sample content on a clean paper that can be easily OCR
2. It is assumed that the System will learn all the locates easily based on features and it is locate
independent
3. Assumption is that a sample will be provided instead creating and inserting without following any standard
Implementation Constraints and Specifications: System will b implemented minimum 3.1 processor dual
core to work efficiently for desired outcomes greater configuration is suggested
DESCRIPTI0N BRIEFLY
This is basically for the insertion of sample. Then these samples are successfully stored in the memory for fute
utilizations.
MAIN G0AL:
● The successful Insertion of New sample by some writer and system identify the author.
Success Measurement:
● The Sample is generated and inserted in system and now will be used for future classification
Precondition:
● Writer must first be registered in System before submitting the sample to recognize it later.
● DATASETS must be completed so that the data must be appropriate and sufficient.
TR1GERS
● The time arrives when samples are successfully inserted.
USE CASE
EVENTS
DESCRIPTION
EVENTS FL0W
1. A writer is registered in system by entering his name his sample space will be created
2. He will write the content according to some standard template
3. The System Under Design uses that sample to train and learn the basic features of the fonts of
content written.
4. The System Under Design uses predefined features that it will get of each font of each content of
every writer and learn it
5. Exception: if the data is not enough or the sample does not satisfy the constraints then the
exception is raised and Writer is alerted to re insert or generate the samples this will be repeated
unless System under development will get the accurate sample to proceed
6. data rejected (invalid) to train well software so ultimately learning of garbage data will effect
the results
7. population and classification will occur on the basis of dataset created by the samples previously
provided
8. preview the results is allowed to users and report generated then to re-classify it after changing the
criteria or filter
9. for data modification return to (SAMPLE MANAGEMENT SYSTEM) and alter samples or remove
10. The preview is based on the Classification table consisting the match confidence and accuracy
and the recognized writer
Implementation Constraints and Specifications: System will b implemented minimum 3.1 processor dual
core to work efficiently for desired outcomes greater configuration is suggested
.
DESCRIPTI0N (BRIEFLY)
This is basically for the deletion of samples. Then these samples are successfully remove from the memory
MAIN GOAL:
● The successful deletion of sample from system
Success Measurement:
● The sample is selected by Writer and then successfully removed without disturbing other ones
Prec0nditi0ns:
● Before deleting the sample a Writer must be exist in System and have submitted atleast one
sample
● DATASETS must be completed so that the data must be appropriate and sufficient.
TR1GERS
● The time arrives when samples are successfully deleted.
USECASE
EVENTS
DESCRIPTION
EVENTS FLOW
1. A writer is first recognized and assured whether he exists in system to be used further
2. Samples from that writer are gathered and then located
3. Writer can view or remove the inserted samples
4 . Once this process is repeated for all writers then classification is initiated by providing
unknown content
Assumptions
1. It is assumed that Writer will be already registered and just select the samples from the list of
samples he submitted to remove
2. It is assumed that the System will not affect the other samples of the same writer as well as the
other writers.
3 Assumption is that a sample will be provided instead creating and inserting without following any standard
DESCRIPTI0N (BRIEFLY)
This use case describes the removing of sample that was previously inserted in the training set
MAIN GOAL:
● The successful deletion of sample from system
Success Measurement:
● The sample is selected by Writer and then successfully removed without disturbing other ones
Prec0nditions:
● Before deleting the sample a Writer must be exist in System and have submitted atleast one
sample
● DATA-SETS must be completed so that the data must be appropriate and sufficient.
TR1GERS
● The time arrives when samples are successfully deleted.
USECASE
EVENTS
DESCRIPTION
Assumpti0ns
1. It is assumed that Writer will b already registered and just select the samples from the list of
samples he submitted to remove
2. It is assumed that the System will not affect the other samples of the same writer as well as the
other writers
3. Assumption is that a sample will be provided instead creating and inserting without following any
standard
Implementation Constraints and Specifications: System will b implemented minimum 3.1 processor dual
core to work efficiently for desired outcomes greater configuration is suggested
DESCRIPTI0N (BRIEFLY)
It is for the classification the samples provided by the different writers . System attempts to check if the training set exits so if
yes that means samples are present so it proceeds and start training and then classify or else it enquires the data set
MAIN GOAL:
● The successful completion of Training module and Classification module
Success Measurement:
● The system is trained quickly and the unknown samples is classified and recognized on the fly
Trigger:
● Classifier has generated the results and is now ready to be viewed
USECASE
EVENTS
DESCRIPTION
EVENTS FL0W
Implementati0n C0nstraints and Specificati0ns: System will b implemented minimum 3.1 processor dual
core to work efficiently for desired outcomes greater configuration is suggested
DESCRIPTI0N (BRIEFLY)
It is for the classification of the samples provided by the different writers . System attempts to check if the training set exits so
if yes that means samples are present so it proceeds and start training and then classify or else it enquires the data set
MAIN GOAL:
● The successful completion of Training module and Classification module
Measurement of success:
● The system is trained quickly and the unknown samples is classified and recognized on the fly
Prec0ndition:
● Atleast two writers must exists in system so that classification will take place
● Enough samples must be present to initiate the system
TR1GERS
● Classifier has generated the results and is now ready to b viewed
EVENTS FL0W
1. Writer user samples are ready to b passed to the learner module
2. Learner module passes it to the feature extractor and returns the object
3. they are then stored which is reffered as learning
4. The System Under Design now proceeds next to start classification
5. Destination address(es) for the result is selecting by user .
Assumpti0ns
1. Assuming Writers are enough and samples are also enough to properly initiate classifier..
Implementation C0nstraints and Specifications: System will b implemented minimum 3.1 processor dual
core to work efficiently for desired outcomes greater configuration is suggested
OS win linux
pre
procesor
core
Application main module
capture
validator
device
USER INTERFACE
● The user interface is the interface through which the user interacts with
the system. Our interface has many options for the user for example
first for upload image then analysis and then classes and classification.
It must be multi tab for proper functioning and data visualization must
be clear and complete. we draw the expected interface for our system
and explain the process step wise for clear understanding.
.
ASSUMPTI0NS
Assumptions are made that the the System under construction will be used by
different writers like students or Teachers as well as authors or bankers as well by
defining the different sources above it is obvious that the sites of usage will also vary
from actor to actor like a banker will use it in banks to identify the illegal passed
document by analyzing it.
DEPENDENC1ES
This is basically for the descriptions of subsystem in the system as our system hand written
classification depends on subsystem sample management system.
4.2 SUB-SYSTEMS
Sample_Manager is the class which is responsible for the handling of input and
removing of all user samples
It is the class which is the engine of our under developing system as it will actually classify the
results
}
}
return req;
}
9 SUPPL1MENTARY D0CUMENTATI0N
9.I REQUIRED TOOLS
THE TOOLS USED ARE BASICALLY (UML) Unified modeling language T00LS