VACOE, AHMEDNAGAR

Chapter 2 REQUIREMENT ANALYSIS

Requirements analysis in and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders, such as beneficiaries or users. Requirement analysis forms the base for design and development. It provides the software designer with the representation of information, function, and behavior that can be translated to data, architectural, interface and component-level designs. The main objective is to state clearly what system wants e actly.

2.1 REQUIREMENT SPECIFICATION:! software requirements specification "#R#$ is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe all of the interactions that the users will have with the software. These specifications are of three types%

2.1.1 Normal Re !"reme#t$: o &'-(haracter recognition should be fast and efficient. o &)-*ser should be provided with the facility of modifying the user handwritten script database. o &+-,*I should be user friendly. Universal Real-Time Language Inde enden! OCR" -

VACOE, AHMEDNAGAR
o &--*ser should be allowed to specify feature e traction methods.

2.1.2 E%pe&te' Re !"reme#t$: o .'-#ystem should provide the facility for specifying input in terms of color and te ture pattern. o .)-#ystem should be platform independent. o .+-#oftware installation should be easy with necessary guidelines. o .--/odification in the database should be done in efficient manner. o .0-#ystem should be designed such that it can be e tendible to accommodate other features e traction methods. 2.1.( E%&"te' Re !"reme#t$: o 1'-#aving the generated output file in folder. o 1)-Identifying inpainting te t.

2.2 )al"'at"o# o* Re !"reme#t$:

Requirement validation e amines that all system requirements have been stated unambiguously and inconsistencies and errors have been detected and corrected. It also ensures that the work products confirmed to the standards established for the process, project and product. The work products produced as a consequence of requirements engineering are assessed during validation. Universal Real-Time Language Inde enden! OCR" 0

VACOE, AHMEDNAGAR
2.2.1 )al"'at"o# o* Normal Re !"reme#t$: &'-!lgorithms implemented should have less time and space comple ity. &)-(haracter database should remain consistent after modifications to the database. &+, &--The ,*I should be such that user can easily specify the query and retrieve saved files.

2.2.2 )al"'at"o# o* E%pe&te' Re !"reme#t$: .+-*ser should be provided with the necessary help files for installation and product use. .0-The #ystem should be e tended only if e tended module do not affect the consistency and performance of the system.

2.2.( )al"'at"o# o* E%&"te' Re !"reme#t$: 1)-#tore file paths of recently saved query character database.

2.( +ar',are Re !"reme#t$:

o 2entium - processor. o 0') /3 R!/. o -4 ,3 hard disk.

2.- So*t,are Re !"reme#t$:

Universal Real-Time Language Inde enden! OCR" 5

VACOE, AHMEDNAGAR
o 6indows 789)4449129:igher ;ersions of <perating #ystem. o <racle9#=>. o ?ava Technology.

Universal Real-Time Language Inde enden! OCR" @