FUNCTION POINT ANALYSIS & ESTIMATION

Slides:



Advertisements
Similar presentations
FPA – IFPUG CPM 4.1 Rules.
Advertisements

Early Effort Estimation of Business Data-processing Enhancements CS 689 November 30, 2000 By Kurt Detamore.
Project Estimation: Metrics and Measurement
Metrics. A Good Manager Measures measurement What do we use as a basis? size? size? function? function? project metrics process metrics process product.
Metrics for Process and Projects
Planning a software project: Function point analysis. José Onofre Montesa Andrés Universidad Politécnica de Valencia Escuela Superior de Informática Aplicada.
Function Point Analysis example. Function point FP is defined as one end-user business function FPA evaluates the system from a user perspective.
R&D SDM 1 Metrics How to measure and assess software engineering? 2009 Theo Schouten.
Software project management (intro)
1 PROJECT SIZING AND ESTIMATING - EFFECTIVELY USING FUNCTIONAL MEASUREMENT Southern California Software Process Improvement.
Predictive Modeling And Reporting Environment (PMRE) CS 552 Senior Design Architecture Review Presenting: Steve Su Ilya Chalyt Yuriy Stelmakh (Architect)
Project Management Metrics.
CS 551 Estimation Fall December QSE Lambda Protocol Prospectus Measurable Operational Value Prototyping or Modeling sQFD Schedule, Staffing,
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
Information Technology Project Management
1 Cost Estimation CIS 375 Bruce R. Maxim UM-Dearborn.
Software Metric capture notions of size and complexity.
Copyright © The David Consulting Group, Inc. 1 UNDERSTANDING and EFFECTIVELY USING FUNCTIONAL MEASUREMENT Presented By The David Consulting Group.
Project Cost Estimation
Cmpe 589 Spring Software Quality Metrics Product  product attributes –Size, complexity, design features, performance, quality level Process  Used.
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Lecture 22 Instructor Paulo Alencar.
COCOMO Models Ognian Kabranov SEG3300 A&B W2004 R.L. Probert.
Chapter 6 : Software Metrics
Chapter 6 The Work Breakdown Structure and Project Estimation Copyright 2012 John Wiley & Sons, Inc. 6-1.
Function Point Analysis What is Function Point Analysis (FPA)? It is designed to estimate and measure the time, and thereby the cost, of developing new.
Personal Estimation with PROBE CS3300 Fall Code Size Estimation Wide Band Delphi (Boehm) Give the team the specs to study Discuss the project goals.
Quality Assurance vs. Quality Control Quality Assurance An overall management plan to guarantee the integrity of data (The “system”) Quality Control A.
Software cost estimation Predicting the resources required for a software development process 1.
Software Metrics Software Engineering.
Software Engineering SM ? 1. Outline of this presentation What is SM The Need for SM Type of SM Size Oriented Metric Function Oriented Metric 218/10/2015.
1 Estimation Function Point Analysis December 5, 2006.
Lecture 4 Software Metrics
Cost Estimation. Problem Our ability to realistically plan and schedule projects depends on our ability to estimate project costs and development efforts.
Project Planning and Estimation
Function Point Analysis. Function Points Analysis (FPA) What is Function Point Analysis (FPA)? Function points are a standard unit of measure that represent.
SEG3300 A&B W2004R.L. Probert1 COCOMO Models Ognian Kabranov.
Introduction to Software Project Estimation I (Condensed) Barry Schrag Software Engineering Consultant MCSD, MCAD, MCDBA Bellevue.
Project Management in the Software Development Environment CIS490.
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 26Slide 1 Software cost estimation l Predicting the resources required for a software development.
Software Size Estimation Copyright, 2006 © L. Ouyang Liubo Ouyang Personal Software Process Lecture 5.
©1999 Addison Wesley LongmanSlide 3.1 Managing IS Projects Planning –Decomposing Project into Activities –Estimating resources –Developing a schedule –Setting.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Effort Estimation In WBS,one can estimate effort (micro-level) but needed to know: –Size of the deliverable –Productivity of resource in producing that.
Team Members and Roles AYE THET MON NG SIEW LENG PRAGATI TIN LAI WAI
Functional Size Measurement Methodologies. What is FSM ? Definitions: Functional Size: A size of the software derived by quantifying the Functional User.
Software Quality Metrics III. Software Quality Metrics  The subset of metrics that focus on quality  Software quality metrics can be divided into: End-product.
Department of Computing and Information Sciences MSE Project Presentation 1 A Three-tier On-line Model For Transaction- based Applications Using VB.NET.
CSE SW Project Management / Module 13 - Function Points and Related Methods Copyright © , Dennis J. Frailey, All Rights Reserved CSE7315M13.
540f07cost12oct41 Reviews Postmortem u Surprises? u Use white background on slides u Do not zip files on CD u Team leader should introduce team members.
Personal Estimation with PROBE CS3300 Fall Process Everybody has one !!! Formal – Completely defined and documented Informal – Just the way things.
Intro to Estimating Part Art, Part Science. Importance of Good Estimates Time (Realistic Deadlines) most software projects are late because the time was.
Cost9b 1 Living with Function Points Bernstein and Lubashevsky Text pp
Estimation Questions How do you estimate? What are you going to estimate? Where do you start?
Cost23 1 Question of the Day u Which of the following things measure the “size” of the project in terms of the functionality that has to be provided in.
Copyright , Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M13 - Version 8.01 SMU CSE 7315 Planning and Managing a Software Project.
THE FAMU-CIS ALUMNI SYSTEM
Alternative Software Size Measures for Cost Estimation
The Work Breakdown Structure and Project Estimation
Project management assignment, Spring 2017
RET Rules One of the following rules applies when counting RETs:
Sizing With Function Points
Function Point Analysis
Software Size Measures for Cost Estimation
Function Point.
Software Metrics “How do we measure the software?”
Activities During SPP Size Estimation
More on Estimation In general, effort estimation is based on several parameters and the model ( E= a + b*S**c ): Personnel Environment Quality Size or.
COCOMO Models.
Software Effort Estimation
COCOMO MODEL.
Presentation transcript:

