The Journal of Korean Institute of Communications and Information Sciences (한국통신학회논문지)

The Korean Institute of Commucations and Information Sciences (한국통신학회)
권호 표지
DOI QR코드

DOI QR Code

On Software Reliability Engineering Process for Weapon Systems

무기체계를 위한 소프트웨어의 신뢰성 공학 프로세스

  • 김기백 (국방과학연구소 2본부 4부) ;
  • 이재천 (아주대학교 시스템공학과)
  • Received : 2011.01.10
  • Accepted : 2011.04.04
  • Published : 2011.04.30
Download PDF
⟨ Previous Next ⟩

Abstract

As weapon systems are evolving into more advanced and complex ones, the role of the software is becoming heavily significant in their developments. Particularly in the war field of today as represented by the network centric warfare(NCW), the reliability of weapon systems is definitely crucial. In this context, it is inevitable to develop software reliably enough to make the weapon systems operate robustly in the combat field. The reliability engineering activities performed to develop software in the domestic area seem to be limited to the software reliability estimations for some projects. To ensure that the target reliability of software be maintained through the system's development period, a more systematic approach to performing software reliability engineering activities are necessary from the beginning of the development period. In this paper, we consider the software reliability in terms of the development of a weapon system as a whole. Thus, from the systems engineering point of view, we analyze the models and methods that are related to software reliability and a variety of associated activities. As a result, a process is developed, which can be called the software reliability engineering process for weapon systems (SREP-WS), The developed SREP-WS can be used in the development of a weapon system to meet a target reliability throughout its life-cycle. Based on the SREP-WS, the software reliability could also be managed quantitatively.

무기체계가 첨단 복합화 형태로 진화하면서 물리적 구현에서 소프트웨어가 차지하는 비중과 중요성은 급격히 증대되고 있다. 특히 네트워크 중심전(NCW)으로 대변되는 현대의 전장 상황에서 신뢰성 있게 운용되는 무기체계를 개발하기 위해서는 신뢰성 있는 소프트웨어의 개발이 필수 불가결한 요소이다. 국내 무기체계의 연구개발 과정에서 하드웨어 구성품과는 다르게 소프트웨어 요소에 대한 신뢰성 관련 기술 활동은 일부 구현된 소프트웨어에 대해 신뢰도 평가를 수행하는 수준이다. 그러나 연구개발 기간에 소프트웨어의 목표 신뢰도를 확보하기 위해서는 무기체계 개발 초기 단계부터 체계적인 신뢰성 공학 활동이 요구된다. 본 연구에서는 범위가 제약되어 있던 그 동안의 소프트웨어 신뢰성 관련 연구 활동을 무기체계 연구개발 수명주기 동안 목표 신뢰도를 만족하는 소프트웨어를 개발할 수 있도록 시스템 공학 관점에서 접근법을 제시하였다. 그 결과 무기체계의 연구개발 수명주기 동안 적용할 수 있는 프로세스를 도출하였는데 이를 무기체계의 소프트웨어 신뢰성 공학 프로세스 (Software Reliability Engineering Process for Weapon Systems: SREP-WS)로 명명하였다. 각종 첨단무기체계 개발에 도출된 SREP-WS를 적용함으로써 소프트웨어 신뢰도를 정량적 관리할 수 있고, 또한 목표 신뢰도를 개발기간 중에 확보할 수 있게 된다.

Keywords

