Function Point Analysis in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Function Point Analysis (FPA)?

Function Point Analysis is a method to measure the size of software by quantifying its functionality from the user's perspective. It helps estimate effort and cost.

beginner

Name the five main components counted in Function Point Analysis.

The five components are: External Inputs, External Outputs, External Inquiries, Internal Logical Files, and External Interface Files.

beginner

Why is Function Point Analysis useful in software projects?

It provides a standardized way to estimate software size, which helps in planning, budgeting, and tracking progress regardless of technology used.

intermediate

How does Function Point Analysis differ from counting lines of code?

FPA measures functionality from the user's view, not the amount of code. This makes it independent of programming language and coding style.

intermediate

What is the role of complexity adjustment in Function Point Analysis?

After counting components, a complexity factor adjusts the total to reflect technical and environmental factors affecting the project effort.

Which of the following is NOT a component counted in Function Point Analysis?

A External Interface Files

B Internal Logical Files

C External Inputs

D Lines of Code

Function Point Analysis counts functional components like inputs and files, not lines of code.

Function Point Analysis primarily measures software size based on:

A Number of developers

B User functionality

C Programming language used

D Number of code comments

FPA measures the software size by the functionality delivered to the user.

What does the complexity adjustment in FPA account for?

A The number of developers

B The programming language

C Technical and environmental factors

D The number of bugs

Complexity adjustment reflects factors like performance, security, and environment that affect effort.

Which component in FPA represents data maintained within the system?

A Internal Logical Files

B External Inputs

C External Outputs

D External Interface Files

Internal Logical Files are data groups maintained inside the system.

Function Point Analysis is independent of:

A Programming language

B Project complexity

C Software functionality

D User requirements

FPA measures functionality, not the language or technology used.

Explain the main purpose and benefits of Function Point Analysis in software development.

Think about how FPA helps project managers understand software work.

List and describe the five components counted in Function Point Analysis.

Focus on the types of data and interactions counted.

Practice

1. What is the main purpose of Function Point Analysis in software engineering?

easy

A. To design the user interface

B. To write the actual code for software

C. To measure the size of software based on its features

D. To test software for bugs

Solution

1. Step 1: Understand the goal of Function Point Analysis

   Function Point Analysis is used to measure software size by counting its features, not for coding or testing.

2. Step 2: Match the purpose with the options

   Among the options, only measuring software size by features matches the purpose.

3. Final Answer:

   To measure the size of software based on its features -> Option C

4. Quick Check:

   Function Point Analysis = software size measurement [OK]

Hint: Focus on measuring software features, not coding or testing [OK]

Common Mistakes:

• Confusing Function Point Analysis with coding or testing
• Thinking it designs UI
• Assuming it measures time instead of size

2. Which of the following is a correct step in the Function Point Analysis process?

easy

A. Counting the number of functions in the software

B. Writing test cases for each function

C. Compiling the source code

D. Deploying the software to users

Solution

1. Step 1: Identify the steps in Function Point Analysis

   The process involves counting functions, weighting them, and adjusting for complexity.

2. Step 2: Compare options with the process steps

   Only counting the number of functions matches the process; other options relate to later stages.

3. Final Answer:

   Counting the number of functions in the software -> Option A

4. Quick Check:

   Function Point Analysis step = counting functions [OK]

Hint: Remember: counting functions is the first step [OK]

Common Mistakes:

• Mixing analysis steps with coding or deployment
• Thinking testing is part of Function Point Analysis
• Confusing compilation with analysis

3. If a software project has 10 input functions, 5 output functions, and 3 inquiry functions, and each input counts as 4 points, output as 5 points, and inquiry as 3 points, what is the total unadjusted function point count?

medium

A. 85

B. 80

C. 90

D. 74

Solution

1. Step 1: Calculate points for each function type

   Input: 10 x 4 = 40 points; Output: 5 x 5 = 25 points; Inquiry: 3 x 3 = 9 points.

2. Step 2: Sum all points to get total function points

   Total = 40 + 25 + 9 = 74 points.

3. Step 3: Verify if any other function types are included

   No other types given, so total unadjusted function points = 74.

4. Final Answer:

   74 -> Option D

5. Quick Check:

   Sum of weighted functions = 74 [OK]

Hint: Multiply counts by weights, then add all [OK]

Common Mistakes:

• Adding counts without weights
• Multiplying weights incorrectly
• Forgetting to sum all function types

4. A software project's function point count was calculated as 120, but the complexity adjustment factor was mistakenly applied as 0.8 instead of 1.2. What is the corrected adjusted function point count?

medium

A. 96

B. 144

C. 120

D. 100

Solution

1. Step 1: Understand the adjustment factor application

   Adjusted function points = Unadjusted count x Complexity factor.

2. Step 2: Calculate corrected adjusted function points

   Corrected = 120 x 1.2 = 144.

3. Final Answer:

   144 -> Option B

4. Quick Check:

   120 x 1.2 = 144 [OK]

Hint: Multiply by correct factor, not the wrong one [OK]

Common Mistakes:

• Using the wrong adjustment factor
• Confusing multiplication with division
• Ignoring adjustment factor altogether

5. A project has the following function counts: 8 inputs, 6 outputs, 4 inquiries, 5 internal logical files, and 3 external interface files. The weights are: inputs=4, outputs=5, inquiries=3, internal files=7, external files=5. The complexity adjustment factor is 1.1. What is the final adjusted function point count?

hard

A. 136.4

B. 176

C. 165

D. 190

Solution

1. Step 1: Calculate unadjusted function points

   Inputs: 8x4=32; Outputs: 6x5=30; Inquiries: 4x3=12; Internal files: 5x7=35; External files: 3x5=15. Sum = 32+30+12+35+15=124.

2. Step 2: Apply complexity adjustment factor

   Adjusted = 124 x 1.1 = 136.4.

3. Final Answer:

   136.4 -> Option A

4. Quick Check:

   124 x 1.1 = 136.4 [OK]

Hint: Multiply counts by weights, sum, then multiply by factor [OK]

Common Mistakes:

• Forgetting to multiply by adjustment factor
• Adding weights instead of multiplying
• Misreading counts or weights