• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1164-1177
• /
• 2005

As the software development process becomes complicated, software requirements become complicated, too. Many efforts are needed in requirements management. It is impossible to define all requirements of software at first, and the development environment changes as project is gone. As the cost of requirements change management is much more than development cost, the changes should be controled immediately through systematic change management. In this paper, I suggest a method to manage requirements change systematically based on the change management process in software product lines. The requirements change at the application engineering process is analyzed and managed using the domain engineering process because the application requirements are customized from the domain requirements in software product lines. Such the consistent change management helps to make decisions about changes by change impact analysis and alternative solution design. Through this method, the potential change costs can be saved because same change requests are not repeated by controlling the change requests completely.

• Journal of Convergence Society for SMB
• /
• v.6 no.1
• /
• pp.7-15
• /
• 2016

As most devices in a wide range of automotive, aerospace, and missile have built-in software that controls the system behaviors, the safety of the software is growing in its importance. That is, the software safety has emerged as one of big issues because the threat of accidents caused by software malfunction is rising. Accident by software can be occurred from user mal-operation, but the fundamental reason of the accident comes from insufficient verification of the safety in software development process. Therefore, this paper presents how the software safety analysis and management activities should be done in the development process. In particular, we propose how to apply the safety analysis and management activities in the prototype or incremental development process.

• Proceedings of the Safety Management and Science Conference
• /
• 2001.05a
• /
• pp.77-81
• /
• 2001

Burn-in is a test procedure to find and eliminate the inherent initial failure of a product during or at the final stage of production process. Software testing is the validation and verification process which is used to cut off the faults from a software. The two have the common function and objective of "debugging". This article summarizes some significant models on the optimal hardware and software burn-in time, and provides the relevant paper lists. The need for the development of the unified burn-in policy of a hardware-software system is addressed.addressed.

• 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 Korea Society of Digital Industry and Information Management
• /
• v.8 no.2
• /
• pp.1-10
• /
• 2012

In this study, software products developed in the course of testing, software managers in the process of testing software test and test tools for effective learning effects perspective has been studied using the NHPP software. The finite failure nonhomogeneous Poisson process models presented and the life distribution applied exponential and log shaped type hazard function. Software error detection techniques known in advance, but influencing factors for considering the errors found automatically and learning factors, by prior experience, to find precisely the error factor setting up the testing manager are presented comparing the problem. As a result, the learning factor is greater than autonomous errors-detected factor that is generally efficient model could be confirmed. This paper, a failure data analysis of applying using time between failures and parameter estimation using maximum likelihood estimation method, after the efficiency of the data through trend analysis model selection were efficient using the mean square error and coefficient of determination.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.7 no.2
• /
• pp.1-8
• /
• 2011

In this study, software products developed in the course of testing, software managers in the process of testing software test and test tools for effective learning effects perspective has been studied using the NHPP software. The finite failure non-homogeneous Poisson process models presented and the life distribution applied extreme distribution which used to find the minimum (or the maximum) of a number of samples of various distributions. Software error detection techniques known in advance, but influencing factors for considering the errors found automatically and learning factors, by prior experience, to find precisely the error factor setting up the testing manager are presented comparing the problem. As a result, the learning factor is greater than automatic error that is generally efficient model could be confirmed. This paper, a numerical example of applying using time between failures and parameter estimation using maximum likelihood estimation method, after the efficiency of the data through trend analysis model selection were efficient using the mean square error.

• Journal of Information Technology Services
• /
• v.8 no.1
• /
• pp.125-142
• /
• 2009

The Ministry of Information and Communication announced "The Guideline for Management of Software Project" in October 2006. The public employees(acquirer) have to manage software projects with this guideline. The guideline was based on the International standard(ISO/IEC 12207) and IEEE standard(IEEE/EIA 12207), and was developed by considering the domestic software industry environment. The guideline can help to establish a software acquisition process for appropriate management of software projects, and the process can increase the management productivity of software projects. This study provides the explanation about the guideline with terms of 5W1H(who(user), what(summary), when(time to apply), where(domain of application), why(objective), how(method of use)) for understanding of the guideline.

• Nuclear Engineering and Technology
• /
• v.48 no.2
• /
• pp.404-418
• /
• 2016

This paper presents a documentation and development method to facilitate the certification of scientific computing software used in the safety analysis of nuclear facilities. To study the problems faced during quality assurance and certification activities, a case study was performed on legacy software used for thermal analysis of a fuelpin in a nuclear reactor. Although no errors were uncovered in the code, 27 issues of incompleteness and inconsistency were found with the documentation. This work proposes that software documentation follow a rational process, which includes a software requirements specification following a template that is reusable, maintainable, and understandable. To develop the design and implementation, this paper suggests literate programming as an alternative to traditional structured programming. Literate programming allows for documenting of numerical algorithms and code together in what is termed the literate programmer's manual. This manual is developed with explicit traceability to the software requirements specification. The traceability between the theory, numerical algorithms, and implementation facilitates achieving completeness and consistency, as well as simplifies the process of verification and the associated certification.

• International journal of advanced smart convergence
• /
• v.12 no.2
• /
• pp.187-192
• /
• 2023

Currently, our society is showing many changes due to the influence of information and communication technology (ICT). At the center of these information and communication technologies are software, intelligence, and sensing technologies. The software-related industry is steadily developing due to various software development policies implemented by the government and related organizations. Software development is desirable, but on the other hand, some negative aspects are also appearing. In this study, we proposed an objective way to infer the progress of software development for reasonable resolution of cases when a dispute related to the progress of development occurred during the software development process. The proposed solution was based on the waterfall model. The outputs generated in each process of the waterfall model are contents excluded from subjectivity. Therefore, it can be used as an objective method for calculating software development progress.

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.699-704
• /
• 2001

Developing a component-based software requires verified and standardized software components. This paper presents a component quality management (CQM) process. The process was developed and applied to the government-sponsored trial projects that developed software components. The process is composed of four phases：quality specification, quality planning, quality control, and quality evaluation. With this process, we can establish quality goals and focus our efforts on the activities to achieve the goals. A component quality model is also suggested to transform the implicit quality requirements into the measurable quality goals and to be used for the basis when we evaluate the quality of software components against the quality goals.