NEtherlands Software Metrics users Association. About NESMA NEderlandse Software Metrieken gebruikers Associatie NEtherlands Software Metrics users Association.

Slides:



Advertisements
Similar presentations
AACEI Contingency Forum Contingency Management
Advertisements

Evolution of Parametric Analysis within Rolls-Royce Purchasing
Best Practices for an Owner Estimating Organization
S Y S T E M S E N G I N E E R I N G.
Software Quality Assurance Plan
© 2011 IBM Corporation Improving Reliability and Making Things Cheaper to Run Tuesday 20th September James Linsell-Fraser, Senior Architect & Client Technical.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
By Collin Smith COBIT Introduction By Collin Smith
1 SYSTEM and MODULE DESIGN Elements and Definitions.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Domain Oriented Modeling, Estimation And Improvement for Aerospace Systems Domains Dan Galorath Copyright 2011 Galorath Incorporated.
© C.Hicks, University of Newcastle WAR/1 Knowledge Management in Capital Goods Companies Dr. Christian Hicks University of Newcastle upon Tyne.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
© The McGraw-Hill Companies, Software Project Management 4th Edition Managing contracts Chapter 10.
The Pricing Decision and Customer Profitability Analysis
SUPPLIER PARTNERSHIP An organization (or customer) purchases its requirements, raw materials, components, and services, from supplier.   Better supplier’s.
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
What is Business Analysis Planning & Monitoring?
Software project management
1 Jon Whitfield Agency CEO Head of Government Internal Audit.
CMMI Course Summary CMMI course Module 9..
S/W Project Management
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
IEEE S2ESC Report1 Software And Systems Engineering Standards Committee (S2ESC) Paul R. Croll S2ESC Sponsor Chair June 2004 Report.
1 Towards a Framework for the Quality Assurance of Practical Skill Ability Akira Kurematsu* Takashi Sakamoto* Yoshito Shubiki** *Accreditation Council.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
1 Phases in Software Development Lecture Software Development Lifecycle Let us review the main steps –Problem Definition –Feasibility Study –Analysis.
ATMOTERM Corp. 4 Langowskiego Street Opole POLAND tel fax DOWNLOAD FREE SOZAT.
Logistics and supply chain strategy planning
Chapter 6 : Software Metrics
The value of benchmarking IT projects Harold van Heeringen Software Cost Engineer, Sogeti Nederland B.V. ISBSG president NESMA board The Russian Managers.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Software Measurement & Metrics
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
Some Sub-Activities within Requirements Engineering 1.Prototyping 2.Requirements Documentation 3.Requirements Validation 4.Requirements Measurements 5.Requirements.
Software Project Management (SPM)
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
Microsoft Operations Framework Morten Lauridsen Engagement Manager Microsoft Consulting Services Morten Lauridsen Engagement Manager.
FEA DRM Management Strategy Presented by : Mary McCaffery, US EPA.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
1) Establish & Identify Scheme 5) Evolve Scheme 4) Review & Modify Scheme Deliverables 3) Operate the Framework 2) Manage Performance Assurance Scheme.
BSBPMG504A Manage Project Costs 7.2 Determine Budget Adapted from PMBOK 4 th Edition InitiationPlanning ExecutionClose Monitor Control The process of aggregating.
Introduction to Software Project Estimation I (Condensed) Barry Schrag Software Engineering Consultant MCSD, MCAD, MCDBA Bellevue.
BSBPMG504A Manage Project Costs Manage Project Costs Project Cost Processes Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG504A.
BSBPMG504A Manage Project Costs 7.1 Estimate Costs Adapted from PMBOK 4 th Edition InitiationPlanning ExecutionClose Monitor Control The process of developing.
BSBPMG503A Manage Project Time 6.4 Estimate Activity Duration The process of approximating the number of work periods needed to complete individual activities.
Systems Development Life Cycle
11 i Upgrade: Is an Assessment Useful for Your Company? By: Bernard Doyle, Applications Software Technology Corp. Marie Klein, Information Resources Inc.
Upgrade PO M. Tyndel, MIWG Review plans p1 Nov 1 st, CERN Module integration Review – Decision process  Information will be gathered for each concept.
CIS 4251 / CIS 5930 SOFTWARE DEVELOPMENT Fall 1999 Sept. 1, 1999 Marge Holtsinger.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Contract management 1. Acquiring software from external supplier This could be: a bespoke system - created specially for the customer off-the-shelf -
Job offer IT Infrastructure Specialist We are currently looking for an IT infrastructure specialist in order to respond to one key-account customer demand.
ERM and Information Risks July 2013 Advisory. 1 © KPMG, a partnership established under Ghanaian law and a member firm of the KPMG network of independent.
Diploma in Procurement & Supply
Software Development Module Code: CST 240 Chapter 6: Software Maintenance Al Khawarizmi International College, AL AIN, U.A.E Lecturer: Karamath Ateeq.
Distinguishing “BEST ESTIMATES” from “best estimates”
7.3 Determine Budget The process of aggregating the estimated costs of individual activities or work packages in order to establish an authorised cost.
SUPPLIER PARTNERSHIP An organization (or customer) purchases its requirements, raw materials, components, and services, from supplier.   Better supplier’s.
How to Run a Successful RFP
Statistical Analysis Based Service Catalogue
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
SUBMISSION TITLE Raghu K T – Director Capgemini.
Introduction to Software Testing
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Cost Estimating Best Practices
Chapter 26 Estimation for Software Projects.
Software cost estimation finally Becoming a real profession !
Presentation transcript:

NEtherlands Software Metrics users Association

