• International Journal of Quality Innovation
• /
• v.7 no.1
• /
• pp.90-97
• /
• 2006

The process of producing software differs in many aspects from that of traditional manufacturing. Software is not manufactured in the classical sense. Development of software more closely resembles the development effort that goes into design new product [1-3]. In this article, we first describe the foundations of process improvement, which all processes can share. The process improvement differences between software and manufacturing process are then discussed, and a defect driven process inspection and improvement is introduced. Based on the discussion, two experiments were designed and the results of the results were collected. Through the comparison, we found that some efficient quality improvement approaches can be easily adapted in the software improvement and that the inspection efficiency is also significant.

• 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.

• 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.

• 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.

• 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.

• The Journal of the Korea Contents Association
• /
• v.9 no.7
• /
• pp.110-120
• /
• 2009

Recently raising the recognition and it joins in about software quality evaluation and authentication and the recognition is augmented in about importance of the high quality security which leads a quality investment from the software development enterprise. The quality investor do to become accomplished but substantially from which degree level, quality investment it leads and the verification of software quality improvement does not become accomplished substantially and with without being it does and wants the enterprises where are clear the quality improvement which leads a quality investment does not set the direction where the problem occurs. From the research which it sees international ISO/IEC 9126 where it is standard and in about software test ISO/IEC 12119 where it is a guide it constructed the metric in base and software tentative instance it led and is accumulated and the defect data which it analyzed. result escape it investigated/to analyze quality level and it analyzed is weak from development process part and a defect level and the quality rating instance of Middleware] software and escape a disposal plan it investigated. The research which it sees it leads and it induces it is quantitative/that there is a possibility of being sufficient it sees the quality increase of Middleware software and the demand which is qualitative.

• 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.

• 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.

• 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.

• 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.