Project Name ILF EIF EO EQ EI Total Unadjusted Function Points Total GSC Total Adjusted Function Points Programmer

can complete how much FP per day Total Man Days

Backup Project Fast Track 7 0 0 3 14 24 1.23 29.52 0.85 34.72941176

Functionality DET RET Value Backup Policy 7 2 7 0 0 0 .

Folders to be backed up. Log file path .DET's considers RET's considerd Start time. Start timer Backup policy . Backup folder name . Folders to be backed up. Start Backup . Add back folders .

Functionality DET RET Value 0 .

Functionality DET FTR Value 0 .

Functionality Display folders to be backed up DET 2 FTR 1 Value DET's FTR's 3 Folder name Folders .

Functionality DET FTR Value Add Backup Policy 7 2 4 Update Backup Policy 7 2 4 Check timer and start back up 8 4 6 0 0 0 0 0 0 0 0 0 0 0 .

Start Backup . Log file path . backup policy . Log file path . Folders to be backed up Backup . Folders to be backed up. Log file path .DET's Start time. Start Backup . Add back folders .Start time. Backup folder name . Folders to be backed up. Folders to be backed up Time of the timer . Start timer Start time. Backup folder name . Add back folders . Add back folders . Start timer FTR's Backup . Start timer Current time . Folders to be backed up. Backup folder name . Start Backup . backup folders and log file .

and supported to be installed at multiple sites for multiple organizations? Was the application specifically designed. and supported to facilitate change? Value Data communications: Distributed data processing Performance Heavily used configuration Transaction rate On-Line data entry End-user efficiency On-Line update Complex processing Reusability Installation ease Operational ease 1 5 5 1 5 5 1 5 5 5 5 5 Multiple sites Facilitate change GSC 5 5 1. developed. etc. and recovery procedures? Was the application specifically designed. developed.GSC Attribute Definitions 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? Did the user require response time or throughput? How heavily used is the current hardware platform where the application will be executed? How frequently are transactions executed. monthly.? 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? How difficult is conversion and installation? How effective and/or automated are startup. daily.23 . weekly. back up.

Sign up to vote on this title
UsefulNot useful