http://www.se.cs.put.poznan.pl These are the search results for the query, showing results 1 to 7. http://www.se.cs.put.poznan.pl/publications/ochodek2011ist Context: The concept of transactions is used in Use Case Points (UCP), and in many other functional size measurement methods, to capture the smallest unit of functionality that should be considered while measuring the size of a system. Unfortunately, in the case of the UCP method at least four methods for use-case transaction identification have been proposed so far. The di ff erent approaches to transaction identification and di ffi culties related to the analysis of requirements expressed in natural language can lead to problems in the reliability of functional size measurement. Objective: The goal of this study was to evaluate reliability of transaction identification in use cases (with the methods mentioned in the literature), analyze their weaknesses, and propose some means for their improvement. Method: A controlled experiment on a group of 120 students was performed to investigate if the methods for transaction identification, known from the literature, provide similar results. In addition, a qualitative analysis of the experiment data was performed to investigate the potential problems related to transaction identification in use cases. During the experiment a use-case benchmark specification was used. The automatic methods for transaction identifi- cation, proposed in the paper have been validated using the same benchmark by comparing the outcomes provided by these methods with on-average number of transactions identified by the participants of the experiment. Results: A significant di ff erence in the median number of transactions was observed between groups using di ff erent methods of transaction identification. The Kruskal-Wallis test was performed with the significance level α set to 0.05 and followed by the post-hoc analysis performed according to the procedure proposed by Conover. Also a large intra- method variability was observed. The ratios between the maximum and minimum number of transactions identified by the participants using the same method were equal to 1.96, 3.83, 2.03, and 2.21. The proposed automatic methods for transaction identification provided results consistent with those provided by the participants of the experiment and functional measurement experts. The relative error between the number of transaction identified by the tool and on-average number of transactions identified by the participants of the experiment ranged from 3% to 7%. Conclusions: Human-performed transaction identification is error prone and quite subjective. Its reliability can be improved by automating the process with the use of natural language processing techniques. No publisher mochodek functional size measurement use case points use-case transaction natural language processing 2015-09-15T20:32:34Z Article Reference http://www.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://www.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://www.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://www.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://www.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 http://www.se.cs.put.poznan.pl/publications/ochodek-2008 Since the early 90's of the previous century, use cases have became informal industry standard for presenting functional requirements. The rapid popularity growth stimulated many different approaches for their presentation and writing styles. Unfortunately, this variability makes automatic processing of use cases very difficult. This problem might be mitigated by the use of transaction concept, which is defined as an atomic part of the use case scenario. In this paper we present approach to the automatic transaction discovery in the textual use cases, through the NLP analysis. The proposed solution was implemented as a prototype tool UCTD and preliminarily verified in a case study.  No publisher mochodek effort estimation use case points requirements engineering natural language processing use cases use-case transaction 2009-09-08T06:25:23Z Inproceedings Reference