• Journal of Korea Society of Digital Industry and Information Management
• /
• v.10 no.4
• /
• pp.19-27
• /
• 2014

Software reliability in the software development process is an important issue. Software process improvement helps in finishing with reliable software product. Infinite failure NHPP software reliability models presented in the literature exhibit either constant, monotonic increasing or monotonic decreasing failure occurrence rates per fault. In this paper, proposes the reliability model with log type mean value function (Musa-Okumoto and log power model), which made out efficiency application for software reliability. Algorithm to estimate the parameters used to maximum likelihood estimator and bisection method, model selection based on mean square error (MSE) and coefficient of determination($R^2$), for the sake of efficient model, was employed. Analysis of failure using real data set for the sake of proposing log type mean value function was employed. This analysis of failure data compared with log type mean value function. In order to insurance for the reliability of data, Laplace trend test was employed. In this study, the log type model is also efficient in terms of reliability because it (the coefficient of determination is 70% or more) in the field of the conventional model can be used as an alternative could be confirmed. From this paper, software developers have to consider the growth model by prior knowledge of the software to identify failure modes which can be able to help.

• Communications of the Korean Institute of Information Scientists and Engineers
• /
• v.25 no.11
• /
• pp.39-44
• /
• 2007

• Journal of the Korea Society of Computer and Information
• /
• v.13 no.2
• /
• pp.1-9
• /
• 2008

As the size of software becomes larger and the features of it become complex. it is really hard to successfully complete the project without following development guidelines. Software process is the best practices and procedures that organizations of high maturity and capability of software development carry out in common, and it is a set of progressive ideas of management. However, complicated and unfamiliar concepts can interrupt the introduction and improvement of software process of the organizations. Even though many kinds of frameworks such as standard of process and maturity measurement models are introduced, it is still difficult to follow software process without fully understanding their relations. The purpose of this study is to support successful internalization of organizations that introduce and use software process. It also suggests the design of standard ontology, standard relationship domain ontology, and the lifestyle of software process and the relations between them.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.15 no.7
• /
• pp.4522-4527
• /
• 2014

Info-communication software contains various functions and services. A software test is the only acceptance test step. Recently, however, all development steps have become important. In particular, the software acceptance step is very high, and a study of the effective use of limited time and resources on acceptance step is needed. This study examined the efficiency of the Test Design Technique for Software Test. The proposed Test Design process was applied to the domain systems of info-communication and the degree of improvement was measured. This paper establishes Software Test design process Infrastructure based on the developed software.

• 제어로봇시스템학회:학술대회논문집
• /
• 1987.10b
• /
• pp.667-669
• /
• 1987

This paper deals with the automation of the brewing process using digital computer. The work has been carried out to develop real-time control software for fermentation process. From the application of the system, quality improvement and effective process management are achieved.

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.27 no.10C
• /
• pp.887-901
• /
• 2002

Software management model divided into the software project model and design estimation model, software matrices model, reliability growth model, process improvement model(or process maturity model) etc. Among these software management models, software complexity model make an estimated of the product software. For a practice of software managed, need to guideline of the static analysis of software. Especially, Software complexity model introduced for the estimation of software quantity and program complexity. In case of measurement the software matrices, its need for us to analysis of software quality and products. On the other hand, we known that complexity program include many defects and consuming of source cost. So, we apply to complexity model using of the program complexity, control structure and volume matrices, interface metrics, process complexity metrics method. In this paper, we represent that the analysis of fault data detected during the system test. Also, we analysis of program control structure and interface, volume matrices in various aspect of switching software. Others, their results utilized similar of project and system development.

• 한국IT서비스학회:학술대회논문집
• /
• 2003.11a
• /
• pp.680-696
• /
• 2003

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

• Proceedings of the Korea Contents Association Conference
• /
• 2007.11a
• /
• pp.591-594
• /
• 2007

We construct the test process site about X-Internet and X-Forms base software. This software is developed with X-Forms base web UI tool. Basically, this software is operated on the Client. Even in operating process, this kind of software could be updated because of user's request, improvement in efficiency, reformation and addition in functions and so on. In order to test a updated software, V-Model will be extended and transformed test process will be proposed. This proposed test process is starting with test plan which defines test object and activities for attainment of process's goal. The following steps are recognizing testcase and data, analysis and design for constructing process environment, setting forth testcase in detail, realization of test methodology, and the arrangement of results. This paper will be helpful to build more efficient process site by managing and recording the test process.

• Journal of KIISE:Software and Applications
• /
• v.29 no.9
• /
• pp.619-630
• /
• 2002

The various software engineering techniques have been come out in order to cope with the software crisis since 1980's. The software Engineering has focused on the process of software component development. The process products a development guide for a quality and productive improvement of software. But, most of the methodologies assume that a new system will be constructed and reused in the future. these do not actually support efficiently how we reuse legacy system's resources and construct a new system. In this paper, we present an efficient Reengineering Process for reusing legacy systems, RUP+re, which extends and customizes RUP. Rup+re consists of Reverse Engineering Workflow, Re-Engineering Workflow and forward Engineering Process. We describe RUP+re's workflows with their own detail steps and verify them practically through the case study. So, we provide efficient guidelines to the software Reengineering process construction which reuses the resources of a legacy system.