...Proceedings: Pacific Northwest Software Quality Conference, 2006 The Challenge of Productivity Measurement David N. Card Q-Labs, Inc dca@q-labs.com Biography- David N. Card is a fellow of Q-Labs, a subsidiary of Det Norske Veritas. Previous employers include the Software Productivity Consortium, Computer Sciences Corporation, Lockheed Martin, and Litton Bionetics. He spent one year as a Resident Affiliate at the Software Engineering Institute and seven years as a member of the NASA Software Engineering Laboratory research team. Mr. Card is the author of Measuring Software Design Quality (Prentice Hall, 1990), co-author of Practical Software Measurement (Addison Wesley, 2002), and co-editor ISO/IEC Standard 15939: Software Measurement Process (International Organization for Standardization, 2002). Mr. Card also serves as Editor-in-Chief of the Journal of Systems and Software. He is a Senior Member of the American Society for Quality. Abstract - In an era of tight budgets and increased outsourcing, getting a good measure of an organization’s productivity is a persistent management concern. Unfortunately, experience shows that no single productivity measure applies in all situations for all purposes. Instead, organizations must craft productivity measures appropriate to their processes and information needs. This article discusses the key considerations for defining an effective productivity measure. It also explores the relationship between quality and productivity...
Words: 4342 - Pages: 18
...and cost ❚ function of the size of the software product in source instructions ❚ function of the most significant software cost drivers Importance of Software Cost Estimation - problems ❚ Software project personnel have no firm basis for telling a manager, customer, or salesperson that their proposed budget and schedule are unrealistic. ❚ Software analysts have no firm basis for making realistic hardware-software tradeoff analysis during the system design phase. ❚ Project managers have no firm basis for determining how much time and effort each software phase and activity should take. USC-CSE Affiliates ❚ Commercial Industry (9) AT&T, Bellcore, EDS, HP, IDE, Motorola, Rational, TI, Xerox ❚ Aerospace Industry (9) E-Systems, Hughes, Litton, Lockheed, Loral, Northrop Grumman, Rockwell, SAIC, TRW ❚ Government (3) DISA, USAF Rome Lab, US Army Research Labs ❚ FFRDC’s and Consortia (5) Aerospace, IDA, JPL, SEI, SPC Partial List of COCOMO Packages ❚ ❚ ❚ ❚ ❚ ❚ ❚ CB COCOMO COCOMOID COCOMO1 CoCoPro COSTAR COSTMODL GECOMO Plus ❚ ❚ ❚ ❚ GHL COCOMO REVIC SECOMO SWAN Steps in Software Estimation ❚ 1. Establish Objectives * Rough Sizing * Make-or-Buy * Detailed Planning ❚ 2. Allocate enough time, dollars, talent ❚ 3. Pin down software requirements * Document definitions, assumptions ❚ 4. Work out as much as detail as objectives permit Steps in Software Estimation ❚ 5. Use several independent techniques and sources * Top-Down vs. Bottom-Up * Algorithms vs. Expert Judgment...
Words: 2250 - Pages: 9
...first published in Boehm's 1981 book “Software Engineering Economics” as a model for estimating effort, cost, and schedule for software projects. COCOMO measures a piece of software by counting the source lines of code (SLOC) in the final program. It requires that a work breakdown structure be done prior to the estimation work. The number of lines of code is then estimated for each of the units of the work breakdown structure. The approach provides guidelines for counting lines of code to encourage some standardization across projects and across organizations. COCOMO is defined in terms of three different models: * Basic model * Determines its estimates of required effort based primarily on your estimate of the software project's size. * Intermediate model * Provides much better estimates because you supply settings for 15 Cost Drivers that determine the effort, and duration of software projects. * Detailed model * Similar to the Intermediate model, but this model uses different Effort Multipliers for each stage of a project. The Function Point Analysis (FPA) technique, originally developed by Alan Albrecht of IBM in the late 1970's, is a method of measuring software base off what the system would deliver to the user, rather than lines of code or...
Words: 527 - Pages: 3
...Software project management Phase 2 Bottom-up Estimation Work Breakdown Structure Deliverable | Tasks | Cost | Source Code | Develop Client’s functions | 8 days | | Develop manager’s functions | 7 days | | Produce Unit Testing modules | 7 days | Unit Testing | Produce Load Testing modules | 7 days | Load Testing | Analyze the performance of the Hotel reservation system | 3 days | Analyze Performance | Document Effort | 1 day | Component Design | Document User Manual | 7 days | User Manual | Document Usefulness of Methodologies | 2 days | Project Evaluation | Document of Estimates | 1 days | | Document | 1 days | Cost Estimate: 1- Function point methods Albrecht: Complexity of Components | Type of components | Low | Average | High | Total | EI: external input: “Input code” | X 3= | 10X4=40 | X6= | 40 | EO: external output: “Reports“ | X4= | 8X5= 40 | X7= | 40 | EQ: external inquiry: “DB Query” | X7= | X10= | 9X15= 135 | 135 | ILF: Internal logical file: “DB files” | 4X5= 20 | X7= | X10= | 20 | EIF: external interface file: “UI” | 2X3=6 | X4= | X6= | 6 | | System size | 241 | There are 10 input type, 8 output,4 internal logical file, 9 external inquiry, and 2 external interface. Both the internal file and interface is low , the output is average and also intput is average. •N.B: 60 lines of Java code are needed on average to implement an FP FP= 241, SLOC = 60 FP x SLOC= 241x 60 =14460 Function point methods...
Words: 393 - Pages: 2
...1 Software Cost Estimation Hareton Leung Zhang Fan Department of Computing The Hong Kong Polytechnic University {cshleung, csfzhang}@comp.polyu.edu.hk Abstract Software cost estimation is the process of predicting the effort required to develop a software system. Many estimation models have been proposed over the last 30 years. This paper provides a general overview of software cost estimation methods including the recent advances in the field. As a number of these models rely on a software size estimate as input, we first provide an overview of common size metrics. We then highlight the cost estimation models that have been proposed and used successfully. Models may be classified into 2 major categories: algorithmic and non-algorithmic. Each has its own strengths and weaknesses. A key factor in selecting a cost estimation model is the accuracy of its estimates. Unfortunately, despite the large body of experience with estimation models, the accuracy of these models is not satisfactory. The paper includes comment on the performance of the estimation models and description of several newer approaches to cost estimation. Keywords: project estimation, effort estimation, cost models. 1. Introduction In recent years, software has become the most expensive component of computer system projects. The bulk of the cost of software development is due to the human effort, and most cost estimation methods focus on this aspect and give estimates in terms of person-months...
Words: 6839 - Pages: 28
...been supported financially and technically by the COCOMO II Program Affiliates: Aerospace, Air Force Cost Analysis Agency, Allied Signal, DARPA, DISA, Draper Lab, EDS, E-Systems, FAA, Fidelity, GDE Systems, Hughes, IDA, IBM, JPL, Litton, Lockheed Martin, Loral, Lucent, MCC, MDAC, Microsoft, Motorola, Northrop Grumman, ONR, Rational, Raytheon, Rockwell, SAIC, SEI, SPC, Sun, TASC, Teledyne, TI, TRW, USAF Rome Lab, US Army Research Labs, US Army TACOM, Telcordia, and Xerox. COCOMO I Boehm proposed three levels of the model: basic, intermediate, detailed. The basic COCOMO'81 model is a single-valued, static model that computes software development effort (and cost) as a function of program size expressed in estimated thousand delivered source instructions (KDSI). The intermediate COCOMO'81 model computes software development effort as a...
Words: 1820 - Pages: 8
...ISSN (Print) : 2319-5940 ISSN (Online) : 2278-1021 International Journal of Advanced Research in Computer and Communication Engineering Vol. 2, Issue 6, June 2013 Accurate Software Size Estimation Using the Updated Function Point Analysis Model Vikas Kumar 1, Sweta Pandey 2 Computer Science and Application, Thapar University, Patiala, India 1 Information Technology, Banasthali University, Jaipur, India 2 Abstract: In this paper; a new Function Point Analysis model has been proposed. In this proposed model, a new general system characteristic is added. The expert user programming also affects the size of software. By including it in the list of general system characteristics, it creates a provision for taking end user facilities into account, while estimating the size of a project. It is clear that proposed FPA provides more accurate size estimates and it will narrow the gap between size estimated and actual size. This will result in more accurate effort and cost estimates, which ultimately results in increased productivity and proper staffing, planning and scheduling. Keywords: FPA, cost estimation, effort, size of project I. INTRODUCTION This document describes the Function point analysis which measures software by quantifying the functionality the software provides to the user based primarily on logical design. Here in this Function Point Analysis model has been proposed which creates a provision for taking end user facilities into account, while estimating the size of...
Words: 1301 - Pages: 6
...Function Point Analysis How to use this document...................................................................................... 1 1 Introduction ......................................................................................................... 2 2 Measures Derived from FPA ............................................................................... 2 3 Different FPA Methods ....................................................................................... 2 4 The advantages of using FPA............................................................................. 3 5 The disadvantages of, or problems using, FPA .................................................. 3 6 Developed v Delivered FPs................................................................................. 4 7 The use of FPs in estimating effort and cost ...................................................... 5 8 Function Point counting procedure ..................................................................... 6 8.1 IFPUG Method ............................................................................................. 6 8.1.1 Complexity Matrices............................................................................... 7 8.1.2 Complexity/UFP Contribution................................................................. 7 8.1.3 Overall FP Count ................................................................................... 8 8.1.4 IFPUG FPA Process Summary..........................
Words: 3966 - Pages: 16
...CS193P IPHONE APPLICATION DEVELOPMENT FALL 2011 Assignment I: Calculator Objective This assignment has two parts. The goal of the first part of the assignment is to recreate the demonstration given in the second lecture. Not to worry, you will be given very detailed walk-through instructions in a separate document. It is important, however, that you understand what you are doing with each step of that walk-through because the second part of the assignment (this document) is to add a couple of extensions to your calculator which will require similar steps to those taken in the walk-through. This assignment must be submitted using the submit script (see the class website for details) by the end of the day next Wednesday. You may submit it multiple times if you wish. Only the last submission will be counted. For example, it might be a good idea to go ahead and submit it after you have done the walk-through and gotten that part working. If you wait until the last minute to try to submit and you have problems with the submission script, you’ll likely have to use one of your valuable late days. Be sure to check out the Hints section below! Materials • Before you start this assignment, you will need to download and install the iOS SDK and Xcode 4 from http://developer.apple.com or using the App Store on Mac OSX. It is critical that you get the SDK downloaded and functioning as early as possible in the week so that if you have problems you will have a chance to talk...
Words: 1918 - Pages: 8
...Constructive Cost Model COCOMO Adapted from Allan Caine Outline COCOMO in a Coconut-shell Complete Examples Intermediate COCOMO: Cost Drivers Advantages and Limitations of COCOMO COCOMO in a Coconut-shell E = a ( KLOC ) Where b E is the Effort in staff months a and b are coefficients to be determined KLOC is thousands of lines of code The Constants Mode Organic 2.4 a 1.05 1.12 1.20 b Semi-detached 3.0 Embedded 3.6 The Modes Organic 2-50 KLOC, small, stable, little innovation Semi-detached 50-300 KLOC, medium-sized, average abilities, medium time-constraints Embedded > 300 KLOC, large project team, complex, innovative, severe constraints Examples Suppose size is 200 KLOC, Organic 2.4(200)1.05 = 626 staff-months Semi-Detached 3.0(200)1.12 = 1,133 staff-months Embedded 3.6(200)1.20 = 2,077 staff-months Project Duration TDEV Where = c(E ) d TDEV is time for development c and d are constants to be determined E is the effort Constants for TDEV Mode Organic 2.5 c 0.38 0.35 0.32 d Semi-detached 2.5 Embedded 2.5 Example Picking up from the last example, Organic E = 626 staff months TDEV = 2.5(626)0.38 = 29 months Semi-detached E = 1,133 TDEV = 2.5(1133)0.35 = 29 months Embedded E = 2077 TDEV = 2.5(2077)0.32 = 29 months Average Staff Size E [staff - months] SS = = = [staff] TDEV [ months] Productivity Size [KLOC] P= = = KLOC staff - month E [staff - months] Complete Example...
Words: 676 - Pages: 3
...[pic] 3D SEISMIC SURVEY DESIGN COURSE OUTLINE This course gives practical background for 3D survey design. It also provides the understanding of acquisition geometries, which is necessary for optimal seismic processing. ABREVIATIONS This is a list of commonly used abbreviations in this course notes. b bin dimension Fdom dominant frequency Fmax maximum frequency MA migration aperture NC number of channels NRL number of receiver lines NSL number of source lines NS number of source points per unit area RI receiver line interval RLI receiver line interval SI source interval SLI source line interval t two-way travel time Vint interval velocity immediately above the reflecting horizon Vave average velocity from surface to the reflecting horizon Xmin largest minimum offset Xmax maximum recorded offset Z depth to reflecting horizon UNITS CONVERSION TABLE To convert imperial To metric units Multiply by from imperial units Inches (in) Centimetres (cm) 2.54 Feet (ft) Meters (m) 0.3048 Miles (mi) Kilometres (km) 1.609 Square Miles (m ) Square Kilometres (km ) ...
Words: 4796 - Pages: 20
...groups basis for assigned to item categorizes has owned by attributes generates categorizes adjusted by assigned by derives counts items for CUSTOMER SUPPLIER for owns has based on based on belongs to belongs to has groups basis for CUSTOMER SITE sells to attributes for adjusts source of results from for generates replenished from assigns derived from assigns SUPPLIER SITE assigned to has class assignment group assignment for used in compiled for item assigned to tabulates count for contained in grouped count for describe location of ITEM CATEGORY PO COMMODITY CODE owned by assigned to an item by ABC ASSIGNMENT GROUP CLASS ABC ASSIGNMENT CYCLE COUNT CLASS CYCLE COUNT ITEM PHYSICAL INVENTORY ITEM COUNT PHYSICAL INVENTORY ADJUSTMENT located ITEM REPLENISH COUNT replenished from COST GROUP ASSIGNMENT HR LOCATION has source having is location for is located at replenishes replenishes replenishes is destination for abc assignment for owned by effects cycle count for adjusts count of adjusts located at count charges for for adjustment to owns is source for owns container items for container items belong to categorizes located at has default model of assigns category from...
Words: 1521 - Pages: 7
...doublespaced: Student name Teacher's name Course Name/section The day, month, and year the paper is due Double-space after the four-line heading, title is centered (capitalized, normal font Papers with a title page: 1/3 from the top:Title Centered (capitalized, normal font) The following information should be centered, with the last line (due date) at the bottom of the title page Student's name Teacher's name Course name/section Word count: (the word count) The paper’s due date Body: After the title, double-space and begin text Paragraphs: .5"/1.27 cm, first line indent Long Quotations: 4 or more lines must have "block quotation" 1"/2.54cm indent for entire length of quote In-text citations*: author's last name and page number (when available) of quote/idea in parenthesis e.g. (Park 42), before the period/full stop. *more info on in-text citations on page 3 Bibliography The title is ‘Works Consulted’ for any sources read. The title is ‘Works Cited’ for works quoted from or referred to in essay. You can have both Works Cited and Works Consulted for essay. The title should be centered at the top of a new page. Includes last name/page number heading in upper right corner Double spaced throughout, no extra spaces between entries or after title. Hanging indents: First line of each entry goes to left margin, subsequent lines in entry are indented .5 inches/1.27 cm. Alphabetical order by last name of the author, or by title if author isn’t given...
Words: 691 - Pages: 3
...Writing about Literature: Documentation Documentation It means acknowledging and referring to the sources from which a writer has taken information and materials from while writing a research paper. The source might be a primary one when the paper is dealing with a specific literary work or works be a certain author or it might be a secondary source when the materials referred to are of other authors who wrote on the same subject/author that the writer is writing his/her paper on. This documentation is important for two reasons: (a) to give the readers an opportunity of checking any information that he may doubt of been misinterpreted, (b) to avoid plagiarism by announcing the statements that are not of his own and are taken from other people. Documentation could be done through one of the following ways: • Textual documentation Almost all the literary papers by nature are dealing with one or more literary works which means certain text or texts are been studied. Titles like "Symbolism in William Blake's Tiger" indicate that the material that is used in the paper will a poem with the mentioned title. Essays and most of the newspaper articles that deal with one single short work without suing secondary sources are using this kind of documentation which is also called informal documentation. The name of the author and the title of the work on which the paper focus on are mentioned near the beginning of the essay as well as some other references like " in the opening...
Words: 1403 - Pages: 6
...I. General Document Guidelines I. Margins: One inch on all sides (top, bottom, left, right) II. Font Size and Type: 12-pt. Times New Roman font III. Line Spacing: Double-space throughout the paper, including the title page, abstract, body of the document, references, appendixes, footnotes, tables, and figures. IV. Spacing after Punctuation: Space once after commas, colons, and semicolons within sentences. Insert two spaces after punctuation marks that end sentences. V. Alignment: Flush left (creating uneven right margin) VI. Paragraph Indentation: 5-7 spaces VII. Pagination: The page number appears one inch from the right edge of the paper on the first line of every page. VIII. Running Head: The running head is a short title that appears at the top of the pages of a paper or published article. The running head is typed flush left at the top of all pages. The running head should not exceed 50 characters, including punctuation and spacing. Using most word processors, the running head and page number can be inserted into a header, which then automatically appears on all pages. IX. Active voice: As a general rule, use the active voice rather than the passive voice. For example, use "We predicted that ..." rather than "It was predicted that ..." X. Order of Pages: Title Page, Abstract, Body, References, Footnotes, Tables, Figures, Appendixes Title Page . Pagination: The Title Page is page 1. I. Running Head: The running head is typed flush left (all uppercase)...
Words: 2344 - Pages: 10
