소프트웨어 개발 초기 단계에서 정량적 소프트웨어 신뢰성 목표 설정 방법 = A Quantitative Goal Setting Method for Software Reliability in Early Stages of Software Development

국문 초록 (Abstract)

소프트웨어 규모와 복잡도가 증가함에 따라 소프트웨어 품질, 특히 신뢰성에 대한 중요성이 증가하고 있다 100% 완벽한 소프트웨어 신뢰성 보장은 불가능하고, 모든 소프트웨어 제품이 높은 수준의 신뢰성을 갖기 위해서는 많은 개발 비용과 노력이 소요된다. 그러므로 소프트웨어 개발 프로젝트와 대상 소프트웨어의 목적에 맞는 신뢰성을 갖도록 소프트웨어 개발이 이루어져야 한다. 이를 위해 본 논문에서는 초기 소프트웨어 개발 단계에서 소프트웨어 신뢰성 목표 설정을 지원하는 정량적인 방법을 제안한다. 기존 소프트웨어 신뢰성 연구에서 신뢰성 목표는 도메인 전문가의 경험에 근거한 정성적 목표 설정을 기반으로 하고 있다. 그러나 동일한 도메인에서도 소프트웨어 용도에 따라 개발 자원, 비용, 그리고 소프트웨어 제품의 목표 신뢰성이 모두 다르기 때문에 이러한 정성적 목표값만으로는 소프트웨어 개발 및 신뢰성 분석/평가가 올바르게 수행되기 어렵다. 그러므로 본 논문에서는 (1) 소프트웨어 개발에 사용되는 자원과 비용, 그리고 소프트웨어 제품이 갖는 품질에 대한 trade-off를 파악할 수 있도록 비용 척도 및 제품 척도를 정의하고, (2) 이러한 비용 요소 및 제품 요소의 trade-off 결과를 조율하여 적정 수준의 자원 및 비용을 활용하면서도 소프트웨어 신뢰성을 최대화 할 수 있도록 의사 결정을 지원하기 위한 방법을 정의한다. 끝으로 (3) 실제 산업에서 수집된 데이터를 활용하여 본 논문에서 제안된 방법이 유용하게 활용될 수 있음을 사례 연구를 통해 보인다.

다국어 초록 (Multilingual Abstract)

As software size and complexity have been increased, the importance of software quality, especially software reliability, has been more emphasized than ever. However, it is impossible to guarantee 100% software reliability and it requires a lot of development cost and efforts to develop high reliable software products. Therefore, a software product should be developed with an appropriate software reliability goal that is fit to software development project and the usage of target software. In this paper, we proposed a technique to support a quantitative software reliability goal setting in the early stage of a software development life-cycle. Existing software reliability studies focuses on the qualitative expert’s knowledge and experiences in the specific domain. However, this qualitative way makes it difficult to accomplish the software development and reliability analysis because software development resources, costs and the reliability goals are different each other even if software products are developed in the same domain. Our contributions of this paper are followings: (1) we define sets of the cost related parameters and product related parameters to identify the trade-offs between software development cost and software reliability goal. (2) we resolve the trade-off results to maximize the software reliability using optimal software development cost and resources. Finally, (3) we show that the proposed way is useful through the case study with industry data which comes from our past projects.

목차 (Table of Contents)

• 요약
• Abstract
• 1. 서론
• 2. 관련 연구
• 3. 정량적 소프트웨어 신뢰성 목표 설정(Quantitative Software Reliability Goal Setting,QSRGS)
• 4. 사례 연구
• 5. 결론 및 향후 연구 과제
• 참고문헌

참고문헌 (Reference)

1 강명묵, "소프트웨어 결함 발견 및 제거 노력 기반 신뢰성 추정 모델" 한국정보과학회 37 (37): 536-547, 2010

2 Toyota Recall Service Centers, "Toyota Prius Anti Lock Brake Problems" Toyota Recall Service Centers 2010

3 VDC Research Group, "The Embedded Software Market Intelligence Program" VDC Research Group 2006

4 United States Senate, "Tactical Aircraft F/A-22 and JSF Acquisition Plans and Implications for Tactical Aircraft Modernization, Statement of Michael Sullivan, Director Acquisition and Sourcing Management Issues" 2005

5 COCOMO Forum, "Systems and Software Cost Modeling Forum"

6 A. Immonen, "Survey of Reliability and Availability Prediction Methods from the Viewpoint of Software Architecture" 7 : 49-65, 2008

7 J. McCall, "Software Reliability, Measurement, and Testing Software Reliability and Test Integration (RL-TR-92-52)" 1992

8 Z. Jelinski, "Software Reliability Research"

9 M. Xie, "Software Reliability Modeling" World Scientific Publishing Company 1991

10 M. R. Lyu, "Software Reliability Engineering: Roadmap" 2007

11 J. D. Musa, "Software Reliability Engineering: More Reliable Software Faster and Cheaper" AuthorHouse 2004

12 D. Lee, "Software Reliability Assurance Using a Framework in Weapon System Development: A Case Study" IEEE/ACIS International Conference on Computer and Information Science 2009

13 International Organization for Standardization and International Electronic Committee, "Software Engineering - Product Quality - Part 1: Quality Model" International Organization for Standardization and International Electronic Committee, 2001

14 B. Boehm, "Software Cost Estimation with COCOMO II" Prentice-Hall 2000

15 Radio Technical Commission for Aeronautics (RTCA), "Software Considerations in Ariborne Systems and Equipment" Radio Technical Commission for Aeronautics (RTCA), 1992

16 S. Yamada, "S-shaped reliability growth modeling for software error detection" 32 : 475-478, 1983

17 R. H. Reussner, "Reliability Prediction for Component- based Software Architectures" 66 : 241-252, 2003

18 N. F. Schneidewind, "Reliability Modeling for Safety- Critical Software" 46 : 88-98, 1997

19 E. d. Ouden, "Quality and Reliability Problems from a Consumer's Perspective: an Increasing Problem Overlooked by Business" 22 : 821-838, 2006

20 F. Brosch, "Parameterized Reliability Prediction for Component-Based Software Architectures" 2010

21 International Electronic Commitee, "Medical device software - Software life cycle processes" International Electronic Commitee 2006

22 Reliability Analysis Center, "Introduction to Software Reliability: A state of the Art Review" Reliability Analysis Center 1996

23 IEEE Standard, "IEEE Standard 1633:2008, IEEE Recommended Practice on Software Reliability" IEEE Reliability Society 2008

24 IEEE Computer Society, "IEEE Guide for the Use of IEEE Standard Dictionary of Measures to Produce Reliable Software" IEEE Computer Society, 1988

25 M. R. Lyu, "Handbook of Software Reliability Engineering" McGraw-Hill Publishing 1995

26 R. Madarchy, "Assessing Quality Processes with ODC COQUALMO" 198-209, 2008

27 J. A. Stafford, "Architecture-level dependence analysis for software systems" 11 : 2001

28 S. S. Gokhale, "Architecture-Based Software Reliability Analysis: Overview and Limitations" 4 : 32-40, 2007

29 C. Jones, "Applied software measurement: assuring productivity and quality" McGraw-Hill 1996

30 R. D. Banker, "An Empirical Test of Object-Based Output Measurement Metrics in a Computer Aided Software Engineering (CASE) Environment" 8 : 127-150, 1994

31 T. Gu, "Adaptive Practice on Software Reliability Based on IEEE Std. 1633 in Frequent Requirement Modifications" 317 : 2010

32 J. J. Hadel, "A Customer- Oriented Approach to Optimizaing Reliability Allocation Within a Set of Weapon-System Requirements" 1995