Iwsm2014 importance of benchmarking (john ogilvie & harold van heeringen)Nesma
The document discusses three cases where the International Software Benchmarking Standards Group (ISBSG) database was used to provide benchmarks and industry data for software project estimation, competitive analysis, and supplier performance measurement.
In the first case, a telecom company used ISBSG data to perform a reality check on an expert estimate for a new software project, which found the estimate to be optimistic. In the second case, a software company analyzed ISBSG data to assess the competitiveness of its bidding process. In the third case, an organization set productivity targets for an outsourced supplier based on ISBSG benchmarks.
Iwsm2014 manage the automotive embedded software (alexandre oriou)Nesma
Renault has adopted the COSMIC method to measure the size of embedded software specified using Simulink. An automated tool has been developed to apply COSMIC measurements to Simulink models. COSMIC measurements are used to estimate development costs and schedules, evaluate supplier productivity, estimate memory requirements, and determine the value of software functions. Renault aims to further integrate COSMIC measures into software quality dashboards to improve project monitoring.
Google Glass is an augmented reality smart glasses prototype developed by Google that displays information in a smartphone-like hands-free format. The device connects to the internet using Wi-Fi networks and shares a similar technical specification to smartphones using Bluetooth and having 5MP camera. Google launched an Explorer program in 2013 that allowed participants to purchase Glass for $1,500 and provide feedback to help shape the future development of the product.
This document summarizes a case study conducted by Jean-François Dumas-Monette and Sylvie Trudel on measuring requirements engineering quality in an agile context using functional size measurement. The researchers conducted measurements on 10 projects from a software company using agile development practices. They found that projects with higher quality requirements had lower development and measurement efforts. The study also identified common defects in requirements that could be addressed to improve quality. Recommendations included training analysts in measurement and formalizing requirements and data modeling practices.
As mentioned on the ISBSG workshop in El Segundo and the MAIN track in the IWSM in Assisi, the Basis of Estimate - Software Services is ready for review.
The document is intended to set a best practice for structuring an Estimate for Software Services.
You are invited to review it.
If interested you're allowed to forward the attached document to reviewers.
Comment by the reviewers can be mailed directly to me: Ton Dekkers ton.dekkers@nesma.nl
The due date for comments is set to Sunday, December 16 2012.
Next step will be incorporating the useful suggestions and preparing a version for the 3rd and final review within AACE.
Iwsm2014 understanding functional reuse of erp (maya daneva) - public releaseNesma
The document summarizes a study on the level of functional reuse achieved by three telecom companies that implemented SAP ERP systems. The study found that:
1) Reuse is possible up to 80% for some modules, but for others the level of reuse varied widely between companies.
2) Reuse was measured according to four levels: from fully reused without changes (Level 3) to not reused at all (Level 0).
3) Results for individual ERP modules like materials management showed reuse levels ranging from 30-80% depending on the business process and company.
Personality and performance in software engineering personnelNesma
The document discusses research into the cognitive and personality factors that influence a person's ability to accurately estimate project costs and timelines. It describes previous studies on the use of case-based reasoning tools and expert judgement to improve estimates. Personality measures including the Big 5 and MBTI are examined for 5 project managers, and their ability to predict effort for a sample project is analyzed along with their scores on grit, affect, metacognition, problem solving and emotional intelligence.
Iwsm2014 importance of benchmarking (john ogilvie & harold van heeringen)Nesma
The document discusses three cases where the International Software Benchmarking Standards Group (ISBSG) database was used to provide benchmarks and industry data for software project estimation, competitive analysis, and supplier performance measurement.
In the first case, a telecom company used ISBSG data to perform a reality check on an expert estimate for a new software project, which found the estimate to be optimistic. In the second case, a software company analyzed ISBSG data to assess the competitiveness of its bidding process. In the third case, an organization set productivity targets for an outsourced supplier based on ISBSG benchmarks.
Iwsm2014 manage the automotive embedded software (alexandre oriou)Nesma
Renault has adopted the COSMIC method to measure the size of embedded software specified using Simulink. An automated tool has been developed to apply COSMIC measurements to Simulink models. COSMIC measurements are used to estimate development costs and schedules, evaluate supplier productivity, estimate memory requirements, and determine the value of software functions. Renault aims to further integrate COSMIC measures into software quality dashboards to improve project monitoring.
Google Glass is an augmented reality smart glasses prototype developed by Google that displays information in a smartphone-like hands-free format. The device connects to the internet using Wi-Fi networks and shares a similar technical specification to smartphones using Bluetooth and having 5MP camera. Google launched an Explorer program in 2013 that allowed participants to purchase Glass for $1,500 and provide feedback to help shape the future development of the product.
This document summarizes a case study conducted by Jean-François Dumas-Monette and Sylvie Trudel on measuring requirements engineering quality in an agile context using functional size measurement. The researchers conducted measurements on 10 projects from a software company using agile development practices. They found that projects with higher quality requirements had lower development and measurement efforts. The study also identified common defects in requirements that could be addressed to improve quality. Recommendations included training analysts in measurement and formalizing requirements and data modeling practices.
As mentioned on the ISBSG workshop in El Segundo and the MAIN track in the IWSM in Assisi, the Basis of Estimate - Software Services is ready for review.
The document is intended to set a best practice for structuring an Estimate for Software Services.
You are invited to review it.
If interested you're allowed to forward the attached document to reviewers.
Comment by the reviewers can be mailed directly to me: Ton Dekkers ton.dekkers@nesma.nl
The due date for comments is set to Sunday, December 16 2012.
Next step will be incorporating the useful suggestions and preparing a version for the 3rd and final review within AACE.
Iwsm2014 understanding functional reuse of erp (maya daneva) - public releaseNesma
The document summarizes a study on the level of functional reuse achieved by three telecom companies that implemented SAP ERP systems. The study found that:
1) Reuse is possible up to 80% for some modules, but for others the level of reuse varied widely between companies.
2) Reuse was measured according to four levels: from fully reused without changes (Level 3) to not reused at all (Level 0).
3) Results for individual ERP modules like materials management showed reuse levels ranging from 30-80% depending on the business process and company.
Personality and performance in software engineering personnelNesma
The document discusses research into the cognitive and personality factors that influence a person's ability to accurately estimate project costs and timelines. It describes previous studies on the use of case-based reasoning tools and expert judgement to improve estimates. Personality measures including the Big 5 and MBTI are examined for 5 project managers, and their ability to predict effort for a sample project is analyzed along with their scores on grit, affect, metacognition, problem solving and emotional intelligence.
IT estimation must make a move from size estimation that is translated to cost to an integral cost estimation practice. This is supported by the Basis of Estimate, a joint standard from NESMA and AACEi. Added is a special welcom for the IWSM 2014 in Rotterdam.
Presentatie van de NESMA voorjaarsconferentie 2012 met daar aan toegevoegd de ideeën voor nieuwe werkgroepen op de vijf aandachtsgebieden die NESMA op het oog heeft voor 2020.
This document presents the results of a systematic mapping study on software product size measurement methods. The study identified 79 different size measurement methods, most of which (86%) measure functional size. Only 19% of methods were novel, while the rest extended or tailored existing approaches. The study found that size measurement is most applicable to data-dominant domains, and future work could focus on tailoring methods for object-oriented development and automated measurement tool development.
The document is an invitation to the IWSM/Mensura 2015 conference to be held from October 5-8 in Krakow, Poland. The conference will take place at the Sheraton Hotel in Krakow and include a banquet in the unique underground Salt Mine in Wieliczka, featuring its beautiful chapel and lake carved entirely out of salt. Attendees are invited to experience the beautiful city of Krakow and visit the historic Salt Mine.
The document discusses a study comparing Agile and waterfall project delivery methods across several metrics. It outlines the study's setup, data collection process from 278 IT projects, and analysis of core metrics like size, duration, effort/cost, and quality. Key findings included Agile projects having shorter duration, higher defects initially but lower over time, and better productivity and time-to-market than waterfall projects, especially for larger projects. Factors contributing to best and worst practices are also examined.
Metrics to improve organisational performance in picturesNesma
The document appears to be an agenda or program for a conference that took place in 2014. It lists several speakers who presented including Rini van Solingen, Ben Roelens, Niels van der Zwan, Niteen Kumar, Arthur Fischer, Cees Kuijpers, Michel Sterling, and Frank Vogelezang who presented on the conference location. It also mentions thanking the speakers, Ton Dekkers, a poster presentation, and a networking buffet and drinks.
Iwsm2014 quantifying long-term evolution of industrial meta-models - a case...Nesma
This document summarizes a case study analyzing the evolution of the AUTOSAR industrial meta-model over 22 releases. Metrics were defined to measure properties like size, length, complexity, coupling and cohesion. The metrics were assessed using the entire meta-model and specific packages. Most metrics were highly correlated. Fan-in and package cohesion were identified as sufficient to quantify meta-model evolution. The authors recommend using these metrics and number of classes to monitor complexity, cohesion, coupling and size in future meta-model releases.
Iwsm2014 evaluating software product quality (ali idri)Nesma
This document summarizes a systematic mapping study of approaches for evaluating software product quality. The study analyzed 57 papers published between 1990 and 2013. It found that most research proposed new evaluation techniques, especially data mining approaches like fuzzy logic and regression. Experiments and case studies were common empirical methods. Future work should focus on evaluating quality characteristics important for mobile applications and using recent quality models like ISO 25010.
Iwsm2014 defining technical risk in software development (vard antinyan)Nesma
This document defines and discusses technical risks in software development. It proposes that technical risks should be defined as the degree of uncertainty regarding the magnitude of difference between the actual solution implemented and the optimal solution. The document outlines research on identifying common technical risks faced by companies and defining risks in a way that supports effective risk assessment and quantification of impacts. Workshops with several companies identified 24 common technical risks. The document also discusses how software metrics can be used to assess technical risks by measuring unwanted consequences and properties of design artifacts.
Wat komt er allemaal bij ketenmonitoring kijken? Wat zijn problemen bij het inrichten, op welke processen moet je je focussen, wat zijn de do´s en de dont´s
Presentatie over de inrichting van de servicedesk voor research data management (RDM) aan de Universiteit van Amsterdam. Kennissessie ondersteuning datamanagement, TU Delft Library, 5 juni 2015.
The Use of Functional Size in the Industry.pdfNesma
In this webinar, the emphasis is on the use of Functional Size in the Industry, and we focus on several use cases where functional size helps organizations to make impactful decisions based on objective metrics and data.
IT estimation must make a move from size estimation that is translated to cost to an integral cost estimation practice. This is supported by the Basis of Estimate, a joint standard from NESMA and AACEi. Added is a special welcom for the IWSM 2014 in Rotterdam.
Presentatie van de NESMA voorjaarsconferentie 2012 met daar aan toegevoegd de ideeën voor nieuwe werkgroepen op de vijf aandachtsgebieden die NESMA op het oog heeft voor 2020.
This document presents the results of a systematic mapping study on software product size measurement methods. The study identified 79 different size measurement methods, most of which (86%) measure functional size. Only 19% of methods were novel, while the rest extended or tailored existing approaches. The study found that size measurement is most applicable to data-dominant domains, and future work could focus on tailoring methods for object-oriented development and automated measurement tool development.
The document is an invitation to the IWSM/Mensura 2015 conference to be held from October 5-8 in Krakow, Poland. The conference will take place at the Sheraton Hotel in Krakow and include a banquet in the unique underground Salt Mine in Wieliczka, featuring its beautiful chapel and lake carved entirely out of salt. Attendees are invited to experience the beautiful city of Krakow and visit the historic Salt Mine.
The document discusses a study comparing Agile and waterfall project delivery methods across several metrics. It outlines the study's setup, data collection process from 278 IT projects, and analysis of core metrics like size, duration, effort/cost, and quality. Key findings included Agile projects having shorter duration, higher defects initially but lower over time, and better productivity and time-to-market than waterfall projects, especially for larger projects. Factors contributing to best and worst practices are also examined.
Metrics to improve organisational performance in picturesNesma
The document appears to be an agenda or program for a conference that took place in 2014. It lists several speakers who presented including Rini van Solingen, Ben Roelens, Niels van der Zwan, Niteen Kumar, Arthur Fischer, Cees Kuijpers, Michel Sterling, and Frank Vogelezang who presented on the conference location. It also mentions thanking the speakers, Ton Dekkers, a poster presentation, and a networking buffet and drinks.
Iwsm2014 quantifying long-term evolution of industrial meta-models - a case...Nesma
This document summarizes a case study analyzing the evolution of the AUTOSAR industrial meta-model over 22 releases. Metrics were defined to measure properties like size, length, complexity, coupling and cohesion. The metrics were assessed using the entire meta-model and specific packages. Most metrics were highly correlated. Fan-in and package cohesion were identified as sufficient to quantify meta-model evolution. The authors recommend using these metrics and number of classes to monitor complexity, cohesion, coupling and size in future meta-model releases.
Iwsm2014 evaluating software product quality (ali idri)Nesma
This document summarizes a systematic mapping study of approaches for evaluating software product quality. The study analyzed 57 papers published between 1990 and 2013. It found that most research proposed new evaluation techniques, especially data mining approaches like fuzzy logic and regression. Experiments and case studies were common empirical methods. Future work should focus on evaluating quality characteristics important for mobile applications and using recent quality models like ISO 25010.
Iwsm2014 defining technical risk in software development (vard antinyan)Nesma
This document defines and discusses technical risks in software development. It proposes that technical risks should be defined as the degree of uncertainty regarding the magnitude of difference between the actual solution implemented and the optimal solution. The document outlines research on identifying common technical risks faced by companies and defining risks in a way that supports effective risk assessment and quantification of impacts. Workshops with several companies identified 24 common technical risks. The document also discusses how software metrics can be used to assess technical risks by measuring unwanted consequences and properties of design artifacts.
Wat komt er allemaal bij ketenmonitoring kijken? Wat zijn problemen bij het inrichten, op welke processen moet je je focussen, wat zijn de do´s en de dont´s
Presentatie over de inrichting van de servicedesk voor research data management (RDM) aan de Universiteit van Amsterdam. Kennissessie ondersteuning datamanagement, TU Delft Library, 5 juni 2015.
The Use of Functional Size in the Industry.pdfNesma
In this webinar, the emphasis is on the use of Functional Size in the Industry, and we focus on several use cases where functional size helps organizations to make impactful decisions based on objective metrics and data.
While traditional performance metrics often measure individual output or adherence to pre-defined plans, measuring performance in agile teams requires a different approach. Agile teams operate in iterative cycles, prioritizing adaptability and learning over rigid goals. So, why do organizations still measure their performance?
By using the right metrics in the right way, organizations can empower their agile teams to thrive and deliver exceptional results.
Software Cost Estimation webinar January 2024.pdfNesma
In this webinar you will learn why Software Cost Estimation is important, what is the Software Cost Estimation Body of Knowledge for Software and the ways you can become a professional certified software cost estimator SCEC!
Nesma event June '23 - How to use objective metrics as a basis for agile cost...Nesma
This document discusses using objective metrics for agile cost estimation and monitoring. It notes that while agile development is challenging to estimate and measure, sizing software using functional points allows for estimation and benchmarking using data. Story points alone do not provide enough information to manage value creation over time. Key metrics like productivity, defects, and where teams spend their effort need to be measured to understand performance. Effort registration is crucial for project control to understand functionality delivered and productivity. Functional size measurement creates reference points to help manage projects.
Nesma event June '23 - Easy Function Sizing - Introduction.pdfNesma
The document introduces a new method called Easy Functional Sizing (EFS) that aims to provide a simpler alternative to the more complex High Level Function Point Analysis method. EFS is designed to be aligned with modern development methods, have fewer debates around function point types, and be easy to learn. It maintains the same level of assessment as High Level FPA but only has 4 pages of definitions and rules organized into 3 components. Initial analysis shows EFS results are comparable to High Level FPA with less than a 2% difference on average. Feedback is requested from reviewers knowledgeable and not knowledgeable in FPA to test if EFS provides enough depth.
The journey of UNISON Cost Engineering in the field of automotive software cost estimation started in 2018. The expectation is that in 2030 the cost of software will be 50% of the total production cost of a car. To help the OEM get a proper understanding of the software development cost they need to use some form of size measurement to compare, challenge and control the cost of software development by the software vendors.
The COSMIC battle between David and Goliath - Paul HusseinNesma
No more exhaustive and emotional discussions on price and deliverables. Predictable prices for projects and changes. No escalating maintenance costs. This can only be done by specifying exactly what you want and outsource it to the right service providers that have the required platform already in place.
Succesful Estimating - It's how you tell the story - Amritpal Singh AgarNesma
Estimating the Cost of something is a profession. But then you have to tell the story about the estimate to whoever needs to hear that story. The success of how you tell the story is determining the success of the cost estimate.
(Increasing) Predictability of large Government ICT Projects - Koos VeefkindNesma
1) The document discusses using Function Point Analysis (FPA) to increase the predictability of large government IT projects.
2) FPA is used to estimate the total development capacity needed and provide periodic estimates of the expected lead time to completion based on measuring function points completed and productivity.
3) Tracking actual function points completed against the initial goal and expected progress allows projects to identify risks and make adjustments to the planning and estimates.
CEBoK for Software Past Present Future - Megan JonesNesma
The Cost Estimation Body of Knowledge for Software is in development for a number of years within ICEAA. First as a section of the general CEBoK, but it will be established as a separate CEBoK-S for Software, since software is becoming very prominent within the cost estimation community.
Agile Development and Agile Cost Estimation - A return to basic principles - ...Nesma
Is there a natural tension between agile development and traditional cost management or do we need to return to basic principles? Even when you are flexible, you still need to make a plan, build an estimate and measure what you have achieved.
Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...Nesma
Agile software development does not always live up to the promises. Especially in the field of IT Cost Management. Without proper estimation and tracking the value cannot be made clear.
Project Succes is a Choice - Joop SchefferlieNesma
Project success is a choice. Don't stop thinking about the best way to do a project, agile or not. Select the best competencies to ensure that the project will be successful.
Deze presentatie beschrijft een praktische implementatie van het gebruik van Nesma functiepunten in Agile deliveries. Deze presentatie is gepresenteerd door Richard Sweer van Infinity tijdens de webinar Afrekenen met functiepunten. Voor meer info: www.nesma.org; conference@nesma.org.
Software sizing as an essential measure past present and future - Dan Galorat...Nesma
The document discusses different methods for software sizing, both historically and currently. It covers lines of code, functional sizes, story points, and more. It also discusses sizing commercial off-the-shelf (COTS) software by considering features, objects, and the required cognition. COTS cognition involves understanding features, referenced and configured tables, and input/output/inquiry services or classes. The percentage of COTS functionality required is also a factor. Overall, the document advocates that there are many viable sizing methods and standards are important, while not dismissing lines of code when appropriate.
2. Ter ere van het 25-jarig bestaan van de NESMA een conferentie in stijl:
• In een van de drukste havens van de wereld
• Op het grootste cruiseschip in Nederland gebouwd
• Twee conferentiezalen en aangrenzende workshopruimtes
• Drie dagen
• Metriekenspecialisten van over de hele wereld
Een conferentie in stijl
3. Het organisatieteam:
• Eric van der Vliet – Linking pin naar bestuur en Rotterdamse zaken
• René Nijland – Sponsoring en financiën
• Frank Vogelezang – Programma en algemeen extern aanspreekpunt
Het uiteindelijke team:
• Program chair – Maya Daneva (UTwente)
• Session chairs / Tijdbewakers (10 – 12 sessies)
• Deurwacht / Pauze tijdbewaking (2 per dag)
• Partner program – Natalia Zolotova
• Administratieve en financiële ondersteuning (MOS / Colette)
4. IWSM in cijfers
FULL PAPERS
country authors submissions
Netherlands 6 5.00
Turkey 7 4.00
Sweden 7 2.00
Canada 5 3.67
Germany 4 2.00
Italy 5 2.50
Indonesia 3 1.00
Japan 3 1.00
Morocco 3 1.17
Austria 2 1.00
France 2 0.67
Spain 2 0.50
Mexico 1 0.50
Poland 1 1.00
Switzerland 1 1.00
15 52 27
SHORT PAPERS
country authors submissions
Netherlands 6 3.00
Germany 2 1.00
Canada 1 0.33
Ecuador 1 0.33
Turkey 1 0.33
16 11 5
WORKSHOPS
country authors submissions
Netherlands 2 2.00
Austria 1 1.00
Brazil 1 1.00
Spain 1 1.00
USA 1 1.00
Canada 1 0.33
Turkey 1 0.33
UK 1 0.33
8 9 7
PROGRAM COMMITTEE
country members
Germany 9
Netherlands 7
Canada 5
United Kingdom 5
Italy 4
United States 4
Turkey 3
Austria 2
Belgium 2
Spain 2
Sweden 2
Brazil 1
Denmark 1
Ecuador 1
Finland 1
France 1
Ireland 1
Japan 1
Morocco 1
Poland 1
Portugal 1
Russian Federation 1
Switzerland 1
Tunisia 1
24 58
6. Keynote sprekers
Functionarissen op strategisch of hoog tactisch (programmamanagement) niveau
die op dinsdagmiddag 7 oktober een presentatie willen geven wat het meetbaar
maken van software (in breedste zin) bijdraagt aan het goed functioneren van de
organisatie of het behalen van doelstellingen.
• Session chairs / Tijdbewakers
• Deurwachten / Pauze tijdbewakers
Aanmelden via info@iwsm-mensura.org
2014.iwsm-mensura.org
Wij zoeken nog:
7. Conferentietarieven
• 3 dagen conferentie en 2 overnachtingen aan boord € 750,00
• 3 dagen alleen conferentie € 600,00
• 1 dag conferentie € 200,00
2014.iwsm-mensura.org
Bezoek de conferentie