• Journal of Korean Society for Quality Management
• /
• v.47 no.1
• /
• pp.151-162
• /
• 2019

Purpose: This study is in order to secure high quality of military supplies, it is important to secure design quality in the development phase. I will review how to establish a quality assurance system in the development phase based on the author's seminar presentation contents and application example of Hanwha Systems Co., Ltd. Methods: To guarantee design quality in the development phase, in 2002, quality assurance system that is adequate for SQA(Software Quality Assurance)'s requirements of CMM(Capability Maturity Model) was conduct. In 2009, based on the CMMI(Capability Maturity Model Integration) Level 5, there has been continuous and reenforced quality assurance activities. Results: By suggesting the construction and a case study on application of R&D quality assurance, it would be helpful for companies aiming to construct or enhance quality assurance system. Conclusion: To secure high quality for military supplies, a development QA system should be established to secure quality in the development phase. In addition, Total life cycle QA system for development, mass production and operation phase should be reestablished.

• Proceedings of the KSR Conference
• /
• 2007.11a
• /
• pp.638-645
• /
• 2007

Computers are increasingly being introduced into safety and reliability critical systems. The safe and reliable operation of these systems cannot be taken for granted. Malfunctions of these systems can have potentially catastrophic consequences and they have already been involved in serious accidents. Software fault prevention, fault tolerance, fault removal and fault forecasting are the techniques to be used, implemented and verified for embedded software in critical systems as the contributors to safety and reliability of the software. To use them when developing a software product, a relationship must be established between them and the development processes, the methods and techniques to be used to develop software, as well as with the different product architectures. Railroad signaling system software is a safety-critical embedded software with realtime and high reliability requirements. The primary purpose of the safety management is to prevent the loss of lives or physical damages arising from potential hazards in the railroad signaling system. This study provides a systematic approach to analysis of potential hazards for their management during the system life cycle to assure the identification and definition of the most appropriate hazards.

• Journal of the Korea Society of Computer and Information
• /
• v.17 no.1
• /
• pp.53-60
• /
• 2012

In this paper, we propose a framework which supports the simple development cycle based on Distributed System using IPO(Input-Process-Output) model. In our proposed framework, once a single class with Input, Process and Output functions is developed, it can be executed like a single application in both presentation layer and middle layer of a distributed system. Our proposed Framework removes dependency on distributed system and makes development cycle decreased from Develop-Build-Deploy-Test cycle to Develop-Test cycle when application programs is developed. The verification of productivity and performance is performed by comparing our Framework with distributed system or lightweight Framework. The results show high productivity due to the considerable amount of reduction in lines of source code and reduction in dependency on distributed system, and show stabler performance than lightweight framework.

• Journal of Digital Convergence
• /
• v.13 no.12
• /
• pp.319-324
• /
• 2015

This paper proposes an integrated management system for products of game software development. Those products generated over software life-cycle are generally huge in numbers, various in kinds and interconnected in relationships among them. Especially they are highly complex and tightly coupled each other because they are used to build another world which is composed of multi-modal data such as graphics, sound, logics and so on. Therefore it is critical to manage development products in an integrated manner to guarantee the quality of software. The proposed system is designed to provide project/requirement/configuration/traceability management capabilities and interfacing to CASE standards. To achieve the objective, it is based on data warehouse technologies which provide central repositories of heterogeneous data, multi-aspect reporting&analysis capabilities, traceability, verification, etc.

• The KIPS Transactions:PartD
• /
• v.9D no.5
• /
• pp.865-876
• /
• 2002

Successful project planning relies on a good estimation of the effort required to complete a project, together with the schedule options that may be available. Existing software effort estimation models are present only the total effort and instantaneous effort function for the software life-cycle. Also, Putnam presents constant effort rate in each phase. However, the size of total effort varies according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in each phase also differs from one project to another. This paper suggests models for effort allocation in planning, specifying, building, testing and implementing phases followed by the project size and development types. These models are derived from 155 different projects. Therefore, these models can be considered as a practical guideline in management of project schedule and effort allocation.

• The KIPS Transactions:PartD
• /
• v.15D no.3
• /
• pp.313-320
• /
• 2008

