Big 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.
Estimating 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 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.
We 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 are a challenging concept. How can NFR data be gathered and used to improve effort/cost estimations.
The 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.
A 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.
Create new functionality, enhance existing functionality, remove technical debt, compensate respective effort in a controlled, measurable way.
Accurate estimations are essential for the success of your project.
Determine the factors that impact your project’s productivity.
Learn about productivity, estimation and team size in Agile.
Compare your project’s estimates to the best in the software industry.
A significant proportion of your IT systems’ budget may be spent on maintenance and support.
Learn about the importance of software size, as an important factor in estimating cost.
Discover how customer satisfaction, cost-effectiveness and quality can be maintained with outsourcing.
Learn about the factors that affect the schedule and budget of your project.
(ABN 16 081 497 636)
Ground Floor
470 St Kilda Road
Melbourne
Victoria 3004
Australia
Email: staff@isbsg.org
Find out about the latest news and events in the world of software metrics.
© Copyright – ISBSG 2024
