2017
DOI: 10.11591/ijeecs.v5.i1.pp220-228
|View full text |Cite
|
Sign up to set email alerts
|

Early Test Effort Prediction using UML Diagrams

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
11
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 15 publications
(11 citation statements)
references
References 6 publications
0
11
0
Order By: Relevance
“…In aspect-oriented programming paradigm, software development and testing are different from other programming paradigms as it supports the concept of Separation of Concerns (SoC) [7], [8]. As observed in Table 4, only a few approaches have used the UML behavior models for testing Aspect-Oriented Programs.…”
Section: Support Of Uml Behavior Model For Aspect-oriented Testing Apmentioning
confidence: 99%
See 2 more Smart Citations
“…In aspect-oriented programming paradigm, software development and testing are different from other programming paradigms as it supports the concept of Separation of Concerns (SoC) [7], [8]. As observed in Table 4, only a few approaches have used the UML behavior models for testing Aspect-Oriented Programs.…”
Section: Support Of Uml Behavior Model For Aspect-oriented Testing Apmentioning
confidence: 99%
“…Efficient and effective test model can be designed by directly using the UML behavioral models. Designing specific test model for testing is a tedious and time-consuming task [8]. Usage of UML behavioral model to test AOP reduces the effort and increases reusability.…”
Section: Support Of Uml Behavior Model For Aspect-oriented Testing Apmentioning
confidence: 99%
See 1 more Smart Citation
“…Data mining ors software analytics studies that use requirements engineering artifacts are scarce [9]. For example, one of these rare studies aims early test effort prediction by using UML diagrams [10]. On the other hand, software data mining studies which are based on sofware code and code change artifacts are common [9].…”
Section: Introductionmentioning
confidence: 99%
“…Accuracy in estimation is a crucial factor for planning software development to evade budget overruns and tardy delivery of software. Estimation of test effort along with development is considered crucial for apprehending quality software [3]. Development of mobile software is considered different from developing traditional software pertaining to its distinctive features such as limited memory, processing power, small and multiple input interface, multiple connections, bandwidth factor, a lower battery, etc.…”
Section: Introductionmentioning
confidence: 99%