• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.10 no.3
• /
• pp.1404-1415
• /
• 2016

Because of the properties of software such as invisibility, complexity, and changeability, software configuration management (SCM) for software artifacts generated during software life-cycle has been used for guarantee of the quality of the software. However, the existing SCM system has only focused on code artifacts and software development document artifacts such as Software Requirements Specification (SRS), Software Design Description (SDD), and Software Test Description (STD). Moreover, software research-oriented project comes out late the code artifacts and the software development document artifacts. Therefore, there is a need for trace and management of software research document artifacts composed of highly abstracted non-functional requirements like 'the purpose of the project', 'the objectives', and 'the progress' before generation of the code artifacts and the software development document artifacts for a long time. Nevertheless, the existing SCM system cannot trace and manage them. In this paper, we propose content-based configuration management system comprised of the relevance link generation phase and content-based testing phase to trace and manage them. The preliminary application results show applicability and feasibility of the proposed system.

• Electronics and Telecommunications Trends
• /
• v.14 no.4 s.58
• /
• pp.1-9
• /
• 1999

In this paper, we summarize the lessons learned from the applications of the software reliability engineering to a large-scale software project. The considered software is the software system of the TDX-10 ISDN switching system. The considered software consists of many components, called functional blocks. These functional blocks serve as the unit of coding and test. The software is continuing to be developed by adding new functional blocks. We are mainly concerned with the analysis of the effects of these software components to software reliability and with the analysis of the reliability evolution. We analyze the static characteristics of the software related to software reliability using failure data collected during system test. We also discussed a pattern which represents a local and global growth of the software reliability as version evolves. To find the pattern of software of the TDX-10 ISDN system, we apply the S-shaped model to a collection of failure data sets of each evolutionary version and the Goel-Okumoto (G-O) model to a grouped overall failure data set. We expect this pattern analysis will be helpful to plan and manage necessary human/resources for a new similar software project which is developed under the same developing circumstances by estimating the total software failures with respect to its size and time.

• Journal of Software Engineering Society
• /
• v.26 no.1
• /
• pp.17-29
• /
• 2013

Software System Evolution is more planned and systematic maintenance process as well as a type of maintenance. The research of software evolution provides basis of decisions for maintenance value through cost-benefit analysis of legacy system and architecture-based software evolution enables engineers to reduce maintenance cost by automation of repetitive evolution tasks. This paper proposes a framework for software system evolution using architectural transformation pattern.

• Proceedings of the KIEE Conference
• /
• 2008.04c
• /
• pp.193-195
• /
• 2008

Safety is important factor in railway system. Now most of the electric and electronic system which is applied in railway system is the embedded system which software is used. The constitution rate of software which is involved in railway system is gradually increasing. Most of the software which is used in railway system is implemented by the software developer. Thus the implemented code has different features according to the developer and this may cause the bad effect on the software's maintenance. International standard IEC 62279 requires an adoption the coding standard to developing the railway software. And it is plan to recommend complying with the coding standard in safety criteria for railway software which is noticed as the regulation of the Korean railway safety law. In this paper, we review the requirement of coding standards which is present in the software criteria for railway software and international standard. Also it investigates the coding standard which is in other safety related industry and presents the effective way to apply the software coding standard to domestic railway industry.

• Journal of the Institute of Electronics Engineers of Korea SP
• /
• v.41 no.6
• /
• pp.137-145
• /
• 2004

The general software configuration management system shows lack of the properties and features of software development environment for multimedia due to its wide range to be covered. Multimedia software development environment has properties like repetitive analysis and simulation using visual programming environment where, beside support of elementary development functions, component or library can be combined and tested interactively. Moreover, the method to look fast and effective for component having similar function is required. In this paper, we present the system which supports the software configuration management method for a simulation tool and the system for the properties in the multimedia software development environment. And we relate our system to real simulation tool so as to check its ability as the software configuration management system for multimedia software development environment.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.11S
• /
• pp.3299-3308
• /
• 1999

One of the most important prerequisites for a successful software process is the collaboration and software requirements negotiation of all stakeholders in the software development process. Remote users using computer networks can negotiate software requirements by computer supported system, and can share their informations. The goal of software requirements negotiation system is an integration of all win conditions and an agreement after resolution of conflicts. The existing systems need an exclusive system and must be dependent on specific platform and network. Users must have the knowledge of all stakeholder's status and use homogeneous collaborating applications. This paper presents the Web-based software requirements negotiation system for the purpose of resolution of the existing systems' problems. The Web-based software requirements negotiation system can be driven by WinWin Spiral model, and it is based on hybrid execution method. The proposed system is validated and tested on heterogeneous environments.

• The Transactions of the Korean Institute of Electrical Engineers P
• /
• v.62 no.1
• /
• pp.30-35
• /
• 2013

Many function of railway signalling system which is in charge of most core function in a railway system are being operated by the software according to the development of computer technology. Accordingly, the source code testing to verify the safety of the railway signalling system software becomes to be more important, and related international standards highly recommend verifications on the source code also. For this reason, several related studies on vital source code verification were executed from several years ago in Korea. This paper performed tests through the application to railway signalling system being applied to the existing actual domestic railway sites through automated testing tools for coding rules of signalling system software and another signaling system software under development in Korea recently, and analyzed their results.

• Proceedings of the IEEK Conference
• /
• 2002.07b
• /
• pp.1339-1342
• /
• 2002

It is difficult to design system software to meet a better separation of concerns, which can provide a number of benefits such as adaptability, extensibility, and modularity in the design and implementation. During design, some aspectual properties, such as synchronization, scheduling, performance and fault tolerance, crosscut the basic functionalities of the system software. By separating functional components from the different aspectual components of the system software in the design, we can provide a better generic design model of system software. Aspect-Oriented Programming is a methodology that aims at separating components and aspects from the early stages of the software life cycle, and using techniques to combining them together at the implementation phase. In this paper we discuss an aspect-oriented framework that can simplify system software design and implementation by expressing it at a higher level of abstraction. Our work concentrates on how to achieve a higher separation of aspectual components, functional components, and layers from each other. Our goal is to achieve a better design model for implementing system software in terms of modularity, reusability and adaptability.

• Electronics and Telecommunications Trends
• /
• v.8 no.3
• /
• pp.39-52
• /
• 1993

This study involves a Common Cause Failure (CCF) problem on the ultra-high reliability required system development such as war game operations, nuclear power control, air traffic control, space shuttle missions, and large scale network communication system. The system situation problems are defined according to CCF, reliability and system fault identifications for the development cast verifications in the multi-version redundant software system. Then, CCF analysis of redundant system, system principles and statistical dependence are also described. This validation oh the CCF in the human software interaction system will notify software engineers to conceive what really is CCF contribution factor, not only the internal but the external ones.

• Journal of Information Technology Services
• /
• v.5 no.3
• /
• pp.83-97
• /
• 2006

The current software company report system in Korea has many problems in its efficiency and effectiveness. In this paper, we investigated the system by surveying the contracting officials and contractors in software development. By analyzing current status and some problems with the survey results, we derived an feasible improvement scheme for the software company report system. We suggested efficient procedures and reporting items for the registration process, some benefits for contractors, and the short-term direction for its implementation.