http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-2.xsd
a toolkit for estimating software development effort & duration
International Software Benchmarking Standards Group
1 online resource (xxii, 289 pages) : illustrations.
Helping you deploy and manage high-performance data transformation solutions across your enterprise; this step-by-step guide explains the tools and methods necessary to extract conclusive business intelligence from disparate corporate data.
Note continued: Scope Management -- Summary -- ISBSG Regression Equation Tables -- Using the ISBSG Regression Equations -- Creating Graphs from the Equations -- Example Effort Estimate Using the Equations -- Summary -- Using the Comparison Technique -- Summary -- Background: Reasoning by Analogy -- Estimating by Analogy -- Advantages of Estimating by Analogy -- Drawbacks of Estimating by Analogy -- Summary -- Work Breakdown Structure: Introduction -- Using Process Models for Micro-Estimation -- Summary -- Subsets Implemented Utilizing Different Technologies -- Code and Reference Tables -- Subsets Characterized by Technical or Other Complexities -- Reused Code -- Summary -- Use of an Organization's Own Experience Data -- Use of the ISBSG Data -- ISBSG Repository -- Guidelines for Use of the ISBSG Data -- Presentation of Statistics -- Using Several Estimation Approaches -- Summary -- Case Study: A Student and Staff Records Management System (SSRM) -- Overview -- Functional Size Measurement -- Project Work Effort and Duration Estimates -- Example 1: Estimating Using Regression Equations -- Using Regression Equations to Generate Estimates for SSRM -- Regression Equations: Functional Size -- Regression Equations: Functional Size and Maximum Team Size -- Discussion -- Example 2: Estimating Using Comparison -- Estimating by Comparison Technique -- Using Estimating by Comparison to Generate Estimates for SSRM -- Discussion -- Example 3: Estimating Using Analogy -- Estimating by Analogy Technique -- Using Estimating by Analogy to Generate Estimates for SSRM -- Discussion -- Summary -- Estimating an Agile Project -- Story Points -- Story Point Scale -- Calibrating the Story Point Scale Using Past Projects -- Development Team Velocity -- Allocating Story Points to Stories -- Estimating Total Project Schedule and Cost at Project Initiation. Note continued: Allocating Stories to Individual Project Iterations -- Reviewing the Process at Project Completion -- Benefits of Agile Software Estimation Using Story Points -- Comparing Story Points and Function Points -- Summary -- Hourly Charge-Out Rate -- Internal Project: Building Software for Your Own Organization -- External Project: Building Software for an External Organization -- Refining Hourly Charge-Out Rate for Project Team Structure -- Indexing the Charge-Out Rate for Inflation and Currency Movements -- Additional Cost Considerations -- Costing Activities Outside Project Development Tasks -- Costing Effort Contributed by Personnel Not Included in the PDR -- Summary -- Additional Steps to Calculate Non-PDR-Related Project Costs -- Using the ISBSG PDR Tables to Create Tables for Your Estimating Framework -- Step 1. Identify the Development Platforms -- Step 2. Extract PDR Distributions Based on Development Languages -- Step 3. Adjust the Extracted PDR Distributions According to Team Size -- Step 4. Benchmarking Your Projects' PDR -- Step 5. Construct the Estimation Framework -- Estimates Are Targets, Not Predictions -- Calculating a Benchmark Estimate for a Planned Project -- Step 1. Adjust PDR for Team Size -- Step 2. Adjust PDR for Project Size -- Step 3. Adjust PDR for Development Language -- Step 4. Calculate Effort Estimate and Consider the Range of Probable Values -- Summary -- How Many FSM Methods Are There? -- Which FSM Method Should I Choose? -- How Hard Is It to Measure Functional Size? -- What Sort of Accuracy Can I Expect from an FSM Measurement? -- Value of FSM as a Size Measurement -- Summary -- ISO/IEC Definitions -- What Is Functional Size? -- Analogies to Illustrate Functional Sizing -- Key to Functional Size Measurement Is to "Think Logical" -- Counting in FSM: An Example Using IFPUG Function Points -- IFPUG Function Point Components. Note continued: What Is Involved in IFPUG Function Point Counting? -- Logical Boundary -- Where Does Functional Size Fit in with the ISBSG and Software Project Estimating? -- Summary -- New Development Case Study -- Sample Set of User Requirements -- Functional User Requirements -- Functional Size Measurement Using ISO/IEC 20926: 2009 [--] IFPUG 4.3 -- Determining the Functional Size -- Enhancement Case Study -- Sample Set of User Requirements -- Functional User Requirements -- Types of Functional. Size -- Summary -- Overview of the COSMIC Functional Size Measurement Method -- Applicability of the Method -- Principles for Measuring the COSMIC Functional Size of a Piece of Software -- Process for Measuring the COSMIC Functional Size of a Piece of Software -- COSMIC Method Documentation -- Summary -- Analysis of the Size of the New Software to Be Developed -- Analysis of the Size of the Enhancement to the Software -- Overall Size of the Software After the Enhancement -- Summary -- Size Measurement of the New Software to Be Developed -- Size Measurement of the Enhancement to the Software -- Overall Size of the Software After the Enhancement -- Summary -- Data Availability -- Data Quality -- What the ISBSG Data Can Be Used For -- Considerations -- ISBSG Project Data Positioning -- Comparing Apples with Apples -- Selecting a Suitable Data Subset -- What You Can Find in the ISBSG Repository -- Project Origin -- Project Context -- Type of Project -- Type of Product -- Development Environment -- Methods and Tools -- Summary -- Additional Documentation -- Presentation of Statistics -- Explanation of Tables -- Use of the Statistics -- Project Delivery Rates -- Project Delivery Rate by Use of CASE Tools -- Project Delivery Rate by Use of Methodology -- Project Delivery Rate by Relationship Between Customer, Developers, Users. Note continued: Project Delivery Rate by Project Size -- Project Delivery Rate by Maximum Team Size -- Impact of Maximum Team Size and Project Size on Project Delivery Rate -- What Are These Estimates Based On? -- Which Equation(s) Should You Use? -- Do These Equations Apply to My Project? -- What Do the Statistics Mean? -- How to Submit a Project -- Description of the Project Benchmark Report -- Terms -- Metrics.
International Software Benchmarking Standards Group ; compiled and edited by Peter R. Hill.
Electronic reproduction. New York, N.Y. : McGraw Hill, 2011. Mode of access: World Wide Web. System requirements: Web browser. Access may be restricted to users at subscribing institutions.
Mode of access: Internet via World Wide Web.
Includes bibliographical references and index.
Project estimation: background, concepts, and approaches
Software estimates: how accurate are they?
SING software and size-approximation accuracy
Some practical software size approximation techniques
Estimating using work breakdown structure
How do I estimate a project comprising varying components?
Project estimation using the ISBSG repository
Estimating for agile software development
Guide to estimating project cost using ISBSG data
Creating a software project estimation framework using the ISBSG repository
Functional size measurement methods in use today
Brief tutorial on functional size measurement (FSM)
Cosmic functional size measurement method
Practical software project estimation : a toolkit for estimating software development effort & duration
New York, N.Y. : McGraw-Hill Education, 2011