About NESMA NEderlandse Software Metrieken gebruikers Associatie NEtherlands Software Metrics users Association from 1995 Started in 1989 as NEFPUG NEderlandse FunctiePUnt Gebruikersgroep NEtherlands Function Point Users Group Not-for-profit Run by volunteers Managed by an ‘elected’ board Organisation structure: association Registered: Chamber of Commerce, Amsterdam

NESMA members (2010) 83 Corporate Members

Mission Improving the predictability of the cost of the delivery of and the maintenance of software Making the predictability objective by means of unambiguous measurement data Offering a set of guidelines to both customer and supplier to get to an agreement on the predictability Providing an independent platform to share knowledge related to the predictability

Strategy NESMA connects parties that are recognised as knowledgeable within the domain of IT cost engineering NESMA connects respected knowledge providers with the IT market NESMA has a voice in organisations supporting decision making in IT NESMA develops, when necessary, own standards to increase the measurability of IT (solutions)

The NESMA playing field NESMA has her initial base on the cost-drivers Her contribution radiates to the four other areas

Cost-drivers Knowledge holder of: Network : Size of the functionality of software Size of the maintenance of software Product Non-Functional Process Quality Technology People COSMIC IFPUG MAIN SIG SWEBOK SPIder ASL/BISL Knowledge development:

Cost Estimation Relations Knowledge holder: Network: Which cost-drivers are suited as input for the calculation of cost or effort for the realisation and the maintenance of software AACE / DACE ICEAA CEBoK Universities / Research Fraunhofer IESE

Estimation Knowledge development : Network: Which methods / models are useful to produce realistic estimates for the delivery and the maintenance of software AACE / DACE Conferences: IWSM SMEF IEEE Tool-vendors Galorath PRICE QSM Cost Xpert SPR

Historical data Knowledge holder: Network: Which organisations do have data about the relevant cost- drivers Benchmarkers Gartner ISBSG Tool-vendors Galorath PRICE QSM Cost Xpert SPR End users

Control / Evaluation Knowledge development: Network: Which software metrics are most suited to control or evaluate projects for the delivery and the maintenance of software ISBSG PMI SIG

A practical example Collaboration AACE / DACE – MAIN Social Media LinkedIn Volunteers NESMA Working Group Product Basis of Estimate Type Best Practice

About A not-for-profit organisation Internationally oriented Recommended Practices a.o. 17R-97: Cost Estimate Classification System 34R-05: Basis of Estimate 40R-08: Contingency Estimating: General Principles 42R-08: Risk Analysis and Contingency Determination Using Parametric Estimating Certification a.o. Certified Cost Consultant™ (CCC™) Certified Cost Engineer™ (CCE™) Certified Estimating Professional™ (CEP™)

Simplified Estimation Model hours (& money) measures risk analysis risks consequences performance size gross hours influences

Size Basis of Estimate Quantity Metrics: excavation and backfill quantities, concrete volumes, piping quantities,... These may be organized by facilities, process train or manufacturing unit. Basis of Estimate – Software Services Requirements: number of use cases, number of backlog items,... Functional size: …Function points Measurement methods: IFPUG, NESMA, COSMIC, FiSMA, … Technical size: (source) lines of code, number of interfaces, modules, … Service size: number of incidents, tickets, users, locations, … These may include expected error range, level of accuracy and method of ‘measuring’ (e.g. “Backfired”, detailed)

PURPOSE GUIDELINES Software Development, Maintenance & Support, Infrastructure RECOMMENDED PRACTICE AACE, MAIN, NESMA Estimation purpose Engagement Scope Description Estimating methodology (FP, expert, etc.) Estimate Classification (1,2,3,4,5) Design Basis (Components lists, units, etc.) Sizing Basis Requirements Functional technical Effort Basis delivery constraints, service levels Planning Basis Working time standby Cost Basis methods and sources, units Assumptions internal, external Allowances Not in the Basis Exclusions No costs included for… Exceptions anomalies or variances on standard Risks and Opportunities assumptions Containments cost elements for mitigation Contingencies Uncertainty, unforeseeable elements Management Reserve changes in scope, effort Reconciliation Changes to previous estimation Benchmarking Comparisons to similar engagements Estimate Quality Assurance Reviews Attachments Level of detail Stage, Deal size/type, fixed price/TM Attachments Basis of Estimate

Mapping Sizing Basis Requirements Functional technical Effort Basis delivery constraints, service levels Planning Basis Working time standby Cost Basis methods and sources, units Benchmarking Comparisons to similar engagements

In Practice

PURPOSE GUIDELINES Software Development, Maintenance & Support, Infrastructure RECOMMENDED PRACTICE AACE, MAIN, NESMA Estimation purpose Engagement Scope Description Estimating methodology (FP, expert, etc.) Estimate Classification (1,2,3,4,5) Design Basis (Components lists, units, etc.) Sizing Basis Requirements Functional technical Effort Basis delivery constraints, service levels Planning Basis Working time standby Cost Basis methods and sources, units Assumptions internal, external Allowances Not in the Basis Exclusions No costs included for… Exceptions anomalies or variances on standard Risks and Opportunities assumptions Containments cost elements for mitigation Contingencies Uncertainty, unforeseeable elements Management Reserve changes in scope, effort Reconciliation Changes to previous estimation Benchmarking Comparisons to similar engagements Estimate Quality Assurance Reviews Attachments Level of detail Stage, Deal size/type, fixed price/TM Attachments H A L na L A H Good Poor

NESMA Netherlands Software Metrics users Association Postbus BB NIJKERK Telephone+31 (0) fax +31 (0)