1 / 20

More than just points

More than just points. NEtherlands Software Metrics users Association. About NESMA. NEderlandse Software Metrieken gebruikers Associatie NEtherlands Software Metrics users Association from 1995

berg
Download Presentation

More than just points

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. More thanjustpoints NEtherlands Software Metrics users Association

  2. About NESMA • NEderlandse Software Metrieken gebruikers AssociatieNEtherlands Software Metrics users Associationfrom 1995 • Started in 1989 as NEFPUGNEderlandse FunctiePUnt GebruikersgroepNEtherlands Function Point Users Group • Not-for-profit • Run by volunteers • Managed by an ‘elected’ board • Organisation structure: associationRegistered: Chamber of Commerce, Amsterdam

  3. NESMA members (2010) • 83 Corporate Members

  4. 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

  5. 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 standardsto increase the measurability of IT (solutions)

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

  7. 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:

  8. 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 • ICEAACEBoK • Universities / Research • Fraunhofer IESE

  9. 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

  10. 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

  11. 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

  12. A practical example • CollaborationAACE / DACE – MAIN • Social MediaLinkedIn • VolunteersNESMA Working Group • ProductBasis of Estimate • TypeBest Practice

  13. About • A not-for-profit organisation • Internationally oriented • Recommended Practices a.o.17R-97: Cost Estimate Classification System34R-05: Basis of Estimate40R-08: Contingency Estimating: General Principles42R-08: Risk Analysis and Contingency Determination Using Parametric Estimating • Certification a.o.Certified Cost Consultant™ (CCC™)Certified Cost Engineer™ (CCE™)Certified Estimating Professional™ (CEP™) • www.aacei.org

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

  15. 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 pointsMeasurement 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)

  16. Purpose guidelines Software Development, Maintenance & Support, Infrastructure recommended practice Estimation purpose Engagement Scope Description Estimating methodology (FP, expert, etc.) Estimate Classification (1,2,3,4,5) Level of detail Stage, Deal size/type, fixed price/TM 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 Basis of Estimate Allowances Not in the Basis Assumptions internal, external 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 Attachments Attachments Attachments AACE , MAIN, Nesma

  17. 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

  18. In Practice

  19. Purpose guidelines Software Development, Maintenance & Support, Infrastructure recommended practice Estimation purpose Engagement Scope Description Estimating methodology (FP, expert, etc.) Estimate Classification (1,2,3,4,5) Level of detail Stage, Deal size/type, fixed price/TM 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 Good H A L H L na A Allowances Not in the Basis Assumptions internal, external 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 Attachments Attachments Attachments Poor AACE , MAIN, Nesma

  20. NESMA Netherlands Software Metrics users Association Postbus 1058 3860 BB NIJKERK Telephone +31 (0)33 - 2473477 fax +31 (0)33 - 2460470 office@nesma.nl www.nesma.nl

More Related