Function Point Calculator

Specify Project Details (optional)

Project Name:
Client Name:
Project Type:	Development Enhancement Maintenance
Module Name:
Assumption (if any):
Estimated By:

Specify Measurement Parameters

Quick ModeDetailed Mode

Measurement Parameters
Complexity	External Inputs (EI)	External Outputs (EO)	External Queries (EQ)	Internal Logical Files (ILF)	External Interface Files (EIF)
Simple
Average
Complex

Specify General System Characteristics (Complexity Parameters)

Data Communications:	Application is pure batch processing or a standalone system. Application is batch processing but has remote data entry or remote printing. Application is batch processing but has remote data entry and remote printing. Application includes online data collection or tele-processing front-end to batch process or query system. Application is more than a front-end, but supports only one type of tele-processing communications protocol. Application is more than a front-end and supports more than one type of tele-processing communications protocol.
Distributed Data Processing:	Application does not aid the transfer of data or processing function between components of the system. Application prepares data for end-user processing on another component of the system, such as spreadsheets and DBMS. Data is prepared for transfer, then is transferred and processed on another component of the system (not for end-user processing). Distributed processing and data transfer are online and in one direction only. Distributed processing and data transfer are online and in both directions. Processing functions are dynamically performed on the most appropriate component of the system.
Performance Requirements:	No special performance requirements were stated by the user. Performance and design requirements were stated and reviewed but no special actions were required. Response time or throughput is critical during peak hours. No special design for CPU utilization was required. Processing deadline is for the next business day. Response time or throughput is critical during all business hours. No special design for CPU utilization was required. Processing deadline requirements with interfacing systems are constraining. In addition, stated user performance requirements are stringent enough to require performance analysis tasks in the design phase. In addition, performance analysis tools were used in the design, development, and/or implementation phases to meet the stated user performance requirements.
Heavily Used Configuration:	No explicit or implicit operational restrictions are included. Operational restrictions do exist, but are less restrictive than a typical application. No special effort is needed to meet the restrictions. Some security or timing considerations are included. Specific processor requirements for a specific piece of the application are included. Stated operation restrictions require special constraints on the application in the central processor or a dedicated processor. In addition, there are special constraints on the application in the distributed components of the system.
Transaction Rates:	No peak transaction period is anticipated Peak transaction period (e.g., monthly, quarterly, seasonally, annually) is anticipated. Weekly peak transaction period is anticipated. Daily peak transaction period is anticipated. High transaction rate(s) stated by the user in the application requirements or service level agreements are high enough to require performance analysis tasks in the design phase. High transaction rate(s) stated by the user in the application requirements or service level agreements are high enough to require performance analysis tasks and, in addition, require the use of performance analysis tools in the design, development, and/or installation phases.
On-line Data Entry:	All transactions are processed in batch mode. 1% to 7% of transactions are interactive data entry. 8% to 15% of transactions are interactive data entry. 16% to 23% of transactions are interactive data entry. 24% to 30% of transactions are interactive data entry. More than 30% of transactions are interactive data entry.
End User Efficiency:	Application require Navigational aids (for example, function keys, anchor jumps, static or dynamically generated menus). Application require Chartings. Application require Dynamically generated pages. Application require Multiple Document Interface (MDI) page. Application require Online help and documents. Application require Automated cursor movement. Application require Scrolling. Application require Remote printing via online transaction. Application require Pre-assigned function keys. Application require Batch jobs to be submitted from online transactions. Application require Cursor selection of screen data. Application require Heavy use of reverse video, highlighting, colors understanding, and other indicators. Application require Hard copy of user documentation. Application require Mouse interfaces. Application require Dynamic pop-up windows. Application require As few screens as possible to accomplish a business function. Application require Bilingual support (support languages; count as four times). Application require Multilingual support (supports more than two languages; count as six items). Application has stated requirements for end-user efficiency and they are strong enough to require design tasks for human factors to be included (for example, minimize key strokes, maximize defaults, use of templates). Application has stated requirements for end-user efficiency and they are strong enough to require use of special tools and processes to demonstrate that the objectives have been achieved.
On-line Update:	None. Online update of one to three control files is included. Volume of updating is low and recovery is easy. Online update of four or more control files is included. Volume of updating is low and recovery easy. Online update of major internal logical files is included. In addition, protection against data lost is essential and has been specially designed and programmed in the system. In addition, high volumes bring cost considerations into the recovery process. Highly automated recovery procedures with minimum operator intervention are included.
Complex Processing:	Application has Specific control (for example, special audit processing) and/or specific security processing. Application has Extensive logical processing. Application has Extensive mathematical processing. Application has Much exception processing resulting in incomplete transactions that must be processed again, for example, an incomplete ATM transactions caused by tele-processing interruption, missing data values, or failed edits. Application has Complex processing to handle multiple input/output possibilities (for example, multimedia or device independence).
Application Reusability:	No reusability required. Reusable code is required within the application. Less than 10% of the application is considered for more than one user’s needs. Ten percent (10%) or more of the application is considered for more than one user’s needs. The application was specifically packaged and/or documented to ease re-use, and the application is customized by the user at source code level. The application was specifically packaged and/or documented to ease re-use, and the application is customized for use by means of user parameter maintenance.
Installation Ease:	No special considerations were stated by the user, and no special set-up is required for installation. No special considerations were stated by the user but special set-up is required for installation. Conversation and installation requirements were stated by the end user and conversion and installation guide were provided and tested. Conversation and installation requirements were stated by the end user and conversion and installation guide were provided and tested. The impact of conversion on project is considered to be important. In addition to 2 from above, automated conversion and installation tool were provided and tested. In addition to 3 from above, automated conversion and installation tool were provided and tested.
Operational Ease:	No special operational considerations other than the normal back-up procedures were stated by the user. Effective start-up, back-up, and recovery processes were provided, but operator intervention is required. Effective startup, back-up and recovery processes were provided, but no operator intervention is required. The application minimizes. The need for tape mounts. The application minimizes. The need for paper handling. The application is designed for unattended operation. Unattended operation means no operator intervention is required to operate the system other than to start up or shut down the application. Automatic error recovery is a feature of the application.
Multiple Site Installations:	User requirements do not require considering the needs of more than one user/installation site. Needs of multiple sites were considered in the design, and the application is designed to operate only under identical hardware and software environments. Needs of multiple sites were considered in the design, and the application is designed to operate only under similar hardware and/or software environments. Needs of multiple sites were considered in the design, and the application is designed to operate only under different hardware and/or software environments. Documentation and support plan are provided and tested to support the application at multiple sites and the application is as described by 1 or 2 from above. Documentation and support plan are provided and tested to support the application at multiple sites and the application is as described by 3 from above.
Facilitate Change:	Flexible query and report facility is required that can handle simple requests; for example, and/or logic applied to only one internal logical file. Flexible query and report facility is required that can handle requests of average complexity; for example, and/or logic applied to only one internal logical file. Flexible query and report facility is required that can handle requests of complex complexity; for example, and/or logic applied to only one internal logical file. Business control data is kept in table that are maintained by the user with online interactive processes, but changes take effect only on the next business day. Business control data is kept in table that are maintained by the user with online interactive processes, but changes take effect immediately.

• 
• We DONOT store this information with us. This information is used only for the purpose of calculation and reporting; and it will be discarded the moment you exit from this page.
• It is advisible to have some knowlegde about function point components before using this tool. This will help you accurately calculate function point and effort estimation. Please refer to: An Introduction to Function Point Analysis.