• The Transactions of the Korea Information Processing Society
• /
• v.6 no.1
• /
• pp.90-95
• /
• 1999

A software growth model, a mathematical model describing the growth behavior of a software system during the evolution process, enables us to predict the future system size and incremental erfort required to meet the planned system size. This paper first introduces a software growth model defined with respect to the cumulative incremental effort. It was assumed that the incremental growth of a software system is proportional to the incremental effort and function of the system size is suggested as a system complexity and then applied to real data for its validation. such a system complexity additionally provides us with a measure for complexity comparison. since the measure is independent of the system size, it is useful for comparing complexities of software systems of different size.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.9 no.13
• /
• pp.29-32
• /
• 1986

A decision procedure to determine when computer software should be released after testing is described. This paper extends optimum release policies minimizing the total expected software cost with a scheduled software delivery time under reliability requirement constraint. Such cost considerations enable us to make a release decision as to when transfer a software system from testing phase to operational phase. The underlying model is software reliability growth model described by a nonhomogeneous poisson process. It is assumed that the penalty cost function due to delay for a scheduled software delivery time is linearly proportional to time. Numerical examples are shown to illustrate the results.

• International Journal of Safety
• /
• v.3 no.1
• /
• pp.38-46
• /
• 2004

This paper introduces the software life-cycle V&V (verification and validation) tasks for the KNICS (Korea nuclear instrumentation and control system) project. The objectives of the V&V tasks are mainly to develop a programmable logic controller (PLC) for safety critical instrumentation and control (I&C) systems, and then to apply the PLC to developing the prototype of an engineered safety features-component control system (ESF-CCS) in nuclear power plants. As preparative works for the software V&V, various kinds of software plans and V&V task procedures have been developed according to the software life-cycle management. A number of software V&V tools have been adopted or developed to efficiently support the V&V tasks. The V&V techniques employed in this work include a checklist-based review and inspection, a requirement traceability analysis, formal verification, and life-cycle based software testing.

• Journal of Korean Society for Quality Management
• /
• v.34 no.3
• /
• pp.1-18
• /
• 2006

CMMI(Capability Maturity Model Integration) has been recognized as a critical method to validate the competitiveness of software development organization since its introduction. CMMI imposes additional requirements on the software development organization which has been established and certified to the ISO 9001 quality management system. This paper reviews the similarities and differences between CMMI and ISO 9001. This paper also examines what ate required to deploy the CMMI on the aircraft software development organization which has been certified to ISO 9001. The results of this study will help software development organization to provide the direction for implementing CMMI. Some suggestions are presented to identify and strengthen the weak portion of the software process quality management system.

• Proceedings of the KSR Conference
• /
• 2009.05a
• /
• pp.2056-2062
• /
• 2009

Recent advances in computer technology have brought more dependence on software to train control systems. Hence, the safety assurance of the vital software running on the railway system is very critical task and yet, not many works have been done. While much efforts have been reported to improve electronic hardware's safety, not so much systematic approaches to evaluate software's safety, especially for the vital software running on board train controllers. In this paper, we have developed the static software testing tool for railway signaling, especially Fagan Inspection supporting tool. This static testing tool for railway signaling can be utilized at the assessment phase, and also usefully at the software development stage also. It is anticipated that it will be greatly helpful for the evaluation on the software for railway signalling system.

• Bulletin of the Korean Space Science Society
• /
• 2006.04a
• /
• pp.117-120
• /
• 2006

HAUSAT-2 flight software was developed by first analyzing the satellite requirements, and incorporating the results into the software. Coding and compiling is done after the software is completed, then individual and integrated tests are performed in order to verify the flight software algorithm. Currently, HAUSAT-2 flight software integrated test has been performed and the test result is serving as a basis for code modification nd additional developments. This paper describes the architecture, development process, and development environment of HAUSAT-2 flight software.

• Journal of the Korean Society of Systems Engineering
• /
• v.8 no.2
• /
• pp.19-25
• /
• 2012

As modern weapon systems have evolved into embedded software systems, the capability to develop, install, and maintain high-quality software products is becoming increasingly valuable in today's competitive aerospace and defense industry. It is desirable, especially for government-contracted projects whose end-users are military personnel, that specific types of software quality elements are assured early during product development; namely, functionality and usability. Motivated by this need to approach improving software quality from a user's perspective, this paper presents a case study that analyzes system-level software integration testing results for a weapon system indigenously developed in the Republic of Korea. Quantitative data, such as software defect ratios and configuration change rates, are computed to observe meaningful trends with respect to functionality - represented by tests designed to verify the system's electrical signal interfaces - and usability, which is evaluated in terms of how often the initial human-computer interface had to be re-designed. Insights gained from these exercises are subsequently presented as a set of "lessons learned" to take into account when developing new software items for complex weapon systems.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.12 no.4
• /
• pp.13-24
• /
• 2016

Defense Acquisition Program Administration's weapon system software development and management guideline specifies the criteria of software reliability tests including static and dynamic tests mainly on C/C++ languages. Recently, Defense Acquisition Program Administration expanded the scope of software reliability test for the various languages including C#, java etc. but specific criteria for them are not established. This study suggests the reliability test procedures and standards on C# programming software in weapon system. For the static test, considering the nature of the C# which depends on .NET framework, this paper introduces applying coding rules recommended by Microsoft Corp. Visual Studio 2012. Block coverage provided by Visual Studio is applied on dynamic tests and the achievement objectives for block coverage according to the software levels(A, B, C) are suggested. Also, the software reliability test procedures and standards proposed by this paper are properly verified through the case study. The result of this study can be used for establishing the specific criteria of the software reliability test for C# programming software in weapon system.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.3 no.1
• /
• pp.19-24
• /
• 2008

To reduce time-to-market, more and more embedded system developers and system-on-chip designers rely on microprocessor-based design methodology. ARM processor has been a major player in this industry over the last 10 years. However, there are many restrictions on developing embedded software using ARM processor in the early design stage. For those who are not familiar with embedded software development environment or who cannot afford to have an expensive embedded hardware equipment, testing their software on a real ARM hardware platform is a challenging job. To overcome such a problem, we have designed VMA (Virtual ARM Machine), which offers easier testing and debugging environment to ARM based embedded system developers. Major benefits that can be achieved by utilizing a virtual ARM platform are (1) reducing development cost, (2) lowering the entrance barrier for embedded system novices, and (3) making it easier to test and debug embedded software designs. Unlike many other purely software-oriented ARM simulators which are independent of real hardware platforms, VMA is specifically targeted on SYS-Lab 5000 ARM hardware platform, (designed by Libertron, Inc.), which means that VMA imitates behaviors of embedded software as if the software is running on the target embedded hardware as closely as possible. This paper will describe how VMA is designed and how VMA can be used to reduce design time and cost.

• The Journal of the Convergence on Culture Technology
• /
• v.7 no.3
• /
• pp.469-474
• /
• 2021

Nowadays, a lot of software engineers struggle with the efficient back-end design of mobile application programs operated on the new mobile platform. It is simply because not only their lack of experiences in developing large scale system but also the unstructured nature of the mobile software, where there are no standard solutions. Furthermore, since big data is at the center of many challenges in system design of mobile software, so an efficient system design scheme is required for the development of such data-intensive applications. In this paper, we propose a systematic and efficient system design method that can figure out the substantial nature of the mobile software and solve the difficulties of the back-end software engineers.