Group-29

Software Engineering Lab

OCR Based Image Text to Speech

Converter System for People with
Visual Disability

Software Estimation Report (SER)

Submitted by:
Krishan Kumar [2021IMT-055]

Ritik Singh [2021IMT-081]

Satyarohan Prakash [2021IMT-086]
 Software Project Estimation Report

Table of Contents

1.0 SIZE ESTIMATION 3

1.1 Function Point Metric 3

1.3 Step 2: Refine Parameters 5

1.4 Step 3: Refine UFP based on the complexity adjustment factor 6

2.0 EFFORT AND TIME ESTIMATION 7

2.1 COCOMO Model: 7

2.2 Estimation of development effort: 8

2.3 Estimation of development time: 8

3.0 PROJECT SCHEDULE BREAKDOWN 8

3.1 Activity Network 8

3.2 PERT Chart 10

2
 Software Project Estimation Report

1.0 SIZE ESTIMATION

It’s important to understand that project size estimation is the most fundamental parameter. If this
is estimated accurately, all other parameters like effort, duration, cost, etc., can be determined
easily.
Currently, two techniques used to estimate project size are:
1. Lines of code or LOC
2. Function point
Both of the above serve as important project size estimation metrics. For our report,
we will be using the Function Point metric.

1.1 Function Point Metric

The function point metric proposes that the size of the software project is directly dependent on
the various functionalities it supports. The more the features supported, the more the size would
be. This technique helps determine the size of the project directly from the problem specification,
so it is helpful to project managers during project planning while determining size.

1.2 Step 1: UFP (Unadjusted Function Point) Computation

Inputs

1. Image input for OCR

2. OCR processing
3. Text extraction
4. Text-to-speech conversion
5. User settings and preferences
6. Error handling

Total Number of Inputs = 6

Total Number of Inputs = 9

Outputs

1. Extracted text
2. Audio output
3. User feedback
3
 Software Project Estimation Report

Total Number of Outputs = 3

Inquiries

1. Request for OCR

2. User settings and preferences
3. User feedback

Total Number of Inquiries = 3

Files

1. User profiles
2. Settings and preferences

Total Number of Files = 2

Interfaces

UFP Calculation:

UFP = (Number of inputs) * 4 + (Number of outputs) * 5 + (Number of inquiries) * 4 + (Number of

files) * 10 + (Number of interfaces) * 10

UFP = (6 * 4) + (3 * 5) + (3 * 4) + (2 * 10) + (0 * 10) = 107

1.3 Step 2: Refine Parameters

Below table is an FPA matrix that shows the weight adjustment factor Type: Simple
Average Complex

Simple Average Inputs

Inputs 3 4 6
Outputs 4 5 7
4
 Software Project Estimation Report

No. of inquiries 3 4 6
No. of files 7 10 15
No. of interfaces 5 7 10

UFP will be computed using the following equation:

UFP =

Where Wi j is the Weight adjustment, and Ci j is the count of values.

Simple Average Inputs

Inputs 0
6 2

Outputs 0
4 3

No. of inquiries 0
3 2

No. of files 0
2 0

No. of interfaces 0
0 0

5
 Software Project Estimation Report

FPA Matrix (Simple, Average, Complex)

• Inputs: 6 Simple + 2 Average + 0 Complex

• Outputs: 4 Simple + 3 Average + 0 Complex
• Inquiries: 3 Simple + 2 Average + 0 Complex
• Files: 2 Simple + 0 Average + 0 Complex
• Interfaces: 0

Refined UFP:

= ((6 * 3) + (2 * 4) + (0 * 6)) + ((4 * 4) + (3 * 5) + (0 * 7)) + ((3 * 3) + (2 * 4) + (0 * 6)) + ((2 * 7) + (0

* 10)) + (0 * 0) = 70

1.4 Step 3: Refine UFP based on the complexity adjustment factor

In this step, we refine the Unadjusted Function Points (UFP) calculated earlier by applying a
Complexity Adjustment Factor (CAF). The CAF is determined based on the complexity of the
software project, taking into account various factors that influence the project's complexity.

Function Point Relative Complexity Adjustment Factors Score: The complexity factors, along
with their assigned scores, are vital in assessing the intricacy of the software project. Here are
the complexity factors and their respective scores used for the OCR-Based Image Text to
Speech Converter System:

