ACM Home Page
Please provide us with feedback. Feedback
Phase distribution of software development effort
Full text PdfPdf (283 KB)
Source
ESEM archive
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement table of contents
Kaiserslautern, Germany
SESSION: Estimation models I table of contents
Pages 61-69  
Year of Publication: 2008
ISBN:978-1-59593-971-5
Authors
Ye Yang  Chinese Academy of Sciences, Beijing, China
Mei He  Chinese Academy of Sciences, Beijing, China
Mingshu Li  Chinese Academy of Sciences, Beijing, China
Qing Wang  Chinese Academy of Sciences, Beijing, China
Barry Boehm  University of Southern California, Los Angeles, USA
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 26,   Downloads (12 Months): 283,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1414004.1414016
What is a DOI?

ABSTRACT

Effort distribution by phase or activity is an important but often overlooked aspect compared to other steps in the cost estimation process. Poor effort allocation is among the major root causes of rework due to insufficiently resourced early activities. This paper provides results of an empirical study on phase effort distribution data of 75 industry projects, from the China Software Benchmarking Standard Group (CSBSG) database. The phase effort distribution patterns and variation sources are presented, and analysis results show some consistency in effects of software size and team size on code and test phase distribution variations, and some considerable deviations in requirements, design, and transition phases, compared with recommendations in the COCOMO model. Finally, this paper discusses the major findings and threats to validity and presents general guidelines in directing effort allocation. Empirical findings from this study are beneficial for stimulating discussions and debates to improve cost estimation and benchmarking practices.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
Basili, V. R.: Software development: a paradigm for the future. Proceedings of the 13th Annual International Computer Software and Application Conference, (1989) 471--485.
 
4
 
5
The Standish Group. 2004 the 3rd Quarter Research Report, (2004). http://www.standishgroup.com
 
6
 
7
Reifer, D.: Industry software cost, quality and productivity benchmarks, software. Tech News 7(2) (July 2004)
 
8
Kroll, P.: Planning and estimating a RUP project using IBM rational SUMMIT ascendant. Technical report, IBM Developerworks (May 2004)
 
9
QSM Inc.: The QSM Software Almanac: Application Development Series (IT Metrics Edition) Application Development Data and Research for the Agile Enterprise. Quantitative Software Management Inc., McLean, Virginia, USA (2006)
 
10
Heijstek, W. and Chaudron, M. R. V.: Effort distribution in model-based development. 2nd Workshop on Model Size Metrics (2007)
 
11
 
12
 
13
 
14
Norden P. V.: Curve Fitting for a Model of Applied Research and Development Scheduling. IBM J. Research and Development, Vol. 3, No. 2, (1958), 232--248.
 
15
Putnam, L. and Myers, W. (1992), Measures for Excellence, Yourdon Press Computing Series.
 
16
He, M., et al.: An Investigation of Software Development Productivity in China. ICSP 2008, (2008) 381--394
 
17
SEER-SEM. http://www.galorath.com/index.php
18
19
20
 
21
Jiang, Z., Naudé, P. and Comstock, C.: An investigation on the variation of software development productivity. International Journal of Computer, Information, and Systems Sciences, and Engineering, Vol. 1, No. 2 (2007) 72--81
 
22
ISBSG Benchmark Release 8. http://www.isbsg.org
 
23
SPR Programming Languages Table 2003, Software Productivity Research. ttp://www.spr.com
 
24
 
25
Software Measurement Services Ltd. 'Small project', 'medium-size project' and 'large project': what do these terms mean?" http://www.measuresw.com/library/Papers/Rule/RulesRelativeSizeScale%20v1b.pdf
 
26

Collaborative Colleagues:
Ye Yang: colleagues
Mei He: colleagues
Mingshu Li: colleagues
Qing Wang: colleagues
Barry Boehm: colleagues