Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases

Software Cost Estimation With Use Case Points – Use Case Analysis

Posted on:

Software cost estimation with use case points is primarily driven by use case analysis. You take into account environmental and technical factors, but they are ultimately only modifiers of the analysis done on the use cases. Each use case contributes to the project cost estimate, and use cases of varying complexity have a varying influence on the cost estimate.

Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases

Software Cost Estimation With Use Case Points – Technical Factors

Posted on:

The technical factors are the first thing you assess when doing a use case point analysis. Technical factors describe the expectations of the users for the delivered software. Generally, it is an assessment of non-functional requirements. There are 13 technical factors that you have to analyze. Read on to see how.

Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases

Software Cost Estimation With Use Case Points – Introduction

Posted on:

Estimating the amount of work required to deliver software is hard. Estimating the amount of work in the very early stages of a project is even harder. A method was developed to estimate the amount of work required by analyzing what the system will allow its users to do. That method is called Estimating With Use Case Points. This article is an introduction to the concept.

Business Analysis / Prioritization / Product Management / Requirements / ROI

Prioritization With ROI and Utility

Posted on:

Prioritization with ROI is generally thought of as a quantitative analysis. For hard ROI, that is true. For soft ROI, it is anything but true. You have to make a prediction of the utility of the requirement or feature. That predicted utility is based on our expected utility, which is based on your past experiences. Your past experiences are reflected in remembered utility, which is a function of experienced utility. How can you know with certainty, and use that to prioritize requirements or features?