• Journal of Applied Reliability
• /
• v.13 no.4
• /
• pp.253-271
• /
• 2013

Since The Korean Reliability Society had been founded in 1999, development history of reliability engineering in Korea is reviewed and research outputs and papers from 2008 to current are analyzed in terms of types of industry, product life cycle, hardware vs software, and theory vs application. The purpose of this research is to review the recent reliability engineering research conducted in Korea including development history as well as published papers to identify the weakness and/or deficiencies in order to suggest the future research directions, which would contribute the development of industries in Korea.

• The Journal of Bigdata
• /
• v.4 no.2
• /
• pp.47-59
• /
• 2019

Recently, the RPA (Robotic Process Automation) solution, which has been spreading in Korea and overseas, allows users to easily automate their tasks with the application GUI (Graphic User Interface), and the number of Korean financial companies which Implemented for automating their business is increasing now. However, as the major supervisory regulations that financial institutions must comply with are based on the existing traditional SDLC (Software Development Life Cycle), it is not proper to be directly applied to RPA that automates end-user works on the level of user's system interface. Therefore, in this paper, we organized the important financial supervisory rules and control items that should be considered for RPA implementation, then surveyed 24 financial companies which have implemented RPA for checking how they applied them. Finally, we would like to present the necessity of revision of related compliance.

• Journal of the Korea Computer Industry Society
• /
• v.5 no.1
• /
• pp.9-18
• /
• 2004

Successful project planning relies on a good estimation of the manpower required to complete a project in addition to the schedule options that may be available. Existing software manpower estimation models present the total manpower and instantaneous manpower distribution for the software life cycle. Putnam's Rayleigh and Phillai et al.'s Gamma models present a model with assumption that the manpower is needed at the system delivery. This means that 40 percent of total manpower is applied at the software development, and the other 60% is applied during maintenance phase. However Warburton observes the manpower is needed during development phase with the peak at the completion of the software design phase. So, the existing models were not appropriate to be applied to practical projects. This paper suggests the Sigmoid model which does not consider the point of manpower peak to fix the problem above. The suggested model showed some improvement when practical data was applied. Therefore, the Sigmoid model can be used as alternative of Rayleigh and Gamma model to estimate distribution of manpower during software development phas.

• International journal of advanced smart convergence
• /
• v.10 no.2
• /
• pp.130-137
• /
• 2021

In the current software project, it is still very difficult to extract and define clear requirements in the requirement engineering. Informal requirements documents based on natural language can be interpreted in different meanings depending on the degree of understanding or maturity level of the requirements analyst. Also, Furthermore, as the project progresses, requirements continue to change from the customer. This change in requirements is a catastrophic failure from a management perspective in software projects. In the situation of frequent requirements changes, a current issue of requirements engineering area is how to make clear requirements with unclear and ambigousrequirements. To solve this problem, we propose to extract and redefine clear requirements by incorporating Design Thinking methodologies into requirements engineering. We expect to have higher possibilities to improve software quality by redefining requirements that are ambiously and unclearly defined.

• Proceedings of the KSME Conference
• /
• 2008.11b
• /
• pp.2845-2849
• /
• 2008

Long Term Asset Management(LTAM) means a plan developed by using LCM(Life Cycle Management) process for optimum life cycle management of significant plant assets at each plant across the fleet. As a part of development of LTAM Strategies on nuclear turbines, a method so as to determine the future failure rates for low pressure turbine facilities at a nuclear plant was studied and developed by using both plant specific and industry-wide performance data. INPO's EPIX data were analyzed and some failure rate evaluation values considering preventive maintenance practices were calculated by using EPRI's PM Basis software. As the result, failure rate functions applicable to a priori and a posteriori replacement of low pressure turbines at a nuclear plant were developed and utilized in an assessment of economics of LCM alternatives on the nuclear turbine facilities in the respects of 40-year and 60-year operation bases.

• Management & Information Systems Review
• /
• v.18
• /
• pp.201-222
• /
• 2006

