Cost9b 1 Living with Function Points Bernstein and Lubashevsky Text pp234-238.

Slides:



Advertisements
Similar presentations
FPA – IFPUG CPM 4.1 Rules.
Advertisements

CPU GROUP Chapter 7. Manage ment Management Report Inquiry Responses Management Inquiries.
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.
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)
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,
Systems Analysis and Design in a Changing World, 6th Edition
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
Project Metrics Infsy 570 Dr. R. Ocker.
1 Cost Estimation CIS 375 Bruce R. Maxim UM-Dearborn.
TRANSACTION PROCESSING SYSTEM Liew Woei Song Muhammad Hofiz Achoson.
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.
Systems Analysis and Design in a Changing World, Fifth Edition
Systems Analysis and Design in a Changing World, Fifth Edition
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
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.
MODULE PLANNING &ESTIMATION.
Chapter 6 : Software Metrics
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.
Version control – Project repository, version management capability, make facility, issue/bug tracking Change control Configuration audit – compliments.
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
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 3 1 Software Size Estimation I Material adapted from: Disciplined.
Project Planning and Estimation
INFO1408 Database Design Concepts Week 15: Introduction to Database Management Systems.
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.
Software Size Estimation Copyright, 2006 © L. Ouyang Liubo Ouyang Personal Software Process Lecture 5.
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
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.
Functional Size Measurement Methodologies. What is FSM ? Definitions: Functional Size: A size of the software derived by quantifying the Functional User.
Department of Computing and Information Sciences MSE Project Presentation 1 A Three-tier On-line Model For Transaction- based Applications Using VB.NET.
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.
FUNCTION POINT ANALYSIS & ESTIMATION
Intro to Estimating Part Art, Part Science. Importance of Good Estimates Time (Realistic Deadlines) most software projects are late because the time was.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 1 Database Systems.
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.
Alternative Software Size Measures for Cost Estimation
RET Rules One of the following rules applies when counting RETs:
Sizing With Function Points
Function Point Analysis
Software Planning
Lecture 17 Software Metrics
Software Development & Project Management
Mk II Function Point Analysis
Alternative Software Size Measures for Cost Estimation
Personal Software Process Software 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:

Cost9b 1 Living with Function Points Bernstein and Lubashevsky Text pp

Cost9b 2 Function Point Analysis How to count function points

Cost9b 3 Function Points u Attempting to measure “functionality” u widely used in business applications

Cost9b 4 Program Features u outputs u inquiries u inputs u files u external interfaces

Cost9b 5 Pressman, Soft Eng, 5th Ed u Outputs –“Each user output that provides application- oriented information to the user is counted. In this context output refers to reports, screens, error messages, and so on. Individual data items within a report are not counted separately”

Cost9b 6 Pressman, Soft Eng, 5th Ed u Inputs –“Each user input that provides distinct application-oriented data to the software is counted. Inputs should be distinguished from inquiries, which are counted separately” u Inquiries –“An inquiry is defined as an on-line input that results in the generation of some immediate software response in the form of an on-line output. Each distinct inquiry is counted.”

Cost9b 7 Pressman, Soft Eng, 5th Ed u Files –“Each logical master file (I.e. a logical grouping of data that may be one part of a large database or a separate file), is counted” u External interfaces –“All machine readable interfaces (e.g. data files on tape or disk) that are used to transmit information to another system are counted.”

Cost9b 8 Dreger, FPA, 1989 u “A function point is defined as one end-user business function” u “business functions made available to the user are identified” u “outputs are items of business information processed by the computer for the end user”

Cost9b 9 Dreger, FPA, 1989 u Inquiries “are direct inquiries into a data base or master file that look for specific data, use simple keys, require immediate response and perform no update functions” u “Inputs are items of business data sent by the user to the computer for processing and to add, change, or delete something.” u “Files are data stored for an application, as logically viewed by the user”

Cost9b 10 Dreger, FPA, 1989 u Outputs –“count each of the outputs leaving the context diagram ‘area under study’ at the lowest (greatest detail) level of the logical … data flow diagram system” –count separately if different format or different processing u Dreger says detail lines and total lines are different, ifpug says no

Cost9b 11 Dreger, FPA, 1989 u Inputs –“count each unique user data or control input that enters the application boundary and also updates (adds to, changes, or deletes from) a logical internal file, data set, table or independent data item.” –“count as one input each uniquely formatted or processed portion...”

Cost9b 12 Dreger, FPA, 1989 u Files –“count each major logical group of user data or control information” u Interfaces –“count as one interface each major logical.. file or other logical group of user-approved data or control information within the application boundary that is set to, shared with, or received from another application.”

Cost9b 13 Weights for features u simple average complex u outputs u inquiries u inputs u files u interfaces

Cost9b 14 Questions u Does the system require reliable backup and recovery? u Are data communications required? u Are there distributed processing functions? u Is performance critical? u Will the system run in an existing, heavily utilized operational environment?

Cost9b 15 Questions u Does the system require on-line data entry? u Does the on-line data entry require the input transaction to be built over multiple screens or operations? u Are the master files updated on-line? u Are the inputs, outputs, files, or inquiries complex? u Is the internal processing complex?

Cost9b 16 Questions u Is the code designed to be reusable? u Are conversion and installation included in the design? u Is the system designed for multiple installations in different organizations? u Is the application designed to facilitate change and ease of use by the user?

Cost9b 17 Adjusted Function Points u FP = FP unadjusted * ( * (sum of ratings ) )

Cost9b 18 AT&T and FPA u “5. The measurements must be repeatable and independent of the observer” u “The prediction accuracy proved to be better than twice of traditional SLOC”