Cited By
View all- Falkner AHaselböck A(2018)Challenges of knowledge evolution in practiceAI Communications10.5555/2594638.259464026:1(3-14)Online publication date: 26-Dec-2018
Software testing sizing in incremental development: A case study
Authors: 
Xiaochun Zhu, Bo Zhou, Lu ChenAuthors Info & Claims
Pages 490 - 493
Abstract
The paper presents a case study on software testing sizing of 20 project releases delivered by a technical team through incremental development. Different sizing metrics including KLOC, development effort, test case number and function sizes are reviewed and evaluated. The results show that KLOC doesn't behave well, development effort surprisingly act as a good measure, test case number is an excellent testing sizing method, and existing function size ways are not suitable in our case. In the meanwhile, several sizing evaluation models are proposed during the discussion.
References
[1]
Albrecht AJ. Gafney JE. 1983. "Software function, source lines of code and development effort prediction: A software science validation", IEEE Trans. on Software Engineering , 9(6): 639-648.
[2]
Park R. "Software size measurement: A framework for counting source statements", Technical Report, CMU/SEI- 92-TR-20, Pittsburgh: Software Engineering Institute. 1992.
[3]
Bielak J. 2000. "Improving size estimates using historical data", IEEE Software , 17 (6):27-35.
[4]
Boehm BW., Abts C., etc. 2000. Software Cost Estimation with COCOMO II . New York: Prentice Hall.
[5]
Briand LC., Emam K., Bomarius F. "COBRA: A hybrid method for software cost estimation, benchmarking and risk assessment", Proc. of the 20th Int'l Conf. on Software Engineering. IEEE CS Press, 1998. 390-399.
[6]
Matson JE., Barrett BE., Mellichamp JM. "Software development cost estimation using function points", IEEE Trans. on Software Engineering , 1994. 20(4):275-287.
[7]
International Function Point Users Group. 2001. Function Point Counting Practices Manual, Release 4.1.1.
[8]
Caroll ER. 2005. "Estimating software based on use case points", In Proc. of the Conf. on Object Oriented Programming Systems Languages and Applications, New York: ACM Press, 257-265.
[9]
Larman C., Basili V. 2003. "Iterative and Incremental Development: A Brief History", Computer , Volume 36, Issue 6, June Page(s):47-56.
[10]
Aranha E., Borba P. 2007. "An Estimation Model for Test Execution Effort", 1st International Symposium on Empirical Software Engineering and Measurement.
[11]
Zhu X., Zhou B., Hou L., Chen J., Chen L. 2008. "An Experience-Based Approach for Test Execution Effort Estimation", In Proceedings of 9th International Conference for Young Computer Scientists, Page(s):1193-1198.
[12]
Jones C. Applied software measurement , McGraw-Hill. 1996.
[13]
Ton D. "Test Point Analysis", 1999.
[14]
Nageswaran S. 2001. "Test effort estimation using use case points", In 14th International Internet Software Quality Week.
[15]
Qu Y., Zhou B., Zhu X. 2008. "Early Estimate the Size of Test Suites from Use Cases", 15th Asia-Pacific Software Engineering Conference, Page(s):487-492.
[16]
Bach J. 2004. Exploratory Testing, in The Testing Practitioner, Second ed. , E. van Veenendal Ed., Den Bosch: UTN Publishers, pp. 253-265.
[17]
Alexander, S., 2005. "Component evolution and versioning state of the Art", ACM SIGSOFT Software Engineering Notes , 30(1):7.
[18]
K. Beck, Extreme Programming Explained: Embrace Change , Addison-Wesley, 1999.
[19]
Cote V., St-Pierre D. "A model for estimating perfective software maintenance projects", In Proc. of International Conference on Software Maintenance, 1990. 26-29 Nov. 1990 Page(s):328 - 334.
[20]
Niessink F., Van Vliet H. "Predicting maintenance effort with function points", In Proc. of International Conference on Software Maintenance, 1997. Oct. Page(s):32-39.
Index Terms
- Software testing sizing in incremental development: A case study
Recommendations
The Application and Research of Software Testing on Agile Software Development
ICEE '10: Proceedings of the 2010 International Conference on E-Business and E-GovernmentSoftware testing is the key for software quality. Agile software development method that is new methodology in recent years embraces change and fixes attention on the delivery of high quality software. Extreme Programming, the most popular one of agile, ...
Software development: what it is, what it should be, and how to get there
Developing large software systems is notoriously difficult and unpredictable. Software projects are often canceled, finish late and over budget, or yield low quality results --- setting software engineering apart from established engineering ...
Comments
Please enable JavaScript to view thecomments powered by Disqus.Information & Contributors
Information
Published In
October 2009
601 pages
ISBN:9781424448425
Publisher
IEEE Computer Society
United States
Publication History
Published: 15 October 2009
Qualifiers
- Article
Acceptance Rates
Overall Acceptance Rate 130 of 594 submissions, 22%
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- View Citations1Total Citations
- 247Total Downloads
- Downloads (Last 12 months)6
- Downloads (Last 6 weeks)0
Reflects downloads up to 12 Dec 2024
Other Metrics
Citations
Cited By
View all- Falkner AHaselböck A(2018)Challenges of knowledge evolution in practiceAI Communications10.5555/2594638.259464026:1(3-14)Online publication date: 26-Dec-2018
View Options
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in