Function Point Analysis in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Function Point Components

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

A Lines of Code

B External Inputs

C External Outputs

D Internal Logical Files

💡 Hint

Think about what Function Point Analysis measures versus traditional code metrics.

Function Point Analysis counts functional components like inputs, outputs, inquiries, internal files, and external interfaces. Lines of Code is a separate metric unrelated to function points.

📋 Factual

intermediate

Purpose of Function Point Analysis

What is the main purpose of using Function Point Analysis in software projects?

A To estimate the number of bugs in the software

B To count the number of developers needed

C To measure the functional size of software based on user requirements

D To calculate the execution speed of the software

💡 Hint

Consider what aspect of software Function Point Analysis quantifies.

Function Point Analysis measures the functional size of software by quantifying the functions the software provides to the user, helping in estimation and planning.

🔍 Analysis

advanced

Calculating Unadjusted Function Points

Given the following counts: 10 External Inputs, 5 External Outputs, 7 External Inquiries, 8 Internal Logical Files, and 3 External Interface Files, what is the total unadjusted function point count?

A 33

B 35

C 30

D 28

💡 Hint

Add all the counts directly as unadjusted function points.

Unadjusted Function Points are the sum of the function point values for all component types: 10 + 5 + 7 + 8 + 3 = 33.

❓ Reasoning

advanced

Effect of Complexity Adjustment on Function Points

If the Value Adjustment Factor (VAF) is 1.2 and the unadjusted function points are 40, what is the adjusted function point count?

A 33.3

B 48

C 40

D 52

💡 Hint

Multiply unadjusted function points by the VAF.

Adjusted Function Points = Unadjusted Function Points × VAF = 40 × 1.2 = 48.

❓ Comparison

expert

Comparing Function Point Analysis and Lines of Code

Which statement best explains a key difference between Function Point Analysis and Lines of Code (LOC) metrics?

A LOC is used only for estimating software cost, while Function Point Analysis is used only for debugging.

B LOC measures user requirements, while Function Point Analysis measures code complexity.

C Function Point Analysis counts the number of developers, while LOC counts the number of functions.

D Function Point Analysis measures software functionality independent of programming language, while LOC depends on the language used.

💡 Hint

Think about what each metric measures and how language affects them.

Function Point Analysis measures the size of software based on functionality and is independent of programming language. LOC counts actual lines of code, which vary by language and coding style.