• Journal of KIISE:Software and Applications
• /
• v.26 no.12
• /
• pp.1455-1467
• /
• 1999

소프트웨어 품질을 정의하기 위한 여러 가지 소프트웨어 품질 모형(SQM : Software Quality Model)이 개발되어 왔다. 이 모형들은 두 가지 목적을 가진다. 한 가지는 소프트웨어 품질 측정이고, 또 다른 목적은 개발 프로세스에서의 소프트웨어 품질 제어이다. 국제 표준인 ISO/IEC 9126은 소프트웨어 측정을 위한 소프트웨어 품질 모형을 제시하였다. ISO/IEC 9126의 품질 모형은 사용 관점에서 소프트웨어 품질을 정의한 모형이다. 이 모형은 개발 프로세스에서의 품질 제어를 하는 측면에서는 불완전한 모형이다. 소프트웨어의 품질이 프로세스 내에서 어떻게 만들어지는지 볼 수 없는 모형이기 때문이다. 따라서, 개발 관점에서의 소프트웨어 품질 모형이 필요하다.본 논문에서는 사용 관점인 ISO/IEC 9126 품질 모형을 기반으로 하여 개발 관점에서의 소프트웨어 품질 모형을 제안한다. 이 모형은 ISO/IEC 9126과 같이 하위 품질 요소가 중복되지 않는 계층적 품질 모형이면서, 개발 프로세스 내에서 제어 가능한 제품 특성에 기반을 둔 개발 관점의 소프트웨어 품질 모형이다. 본 논문에서는 소프트웨어 품질 모형 구축 시, 품질 속성간의 선후조건관계를 설정하여 품질 속성간 중복되었던 제품 특성을 한 품질 속성 내 귀속시킨다. 품질 속성 별 제품 특성을 기반으로, 프로세스 내에서 제품 특성을 측정하는 메트릭스를 제안한다. 본 논문에서 제안한 품질 모형과 ISO/IEC 9126을 비롯한 기존 품질 모형과 비교 분석한다.Abstract Several SQMs(Software Quality Models) have been developed to define a software quality. These models have two goals. One is to measure a software quality, the other is to control a software quality. The SQM of ISO/IEC 9126 is defined from the user's viewpoint. This model is an incomplete model in controlling a software quality in the development process. Since this model cannot show how to build a high quality software, the SQM of the developer's view is needed.We suggest the SQM of the developer's view. This model is a completely hierarchical model and is based on product properties. For this model, we define implicative relations among quality attributes for 1:m relations of quality attributes and product properties. So, we solve the problem of a quality attribute overlapping with other quality attributes. We suggest metrics based on our SQMs. Further, we evaluate our SQM by comparing our SQM with other SQMs.

• Journal of Korean Society for Quality Management
• /
• v.13 no.2
• /
• pp.61-65
• /
• 1985

The quality of a final SOFTWARE PACKAGE depends on many complicated factors in the software development process. This paper describes ststistical methods for establishing relationships between final quality and development process factors. The final software quality is represented by the number of errors through the system test phase. The data presented here were gathered during the course of a real IS-month development project. Regression theory is used for data analysis. Some of the interesting results include the observation that specification changes during the development process have an adverse effect on final software quality.

• The KIPS Transactions:PartD
• /
• v.9D no.4
• /
• pp.629-638
• /
• 2002

As the application area of software grows bigger and the importance of software quality increases, software quality evaluation method is also getting a lot of attention. To evaluate the software quality properly, we need an objective and concrete evaluation mechanism. In general, practitioners customize the international standards to their own needs for this purpose. Package software documents plat an important role in software quality evaluation because it provides the information that helps customers use the software effectively and conveniently. h great deal of efforts has been made in terms of international standards for documentation and documentation process. However, those international standards are too abstract to be applied directly to domestic software packages. In this paper, we developed a guidelines and checklists for writing and evaluating package software documents. Our research basically followed ISO 12119, ISO 9127 and some related research results. Also we proved the effectiveness of this research through actual tests with package softwares.

• Information Systems Review
• /
• v.6 no.2
• /
• pp.195-208
• /
• 2004

In this paper we propose a new software project development management model incorporating quality management to schedule management. Though many efficient techniques such as code review and inspection are used to remove defects, the effect of defect removal time on project schedule hasn't been studied much. However, poor quality management has an important effect upon overall schedule and sometimes software projects fails due to it. Thus, quality management and schedule management should be considered together and we need to reflect the time to maintain software quality into the schedule management. For the proposed model we introduced "Quality Value" representing the needed time to remove software defects. We assume PSP/TSP to gather the needed data for quality value. The proposed model can be used to predict the effect of software defects on schedule in advance and to prevent schedule lag.

• Journal of KIISE
• /
• v.42 no.7
• /
• pp.878-888
• /
• 2015