FUNCTION POINT ANALYSIS & ESTIMATION Gurpreet Singh M.Tech CSE Part Time – 3rd Semester Roll No. 17 & Regd. No. 40800066

Copyright © 2005. The David Consulting Group, Inc.

What is Function Point Analysis (FPA)? It is designed to estimate and measure the time, and thereby the cost, of developing new software applications and maintaining existing software applications. It is also useful in comparing and highlighting opportunities for productivity improvements in software development. It was developed by A.J. Albrecht of the IBM Corporation in the early 1980s. The main other approach used for measuring the size, and therefore the time required, of software project is lines of code (LOC) – which has a number of inherent problems. Copyright © 2005. The David Consulting Group, Inc.

The Function Point Methodology Five key components are identified based on logical user view Inputs Outputs Inquiries Internal Logical Files External Interface Files Input Inquiry Output Internal Logical Files Application External Interface File Copyright © 2005. The David Consulting Group, Inc.

Copyright © 2005. The David Consulting Group, Inc.

The Function Point Methodology 14 Optional General Systems Characteristics are evaluated and used to compute a Value Adjustment Factor (VAF) General System Characteristics Data Communication On-Line Update Distributed Data Processing Complex Processing Performance Objectives Reusability Heavily Used Configuration Conversion & Install Ease Transaction Rate Operational Ease On-Line Data Entry Multiple-Site Use End-User Efficiency Facilitate Change The final calculation is based upon the Unadjusted FP count X VAF Copyright © 2005. The David Consulting Group, Inc.

Copyright © 2005. The David Consulting Group, Inc.

What is Function Point Analysis (FPA)? These function-point counts are then weighed (multiplied) by their degree of complexity: Simple Average Complex Inputs 2 4 6 Outputs 3 5 7 Files 5 10 15 Inquires 2 4 6 Interfaces 4 7 10 Copyright © 2005. The David Consulting Group, Inc.

What is Function Point Analysis (FPA)? A simple example: inputs 3 simple X 2 = 6 4 average X 4 = 16 1 complex X 6 = 6 outputs 6 average X 5 = 30 2 complex X 7 = 14 files 5 complex X 15 = 75 inquiries 8 average X 4 = 32 interfaces 3 average X 7 = 21 4 complex X 10 = 40 Unadjusted function points 240 Copyright © 2005. The David Consulting Group, Inc.

What is Function Point Analysis (FPA)? Continuing our example . . . Complex internal processing = 3 Code to be reusable = 2 High performance = 4 Multiple sites = 3 Distributed processing = 5 Project adjustment factor = 17 Adjustment calculation: Adjusted FP = Unadjusted FP X [0.65 + (adjustment factor X 0.01)] = 240 X [0.65 + ( 17 X 0.01)] = 240 X [0.82] = 197 Adjusted function points Copyright © 2005. The David Consulting Group, Inc.

Copyright © 2005. The David Consulting Group, Inc.

Copyright © 2005. The David Consulting Group, Inc.

Copyright © 2005. The David Consulting Group, Inc.

FUNCTION POINT ANALYSIS Project Estimation DEFINITION CAPABILITY ESTIMATE PROJECT SIZE PROJECT COMPLEXITY RISK FACTORS REQUIREMENT discuss estimating, the issue of sizing vs. estimating the issue is that I did more work, not that I delivered more functionality your estimating model has to account for the more work that comes with increased complexity X X Schedule Costs Effort FUNCTION POINT ANALYSIS Copyright © 2005. The David Consulting Group, Inc.

Copyright © 2005. The David Consulting Group, Inc.

Copyright © 2005. The David Consulting Group, Inc.

Copyright © 2005. The David Consulting Group, Inc.

Copyright © 2005. The David Consulting Group, Inc.

Conclusions Project Management can be successful Requirements can be managed Projects can be sized Performance can be successfully estimated Process improvement can be modeled Measurement can be accomplished Copyright © 2005. The David Consulting Group, Inc.

Thanks Copyright © 2005. The David Consulting Group, Inc.