2011
DOI: 10.1007/978-3-642-20573-6_47
|View full text |Cite
|
Sign up to set email alerts
|

Cluster Analysis & Pso for Software Cost Estimation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0

Year Published

2011
2011
2024
2024

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(7 citation statements)
references
References 5 publications
0
7
0
Order By: Relevance
“…For the purpose of experimentation, the SEEPC toolbox was provided with a training set of 36 values [13] derived from the COCOMO 81 dataset. Upon training the model, 3 clusters were obtained.…”
Section: Experimentation and Sample Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…For the purpose of experimentation, the SEEPC toolbox was provided with a training set of 36 values [13] derived from the COCOMO 81 dataset. Upon training the model, 3 clusters were obtained.…”
Section: Experimentation and Sample Resultsmentioning
confidence: 99%
“…The MARE values are shown in Table 2. The SEEPC model makes use of efficient clustering and PSO to learn and develop in its course of usage [13]. As such, it is more efficient for making long term accurate predictions than the traditional COCOMO model.…”
Section: Experimentation and Sample Resultsmentioning
confidence: 99%
“…Compared to previous algorithms, the proposed algorithm has demonstrated superior results in cost prediction. The International Software Benchmarking Standards Group (ISBSG) dataset has been utilized for a linear regression model based on the criteria of relative error values [10]. The ISBSG dataset includes 3042 software projects from different companies during the last 6 years.…”
Section: Related Workmentioning
confidence: 99%
“…r Theme relevance-There has been a growth in the number of software projects (Sethi et al, 2011;Bazaz et al, 2012); project risk in this segment (Bazaz et al, 2012); and in the use of Scrum (VersionOne, 2016), which is the most popular agile methodology (Azizyan et al, 2011;Meier and Ivarsson, 2013;Mundra et al, 2013;VersionOne, 2016).…”
Section: Introductionmentioning
confidence: 99%
“…This research is conducted for the following reasons: Theme relevance—There has been a growth in the number of software projects (Sethi et al., ; Bazaz et al, ); project risk in this segment (Bazaz et al., ); and in the use of Scrum (VersionOne, ), which is the most popular agile methodology (Azizyan et al., ; Meier and Ivarsson, ; Mundra et al., ; VersionOne, ). Use of risk management in software projects—Generally, it is observed that there exists a lack of risk management in software projects using Scrum (Hijazi et al., ; Tomanek and Juricek, ), and software projects in general (Bannerman, ; Junior et al., ; Singh et al., ). Software project success—Risk management can increase the chance of success in software projects (SEI, ; Chowdhury and Arefeen, ; Bannerman, ) by reducing their uncertainties and chances of failure (Wet and Visser, ). On the other hand, the absence of risk management procedures is one of the reasons for the failure of these projects (Charette, ; Dey et al., ; Lu et al., ). Characteristics of risk management—Agile methodologies do not explicitly suggest risk management processes (Nelson et al., ; Nyfjord and Kajko‐Mattsson, ; Khatri et al., ; Moran, ). …”
Section: Introductionmentioning
confidence: 99%