• Corrosion Science and Technology
• /
• v.23 no.2
• /
• pp.131-138
• /
• 2024

This paper introduces Primetals Technologies' Through-Process Optimization (TPO) Services and Through-Process Quality Control (TPQC) System, which integrate domain knowledge, software, and automation expertise to assist steel producers in achieving operational excellence. TPQC collects high-resolution process and product data from the entire production route, providing visualizations and facilitating quality assurance. It also enables the application of artificial intelligence techniques to optimize processes, accelerate steel grade development, and enhance product quality. The main objective of TPO is to grow and digitize operational know-how, increase profitability, and better meet customer needs. The paper describes the contribution of these systems to achieving operational excellence, with a focus on quality assurance. Transparent and traceable production data is used for manual and automatic quality evaluation, resulting in product quality status and guiding the product disposition process. Deviation management is supported by rule-based and AI-based assistants, along with monitoring, alarming, and reporting functions ensuring early recognition of deviations. Embedded root cause proposals and their corrective and compensatory actions facilitate decision support to maintain product quality. Quality indicators and predictive quality models further enhance the efficiency of the quality assurance process. Utilizing the quality assurance software package, TPQC acts as a "one-truth" platform for product quality key players.

• Journal of Korea Multimedia Society
• /
• v.21 no.9
• /
• pp.1099-1109
• /
• 2018

Most of the automotive electronic systems are equipped with control software. ISO 26262 standard has been published to prevent unreasonable risk due to E/E system malfunction. And many automotive companies apply ISO 26262 for safe series product. In ISO 26262 standard, the product quality improves through deductive and inductive safety analysis in all processes including system and software development phase. However, there are few studies on software safety analysis than systems. In the paper, we study the software FMEA(Failure Mode Effect Analysis) technique for product quality of vehicular embedded software. And we propose an effective guideline of software FMEA as EPB industrial practice.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.40 no.3
• /
• pp.27-37
• /
• 2017

As the global uncertainty of manufacturing has increased and the quality problem has become global, the recall has become a fatal risk that determines the durability of the company. In addition, as the convergence of PSS (product-service system) product becomes common due to the development of IT convergence technology, if the function of any part of hardware or software does not operate normally, there will be a problem in the entire function of PSS product. In order to manage the quality of such PSS products in a stable manner, a new approaches is needed to analyze and manage the hardware and software parts at the same time. However, the Fishbone diagram, FTA, and FMEA, which are widely used to interpret the current quality problem, are not suitable for analyzing the quality problem by considering the hardware and software at the same time. In this paper, a quality risk assessment model combining FTA and FMEA based on defect rate to be assessed daily on site to manage quality and fishbone diagram used in group activity to solve defective problem. The proposed FTA-FMEA based risk assessment model considers the system structure characteristics of the defect factors in terms of the relationship between hardware and software, and further recognizes and manages them as risk. In order to evaluate the proposed model, we applied the functions of ITS (intelligent transportation system). It is expected that the proposed model will be more effective in assessing quality risks of PSS products because it evaluates the structural characteristics of products and causes of defects considering hardware and software together.

• Journal of Convergence Society for SMB
• /
• v.1 no.1
• /
• pp.19-28
• /
• 2011

In today and near future, most of the commercially manufactured IT products will be evolved into software convergence product. Recently, the embedded software products is called as 'Software Convergence Products.' This phenomenon does not simply show the trendy fashion, but has the seriously implication that the functionalities of IT product is accomplished and evolved via software technology, not via mechanical nor electrical means. It will become true that the quality of the convergence product is dominantly governed by the software it uses. Meanwhile, we are facing with the threatening fact that software defects in the mass products will requires tremendous amounts of cost proportional to the quantity of the product. We can remind ourselves of the disasters that have been already happened, such as Automotive recalls, Smart-phone recalls, and others. In software engineering, there have been large amount of work done in software quality improvement for the past couple of decades. Software process improvement, and testings are the representative ones. But we are facing with limitations of those traditional approaches in current convergence industry; exponentially increasing software sizes and rapid changes in software technology. In this paper, we analyze the characteristics of the software convergence industry, the limitations of the traditional Software quality improvement approaches. We suggest a new approaches in software quality improvement in different angles of thought and philosophy.

• Management & Information Systems Review
• /
• v.25
• /
• pp.275-296
• /
• 2008

We tested the relationship of elements in influence about software performance. our research is detect the significant element in the software system. we affronted to find relation elements with software quality and seek what relationship is the most important in performance activity. this study's result will be useful for them ; first, give to product a high quality guide line to software developer. second, it will be use for basic information about in software examine research.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.31 no.4
• /
• pp.100-105
• /
• 2008

Cost reduction, time to market, and quality improvement of software product are critical issues to the software companies which try to survive in recent competitive market environments. Software Product Line Engineering (SPLE) is one of the approaches to address these issues. The goal of software product line is to maximize the software reuse and achieve the best productivity with the minimum cost. In software product line, software components are classified into the common and variable modules for composition work. In this paper, we proposed a dynamic composition process based on aspect-oriented programming methodology in which software requirements are classified into the core-concerns and cross-cutting concerns, and then assembled into the final software product. It enables developers to concentrate on the core logics of given problem, not the side-issues of software product such as transactions and logging. We also proposed useful composition patterns based on aspect oriented programming paradigm. Finally, we implemented a prototype of the proposed process using Java and Aspect to show the proposed approach's feasibility. The scenario of the prototype is based on the embedded analysis software of telecommunication devices.

• KIPS Transactions on Software and Data Engineering
• /
• v.3 no.1
• /
• pp.1-6
• /
• 2014

Many companies have tried to adopt Software Product Line Engineering for improving the quality and productivity of information systems and software product. There are several models defined in software product line methodology and each model has different abstraction level. Therefor it is important to maintain the traceability and consistency between models. In this paper, consistency checking rules are suggested by traceability matrix of work products.

• Journal of Information Technology Applications and Management
• /
• v.27 no.2
• /
• pp.37-50
• /
• 2020

This paper is very exploratory and addresses the issue 'Is a general quality model of software possible?'. If possible, how specific can/should it be?' ISO 25000 Series SQuaRE is generally regarded as a general quality model which can be applied to most kinds of software. Usability is one of the 8 characteristics of SQuaRE's Product Quality Model. It is the main issue associated with SQuaRE's Quality in Use Model too. it is the most important concept associated software quality since using is the only ultimate goal of software products. Playability, however, is generally regarded as a special type of usability, which can be applied to game software. This common idea contradicts with the idea that SQuaRE is valid for most kinds, at least many kinds, of software. The empirical evidences of this paper show that SQuaRE is too specific to be a general quality model of software.

• 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 the Korea Academia-Industrial cooperation Society
• /
• v.16 no.1
• /
• pp.691-696
• /
• 2015

The interest in software defects is growing. Companies are working on reducing them by various ways with a software development part, customer service part and quality management part. The defect data collected from them will be analyzed according to the condition and purpose to minimize the defect, and it will contribute to improving the quality of products. This study analyzed the software defect progress for companies based on the test maturity model, and set up the defect preventing process. They were applied to the project, and the number of defects decreased from 106 to 16. This study focused on the existing defect, which is a basic requirement for software quality management, and have importance by presenting a way to improve the software product quality with minimum resources.