0% found this document useful (0 votes)
1 views3 pages

Software Assignment

Uploaded by

aiimaaima073
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
1 views3 pages

Software Assignment

Uploaded by

aiimaaima073
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SOFTWARE PROJECT MANAGEMENT

Assignment 1

Name: Areeba

Roll no: BIT 23033

Submitted to: Sir Younus


Function-Oriented Metrics: Function Point

Introduction

Software engineering uses measurement techniques to estimate the size, effort, and quality of software systems.
One important approach is Function-Oriented Metrics, which measure software based on the functionality
delivered to the user instead of lines of code. A key technique in this category is Function Point (FP) Analysis,
explained in Roger S. Pressman’s Software Engineering: A Practitioner’s Approach.

Function Point Analysis estimates software size by focusing on user-visible functions. It is independent of
programming language and useful during early project planning.

Function-Oriented Metrics

Function-oriented metrics measure software based on user functionality rather than code size.

Main objectives:

●​ Measure software functionality


●​ Estimate effort and cost
●​ Evaluate productivity
●​ Support project planning

These metrics are useful when requirements are known, but coding has not started.

Function Point Analysis (FPA)

Function Point Analysis measures software size by counting functionality from the user’s perspective.

A Function Point represents a unit of software functionality delivered to the user.

Instead of lines of code, FP counts user functions like inputs, outputs, files, and queries.

Components of Function Points

FP is based on five components:

●​ External Inputs (EI): User data inputs (e.g., login, registration)


●​ External Outputs (EO): System outputs (e.g., reports)
●​ External Inquiries (EQ): Data retrieval requests (e.g., search)
●​ Internal Logical Files (ILF): Internal databases (e.g., student records)
●​ External Interface Files (EIF): External system files used by system
Steps in Function Point Calculation

1.​ Identify EI, EO, EQ, ILF, EIF


2.​ Classify each as low, average, or high complexity
3.​ Assign standard weights to each function
4.​ Compute Unadjusted Function Points (UFP)
5.​ Apply Value Adjustment Factor (VAF) based on system characteristics
6.​ Final FP = UFP × VAF

Advantages

●​ Independent of programming language


●​ Useful in early project estimation
●​ Helps measure productivity
●​ Improves cost and effort estimation
●​ Widely accepted standard method

Limitations

●​ Some subjectivity in complexity evaluation


●​ Requires experience for accurate results
●​ Time-consuming for large systems
●​ Less useful for very small projects

Conclusion

Function Point Analysis is a widely used function-oriented metric in software engineering. As explained in
Pressman’s book, it measures software based on user functionality instead of code size. It helps in estimation,
planning, and productivity analysis. Despite some limitations, it remains an effective and practical method for
software measurement.

You might also like