NESMA - More than just points

796 views
675 views

Published on

NESMA is most commonly known as the owner of the Dutch FPA functional size measurement standard ISO/IEC 24570. In this presentation we show that NESMA is more than just function points and we present our vision for software metrics in 2020.

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
796
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
12
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

NESMA - More than just points

  1. 1. NEtherlands Software Metrics users Association
  2. 2. 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
  3. 3. NESMA members (2010)  83 Corporate Members IT Services Large (14) Tools (8) Industry (4) IT Services Small (16) Financial (11) Education (2) 5% 2% Consultancy (15) Governement (13) 17% 16% 19% 13% 10% 18%
  4. 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. 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 standards to increase the measurability of IT (solutions)
  6. 6. The NESMA playing field  NESMA has her initial base on the cost-drivers  Her contribution radiates to the four other areas
  7. 7. Cost-drivers Knowledge holder of: Network :  Size of the functionality of  COSMIC software  Size of the maintenance of software  IFPUG  MAIN Knowledge development:  Product Non-Functional  Process  Quality  Technology  People  SIG  SWEBOK  SPIder  ASL/BISL
  8. 8. Cost Estimation Relations Knowledge holder: Network:  Which cost-drivers are suited  AACE / DACE as input for the calculation of cost or effort for the realisation and the maintenance of software  ICEAA CEBoK  Universities / Research  Fraunhofer IESE
  9. 9. Estimation Knowledge development : Network:  Which methods / models are  AACE / DACE useful to produce realistic estimates for the delivery and the maintenance of software  Conferences:  IWSM  SMEF  IEEE  Tool-vendors  Galorath  PRICE  QSM  Cost Xpert  SPR
  10. 10. Historical data Knowledge holder: Network:  Which organisations do have  Benchmarkers  Gartner  ISBSG  Tool-vendors  Galorath  PRICE  QSM  Cost Xpert  SPR  End users data about the relevant costdrivers
  11. 11. Control / Evaluation Knowledge development: Network:  Which software metrics are  ISBSG most suited to control or evaluate projects for the delivery and the maintenance of software  PMI  SIG
  12. 12. A practical example  Collaboration AACE / DACE – MAIN  Social Media LinkedIn  Volunteers NESMA Working Group  Product Basis of Estimate  Type Best Practice
  13. 13. 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™)  www.aacei.org
  14. 14. Simplified Estimation Model size risk analysis performance risks gross hours measures influences consequences hours (& money)
  15. 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 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)
  16. 16. Estimation purpose RECOMMENDED PRACTICE Basis of Estimate PURPOSE GUIDELINES Software Development, Maintenance & Support, Infrastructure 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 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. 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. 18. In Practice
  19. 19. PURPOSE GUIDELINES Software Development, Maintenance & Support, Infrastructure Good H A L na L A H Poor 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 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
  20. 20. NESMA Netherlands Software Metrics users Association Postbus 1058 3860 BB NIJKERK Telephone fax +31 (0)33 - 2473477 +31 (0)33 - 2460470 office@nesma.nl www.nesma.nl

×