Empirical Analysis for High Quality Software Development
- 1 IT Software Operations Unit, NEC Corporation, Tokyo, Japan
- 2 Department of Social Management Engineering, Graduate School of Engineering, Tottori University, Tottori, Japan
Abstract
It remains important for a development organization to configure a software process that enables it to develop software products with the least possible number of defects after shipment. A development organization of CMMI level 5 has, over three years, been strived to improve those software projects that had been noted as having many defects after shipment. In this paper, we discuss our organization’s improvement (Kaizen) activities, to analyze the important matters of software process to be considered when developing a software product with the least possible number of defects after shipment. Our results are identified by three important points; 1) early ensured quality by defect detection during design or code review; 2) quality assurance for both process quality and product one; and 3) quantitative management by which data of the appropriate resolution can be collected at an appropriate timing.
- W. S. Humphrey, “Winning with Software: An Executive Strategy,” Pearson Education, Inc., New Jersey, 2002.
- N. Honda, “Beyond CMMI Level 5—Comparative Analysis of Two CMMI Level 5 Organizations,” Software Quality Professional, Vol. 11, No. 4, 2009, pp. 4- 12.
- N. Honda, “Software Quality Accounting—Quality Assurance Technology That Supports High Quality Software Development at NEC,” JUSE Press, Tokyo, 2010.
- B. Boehm, “Software Engineering Economics,” Prentice- Hall, Englewood Cliffs, 1981.
- T. Gilb and D. Graham, “Software Inspection,” Addison-Wesley, Reading, 1993.
- SQuBOK Study Team, “SQuBOK Guide—Software Quality Body of Knowledge (in Japanese),” Ohmsya, Tokyo, 1997.
- JUSE, “Research Report for CMMI Level 5 Organizations,” Tokyo, 2009. http://www.juse.or.jp/software/86/attachs/kikaku_1.pdf