http://se.cs.put.poznan.pl These are the search results for the query, showing results 1 to 5. http://se.cs.put.poznan.pl/knowledge-base/software-projects-database/use-case-based-effort-estimation/use-case-based-effort-estimation-database-uceedb The goal of UCEEDB is to collect use-case-based requirements specification and actual effort from real software projects. It enables calibration of effort estimation methods that relay on use-case-based functional size measurement (FSM), such as Use Case Points, Transactions, and TTPoints. No publisher mochodek effort estimation use case points ttpoints benchmark metrics use-case transaction 2011-04-06T17:27:11Z Rich document http://se.cs.put.poznan.pl/knowledge-base/software-projects-database/use-case-based-effort-estimation This database provides data required to estimate effort based on use cases (Use Case Points, Transactions, TTPoints etc.) No publisher mochodek use case points ttpoints use-case transaction use cases 2011-01-11T16:15:07Z Folder http://se.cs.put.poznan.pl/publications/mochodek2010ucp Context: The Use Case Points (UCP) method can be used to estimate software development effort based on a use-case model and two sets of adjustment factors relating to the environmental and technical complexity of a project. The question arises whether all of these components are important from the effort estimation point of view. Objective: This paper investigates the construction of UCP in order to find possible ways of simplifying it. Method: The cross-validation procedure was used to compare the accuracy of the different variants of UCP (with and without the investigated simplifications). The analysis was based on data derived from a set of 14 projects for which effort ranged from 277 to 3593 man-hours. In addition, the factor analysis was performed to investigate the possibility of reducing the number of adjustment factors. Results: The two variants of UCP - with and without unadjusted actor weights (UAW) provided similar prediction accuracy. In addition, a minor influence of the adjustment factors on the accuracy of UCP was observed. The results of the factor analysis indicated that the number of adjustment factors could be reduced from 21 to 6 (2 environmental factors and 4 technical complexity factors). Another observation was made that the variants of UCP calculated based on steps were slightly more accurate than the variants calculated based on transactions. Finally, a recently proposed use-case-based size metric TTPoints provided better accuracy than any of the investigated variants of UCP. Conclusion: The observation in this study was that the UCP method could be simplified by rejecting UAW; calculating UCP based on steps instead of transactions; or just counting the total number of steps in use cases. Moreover, two recently proposed use-case-based size metrics Transactions and TTPoints could be used as an alternative to UCP to estimate effort at the early stages of software development. No publisher mochodek effort estimation use case points ttpoints use-case transaction 2015-09-14T11:44:49Z Article Reference http://se.cs.put.poznan.pl/publications/ra4-10 No publisher mochodek ttpoints domain model requirements engineering SRS use cases model 2010-09-13T12:40:07Z Techreport Reference http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/enhancing-use-case-based-effort-estimation-with-transaction-types Recently we have conducted some research regarding use-case-based effort estimation. Results were presented at CEE-SET'09 conference. If you would like to read how knowledge about use-case transactions semantics can help in estimating effort, go ahead and see the presentation. If you like the idea you can find more information in the paper. No publisher mochodek effort estimation use case points ttpoints requirements engineering use cases use-case transaction 2010-09-04T11:21:15Z Blog Entry