Software project planning includes several processes for estimating the effort required to complete software project tasks, allocating human resources to tasks, and creating a project plan. Because software planning is becoming more complicated as the size of software projects grow, it is difficult for project managers to decide on a reasonable project plan. To help them, many automatic software project planning approaches have been proposed. The approaches all focus on minimizing project duration. But if the plan is simply to minimize the duration, without considering software quality, the plan can harm the eventual software quality. In our research to create a reasonable project plan, we consider software quality as well as duration of the project, by defining a software quality score. The project manager can plan the project to maximize software quality for a specific project duration.

• International journal of advanced smart convergence
• /
• v.9 no.4
• /
• pp.149-155
• /
• 2020

In the software industry of Korean Small and Medium-sized Enterprise(SME)s, the development process is often not mature. This may lead to failures in quality control and output management. As a result, the quality of the software can be degraded. To solve the problem, the software visualization technique, which is from the National IT Industry Promotion Agency Software Engineering Center can be applied. We have experienced with mentoring not only the visualization of software development process, but also various visualization process of SMEs. However, the existing software visualization method was difficult to install environment and its time cost was high. This paper proposes a software visualization environment through a cloud service along with a case of building a software visualization environment. We expect that this method will make it easier to build a visualization environment and improve the quality of SME software.

• Asia-Pacific Journal of Business Venturing and Entrepreneurship
• /
• v.4 no.1
• /
• pp.29-65
• /
• 2009

This study is The Effect of the on the purchase behavior of the Software Quality. To have purchased the software in a Consumer surveys were conducted. The following is a summary of results of this research. First, the software quality and significant consumer purchasing behavior (+) of influence. Functionality, usability, portability of software quality attributes the impulse buying and buy more of both the (+) showed the influence. Second, software quality is urge consumers to purchase significant (+) of influence. Functionality, reliability, usability, portability of software quality (+) showed the influence. Third, the software quality In the consumer buy more significant Chung (+) showed the influence. Software quality, functionality, usability, portability name (+) influence. In conclusion, the quality of the software in consumer purchasing behavior (+) were of significant influence. In particular, factors that functionality, usability factors, portability factor in the relatively large influence on the purchasing behavior. Software technology development, planning, development, testing, and in each step must keep in mind the following. First, the software, when used in certain conditions, Inherent ability to meet the needs and requirements set forth to provide the appropriate functionality and accuracy as the ability of software products each other with the capabilities to the effective and thorough security features should be required. Second, software, a user-specified criteria to use in understanding and learning, and must, and the ability to prefer. Software for users to understand and easy to use, whether the check. In particular, understanding the interface, Help understanding, understand the input and output data, and interface consistency, the user information, the message must be equipped and easy to understand. In addition, ease of learning to be self-learning, and help ease of access shall be required. Third, in certain circumstances, a different environment to transfer be equipped with the functionality of the software. Applying data structures and application environment, helping transplant convenience must keep in mind sex.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.1 no.1
• /
• pp.55-62
• /
• 2000

Factory automation of enterprise has become one of the most important method that acquire competition power. Therefore, it is necessary to evaluate quality of automation software for quality enhancement of factory automation system. duality is affected to technical quality of software in automation of making. In this study, we established a quality evaluation system, evaluation Process and metrics for factory automation software, and implemented quality evaluation tool which can support quality progress of automated software.

• International Journal of Computer Science & Network Security
• /
• v.21 no.7
• /
• pp.284-296
• /
• 2021

Quality Models are important element of the software industry to develop and implement the best quality product in the market. This type of model provides aid in describing quality measures, which directly enhance the user satisfaction and software quality. In software development, the inheritance technique is an important mechanism used in object-oriented programming that allows the developers to define new classes having all the properties of super class. This technique supports the hierarchy design for classes and makes an "is-a" association among the super and subclasses. This paper describes a standard procedure for validating the inheritance metric in Quality Model for Object-Oriented Design (QMOOD) by using a set of nine properties established by Weyuker. These properties commonly using for investigating the effectiveness of the metric. The integration of two measuring methods (i.e. QMOOD and Weyuker) will provide new way for evaluating the software quality based on the inheritance context. The output of this research shows the extent of satisfaction of the inheritance metric in QMOOD against Weyuker nine properties. Further results proved that Weyker's property number nine could not fulfilled by any inheritance metrics. This research introduces a way for measuring software that developed using object-oriented approach. The theoretical validation of the inheritance metric presented in this paper is a small step taken towards producing quality software and in providing assistance to the software industry.

• Journal of Digital Convergence
• /
• v.13 no.10
• /
• pp.1-7
• /
• 2015

Many people are interesting software quality. Because of, we depend on software in our life. In terms of, I think, good software is a good quality software. So, when we develop the software, we need trying to improve software quality. In this paper, we analyze software test data. We emphasize that software quality is very important in our life. We use software experimental data, in order to analyze of software quality. On the basis of ISO/IEC 9126-2, we classify the test data and we analyze the difference of error frequency according to functionality, reliability, usability, efficiency, maintainability, portability. We analyze the number of test and used time according software type. We want to search effect variable, going through testing result and measurement convergence, we know the effect variable of functionality and efficiency.