Scribd
Upload
44 views9 pages

Estimation Report For Music Management System

This document contains a software project estimation report submitted by 4 students. It includes: 1) A function point analysis that estimates the project size at 85.91 function points based on 7 variables. 2) An activity network diagram and PERT chart that breaks the project into 7 tasks with estimated durations and dependencies. 3) References for the function point analysis and modeling tools used.

Uploaded by

Khumanshu Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
44 views9 pages

Estimation Report For Music Management System

This document contains a software project estimation report submitted by 4 students. It includes: 1) A function point analysis that estimates the project size at 85.91 function points based on 7 variables. 2) An activity network diagram and PERT chart that breaks the project into 7 tasks with estimated durations and dependencies. 3) References for the function point analysis and modeling tools used.

Uploaded by

Khumanshu Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

ESTIMATION REPORT

Submitted by:
Gagandeep Singh (2021BCS-026)
Parth Pawar (2021BCS-051)
Vedant Maske (2021BCS-069)
Aditya Meena (2019BCS-003)
CONTENTS
1. Size Estimation (Function Point Metrics)
2. Project schedule breakdown (Activity network and PERT chart)

3. References
1. Size Estimation (Function Point Metrics)
Step 1: Estimating the variables and Calculating UFP for the FP Metric of size
estimation

 Inputs- 4
1. Users’ Details (Simple)
2. Pincode (Simple)
3. Location (Simple)
4. Requested Songs (During bidding) (Simple)

 Output- 3
1. Playlist Details (Simple)
2. Profile Details (Average)
3. Songs Bidding Details (Average)

 Inquiries- 2
1. Next song on the playlist (simple)
2. Song on the bidding list. (Simple)

 Files- 3
1. User Details (Simple)
2. Profile Information (Average)
3. Songs playlist (Simple)

 Interface- 1
1. Music Player API for getting songs to be played (Average)

UFP = 3*4 + 1*4 + 2*5+ 2*3+ 2*4 + 2*7+ 1*10 + 1*7 = 71

Step 2: Calculating the Refined UFP based on the complexities of all the variables

Simple Average Complex

Input 4 0 0

Output 1 2 0
Inquiries 2 0 0

Files 2 1 0

Interface 0 1 0

Refined UFP =3*4 + 1*4 + 2*5+ 2*3+ 2*4 + 2*7+ 1*10 + 1*7

= 68

Refined UFP = 71

Step 3: Calculating the DI, TCF , FP

Average DI =14*4 = 56

TCF =(0.65 + 0.01 * DI)

TCF =1.21

FP =UFP * TCF

FP =85.91

Effort and Development Time Estimation (COCOMO Model):

LOC Estimation:

1. Registration:
2. Login:
3. Playlist:
4. Profile Details-
5. Home screen page:
6. Spotify connection and authentication
7. Requested song
8. Songs on demand
9. Miscellaneous

LOC is approximately 11 KLOC.

Therefore, it is an organic software

Effort = 2.4*(KLOC^1.05) PM

= 2.4 *(10.86^1.05) PM

Effort = 29.7628 PM

Development Time = 2.5*(Effort)^0.38 Months

= 2.5 *(29.7628)^0.38 Months

Development Time = 9.077 Months

Average Staff Size =Effort/ Development Time

Average Staff Size =3.27

Productivity =KLOC/ Effort

Productivity =0.37
2. Project schedule breakdown (Activity network
and PERT chart)

The Activity Network Representation

Task Task Duration Dependent on


Number (Days) Task

T1 Specification 10

T2 Design Database 25 T1

T3 Design Interface 30 T1

T4 Code Database 40 T2

T5 Code Interface 45 T3

T6 Integrate and Testing 65 T4, T5

T7 Write User Manual/ 45 T1


Documentation
The Activity Network

Projected Parameters Computed from Activity Network

Task Early Start Early Finish Latest Start Latest Finish Slack Time

Specification 0 10 0 10 0

Design Database 10 35 20 45 10

Design Interface 10 40 10 40 0

Code Database 35 75 45 85 10

Code Interface 40 85 40 85 0

Integrate and Testing 85 150 85 150 0

Write User Manual/ 10 55 40 85 30


Documentation
The PERT Chart

The critical path is shown with blue color


3. References

 https://nibmehub.com/opac-
service/pdf/read/Modeling%20with%20UML_%20Language-%20Concepts-
%20Methods.pdf
 https://www.visual-paradigm.com/

You might also like