• Proceedings of the Safety Management and Science Conference
• /
• 2006.04a
• /
• pp.525-544
• /
• 2006

This paper is to introduce guidelines for project quality management system. International standards such as ISO 10006, IEC 62198, ISO/IEC TR 16326 and ISO 15188 are considered. This study is to discuss guidelines for quality management in projects, and application guidelines for project risk management, and guide for the application of ISO/IEC 12207 to software project management, and project management guidelines for terminology standardization.

• Proceedings of the Korean Institute of Navigation and Port Research Conference
• /
• 2022.06a
• /
• pp.88-90
• /
• 2022

For the quality management of software developed in Marine digital AtoN Information management and service system development project, an international standard-based quality process and a project management system-based communication and information sharing system were established. In addition, high-quality software development is achieved by monitoring the status of project output creation and supporting software quality inspection and verification.

• The KIPS Transactions:PartD
• /
• v.11D no.6
• /
• pp.1277-1286
• /
• 2004

The concern and request of high-quality software has been increased according to the rapid transition of society to information-oriented era. Therefore activities of software quality management are regarded as serious as the activities of software development. Moreover, stakeholder of software may have various views of software quality. And some quality characteristics need to be managed with priorities in Software Development Life Cycle (SDLC). Hence we recognized that weights of quality characteristics might be useful to improve efficiency of quality management activities. However, this topic has not actively issued because its necessity and effectiveness has been ignored. This paper presents a technique to decide weights of software quality characteristics in SDLC. It is based on ISO/IEC 9126 which is the standard for software product quality. It is accomplished by questionnaires intended for stakeholder in software development and weight analysis through AHP (Analytic Hierarchical Process) method. Accordingly, it can select quality characteristics by weight in SDLC. And then it helps us to acquire high duality software through measuring software quality quantitatively and expecting the quality after completion of software development.

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

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

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.22 no.1
• /
• pp.87-93
• /
• 2021

As the portion of modern weapons systems equipped with electronic components increases, the presence of embedded software has also increased, subsequently drawing interest in quality management and development methods. Unlike mechanical systems, software is logically intangible, hard to troubleshoot, and hard to reuse, making it hard to utilize limited resources when exposed to failures. The United States had successful results in establishing the Capability Maturity Model (CMM) by studying and applying separate processes for development and quality management of defense software. South Korea has also established, and utilizes, a standard of development and quality management for defense software based on international standards. However, some say those standards still remain at a basic level, and should be modified along with the progress in software. If the standard stays at a basic level, compared to software progression, the cost to reuse and restore resources will increase exponentially. This paper discusses improvement in the test processes for defense software through the Test Maturity Model-integration (TMMi)-derived from the CMM-and presents a blueprint for defense software quality management.

• Plant Journal
• /
• v.6 no.2
• /
• pp.56-61
• /
• 2010

In this paper, an integrated management software is developed to promote the business competitive power. The interoperability among the software accounts for an ever growing performance of petrochemical plant project. If the interoperability is built up, company has taken advantages of quality, schedule, cost, and safety by active communication. The advantage of an integrated management software is examined in three aspects. In efficiency aspect, It takes advantage of the saving about the various information and the standard of project performance procedure. In quality, the integration gave aid to a quality improvement through team collaboration and data management within project life cycle. In cost, poor communications between systems waste 30% of project costs. If information could be inputted once and used by all, reductions in delivery time up to 40% were possible. Therefore, 10% savings of engineering cost was also possible.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.5 no.4
• /
• pp.263-272
• /
• 2009

Nowadays, lots of software that have similar functions is being produced. Hence it is getting more important to select the best and suitable software for each individual or company. Moreover, there are few trustworthy materials regarding to the objective procedure and criteria for the best evaluation of the software quality. To overcome these problems, benchmarking has been carried out. However, benchmarking is also confronting the limit of quality evaluation verification due to the difficult of the objectification of the major test items. To solve these problems, some others try to evaluate the quality of software using objective criteria of evaluation based on ISO/IEC standards. Nevertheless, this method using these defined evaluation items and criteria may result in not very reliable outcome. Therefore, this paper offers the evaluation items reflected in the characteristics of each software in order to prove the validity of the proposed method. Moreover, the objective and quantitative criterion which analyzes and reflects the organization characteristics using AHP methodology is applied to the experiment and performance evaluation. Hence we expect that the proposed method provides the needs of the re-establishment of software quality evaluation criteria and the improvement of process in terms of management.

• Asia pacific journal of information systems
• /
• v.20 no.2
• /
• pp.87-101
• /
• 2010

Software as a service (SaaS) is one of the most-talked about trends in IT. Unlike traditional perpetual licensing model, software applications are sold on subscription bases and services are provided over web by the vendors. It is said that SaaS can make vendors to invest more on R&D than on marketing while offering its customers better quality software applications at lower costs. By empirically comparing vendors providing their software applications either by SaaS or by traditional perpetual licensing model, we examine whether or not SaaS really increases overall customer benefits in terms of cost efficiency, software quality, and customization. We show that SaaS may not provide better quality or cost efficient software applications than perpetual licensing does. Then we provide two practical tools which are useful for customers to evaluate whether SaaS is better than perpetual licensing for the purposes of software applications they want to adopt.

• Proceedings of the Safety Management and Science Conference
• /
• 2001.11a
• /
• pp.151-155
• /
• 2001

This paper presents the interrelationship chart between software quality characteristics and engineering attributes. The software quality characteristics and their subcharacteristics are excerpted front IS0/1EC 9126 standards, and the engineering attributes are from Deutsch and Willis[4]. Based on the previous studies and subjective judgement, trisected interrelationship(strong, medium, weak) between these two groups are derived. The results are summarized in a table, and can be used as a quick reference guide to the software quality engineering applications such as quality evaluations for software products, selection of key engineering attributes for high-quality software production, and so forth.