References

  1. Reliability Program for Systems and Equipment Development and Production (MIL-STD-785B), DoD U.S, Sep. 1980.
  2. Reliability Modeling and Prediction (MIL-STD- 756B), DoD U.S, May 1963.
  3. Reliability Prediction of Electronic Equipment (MIL-HDBK-217F), DoD U.S, Dec. 1991.
  4. H.D. Mills "On the statistical validation of computer program," IBM FSD, Jul. 1970.
  5. Introduction to Software Reliability: A state of the Art Review, Reliability Analysis Center, pp. 100, Dec. 1996.
  6. Z. Jelinski, P.B. Moranda, "Software reliability research" In Statistical Computer Performance Evaluation, W. Freiberger (ed.), Academic Press, New York, 1972.
  7. A.L. Goel, K. Okumoto, "Time-dependent error-detection rate model for software and other performance measures," IEEE Transaction on Reliability 28, 206-211, 1979.
  8. T.J. McCabe, "A complexity measure," IEEE Trans. Software Engineering Vol.SE-2(4), 1976.
  9. M.H. Halstead, Elements of Software Science, Elsevier, New York, 1997.
  10. Introduction to Software Reliability: A state of the Art Review, Reliability Analysis Center, pp 99.
  11. Fatemeh Zahedi and Noushin Ashrafi, "Software Reliability Allocation Based on Structure, Utility, Price, and Cost," IEEE transactions on software engineering, Vol.17, No.4, pp.345-356, 1991. https://doi.org/10.1109/32.90434
  12. Y.W. Leung, "Optimal Reliability Allocation for Modular Software System Designed for Multiple Customers," IEICE transactions on information and systems, Vol.79, No.12, pp.1655-1662, 1996.
  13. Y.W. Leung, "Software reliability allocation under an uncertain operational profile," The journal of the Operational Research Society, Vol.48, No.4, pp.401-411, 1997. https://doi.org/10.1057/palgrave.jors.2600384
  14. C. Huang, R.Z. Xu, L.P. Zhang, "Software Reliability Allocation Model Based on Cost-controlling," Asian international workshop on advanced reliability modeling, AIWARM 2004, pp.173-180, 2004.
  15. Norman Schneidewind, "Allocation and analysis of reliability: multiple levels: system, subsystem, and module," Innovations in Systems and Software Engineering: a NASA journal, Vol.2, No.3/4, pp.121-136, 2006. https://doi.org/10.1007/s11334-006-0008-6
  16. Electronic Reliability Design Handbook (MIL-HDBK-338B), pp.9.1-9.69, Oct., 1998.
  17. Michael R. Lyu, "Software Reliability Engineering: A Roadmap," ICSE2007, 2007.
  18. IEEE Std 1633 Recommended Practice on Software Reliability, IEEE Reliability Society, pp.4, Jun 2008.
  19. Hoang Pham, Software Reliability, Springer, 2000
  20. Peter B. Lakery, Ann Marie Neufelder, System and Software Reliability Assurance Notebook, pp.4.14, 2005.
  21. Peter B. Lakery, Ann Marie Neufelder, System and Software Reliability Assurance Notebook, 7.10-7.15, 2005.
  22. S. Yamada, M. Ohba, S. Osaki, "S-shaped reliability growth modeling for software error detection," IEEE Transactions on Reliability 12, 475-484, 1983.
  23. S. Yamada, K. Tokuno, S. Osaki, "Imperfect debugging models with fault introduction rate for software reliability assessment," International Journal of Systems Science 23(12), 2253-2264, 1992. https://doi.org/10.1080/00207729208949453
  24. IEEE Std 1633 Recommended Practice on Software Reliability, IEEE Reliability Society, pp.16-36, Jun 2008.
  25. Peter B. Lakery, Ann Marie Neufelder, System and Software Reliability Assurance Notebook, pp.4.1-4.21, 2005.
  26. 체계개발단계 내장형 소프트웨어 개발관리 업무 편람, 방위사업청, 2008.
  27. 신주환, 김용국, 이성은, 검독수리-A급 전투체계 소프트웨어 신뢰도 분석 (ADDR-415-081426), 국방과학연구소, 2008.
  28. 김홍수외 6, 소프트웨어 신뢰성 향상 방안 및 모델 개발 (ADDR-412-100046), 국방과학연구소, 2009.
  29. Systems Engineering-System Life Cycle Processes (IEEE Std 15288), IEEE, pp.5-39, 2004.
  30. Software Life Cycle Processes (ISO/ IEC 12207), ISO/IEC, 1998.
  31. 종합군수지원 개발 실무지침서, 방위사업청, pp.65, 2009.
  32. 김효창, 조용석, M-SAM 체계의 신뢰도 목표값 설정 연구 (MADC-516-030530), 국방과학연구소, 2003.
  33. 최광조, 노병래, 차기전차 RAM-D 요구조건/설계 목표 및 예측결과 (GSDC-519-050291), 국방과 학연구소, 2005.
  34. 배상수, 생물독소분석 식별기 OMS/MP에 따른 RAM 설정(안) (ADDR-523-080178), 국방과학연구소, 2008.
  35. Procedures for Performing a Failure Mode, Effects and Criticality Analysis (MIL-STD-1629A), DoD U.S, Dec 1980.
  36. The DACS Software Reliability Sourcebook, DACS, pp.7.2, Sep., 2001.
  37. Guidelines for safety analysis of vehicle based programmable systems, MISRA, Nov., 2007.
  38. http://www.misra.org.uk/
  39. 연구개발 프로세스 표준화 규정(안), 국방과학연구소, 2010.