A typical software development life cycle consists of a series of phases, each of which has some ability to insert and detect defects. To achieve desired quality, we should progress the defect removal with the all phases of the software development. The well-known model of phase-based defect profile is Gaffney model. This model assumes that the defect removal profile follows Rayleigh curve and uses the parameters as the phase index number. However, these is a problem that the location parameter cannot present the peak point of removed defects when you apply Gaffney model to the actual situation. Therefore, Gaffney model failed to represent the actual defect profile. This paper suggests two different models: One is modified Gaffney model that introduce the parameter of Putnam's SLIM model to replace of the location parameter, the other is the growth function model because the cumulative defect profile shows S-shaped. Suggested model is analyzed and verified by the defect profile sets that are obtained from 5 different software projects. We could see from the experiment, the suggested model performed better result than Gaffney model.

• The KIPS Transactions:PartD
• /
• v.9D no.2
• /
• pp.259-266
• /
• 2002

The main issue in software development is the ability of software project effort and cost estimation in the early phase of software life cycle. The regression models for project effort and cost estimation are presented by function point that is a software sire. The data sets used to conduct previous studies are of ten small and not too recent. Applying these models to 789 project data developed from 1990 ; the models only explain fewer than 0.53 $R^2$(Coefficient of determination) of the data variation. Homogeneous group in accordance with project delivery rate (PDR) divides the data sets. Then this paper presents general effort estimation models using project delivery rate. The presented model has a random distribution of residuals and explains more than 0.93 $R^2$ of data variation in most of PDR ranges.

• Journal of Internet Computing and Services
• /
• v.20 no.3
• /
• pp.1-11
• /
• 2019

Today's software systems are becoming larger and more complicated, and the risk of accidents and failures have also grown larger. Software failures and accidents in industrial fields such as automobiles, nuclear power plants, railroad industries, etc. may lead to severe damage of property and human life. The safety-related international standards, such as IEC 61508 have been established and applied to industries for decades. The safety life cycle specified in the standards emphasize the activities to develop safety requirements through hazard and risk analysis in the early stage of software development. In this paper, we propose 'Hazard Analysis Process based on STPA using SysML' in order to ensure the safety of software at the early stage of software development. The proposed hazard analysis can be effectively performed minimizing the loss of hazard by using the BDD and the IBD of SysML to define the control structure of a system. The proposed method also improves the specification of the safety constraints(requirement) by using SD. As a result, it is possible to identify the hazard without missing and identify the hazard scenarios in detail, and safety can be sufficiently ensured in the early stage of software development.

• Journal of the Korean Society of Systems Engineering
• /
• v.17 no.2
• /
• pp.91-97
• /
• 2021

User interface for cancer classification system is a software application with clinician's friendly tools and functions to diagnose cancer from pathology images. Pathology evolved from manual diagnosis to computer-aided diagnosis with the help of Artificial Intelligence tools and algorithms. In this paper, we explained each block of the project life cycle for the implementation of automated breast cancer classification software using AI and machine learning algorithms to classify normal and invasive breast histology images. The system was designed to help the pathologists in an automatic and efficient diagnosis of breast cancer. To design the classification model, Hematoxylin and Eosin (H&E) stained breast histology images were obtained from the ICIAR Breast Cancer challenge. These images are stain normalized to minimize the error that can occur during model training due to pathological stains. The normalized dataset was fed into the ResNet-34 for the classification of normal and invasive breast cancer images. ResNet-34 gave 94% accuracy, 93% F Score, 95% of model Recall, and 91% precision.

• Journal of The Korean Association of Information Education
• /
• v.11 no.4
• /
• pp.483-495
• /
• 2007

In this paper, to establish a way controlling educational contents, range of contents for quality control are offered. And a life-cycle suitable for present circumstance has defined and successive quality control process has suggested supporting development and use of the contents through analyzing the life cycle of its software and previous contents. A life cycle is defined as whole process from formation of contents to its extinction. The developing process includes stages of planning, designing, manufacturing, and the applying process includes evaluation, circulation and management. Suitable quality control guidelines for each process have established and offered. Aim of this paper is also to develop a model which is applicable to developers as well as supporters who help the developing process.