BAE Systems Insyte Software Estimation
|
|
- Constance Shepherd
- 6 years ago
- Views:
Transcription
1 BAE Systems Software Estimation Steve Webb BAE Systems Estimating Focus Group Chairman Engineering Estimation & Measurement Manager 22 April
2 Background BAE Systems Estimating Focus Group covers the whole of BAE except North America produced BAE Systems Engineering & Software Estimation Handbooks, Guides, Estimation Workbooks, BAE Systems Code Counter tool, UK BAE Systems COSYSMO model BAE Systems Integrated System Technologies () covers defence, homeland security & complex, mission-critical solutions across 15 UK sites with around 4,000 staff software projects: range from 1 person to many hundreds of effort-years of development per project large systems of around 1,000,000 hand-written logical Source Lines Of Code plus auto-generated code has a CMMI initiative & some parts are CMM level 3 2
3 Software Bids bid estimates do not contain any hidden contingency Accurate estimates are essential to reduce the amount of contingency to win orders Bid estimates are produced by engineering staff for the bid team Bids are independently reviewed in 5 stages: 1. Estimation Review for estimation completeness, accuracy, etc done by Engineering 2. Cost Review by the company Chief Engineer (or team) 3. Technical Bid Review (meets Win Strategy, Target Cost, ITT) 4. Phase 2A Review the chair is independent of the Bid team 5. Commercial Review 1 & 2 are performed by Engineering staff who understand software & estimation 3
4 Software Estimation Process has a Common Software Engineering Process (CSEP) Only 1 Software Measurement process Only 1 Software Estimation process & all software bids use it This presentation will concentrate on Software Estimation process Next 3 slides show 3 of the 12 html Software Estimation process pages All statements requiring action in this process are really shalls statements 4
5 5
6 6
7 7
8 Estimation Methods: Analogy (e.g. within 10%) - a preferred method Expert Judgement Top-down Bottom-up Parametric Models (e.g. within 20%) e.g. COCOMO II, own tools Proxy (e.g. Use Case points) Used to create size & effort estimates 8
9 Estimate at least 2 different ways Estimate at least 2 ways at the CSCI/component (i.e. Computer Software Configuration Item) level & combine them into 1 overall estimate E.g., estimate 1 = Top-down (analogy size based), estimate 2 = Bottom-up Bottom-up estimate is broken down into s/w lifecycle phases, work products, support & management activities use generic software WBS document Two staff independently estimating the same way is only deemed as 1 way Using 3 points estimation (min, most likely, max) is part of estimating 1 way At bid phase more accuracy is achieved by estimating 2 different ways, using single point estimates, than estimating just 1 way with 3-points One estimate must be derived from work product size e.g. number of: Logical Source Lines Of Code Use Cases points Document lines (e.g. Design, Test documents) 9
10 Bid Estimates Reconcile these estimates into 1 final estimate Estimate 1: Top-down Size Analogy (inc. 3-points) Estimate 2: Bottom-up (inc. 3-points) Estimate n Final Effort Estimate (inc. 3-points) 50%, 70%, 90% development uncertainty points 10
11 Estimate Reconciliation Resolved at the component level Find out why the difference in predicted effort e.g. check estimates cover same scope, check level of detail, check expected accuracy Ensure within bounds of each other e.g. within 10% of median If estimate(s) still outside these bounds then e.g.: estimate additional estimated way(s) improve the accuracy by estimating in more detail increase use of Delphi technique No hard rules on how to combine the estimates Sometimes use Wideband Delphi but normally use Delphi group meeting 11
12 Development Uncertainty Risk estimates use Triangular distribution Development uncertainty estimates typically use Beta distribution & deterministic formulae - this is as accurate as Monte-Carlo Mandated to estimate 50%, 70%, 90% development uncertainty effort pts If high uncertainty then Monte Carlo 50%, 70%, 90% schedule pts are done Management may decide more than the above is required Technical & Management Contingency budgets hold development reserve Technical Contingency budget takes into account the amount of development uncertainty and the amount of risk 12
13 David Henry study & Software Estimation: Perfect Practice Makes Perfect by David Henry Read the June 2002 CrossTalk article by David Henry Engineers used 3-point estimates & deterministic Beta distribution spreadsheet which contained history and comments - very useful feedback loop Accuracy of estimates dramatically improved doing weekly estimation Average % difference between estimates and actual task completion times Month 1 - typically were under-estimates Variance in group Month 1 75% 25% - 150% Month 3 35% Month 6 25% Some staff (inc. subject matter experts) will significantly under-estimate the max pt without practice can result in estimated 90% pt becoming actual 70% pt See next slide for the software engineer spreadsheet for estimating development uncertainty using a deterministic formulae for effort/cost 13
14 3-point Spreadsheet Three Point Estimation Spreadsheet (BMS Id 19608) Overall Information: Overall 50% pt = sum of 50% pts = 4,991.7 Feed-back information: Total Expected - completed activities only = 1,650.0 Total Actual - completed activities only = 1,962.0 Total Difference (compared to Expected) = 19% Task Name Minimum Most Likely Maximum Individual 50% Point Actual % Difference Task % Task 2 Task Uses the Traditional Beta Distribution % 33% Task 4 Task 5 Use the spreadsheet with either 200 effort or 250size (not 350 both) % 0% engineers use this spreadsheet to monitor their estimation capabilities 14
15 Estimating Size Size (or the size of the changes) is a big driver of costs Staff tend to underestimate size resulting in underestimated effort figure Key size items estimated by 2 staff independently of each other i.e. Delphi Analogy data obtained from Engineering Size & Productivity database All projects must write a detailed measurement report comparing the bid estimate with actuals It must include size, effort, productivity, at project & component level & include performance factors, software lifecycle effort percentages BAE Systems Software Size Estimation workbook estimates 10%, 50%, 70% and 90% size and effort development uncertainty points 15
16 BAE Systems Code Counter Tool One of the most advanced tools of its type Used across the whole of BAE including CMMI level 5 companies Tool was developed by DoD tasked USC to produce a SLOC difference tool Counts 16 languages and different types of Assembler Counts logical SLOC and physical SLOC Counts amount of new files, deleted files Counts amount of added, changed, unmodified, deleted SLOC within a file Counts at file, component or any directory level Can exclude counting source test files by using ignore file/folder facility Has a self-check counting mechanism Has GUI and Batch mode Easily installed by the engineer 16
17 Using this Tool counts new, added, adopted, adapted & deleted SLOC per component Using actual effort it has been easy to populate the Engineering Size & Productivity database New Malden very large projects e.g. Type 23, Type 45, Astute keep measurements at the component level In general the data confirms the COCOMO II Reuse Model as a valid model Model breaks down on very large projects with many small modifications i.e. COCOMO II AA should be zero but we set it to non-zero 17
18 Logical SLOC production monitored by DataDrill Project Manual Logical SLOC Size 18
19 BAE Systems Software Size Estimation workbook Estimates effort for new, adapted and adopted work Uses COCOMO II Reuse Model to estimate adopted & adapted productivity It requires input of size (e.g. SLOC, Use Case Pts) & new work productivity 19
20 BAE Systems Software Size Estimation workbook example Whole workbook is far too big to get on to a slide 10,167 is an exact figure as counted by BAE Systems Code Counter E.g. component with new work (i.e. blue) plus adapting 10,167 logical SLOC with e.g. Reqs Rework = 2%, Code Rework 10%, Integration Test = 15% Functional Name (cells A11 to A45) Size min Size most likely Size max Size 50% Reuse Min Reuse Most Likely Reuse Max Reuse 50% Est. % Reqs Anal. Rework Est. % Arch. Design Rework Est. % Detailed Design Rework Est. % Code & Unit Test Rework Est. % Int. & Test Rework Est. % Fn Proving (FAT) Rework AAF TOTAL 2,000 2,500 3,500 2,583 10,167 10,167 10,167 10,167 Component example 2,000 2,500 3,500 2,583 10,167 10,167 10,167 10,167 2% 2% 10% 10% 15% 20% 10.2 % 20
21 Use appropriate historical data It is important to use appropriate data for Analogy estimates Productivity will vary tremendously on different projects for valid reasons Logical SLOC size alone accounts for 2 times difference in productivity Type of modification e.g. new code compared to changed code can show 2 times difference Performance factors (inc. product complexity) accounts for 3 times difference So a similar component is used in the analogy comparison 21
22 Performance Factors BAE Systems Software Size Estimation workbook requires to know what changes to performance factors have occurred since historical data Most factors are described in the COCOMO II Model Definition Manual Some of the key factors are: produced similar systems before applications, tools, programming, platform experience staff capabilities product (technical) complexity amount of reuse component coupling schedule compression the requirements quality (completeness, stability) the effects of multi-site working Often staff estimate the differences in performance factors without using COCOMO II 22
23 Performance Factors Example Performance Factor Applications Experience Programming Experience Schedule Duration Base Estimated Modifier Comments Effect % decrease 10% 0.9 Since this component was first developed staff applications experience has improved. decrease 10% 0.9 Now more experience of C# increase 15% 1.15 This component is on the critical path. It is required to be produced in 8.5 months not the typical 10 months. TOTAL = 0.90 * 0.90 * 1.15 If 100 units of effort were spent on original project it would have taken 90 units with the applications experience staff they now have The above is multiplicative and tries to behave like parametric tools TOTAL of <1 will mean an increase of productivity If original productivity was 2.0 SLOC/hr then new prod. = 2.0 / 0.93 = 2.15 SLOC/hr If a large no. of factor differences between old and new component then a COCOMO II estimate is produced instead 23
24 24
25 Review & Record Estimate Independently reviewed by someone who understands s/w & estimating Checks it is complete & compliant with estimates objectives & constraints Estimate is accurate given purpose of estimate (e.g. ROM, fixed price) Confirm it is traceable from top to bottom level It has no overlaps or inconsistencies internally or with other estimates All estimating figures (size, effort, cost, schedule duration, probability pts, expected accuracy) look reasonable Check rationale, assumptions, justifications Check all funding issues & dependencies are explicit Confirm risks been identified & risk estimates are adequate & appropriate Confirm risk mitigation actions budget is in the development estimate Identify & record any issues to be resolved, additional information to be supplied and/or questions to be answered prior to approval 25
26 Software Functional Manager (or delegated person): Independently reviews the bid estimate Records bid information in the Software Estimates Register Ensures bid Estimation Checklist is completed by estimator & reviewer Checklist helps estimators & reviewer and acts a sign-off Confirms all outstanding review actions been cleared Ensures the bid estimate is under configuration control 26
27 detailed measurement definitions e.g. How to count Size (e.g. Logical SLOC size, Use Case points) How to convert auto-generated SLOC into logical SLOC size How to count effort - what is software work, what is systems work, what is included in the software lifecycle Clear what is risk and what is uncertainty Without detailed definitions staff will estimate differently 27
28 Estimation Measurement report data contains: Bid estimated size and actual logical SLOC size At project level & component level record the actual amount of new, added, changed & unmodified logical SLOC New = new component Predicted & actual logical SLOC/hr productivity project & component level Record the reasons for the productivity (+ve & -ve) Software Lifecycle Breakdown, e.g. % spent on requirements, design, coding, integration & system test, management, configuration management Defect density per component Defect leakage table Amount of Rework in-phase and out-of-phase Amount of unpaid requirements growth & volatility 28
29 Summary Follow a well defined estimation process Use Analogy as much as possible Use Delphi technique Ensure size is estimated accurately Use a Code Counter to count logical SLOC size & differences Use a company Engineering Size & Productivity database Estimate probability points for uncertainty & risk Estimate at least 2 different ways at component level Use a checklist to ensure key estimation aspects are performed Perform an independent review looking at how good the estimate is in detail by staff who understand the software domain & estimation Develop feed-back loops between estimates and actuals Regularly re-estimate during s/w lifecycle for more accurate estimates 29
30 Any Questions? 30
31 BAE Systems Integrated System Technologies () Limited Victory Point Lyon Way, Frimley, Camberley Surrey, GU16 7EX United Kingdom Telephone +44 (0) Fax +44 (0) Steve Webb: Telephone
MTAT Software Economics. Session 6: Software Cost Estimation
MTAT.03.244 Software Economics Session 6: Software Cost Estimation Marlon Dumas marlon.dumas ät ut. ee Outline Estimating Software Size Estimating Effort Estimating Duration 2 For Discussion It is hopeless
More informationEffective Software Sizing A Galorath Web Seminar 01 September 2004
Effective Software Sizing A Galorath Web Seminar 01 September 2004 1 Effective Software Sizing What are we estimating? What is software? Why do we care? What do we mean by software size? How do we measure
More informationCMMI and FPA. the link and benefit of using FPA when rolling out CMMI. Christine Green IFPUG - Certified Function Point Specialist EDS
CMMI and FPA the link and benefit of using FPA when rolling out CMMI Christine Green IFPUG - Certified Function Point Specialist EDS and the EDS logo are registered trademarks of Electronic Data Systems
More informationSoftware Cost Estimation Issues for Future Ground Systems
Software Cost Estimation Issues for Future Ground Systems Nancy Kern Software Engineering Department ETG/RSD The Aerospace Corporation Outline ➊ Background ➋ Software Cost Estimation Research OO Software
More informationSoftware Cost Metrics Manual
MOTIVATION Software Cost Metrics Manual Mr. Wilson Rosa Dr. Barry Boehm Mr. Don Reifer Dr. Brad Clark Dr. Ray Madachy 21 st Systems & Software Technology Conference April 22, 2009 DOD desires more credible
More informationSoftware Estimation. Estimating Software Size
Appendix C - Software Estimation 1 Software Estimation Accurately estimating software size, cost, effort, and schedule is probably the biggest challenge facing software developers today. A discussion of
More informationApplying PSM and Insight within a Small Organization
Applying PSM and within a Small Organization 5th Annual 2001 PSM Users Group Conference Mary Ann McGarry Software Technical Advisor (IITRI) Spectrum Engineering Sector mmcgarry@iitri.org Agenda Organizational
More informationSoftware Cost Risk Estimation and Management at the Jet Propulsion Laboratory
Software Cost Risk Estimation and Management at the Jet Propulsion Laboratory Jairus Hihn Karen Lum 17 th International Forum on COCOMO and Software Cost Modeling October 22-25, 25, 2002 Background & Context
More informationPMP EXAMINATION PREP CHAPTER 6 SCHEDULE MANAGEMENT. PMP Exam Prep
PMP EXAMINATION PREP CHAPTER 6 SCHEDULE MANAGEMENT PMP Exam Prep PROJECT SCHEDULE MANAGEMENT Page 223 Schedule Management Process : Contains 6 of the 49 total processes Plan Schedule Management Define
More informationIntroduction to Cost Estimation - Part I
Introduction to Cost Estimation - Part I Best Practice Checklists Best Practice 1: Estimate Purpose and Scope The estimate s purpose is clearly defined The estimate s scope is clearly defined The level
More informationTHE PMP EXAM PREP COURSE
THE PMP EXAM PREP COURSE Session 2 PMI, PMP and PMBOK are registered marks of the Project Management Institute, Inc. www.falconppm.com Agenda 9:00 10:15 Practice the PMP Questions 10:15 10:30 Break 10:30
More informationSoftware Project Management
Software Project Management Session 4: WBS, Estimation & Scheduling Dr. E. Wallmüller, Project Management, Spring 2006 1 Estimation Predictions are hard, especially about the future, Yogi Berra 2 Types:
More informationScheduling 2 Day Structure
Day 1 Session 1: Design and Structure your Schedule 1. The need for planning and scheduling a. Purpose = communication not control b. Understand audience 2. Simple -v- complex projects 3. Planning -v-
More informationSoftware Technology Conference
30 April 2003 Costing COTS Integration Software Technology Conference Salt Lake City Linda Brooks 1 Objective Provide a roadmap for doing an estimate for a Commercial Off-the-Shelf (COTS) software intensive
More informationSoftware Growth Analysis
Naval Center for Cost Analysis Software Growth Analysis June 2015 Team: Corinne Wallshein, Nick Lanham, Wilson Rosa, Patrick Staley, and Heather Brown Software Growth Analysis Introduction to software
More informationProject Time Management
Project Time Management Project Time Management Project Time Management includes the processes required to manage timely completion of the project. Plan schedule management The process of establishing
More informationT Software Testing and Quality Assurance Test Planning
T-76.5613 Software Testing and Quality Assurance 10.10.2007 Test Planning Juha Itkonen Outline Test planning, purpose and usage of a test plan Topics of test planning Exercise References: IEEE Std 829-1998,
More informationPMP Exam Preparation Course Project Time Management
Project Time Management 1 Project Time Management Processes Define Activities Sequence Activities Estimate Activity Resources Estimate Activity duration Develop Schedule Control Schedule In some projects,
More informationPLANNING AND ESTIMATING
Slide 9.1 Overview Slide 9.2 PLANNING AND ESTIMATING Planning and the software process Estimating duration and cost Components of a software project management plan Software project management plan framework
More informationDeveloping a Cost Estimation Probability Model of a Large Multi-Year System An Experience Report
Developing a Cost Estimation Probability Model of a Large Multi-Year System An Experience Report NDIA 2012 Kathleen Dangle, Madeline Diep, and Forrest Shull Fraunhofer Context of Our Experience Program
More informationPersonal Software Process SM for Engineers: Part I
Personal Software Process SM for Engineers: Part I Introduction to the PSP SM Defect Removal Estimation of Project Size Microsoft Project Design READING FOR THIS LECTURE A Discipline for Software Engineering,
More informationFundamental estimation questions. Software cost estimation. Costing and pricing. Software cost components. Software pricing factors
Fundamental estimation questions Software cost estimation How much effort is required to complete an activity? How much calendar time is needed to complete an activity? What is the total cost of an activity?
More informationAddressing the Challenges of Systems Engineering Estimation
Addressing the Challenges of Systems Engineering Estimation Karen McRitchie/Kathy Kha, Galorath Incorporated 2016 Copyright Galorath Incorporated 1 ABSTRACT Cost is a crucial factor in evaluating the viability
More informationPresented at the 2013 ICEAA Professional Development & Training Workshop - ODASA-CE Software
ODASA-CE Software Growth Research ICEAA 2013 Authors: Lauren Nolte, Kevin Cincotta, Eric Lofgren, Remmie Arnold Sponsor: Shawn Collins, ODASA-CE Outline 1. Background & Purpose Software Estimating Process
More informationProject Managers Guide to Systems Engineering Measurement for Project Success
Practical Software and Systems Measurement Project Managers Guide to Systems Engineering Measurement for Project Success June 16, 2017 Greg Niemann gregory.niemann@lmco.com Project Managers Guide to Systems
More informationSoftware Maintenance, Sustaining Engineering, and Operational Support
Software Maintenance, Sustaining Engineering, and Operational Support Estimating Software Maintenance Costs for U.S. Army Weapons Systems Office of the Deputy Assistant Secretary of the Army for Cost and
More informationPROJECT TIME MANAGEMENT
PROJECT TIME MANAGEMENT ESTIMATE ACTIVITY DURATION PLANNING MONITORING & CONTROLLING 6.1 Plan Schedule Mgt 6.7 Control Schedule 6.2 Define Activities 6.3 Sequence Activities 6.4 Estimate Activity Resources
More informationLife Cycle Plan (LCP)
Life Cycle Plan (LCP) Mission Science Information and Data Management System 3.0 Team 03 Fei Yu: Project Manager, Life Cycle Planner Yinlin Zhou: Prototyper, Operational Concept Engineer Yunpeng Chen:
More informationSYED AMMAL ENGINEERING COLLEGE (An ISO 9001: 2008 Certified Institution)
MG6088 SOFTWARE PROJECT MANAGEMENT 1. Define software project management. QUESTION BANK UNIT - 1 PART A 2. Point out the characteristics of software project? 3. List the activities covered by software
More informationDRAFT. Effort = A * Size B * EM. (1) Effort in person-months A - calibrated constant B - scale factor EM - effort multiplier from cost factors
1.1. Cost Estimation Models Parametric cost models used in avionics, space, ground, and shipboard platforms by the services are generally based on the common effort formula shown in Equation 1. Size of
More informationSynthesis of Existing Cost Models to Meet System of Systems Needs
Paper #128 Synthesis of Existing Cost Models to Meet System of Systems Needs Jo Ann Lane University of Southern California Center for Software Engineering 941 W. 37th Place, SAL Room 328 Los Angeles, CA
More informationA Parametric Approach to Project Cost Risk Analysis
A Parametric Approach to Project Cost Risk Analysis By Evin Stump Senior Systems Engineer Galorath Incorporated Preface Risk arises when the assignment of the probability of an event is statistically possible
More informationChapter 6. Software Quality Management & Estimation
Chapter 6 Software Quality Management & Estimation What is Quality Management Also called software quality assurance (SQA) s/w quality:- It is defined as the degree to which a system, components, or process
More informationCalibration and Historical Data Chapter 8
Dilbert Scott Adams Dilbert Scott Adams Dilbert Scott Adams Calibration and Historical Data Chapter 8 Calibration: used to convert counts to estimates Example: Counting defects late in the project Given
More informationManagement of Software Engineering. Ch. 8 1
Management of Software Engineering Ch. 8 1 Project control Ch. 8 2 Work Breakdown Structure WBS describes a break down of project goal into intermediate goals Each in turn broken down in a hierarchical
More informationSoftware Engineering. Lecture 2: The Personal Software Process
Chair of Software Engineering Software Engineering Prof. Dr. Bertrand Meyer March June 2007 Lecture 2: The Personal Software Process PSP: the background CMMI: Capability Maturity Model Integration (originally:
More informationSpelunking Tools - Phoenix IEEE-CS May 3, Dan Houston, Ph.D. Estimation Techniques for Software Projects
Spelunking Tools - Estimation Techniques for Software Projects Phoenix IEEE-CS May 3, 2006 Dan Houston, Ph.D. Caves Software Costing and Sizing Accuracy vs. Phase Taken from COCOMO II Model Definition
More informationProject Management Professional (PMP) Exam Prep Course 6 - Project Schedule Management
Project Management Professional (PMP) Exam Prep Course 6 - Project Slide 1 Looking Glass Development, LLC (303) 663-5402 / (888) 338-7447 4610 S. Ulster St. #150 Denver, CO 80237 information@lookingglassdev.com
More informationCOSYSMO: A Systems Engineering Cost Model
COSYSMO: A Systems Engineering Cost Model Ricardo Valerdi and Barry W. Boehm Abstract: Building on the synergy between Systems engineering and Software Engineering, we have developed a parametric model
More informationYou document these in a spreadsheet, estimate them individually and compute the total effort required.
Experience-based approaches Experience-based techniques rely on judgments based on experience of past projects and the effort expended in these projects on software development activities. Typically, you
More informationPMP Exam Preparation Course Project Scope Management
Project Scope Management 1 Product Scope Product scope The features and functions that are to be included in your products or service or result of the project. Completion is measured against the product
More informationRISK MANAGEMENT SUPPLEMENT TO IEEE
SMC Tailoring SMC-T-005 15 May 2015 ------------------------ Supersedes: SMC-T-005 (2014) Air Force Space Command SPACE AND MISSILE SYSTEMS CENTER TAILORING RISK MANAGEMENT SUPPLEMENT TO IEEE-15288.1 APPROVED
More informationEffective Use of Function Points for Analogous Software Estimation
Effective Use of Function Points for Analogous Software Estimation Dan French, PMP, CFPS, CSM Principal Consultant dfrench@cobec.com 202-827-1316 www.cobec.com Agenda -Introduction -Definition of Analogous
More informationSystem Cost Modeling Using Proxy Estimation and COSYSMO
System Cost Modeling Using Proxy Estimation and COSYSMO October 21, 2014 Reggie Cole Lockheed Martin Senior Fellow reggie.cole@lmco.com Kevin Woodward Lockheed Martin Fellow kevin.woodward@lmco.com 1 We
More informationGEARING FACTORS. The A FLEXIBLE SIZING APPROACH
GEARING FACTORS The A FLEXIBLE SIZING APPROACH MB Duration (Months) DERIVING GEARING FACTORS Determining the scope of a proposed system is one of the most challenging aspects of any software estimate.
More informationCurrent and Future Challenges for Ground System Cost Estimation
Current and Future Challenges for Ground System Cost Estimation Barry Boehm, Jim Alstad, USC-CSSE GSAW 2014 Working Group Session 11F Cost Estimation for Next-Generation Ground Systems February 26, 2014
More informationEstimating Size and Effort
Estimating Size and Effort Massimo Felici and Conrad Hughes mfelici@staffmail.ed.ac.uk conrad.hughes@ed.ac.uk http://www.inf.ed.ac.uk/teaching/courses/sapm/ Slides: Dr James A. Bednar SAPM Spring 2009:
More informationA Methodology and Implementation For Software System Cost and Risk Estimation
A Methodology and Implementation For Software System Cost and Risk Estimation John Gaffney, Lockheed Martin Systems & Software Resource Center Jeanne Bridel, Lockheed Martin Transportation and Security
More informationSoftware cost estimation
Software cost estimation Joseph Bonello (based on slides by Ian Sommerville) Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for software productivity
More informationLECTURE 5 SCOPE MANAGEMENT FOR SOFTWARE PROJECT. S.No Management Process Output Documents for Scope Management
LECTURE 5 SCOPE MANAGEMENT FOR SOFTWARE PROJECT The Six Scope Management Processes 1. Plan Scope Management 2. Collect Requirements 3. Define Scope 4. Create WBS 5. Control Scope 6. Validate Scope S.No
More informationAppendix. Process Inputs and Outputs
3601cA.fm Page 493 Wednesday, October 26, 2005 12:47 AM Appendix A Process and Throughout this book, PMP: Management Professional Study Guide, 3rd Edition, I ve discussed the inputs and outputs to the
More information1.Which of the items listed below is not one of the software engineering layers?
1.Which of the items listed below is not one of the software engineering layers? Process Manufacturing Methods Tools 2.The software quality assurance activity which is performed to check errors in logic,
More informationSoftware Engineering
Software Engineering Project Management 1 Objectives To explain the main tasks undertaken by project managers To introduce software project management and to describe its distinctive characteristics To
More information2011 SCEA Conference Presentation Function Point Analysis: One Size Fits All
2011 SCEA Conference Presentation Function Point Analysis: One Size Fits All Dan French, CFPS dfrench@cobecconsulting.com Program Introduction Origins of Function Points Common Misconceptions Regarding
More informationTime Management PLANNING
Time Management 6.1 Plan Schedule Management: The process of establishing policies, procedures and documentation for planning, developing, managing, executing and controlling the project schedule # Schedule
More informationSoftware Project Management. Software effort
Software Project Management Chapter Five Software effort estimation 1 Objectives The lecture discusses: why estimating is problematic (or challenging ) the main generic approaches to estimating, including:
More informationData-Driven Estimating Lessons Learned
Data-Driven Estimating Lessons Learned Melissa Winter Solutions Architect Canadian Cost Symposium October 21, 2014 2013 PRICE Systems, LLC All Rights Reserved Decades of Cost Management Excellence 1 Knowledge
More informationMORS Introduction to Cost Estimation (Part I)
MORS Introduction to Cost Estimation (Part I) Mr. Huu M. Hoang Slide 1 Disclosure Form Slide 2 Module Four Module #(s) Items covered Presenter Start Stop One (1) Overview and Background (1) Define Estimate
More informationPROJECT EXECUTION PLANNING FOR COST AND SCHEDULE MANAGERS
PROJECT EXECUTION PLANNING FOR COST AND SCHEDULE MANAGERS ALLEN C. HAMILTON PMP CCE Project Management Associates LLC 3 Totten Way, Suite 110 Morris Plains, New Jersey 07950 USA Telephone: +1 973 984-1853
More informationIntegration Mgmt / Initiating Process Group 4.1 Develop Project Charter
1 Mgmt / Initiating Process Group 4.1 Develop Project Charter Project statement of work Business Case Contract Enterprise environmental factors Project charter Expert judgement 26/02/2013 18:22:56 1 2
More informationGoals of course. Themes: What can you do to evaluate a new technique? How do you measure what you are doing?
MSWE 607: Software Life Cycle methods and Techniques Instructor: Professor Marvin V. Zelkowitz Office: 4121 AV Williams Phone: 405-2690 or 403-8935 (Fraunhofer Center) Email (Best way to contact) mvz@cs.umd.edu
More informationDarshan Institute of Engineering & Technology for Diploma Studies
RESPONSIBILITY OF SOFTWARE PROJECT MANAGER Job responsibility Software project managers take the overall responsibility of project to success. The job responsibility of a project manager ranges from invisible
More informationThe Impact of Requirements on Software Quality Across Three Product Generations
The Impact of Requirements on Software Quality Across Three Product Generations John Terzakis Intel Hudson, MA USA john.terzakis@intel.com Abstract In a previous case study, we presented data demonstrating
More informationTEST METRICS: A PRACTICAL APPROACH TO TRACKING AND INTERPRETATION
BIO PRESENTATION SUPPLEMENTAL MATERIALS T8 May 20, 2004 11:15AM TEST METRICS: A PRACTICAL APPROACH TO TRACKING AND INTERPRETATION Shaun Bradshaw Questcon Technologies Inc International Conference On Software
More informationWhat are Requirements? SENG1031 Software Engineering Workshop 1. My Notes. System Overview: The Big Picture
What are Requirements? SENG1031 Software Engineering Workshop 1 Requirements, An Overview Peter Ho CSE, UNSW 5 Aug 2010 Requirements are a collection of statements defined by the System Stakeholders. These
More informationUnit 381 IT Project Management Level 3. Credit value 10. Rationale
Unit 381 IT Project Management Level 3 Credit value 10 Rationale The aim of this unit is to enable candidates to understand the business environment within which new projects are initiated. Candidates
More informationProject Documentation Checklist. Table of Contents
COMPANY NAME Project Documentation Checklist Table of Contents Revision History... 2 Initiation and Feasibility Study... 1 Requirements (Feasibility study supports project funding)... 2 Design/Project
More informationBootstrapping Process Improvement Metrics: CMMI Level 4 Process Improvement Metrics in a Level 3 World
Jet Propulsion Laboratory! Bootstrapping Process Improvement Metrics: CMMI Level 4 Process Improvement Metrics in a Level 3 World Jairus Hihn Scott Morgan Jet Propulsion Laboratory, California Institute
More informationProject Management CSC 310 Spring 2017 Howard Rosenthal
Project Management CSC 310 Spring 2017 Howard Rosenthal 1 No?ce This course is based on and includes material from the text: Effective Project Management - Traditional, Agile, Extreme 7TH Edition Authors:
More informationCMMI V2.0 MODEL AT-A-GLANCE. Including the following views: Development Services Supplier Management. CMMI V2.0 outline BOOKLET FOR print.
CMMI V.0 MODEL AT-A-GLANCE Including the following views: Development Services Supplier Management CMMI V.0 outline BOOKLET FOR print.indd CMMI V.0 An Integrated Product Suite Designed to meet the challenges
More informationEstimating SW Size and Effort Estimating Size and Effort
Estimating SW Size and Effort Estimating Size and Effort Dr. James A. Bednar jbednar@inf.ed.ac.uk http://homepages.inf.ed.ac.uk/jbednar Dr. David Robertson dr@inf.ed.ac.uk http://www.inf.ed.ac.uk/ssp/members/dave.htm
More informationTest Metrics: A Practical Approach to Tracking & Interpretation
Test Metrics: A Practical Approach to Tracking & Interpretation Prepared By: Shaun Bradshaw Director of Quality Solutions Questcon Technologies Abstract It is often said, You cannot improve what you cannot
More informationObject-Oriented and Classical Software Engineering THE SOFTWARE PROCESS 9/17/2017. CHAPTER 3 Slide 3.2. Stephen R. Schach. Overview Slide 3.
Slide 3.1 CHAPTER 3 Slide 3.2 Object-Oriented and Classical Software Engineering THE SOFTWARE PROCESS Eighth Edition, WCB/McGraw-Hill, 2011 Stephen R. Schach Overview Slide 3.3 Overview (contd) Slide 3.4
More informationA Review of Agile Software Effort Estimation Methods
A Review of Agile Software Effort Estimation Methods Samson Wanjala Munialo. Department of Information Technology Meru University of Science and Technology Meru - Kenya Geoffrey Muchiri Muketha Department
More informationInformation Technology Estimation & Measurement
Information Technology Estimation & Measurement PRICE Systems PSM JULY 2004 David P. Seaver Technical Director david.seaver@pricesystems.com 240.725.0836 Price Systems LLC Program Affordability Management
More informationInternational Association of Certified Practicing Engineers
www.iacpe.com Knowledge, Certification, Networking Page: 1 71 IACPE No 19, Jalan Bilal Mahmood 80100 Johor Bahru Malaysia The International is providing the introduction to the Training Module for your
More informationWhat s in the Code Unraveling the Enigma of Legacy Systems. logical solutions. adjusted to the need
What s in the Code Unraveling the Enigma of Legacy Systems logical solutions adjusted to the need Wouldn t it be brilliant to have a logical solution to: IDENTIFY SERVICES: Start with your business analysis,
More informationIncreasing Bid Success Through Integrated Knowledge Management
Increasing Bid Success Through Integrated Knowledge Management CIMdata Commentary Key takeaways: Program success begins in the proposal phase when the focus is on both minimizing risk and defining the
More informationBASIS OF ESTIMATE AS APPLIED FOR THE SOFTWARE SERVICES INDUSTRIES TCM Framework: 7.3 Cost Estimating and Budgeting
AACE International Recommended Practice No. 74R-13 BASIS OF ESTIMATE AS APPLIED FOR THE SOFTWARE SERVICES INDUSTRIES TCM Framework: 7.3 Cost Estimating and Budgeting Rev. Note: As AACE International Recommended
More informationProfessor Hausi A. Müller PhD PEng FCAE Department of Computer Science Faculty of Engineering University of Victoria
Professor Hausi A. Müller PhD PEng FCAE Department of Computer Science Faculty of Engineering University of Victoria www.engr.uvic.ca/~seng321/ courses1.csc.uvic.ca/courses/201/spring/seng/321 SENG 321
More informationTestkings PMP 705q. PMI PMP. Project Management Professional v5
Testkings PMP 705q Number: PMP Passing Score: 800 Time Limit: 120 min File Version: 14.5 PMI PMP Project Management Professional v5 This is my first share of braindumps questions. Very helpful study center
More informationA Proven Approach to Requirements Engineering
Requirements A Proven Approach to Requirements Engineering The Why, What and How of REVEAL November 2013 System Assurance Architectures CONTENT A. Why do we need B. C. REVEAL Overview D. E. A // WHY DO
More informationExam questions- examples
Exam questions- examples The following are examples of exam questions. At the exam there will be similar questions with similar level of difficulty. In the question pool there will be questions related
More informationDevelop software code and to specification
Overview This unit is about developing simpler code and carrying out unit testing to meet the requirements of software products and applications where their business impact and technical complexity is
More informationKnowledge Areas According to the PMBOK edition 5. Chapter 4 - Integration
Knowledge Areas According to the PMBOK edition 5 Chapter 4 - Integration 4.1 - Develop Project Charter Process Project statement of work Expert Judgment Project charter Business case Facilitation techniques
More informationCompiled by Rajan Humagai
Compiled by Rajan Humagai www.pavementengineering.com.au Project Processes Inputs, Tools & Techniques and Outputs. (Based on PMBOK 5 th Edition) 1. Project Integration 1. Develop 1. Project Statement Of
More informationDesign to Cost Updated on with Audiences Responses on 25 June 2010
Design to Cost Updated on with Audiences Responses on 25 June 2010 With five-minute perspectives from Andrew Langridge Linda Newnes Philip Wardle Steve Wiseall and the opportunity for contributions from
More informationTest Estimation Seeing the Future of Your Test Effort
Test Estimation Seeing the Future of Your Test Effort How Long Will Testing Take What makes an estimate a good one? Accurately predicts and guides the project s future Realistic: All tasks included, accurately
More informationLife Cycle Cost Estimate (LCCE)
Life Cycle Cost Estimate (LCCE) Assessments 2013 ICEAA Annual Conference New Orleans, Louisiana June 17-21, 2013 Casey D. Trail Colleen Craig David Brown Motivation A particular program support and cost
More informationEstimating Duration and Cost. CS 390 Lecture 26 Chapter 9: Planning and Estimating. Planning and the Software Process
CS 390 Lecture 26 Chapter 9: Planning and Estimating Before starting to build software, it is essential to plan the entire development effort in detail Planning continues during development and then postdelivery
More informationS3. Step 3 Develop Roadmap
S3. Step 3 Develop Roadmap PART OF IT STRATEGY TOOLIKIT VERSION 0.5 MAY 2007 1 TABLE OF CONTENTS S3-1. DETERMINE PRIORITIES... 3 S3-1.1 ASSESS DEPENDENCIES... 3 S3-1.2 PRIORITISE BUILDING BLOCKS... 3 S3-1.3
More informationCOSYSMO-IP COnstructive SYStems Engineering Cost Model Information Processing. Headed in a new direction
COSYSMO-IP COnstructive SYStems Engineering Cost Model Information Processing Headed in a new direction Dr. Barry Boehm Ricardo Valerdi Gary Thomas Don Reifer October 24, 2002 Outline Workshop Objectives
More informationPMP Exam Prep Study Group Input-Output-Tools #3a
PMP Exam Prep Study Group Input-Output-Tools #3a Presented by Project Masters Inc. *Throughout this presentation, we reference and recognize the following trademarks, service marks, and copyrights of the
More informationInitiation Group Process. Planning Group Process
Initiation Group Process Develop Project Charter Project statement of work Expert judgment Project charter Business case Contract (if third party project) EEF: government/industry standards, organizational
More informationFigure 1 Function Point items and project category weightings
Software measurement There are two significant approaches to measurement that project managers need to be familiar with. These are Function Point Analysis (Albrecht, 1979) and COCOMO (Boehm, 1981). 1.
More informationPerformance modeling of interacting humanmachine distributed processes:
Performance modeling of interacting humanmachine distributed processes: Building a Simulation Model to Characterize Interacting Workflows and to Explore New Workflow Alternatives Janet E. Wedgwood (PI)
More informationConcepts of Project Management. All projects have followings.
Concepts of Project Management All projects have followings. An overall goal A project manager Individual tasks to be performed Timing for those tasks to be completed (such as three hours, three days,
More informationM3 Playbook Guidance. 1.1 Establish Initial Customer PMO and Processes. Human Resources (HR)/Staffing Plan
M3 Playbook Guidance Phase 1: Readiness This guidance is intended for use by organizations to confirm and validate that their plans are comprehensive and have adequate level of detail for proper migration
More informationProject Plan. Co-op Evaluation System. Senior Project Team Members: Tyler Geery Maddison Hickson Casey Klimkowsky Emma Nelson
Project Plan Co-op Evaluation System Senior Project 2014-2015 Team Members: Tyler Geery Maddison Hickson Casey Klimkowsky Emma Nelson Faculty Coach: Samuel Malachowsky Project Sponsors: Jim Bondi (OCECS)
More informationProject Management Framework
Project Management Framework What s Project? - Why Project? What s Project Management? - Why Project Management? What s Project Management Professionals? - Why Project Management Professionals? Project
More information