Automatic Transactions Identification in Use Cases

Ochodek, Mirosław; Nawrocki, Jerzy

doi:10.1007/978-3-540-85279-7_5

Cited by 24 publications

(23 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The Event meta-class is further extended to include Sender, Receiver, Action, and Argument meta-classes based on the above-mentioned reasons. In addition, following Diev's transaction definition [46] and the transaction model proposed by Ochodek and Nawrocki [56], we enumerated four types of actions relevant from the use case transaction point of view. This is shown through an enumerated metaattribute called action Type in the Action meta-class.…”

Section: Use Case Action Stepsmentioning

confidence: 99%

Extending the UML use case metamodel with behavioral information to facilitate model analysis and interchange

Misbhauddin

Alshayeb

2013

Softw Syst Model

View full text Add to dashboard Cite

Use case diagrams are primary artifacts used for modeling functional requirements. Use case diagrams are part of the Unified Modeling Language (UML) suite of models that has become a de facto standard for modeling object oriented languages. Each model in this suite is described by a metamodel that dictates its syntax and semantics. The use case diagram is considered the most controversial diagram in UML. Practitioners claim that the use case diagram cannot be used as a valuable artifact for requirement analysis. The main reason behind this concern is the lack of behavioral description of a use case depicted within the model. Quite a few extensions to the use case metamodel have been proposed in literature to incorporate behavioral aspect of a use case within the metamodel. All these extensions omit a few important features like generalization and most of them can only be used for model representation and cannot be used for model analysis and evaluation. In this paper, we propose an extension to the UML use case metamodel with use case behavior specification elements. The main objective of the proposed extension is to provide a complete metamodel for use case diagrams which includes representation for all its elements and relationships in a conflict-free manner and one that includes information for model analysis, evaluation, and interchange among modeling tools. In order to include all valuable information related to a use case, a number of use Communicated by Dr. case representation templates were considered for the proposed extension. Simultaneously, to enable the use case models generated based on the proposed metamodel to be used for analysis, pertinent information related to model usage in analysis such as effort estimation, use case scheduling, and use case metrics evaluation were considered from published studies, tools, and paradigms and included within the proposed metamodel.

show abstract

Section: Use Case Action Stepsmentioning

confidence: 99%

Extending the UML use case metamodel with behavioral information to facilitate model analysis and interchange

Misbhauddin

Alshayeb

2013

Softw Syst Model

View full text Add to dashboard Cite

show abstract

“…Authors in (Diev, 2006) and (Anda et al, 2001) worked on adjustment factors, while others in (Anda et al, 2001) and (Arnold and Pedross, 1998) highlighted the discrepancies in designing use case models. Researchers in (Robiolo and Orosco, 2008), (Robiolo et al, 2009) and (Ochodek and Nawrocki, 2008) proposed different size metrics such as transactions, TTPoints and paths, while others (Periyasamy and Ghode, 2009;Wang et al, 2009;Schneider and Winters, 2001;Braz and Vergilio, 2006;Nassif et al, 2011a,b;Mohagheghi et al, 2005;Ochodek et al, 2011) went further to extend the UCP model by providing new complexity weights or by modifying the method used to predict effort.…”

Section: Related Workmentioning

confidence: 99%

Towards an early software estimation using log-linear regression and a multilayer perceptron model

Nassif

Ho²,

Capretz

2013

Journal of Systems and Software

175

160

View full text Add to dashboard Cite

This article appeared in a journal published by Elsevier. The attached copy is furnished to the author for internal non-commercial research and education use, including for instruction at the authors institution and sharing with colleagues.Other uses, including reproduction and distribution, or selling or licensing copies, or posting to personal, institutional or third party websites are prohibited. a b s t r a c tSoftware estimation is a tedious and daunting task in project management and software development. Software estimators are notorious in predicting software effort and they have been struggling in the past decades to provide new models to enhance software estimation. The most critical and crucial part of software estimation is when estimation is required in the early stages of the software life cycle where the problem to be solved has not yet been completely revealed. This paper presents a novel log-linear regression model based on the use case point model (UCP) to calculate the software effort based on use case diagrams. A fuzzy logic approach is used to calibrate the productivity factor in the regression model. Moreover, a multilayer perceptron (MLP) neural network model was developed to predict software effort based on the software size and team productivity. Experiments show that the proposed approach outperforms the original UCP model. Furthermore, a comparison between the MLP and log-linear regression models was conducted based on the size of the projects. Results demonstrate that the MLP model can surpass the regression model when small projects are used, but the log-linear regression model gives better results when estimating larger projects.

show abstract

“…Authors in [11] and [12] worked on adjustment factors, while others in [12] and [13] highlighted the discrepancies in designing use case models. Researchers in [14], [15] and [16] proposed different size metrics such as Transactions, TTPoints and Paths, while others [17], [18], [19], [20], [21], [22], [23], [24] and [25] went further to extend the UCP model by providing new complexity weights or by modifying the method used to predict effort. Neural network models such as [26], [27], [28], [29], [30] and [31] were used to predict software effort.…”

Section: Related Workmentioning

confidence: 99%