KIPS Transactions on Software and Data Engineering (정보처리학회논문지:소프트웨어 및 데이터공학)

Korea Information Processing Society (한국정보처리학회)
권호 표지
DOI QR코드

DOI QR Code

A Study on Extraction of Additional Information Methodology for Defect Management in the Design Stage

설계단계의 결함관리를 위한 추가정보 추출에 관한 연구

  • Received : 2020.07.17
  • Accepted : 2020.07.30
  • Published : 2020.10.31
Download PDF
⟨ Previous Next ⟩

Abstract

Software design are an important phase in the software developments. In order to manage software design, we propose additional information. Additional information suggests a standard and quantitative methods. In this study, we propose additional information at the design stage for defect management.

소프트웨어 설계는 구현을 하기 위하여 중요한 단계이다. 소프트웨어 설계의 결함관리를 위하여 추가적인 정보를 제안하고자 한다. 추가적인 정보는 방법론을 제시하고 정량적인 방법으로 접근한다. 본 연구에서는 결함관리를 위하여 설계 단계의 추가적인 정보를 제시하고자 한다.

Keywords

References

  1. Roger S. Pressman, "Software Engineering," McGraw-Hill Higher Education, 2005.
  2. Harold W. Lawson, "An Assessment Methodology for Safety Critical Computer Based Systems," Proceedings of CSR 12th Annual Workshop on Safety and Reliability of Software Based Systems, pp.183-200, 1995.
  3. Peter L. Goddard, "A Combines Analysis Approach To Assessing Requirements for Safety Critical Real-Time Control Systems," Proceeding Annual Reliability & Maintainability Symposium, pp.227-230, 1993.
  4. Swarup, M. Ben and P. Seetha Ramaiah, "A Software Safety Model for Safety Critical Application," Proceedings of International Forum on Computer Science-Technology and Applications, pp.21-32, 2009.
  5. Stephen S. Cha, Nancy G. Leveson, and Timothy J. Shimeall, "Safety Verification in MURPHY using Fault Tree Analysis," Proceeding on the 10th International Conference on Software Engineering, pp.377-386, 1988.
  6. Hye-Jung Jung, "The Analysis of Software Fault and Application Method of Weight using the Testing Data," Journal of Korea Multimedia Society, Vol.14, No.6, pp. 766-774, 2011. https://doi.org/10.9717/kmms.2011.14.6.766
  7. IEC 60812, "Procedures for Failure Mode and Effect Analysis (FMEA)," 2006.
  8. SEMATECH, "Failure Modes and Effects Analysis (FMEA): A Guide for Continuous Improvement for the Semiconductor Equipment Industry," 1992.
  9. IEEE Standard for Software Reviews, IEEE Std 1028-2008, 1998.
  10. Software Engineering Standards, IEEE Computer Society, 1994.
  11. I. Somerville, Software Engineering, Addison-Wesley, 2001.
  12. "Software Risk Abatement", AFCS/AFLC Pamphlet 800-45, U.S. Air Force, 1988.
  13. B, W. Boehm, "Software Risk Management", IEEE Computer Society Press, 1989.
  14. D. W. Karolak, "Software Engineering Risk Management", IEEE Computer Society Pess, 1996.
  15. "Software bugs cost US economy dear," Jun. 10, 2009. Archived from the original on June 10, 2009. Retrieved Sept. 24, 2012.
  16. IEEE Annals of the History of Computing, Vol.22, Issue.1, 2000.
  17. "Testing experience : te : the magazine for professional testers," Testing Experience. Germany: testingexperience: 42, Mar. 2012.
  18. McDonald, Marc; Musson, Robert; Smith, Ross. The Practical Guide to Defect Prevention. Microsoft Press. p. 480, 2007.
  19. Allen, Mitch (May-June 2002). "Bug Tracking Basics: A beginner's guide to reporting and tracking defects," Software Testing & Quality Engineering Magazine, Vol.4 No.3. pp.20-24. Retrieved Dece. 19, 2017.
  20. Watts S. Humphrey, "Introduction to the Personal Software Process," PEASON, 2003.