As the competition between countries has become higher and the notion of software quality has been widely spread. it has been necessary to develop technologies that can ensure and produce high quality software. With the advent of information-oriented society. quality control has to transfer to the quality control activities focused on software system instead of those activities focused on hardware system. If so, how do we get to handle the quality control on the basis of the new approach. Also, as software applications have grown. so too has the importance of software quality. In order to manage software quality, the technology to specify and evaluate both the software product quality and development process quality objectively quantitatively is most important. To produce products of good quality, we need a more progressive quality control system according to the need of software development life cycle. In other words, we do software right the first time or build quality in the process. On the basis intermediate and final time or build quality in the process. On the basis of data achieved, we can evaluate the products according to the consequences of the data, What are the problems to contrive the software quality control system?, we con promote the quality of products. To achieved that goal, we con provide a suitable the technique and method of software quality control.

• Journal of Korean Society of Archives and Records Management
• /
• v.5 no.1
• /
• pp.65-77
• /
• 2005

This paper aims to introduce the background history and development of records management in brief prior to and after the 1990s based on the records life cycle. This paper also explains the development of electronic document imaging systems and shifts to ERM systemsin the 1990s. The paper explains functional requirements in archival management and software application standards suggested by the industry of electronic records management. The paper concludes with providing problems and issues associated with software design in electronic records management for further development.

• Management & Information Systems Review
• /
• v.15
• /
• pp.245-262
• /
• 2004

As the competition between countries has become higher and the notion of software quality has been widely spread. it has been necessary to develop technologies that can ensure and produce high quality software. With the advent of information-oriented society. quality control has to transfer to the quality control activities focused on software system instead of those activities focused on hardware system. If so, how do we get to handle the quality control on the basis of the new approach. Also, as software applications have grown, so too has the importance of software quality. In order to manage software quality, the technology to specify and evaluate both the software product quality and development process quality objectively quantitatively is most important. To produce products of good quality, we need a more progressive quality control system according to the need of software development life cycle. In other words, we do software right the first time or build quality in the process. On the basis intermediate and final time or build quality in the process. On the basis of data achieved, we can evaluate the products according to the consequences of the data, What are the problems to contrive the software quality control system?, we con promote the quality of products. To achieved that goal, we con provide a suitable the technique and method of software quality control.

• Proceedings of the Korean Society for Quality Management Conference
• /
• 2004.04a
• /
• pp.114-119
• /
• 2004

Software verification and validation(V&V) is a means to develop high-quality software and assure safety and reliability for software. Also, we can achieve the desired software quality through systematic V&V activities. The software to be applied safety critical system like nuclear power plants is required to setup the V&V methodology that comply with licensing requirements for nuclear power plants and should be performed V&V activities according to it. In this paper, we classified safety-critical, safety-related and non-safety for software according to safety function to be peformed and define V&V activities to be applied software grade. Also, we defined V&V activities, procedures and documentation for each phase of software development life cycle and showed techniques and management to perform V&V. Finally, we propose the V&V framework to be applied software development of SMART(System-integrated Modular Advanced ReacTor) MMIS (Man-Machine Interface System) and to comply with domestic licensing requirements.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.22 no.53
• /
• pp.99-109
• /
• 1999

The International Organization for Standardization(ISO) is a worldwide federation of national standards bodies. Through ISO Technical Committees(TC), various International Standards are being carried out. Each member body interested in a subject for which a TC has been established has the right to be represented on that committee. ISO collaborates closely with the International Electro-technical Commission(IEC) on all matters of electro-technical standardization. ISO established the ISO 9000 Family standard in 1987, and International Standard ISO 9000-3 was worked by ISO/TC 176, Quality management and quality assurance, Subcommittee 2(SC 2), Quality systems, in accordance with the ISO/IEC Directives, Part 3: 1997 Rules for the structure and drafting of International Standards, Many organizations have applied the ISO 9000-3 for their quality system standard in the software sector. That means that ISO 9000-3: 1991 and ISO 9000-3: 1997 have been used successfully by the software industry as the internationally accepted interpretation of ISO 9001 for the development and maintenance of computer software. Additionally ISO 9000-3: 1997 involved how the software life cycle processes defined in ISO/IEC 12207: 1995, Information Technology - Software Life Cycle Processes related to the requirements of ISO 9001:1994. After having performed full reviews of the WD3, CD1, CD2 and DIS drafts of the future ISO 9001:2000, this document will partly replace the part of ISO 9000-3: 1997 for measurement analysis and improvement of quality management system in computer software industry, as an interpretation for organizations and certification bodies, which will be withdrawn when ISO 9001:1994 is replaced by ISO 9001:2000,.