To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Analysis of Extra Large Projects
/in project controlWe will look at the XL projects in the ISBSG database. These are projects with a functional size that is greater than 3000 Nesma or IFPUG function Points. The following characteristics will be investigated: delivery rate and speed, projects per industry sector, project duration based on programming language, year of completion.
How to Use ISBSG Data for Software Project Estimation
/in estimationThis short paper discusses how ISBSG data is used by leading industry experts, including certified Software Cost Estimators, to estimate the cost of software development projects. The paper discusses the difficulties and challenges inherent in software project cost estimation. It also explores how estimation has evolved in Agile contexts. A detailed example demonstrates the steps taken to make a cost estimation for a sample project.
BIG Data for Software Engineering Estimation
/in estimationBig Data in software engineering estimation, can be a valuable tool to improve the accuracy, efficiency, and transparency of the estimation process. However, it is important to be aware of the challenges associated with using big data before adopting this approach.
Concept of Operation
/in estimationEstimating the cost and schedule of custom software development from preliminary requirements or a Concept of Operations (ConOps) document can be challenging. Software size and productivity are major drivers of software development costs. This presentation outlines a streamlined six-step process to develop a data-founded and defensible cost and schedule ROM estimate from high-level requirements/ConOps documents. A sample ConOps case study will be used to demonstrate the six-step process.
Software Cost Estimation
/in estimationSoftware development projects often fail to meet expectations, exceed budgets, and overrun schedules. Often, the cause is bad estimation practices.
Nesma and the International Cost Estimation and Analysis Association (ICEAA) developed the Cost Estimation Body of Knowledge for Software (CEBoK-S).
This presentation addresses the industry’s main issues, CEBoK-S and aims to solve these issues. ISBSG data is used to estimate software projects using functional size and relevant historic data.
Prioritizing Requirements
/in productivityWe present the methods that focus solutions to the “Next Release Problem” for agile-driven developments. This includes: new algorithm proposals and novel techniques that model how the software requirements interact .
Non-Functional Requirements
/in estimationNon-Functional Requirements are a challenging concept. How can NFR data be gathered and used to improve effort/cost estimations.
Estimating Software Costs
/in estimationThe presentation describes capabilities and capability-based planning. Discussed are the challenges in software cost estimation and how capability-based cost estimation models for software differ throughout the life cycle. I conclude with a summary methodology to develop a capability-based cost estimation for software, which is to define capability groups with similar software functions and associated effort ranges.
Agile Metrics and the Impact of Team Size
/in agileA study of agile projects in the ISBSG dataset that included metrics such as the number of sprints/iterations and sprint/iteration length was done. This resulted in a normalized velocity metric (FPs Per Sprint Week/Person) that could be used to for benchmarking purposes. This metric, along with team size could be used to examine the productivity changes with different team sizes.
Analysis of Practical Software Project Estimation
/in estimationLearn how Project Delivery Rate can be estimated using software and team sizes, using the ISBSG book, “Practical Software Project Estimation”.
Monitoring Agile Development
/in agileCreate new functionality, enhance existing functionality, remove technical debt, compensate respective effort in a controlled, measurable way.
Analysis of Project Size per Year
/in sizingThis short paper examines whether there have been more New Development or Enhancement type projects submitted to the ISBSG Repository. It investigates whether the median project size for these projects has increased or decreased over time.
Analysis of Maintenance and Support Productivity
/in maintenance and support, productivityThe short paper analyses the effort spent on general and specific software maintenance and support activities.
Benchmark Report
/in benchmarkingHow would you like to have your project’s productivity benchmarked against the ISBSG Repository? This short paper explains how you can receive a free benchmark report, when you submit project data to the ISBSG repository.
Analysis of Application Groups
/in productivityThis short paper compares the productivity of projects that have different application types, from the ISBSG Repository. The application types are: Business Applications, Real-Time Applications, Mathematically-Intensive Application and Infrastructure Software.