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-engineering-blog/garmus-function-point-analysis This is a must-have book for anyone who is seriously interested in counting IFPUG FPA and does not have access to official IFPUG counting practices manual. No publisher mochodek metrics effort estimation review function point analysis 2010-09-04T11:48:56Z Blog Entry http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucp The Use Case Points (UCP) method, proposed by Gustav Karner can be used to estimate effort early in the project life-cycle, with relatively low cost. It is based on two main inputs which are actors complexity, measured based on the interface actor uses to communicate with the system; and use-case complexity measured in the number of so-called transactions in use-case scenarios. Here, I would like to present you basic information about the original method proposed by Karner. No publisher mochodek effort estimation use case points metrics use cases use-case transaction 2010-09-01T10:12:30Z Blog Entry http://se.cs.put.poznan.pl/knowledge-base/software-projects-database/use-cases-database-ucdb/use-cases-database-ucdb The goal of UCDB is to collect use-case-based requirements specification from real software projects. No publisher mochodek metrics benchmark use cases 2009-12-09T07:28:47Z Rich document http://se.cs.put.poznan.pl/publications/alchimowicz-2008 In the paper an approach to developing a use-cases benchmark is presented. The benchmark itself is a referential use-case-based requirements specification, which has a typical profile observed in real projects. To obtain this profile an extensive analysis of 432 use cases coming from 11 projects was performed. Because the developed specification represents those found in real projects, it might be used in order to present, test, and verify methods and tools for use-case analysis. This is especially important because industrial specifications are in most cases confident, and they might not be used by researchers who would like to replicate studies performed by their colleagues. No publisher mochodek metrics requirements engineering benchmark use cases 2011-12-28T11:22:07Z Inproceedings Reference