1. Requirement for reliable backup and recovery: Score 4

2. Requirement for data communication: Score 5
3. The extent of distributed processing: Score 2
4. Performance requirements: Score 3
5. Expected operational environment: Score 4
6. The extent of online data entries: Score 5
7. The extent of multi-screen or multi-operation online data input: Score 4
8. The extent of online updating of master files: Score 4
9. The extent of complex inputs, outputs, online queries, and files: Score 2
10. The extent of complex data processing: Score 1
11. The extent of conversion and installation included in the design: Score 4
12. The extent of multiple installations in an organization and variety of customer
organizations: Score 5

6
 Software Project Estimation Report

13. The extent of change and focus on ease-of-use: Score 5

Degree of Influence (DI): 48 The Degree of Influence (DI) represents the collective influence of
these complexity factors on the project's overall complexity. It is calculated as the sum of the
scores assigned to each complexity factor.

DI = Σ (Scores of Complexity Factors) = 4 + 5 + 2 + 3 + 4 + 5 + 4 + 4 + 2 + 1 + 4 + 5 = 48

Complexity Adjustment Factor (CAF): The Complexity Adjustment Factor (CAF) is calculated
based on the Degree of Influence (DI) using the following formula:

CAF = 0.65 + 0.01 * DI

In the case of the OCR-Based Image Text to Speech Converter System, the CAF calculation is as
follows:

CAF = 0.65 + 0.01 * 48 = 0.65 + 0.48 = 1.13

Function Point (FP) Calculation: With the CAF determined, we can now refine the Unadjusted
Function Points (UFP) calculated earlier. The Function Point (FP) is calculated by multiplying the
UFP by the CAF:

Function Point = UFP * CAF

For the OCR-Based Image Text to Speech Converter System:

UFP = 154 CAF = 1.13

Function Point = 154 * 1.13 = 174.02

2.0 EFFORT AND TIME ESTIMATION

2.1 COCOMO Model:

The COCOMO model is used to estimate time and effort for any software project. This
software project is based on the organic category of development complexity. This is a reliable
process for an approximate estimation of the project parameters. COCOMO model will
estimate software parameters using the following expressions:

Effort = a1 ✕ (KLOC)^ b1 PM

7
Software Project Estimation Report

Tdev = c1 ✕ (Effort)^ d1 months

where,
➔ KLOC is the estimated size of the software product expressed in Kilo Lines Of
Code.
➔ a1, b1, c1, d1 are constants for each category of the software product. ➔ Tdev is
the estimated time to develop the software, expressed in months.

➔ Effort is the total effort required to develop the software product, expressed in
person-months (PMs).

LOC Estimation:
1. Registration: 250
2. Login: 150
3. Home Page: 500
4. Health Details: 300
5. Profile Pages: 350
6. Discussion Forum: 470
7. Miscellaneous: 430

2.2 Estimation of development effort:

= 2.4 * (KLOC)^1.05
= 2.4 * (2.45)^1.05
= 6.14944 PM

2.3 Estimation of development time:

= 2.5 * (EFFORT)^0.38
= 2.5 * (6.14944)^0.38
= 4.9853 months

3.0 PROJECT SCHEDULE BREAKDOWN

8
 Software Project Estimation Report

3.1 Activity Network

An activity network shows different activities making up a project, their estimated durations, and
their interdependencies. Two equivalent representations for activity networks are possible are in
use:

➔ Activity On Node
➔ Activity On Edge

THE ACTIVITY NETWORK

9
 Software Project Estimation Report

3.0 The PERT Chart

Project Evaluation and review technique (PERT) charts are a more sophisticated form of activity
chart. PERT charts like activity networks consist of a network of boxes and arrows. The boxes
represent activities, and the arrows represent task dependencies. A PERT chart represents the
statistical variations in the project estimates, assuming these to be a normal distribution. PERT
allows for some randomness in task completion times and therefore provides the capability to
determine the probability of achieving project milestones based on the probability of completing
each task along the path to that milestone. Each task is annotated with three estimates:

Optimistic (O): The best possible case task completion time.

Most likely estimate (M): Most likely task completion time.
Worst case (W): The worst possible case task completion time

10