function points
DESCRIPTION
FPsTRANSCRIPT
![Page 1: Function Points](https://reader036.vdocuments.us/reader036/viewer/2022082504/55cf9b6c550346d033a60109/html5/thumbnails/1.jpg)
Project Name Reliable Chat ApplicationILF 21EIF 0EO 0EQ 9EI 6Total Unadjusted Function Points 36Total GSC 0.79Total Adjusted Function Points 28.44
1.5Total Man Days 18.96
Phases Percentage Man DaysRequirement Gathering 20 3.792Technical Design 20 3.792Execution 100 18.96Testing 5 0.948
Total Man Days 27.492Number of Developers 2
Total Project Schedule 13.746
per day
![Page 2: Function Points](https://reader036.vdocuments.us/reader036/viewer/2022082504/55cf9b6c550346d033a60109/html5/thumbnails/2.jpg)
Functionality DET RET ValueRooms 1 1 7User 2 1 7Message 1 1 7
![Page 3: Function Points](https://reader036.vdocuments.us/reader036/viewer/2022082504/55cf9b6c550346d033a60109/html5/thumbnails/3.jpg)
Functionality DET RET Value
![Page 4: Function Points](https://reader036.vdocuments.us/reader036/viewer/2022082504/55cf9b6c550346d033a60109/html5/thumbnails/4.jpg)
Functionality FTR RET Value0
![Page 5: Function Points](https://reader036.vdocuments.us/reader036/viewer/2022082504/55cf9b6c550346d033a60109/html5/thumbnails/5.jpg)
Functionality FTR RET ValueShow rooms 1 1 3Show users 1 1 3Display Message 1 1 3
![Page 6: Function Points](https://reader036.vdocuments.us/reader036/viewer/2022082504/55cf9b6c550346d033a60109/html5/thumbnails/6.jpg)
Functionality FTR RET ValueLogin Screen 1 1 3Send Message 1 1 3
![Page 7: Function Points](https://reader036.vdocuments.us/reader036/viewer/2022082504/55cf9b6c550346d033a60109/html5/thumbnails/7.jpg)
GSC Attribute Definitions Value
1
Distributed data processing 1
1
Heavily used configuration 1
1
On-Line data entry 1
End-user efficiency 1
On-Line update 1
Complex processing 1
Reusability 1
1
Operational ease 1
Multiple sites 1
Facilitate change 1
GSC 0.79
Data communications:
How many communication facilities are there to aid in the transfer or exchange of information with the application or system?
How are distributed data and processing functions handled?
Performance Did the user require response time or throughput?
How heavily used is the current hardware platform where the application will be executed?
Transaction rate How frequently are transactions executed; daily, weekly, monthly, etc.?
What percentage of the information is entered On-Line?
Was the application designed for end-user efficiency?
How many ILF’s are updated by On-Line transaction?
Does the application have extensive logical or mathematical processing?
Was the application developed to meet one or many user’s needs?
Installation easeHow difficult is conversion and installation?
How effective and/or automated are start-up, back up, and recovery procedures?
Was the application specifically designed, developed, and supported to be installed at multiple sites for multiple organizations?
Was the application specifically designed, developed, and supported to facilitate change?