1997
DOI: 10.1109/32.624305
|View full text |Cite
|
Sign up to set email alerts
|

A model for software development effort and cost estimation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
73
0

Year Published

1999
1999
2020
2020

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 147 publications
(73 citation statements)
references
References 10 publications
0
73
0
Order By: Relevance
“…With movement of value towards 0, the model significantly explains low presence of prediction error. The bias is defined mathematically as [9]:…”
Section: ) Biasmentioning
confidence: 99%
See 1 more Smart Citation
“…With movement of value towards 0, the model significantly explains low presence of prediction error. The bias is defined mathematically as [9]:…”
Section: ) Biasmentioning
confidence: 99%
“…It measures the closeness with which the model predicts the bugs and mathematical representation of this characteristic is given as [9]. …”
Section: ) Root Mean Square Prediction Error (Rmspe)mentioning
confidence: 99%
“…Many software effort/cost estimation models where proposed to help in providing a high quality estimate to assist a project manager in considering the best decisions for a project [8], [9]. Many software cost estimation models were reported in the literature [10]- [13]. These models were used to help project managers to estimate effort, time and cost.…”
Section: • Inadequate Financial Resourcesmentioning
confidence: 99%
“…The computer facilities represent the computer time, which is necessary for failure detection and rectification. The influence of software testing effort has been included in several SRGMs Putnam [30]; Pillai and Nair [23]; Kapur, Garg, and Kumar [18]; Xie [26]; Ichimori, Yamada, and Nishiwaki [11]; Kapur and Bardhan [16]; Huang et al [9]; Kapur et al [19], Myers [21] planned that software will be constructed and tested individually in a chronological step. Yamada et al [27], Hou, Kuo, and Chang [7], Pham and Zhang [22] have recommended that system level software testing occurred only after the system was completely developed.…”
Section: Research Backgroundmentioning
confidence: 99%