• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.699-704
• /
• 2001

Developing a component-based software requires verified and standardized software components. This paper presents a component quality management (CQM) process. The process was developed and applied to the government-sponsored trial projects that developed software components. The process is composed of four phases：quality specification, quality planning, quality control, and quality evaluation. With this process, we can establish quality goals and focus our efforts on the activities to achieve the goals. A component quality model is also suggested to transform the implicit quality requirements into the measurable quality goals and to be used for the basis when we evaluate the quality of software components against the quality goals.

• The Journal of the Korea Contents Association
• /
• v.10 no.8
• /
• pp.84-94
• /
• 2010

ESM can do and wishes to investigate ESM software field base technology and investigate ESM software technology, market, standard and evaluation certification trend and develop evaluation model of ESM software that it becomes foundation to protect ESM software effectively that develop quality evaluation model of ESM software in this research by integration security administration system that gather fire wall, IDS, VPN etc. various kind of security solution by one. That is, because reflecting requirement of ESM software, develop evaluation module and proposed evaluation example along with method of exam.

• Journal of Information Technology Services
• /
• v.10 no.4
• /
• pp.191-204
• /
• 2011

Recently, many software companies are trying to improve the software quality and project outcome with more costs and efforts in development time. In the software convergence and integration environments, it is required efforts to gain high quality of software. In other words, it is required to utilize software engineering knowledge and technology for higher software quality and better software project productivity. The Software development productivity can be varied by software process capability according to building a framework for software development, selection and use of appropriate technology, human resource management. Software process capability will influence software project outcome which is the general opinion. This study provides empirical evidence about software engineering efforts and investment approach to lead software project performance. We measured the software engineering efforts by SW engineering level and analyzed the corelation between software engineering level and schedule deviation. And, we verified that this performance is affected by the size of software company. As a result, software process capability is important to build a infrastructure and develop systematically software project. The higher software engineering level can lead to improved software project performance.

• The KIPS Transactions:PartD
• /
• v.11D no.7 s.96
• /
• pp.1459-1466
• /
• 2004

As the area of software application is increased. the software is becoming larger and more complex. In addition, development of the high quality software within the limits of the budget is strongly demanded. Many methodologies, such as software process improvement, object-ori-ented development, requirement-engineering, and software metrics have been introduced in the software development process in order to attain such objectives. Among those techniques. Requirements-Engineering gives basic guideline to develop high quality software. In other word. in order to develop high quality software, requirements should be elicited, and described. And with proper reviews and management. the quality of requirements can be improved. In this paper, quantitative measurement method that is based on IEEE Std-830-1998 for the require-ment-specifications is proposed.

• Journal of the Korea Convergence Society
• /
• v.8 no.10
• /
• pp.37-43
• /
• 2017

In this paper, we propose a method for estimation software quality in terms of software test data, and it is necessary to predict the period of time required for software test evaluation. We need a model to understand of estimation of software quality. In this paper, we propose a model to estimate the number of days for software test using the data obtained through the tester's sex, and present a model for analysing the number of errors according to six quality characteristics by software type.

• Journal of Convergence for Information Technology
• /
• v.12 no.5
• /
• pp.15-20
• /
• 2022

This research studied the evaluation of reliability among the software quality characteristics: suitability, reliability, usability, portability, maintainability, performance efficiency, security, and compatibility. It proposes a quantitative evaluation of reliability in the measurement of software quality. This study introduces a method for measuring the failure rate included in maturity during reliability evaluation, which is one of the characteristics of software quality, and is a study with experimental data on how the failure rate changes depending on the form of failure data. Focusing on software testing, the failure rate was measured and compared according to the type of failure data by applying it to the software reliability growth model, focusing on the number of failures per day. The failure rate was measured around the failure time found through the 6-day test, and the failure rate was compared with the failure rate proposed by the international standard ISO/IEC 25023 using the measurement results, and the application was reviewed according to the data type.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.103-110
• /
• 2002

In component-Based Software Development, the quality of indivisual component is play an important role in quality decision of the whole software. So we need the practical strategy for component testing. In general, component testing can divide focus into producer position and consumer position. In this paper, because the consumer position uses output of the producer position, testing domain is deployed in the producer position. We propose RUP based five step testing processes for component quality evaluation and implements a case study of EJB environment for appling our testing process. This paper shows that proposed five step processes are applicable to component quality evaluation.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2006.05a
• /
• pp.241-244
• /
• 2006

소프트웨어 품질 평가를 위해서 국제 표준 ISO/IEC 9126의 표준문건은 현재 ISO/IEC 25000 이란 이름으로 새롭게 제정되어지고 있다. 본 논문에서는 소프트웨어 품질 평가를 위한 국제 표준 문건의 신뢰성의 평가 방안에 대한 연구의 진행사항을 소개하고 신뢰성의 품질 평가를 위한 표준 제정 연구를 위한 기초 자료를 제시한다. 신뢰성 성장 모델을 소개하고 소프트웨어 신뢰성 성장 모델에 적용하여 평가할 수 있는 방안을 소개한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2005.11a
• /
• pp.337-340
• /
• 2005

소프트웨어 품질 평가에 대한 관심이 고조되면서 소프트웨어 품질 평가를 위한 방법은 국제적으로 활발히 연구되고 있다. 국내의 시험 평가 기관에서는 대체적으로 ISO/IEC 9126에 의한 품질 평가 방법을 적용하여 소프트웨어 품질을 평가하고 있으나 현재 국제적으로 소프트웨어 품질 평가를 좀더 정량적으로 정확히 하기 위하여 평가 메트릭을 새롭게 제정하기 위한 연구를 진행 중에 있다. 국내에서도 이와 같은 소프트웨어 품질 평가를 위한 모델 연구가 필요할 것으로 보여지며 이러한 기초자료로 현재 진행되어지고 있는 국내외 소프트웨어 품질 평가 표준화 동향 조사를 본 연구에서 진행하였다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2011.04a
• /
• pp.1398-1400
• /
• 2011

2000년 초에 PC간 인터넷을 통한 음성통화를 시작으로 최근에는 스마트폰의 전용 애플리케이션까지 VoIP 기반의 음성통화 서비스가 발전해왔다. 이에 따라, VoIP를 통한 외부 공격 및 침입에 대한 사례가 발생되고 이를 해결하기 위한 보안 소프트웨어들이 나오기 시작하였다. 일반적으로 VoIP기반의 소프트웨어에 대한 품질 기준은 사용자의 통화품질이 최우선 이었다. 하지만, GS시험.인증 과정을 통해 VoIP 보안 소프트웨어가 통화품질에는 직접적인 영향을 미치지는 않지만 전체 운영 시스템에 미치는 영향을 확인하고, 시험 중 발생한 문제에 대한 해결 방안 제시를 통해 VoIP의 품질을 향상시킬 수 있었다.