• Proceedings of the KIEE Conference
• /
• 2005.05a
• /
• pp.185-187
• /
• 2005

The reactor protection system is the most important function for the safe operation of nuclear powerplants (NPPs) in that such system protects a nuclear reactor tore whose damage can cause an enormous disaster to the nuclear facility and the public. A digital reactor protection system (DRPS) is being developed in KAERI for use in the newly-constructed NPPs and also for replacing the existing analog-type reactor Protection systems. In this paper, an software verification and validation (V&V) activities for DRPS, which are independent of the DRPS development processes, are described according to the software development life cycle. The main activities of DRPS V&V processes are the software planning documentations, the verification of software requirements specification (SRS) and software design specification (SDS), the verification of codes, the tests of the integrated software and system. Moreover, the software safety analysis and the software configuration management are involved in the DRPS V&V processes. All of the V&V activities are described, in detail, in this paper.

• The Transactions of the Korean Institute of Electrical Engineers P
• /
• v.65 no.4
• /
• pp.242-249
• /
• 2016

The railway system is being converted to the computer system from the existing mechanical device, and the dependency on software is being increased rapidly. Though the size and degree of complexity of software for railway system are slower than the development speed of hardware, it is expected that the size will be grown bigger gradually and the degree of complexity will be increased also. Accordingly, the validation of reliability and safety of embedded software for railway system was started to become influential as the important issue. Accordingly, various software test and validation activities are highly recommended in the international standards related railway software. In this paper, we presented a software coding analysis tool using symbolic execution for railway system, and presented its result of implementation.

• 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 the Korea Society for Simulation
• /
• v.19 no.1
• /
• pp.153-160
• /
• 2010

Most part of errors in software development process are included during the stage of requirements definition and design. And correction or elimination of errors from those stages requires much more efforts and costs than those from the later part of software development process. However, despite of the importance of the validation of requirement definition and design stages, several kinds of problem have made it hard to be done successfully. Therefore, in this paper, we introduce a novel validation process for the preliminary design stage. The validation process is based on simulations of model and it can be used to validate requirements and model simultaneously. Models in the validation process will take only the behavior of software and be built on Ptolemy framework. The usability of our validation process is confirmed with a case study over DNS system environment. And the result of simulation shows well-known errors or vulnerabilities can be found with simulations of model which has the behavior of software. This means our validation process can be used as a process to validate requirements and models during the early stage of software development process.

• Journal of the Korean Society for Aeronautical & Space Sciences
• /
• v.40 no.6
• /
• pp.548-554
• /
• 2012

Verification and validation of operational software of the flight control computer, which is flight safety critical, is very important to prove correctness and faultness of the software. To verify the real-time softare requirement on operational software of flight control computer, real-time software internal parameter and variable monitoring technics on hardware-in-the-loop environment, similar to on-flight environment, is required. This paper describes flight safety critical software validation and verificiation environment using standard debugging interface, NEXUS 5001.

• Journal of Korea Game Society
• /
• v.11 no.6
• /
• pp.53-60
• /
• 2011

Since the importance of software reliability for game service increases continuously, the reliability evaluation becomes very important. This research performed an experiment which was intended to analyze the effect of software verification and validation, a representative activity of the software development process, on the software reliability. The results from the experiments provided the reliability evaluation based on the development process (e.g., Bayesian Belief Network based reliability estimation) with very useful bases.

• 한국IT서비스학회:학술대회논문집
• /
• 2006.11a
• /
• pp.190-193
• /
• 2006

Ther are many stages of the development for the embedded systems' hardware and software as well, which results in many test stages of it with respect to corresponding development stages. The software validation of embedded systems is taken into consideration for the testers to make sure that the systems work correctly after the deployment. Among test stages, especially control logic level testing and system validation testing are considered as the most important test, because the robustness of embedded systems' software can be validated by those two level of tests. in this paper, we would like to introduce the idea of how software test system for embedded systems can be established and of what necessary components are needed

• International Journal of Internet, Broadcasting and Communication
• /
• v.15 no.2
• /
• pp.218-226
• /
• 2023

In Korea, we still use function point based cost estimations for software size and cost of a project. The current problem is that we make difficultly calculating function points with requirements and also have less accurate. That is, it is difficult for non-experts to analyze requirements and calculate function point values with them, and even experts often derive different function points. In addition, all stakeholders strongly make the validity and accuracy of the function point values of the project before /after the development is completed. There are methods for performing function point analysis using source code [1][2][3][4] and some researchers [5][6][7] attempt empirical verification of function points about the estimated cost. There is no research on automatic cost validation with source code after the final development is completed. In this paper, we propose automatically how to calculate Function Points based on natural language requirements before development and prove FP calculation based on the final source code after development. We expect validation by comparing the function scores calculated by forward engineering and reverse engineering methods.

• Journal of the military operations research society of Korea
• /
• v.22 no.2
• /
• pp.90-112
• /
• 1996

Research issues in software engineering in recent may be object oriented methodology and software quality. Since Halstead has proposed metric-software science in 1977, software quality area has been studied in steady but inactively until 1980s. As international standards such as ISO 9000-3, 9126 were enacted in 1990s early, interest in software quality is increased but many problems such as how to validate metric, measure quality or apply metric are remained. This paper proposes software quality metric methodology which software developer or project manager can use in measuring quality and validating metric during software development. The methodology is classified by several phases: establishment of quality requirement, identification of quality metric, data collection, metric implementation, metric validation. In order to show its applicability, test program, metrics and data are applied to each phase of the methodology. Consideration of this methodology as a methodology for software quality measurement similar to development methodology for software development is needed.

• International Journal of Computer Science & Network Security
• /
• v.21 no.7
• /
• pp.284-296
• /
• 2021

Quality Models are important element of the software industry to develop and implement the best quality product in the market. This type of model provides aid in describing quality measures, which directly enhance the user satisfaction and software quality. In software development, the inheritance technique is an important mechanism used in object-oriented programming that allows the developers to define new classes having all the properties of super class. This technique supports the hierarchy design for classes and makes an "is-a" association among the super and subclasses. This paper describes a standard procedure for validating the inheritance metric in Quality Model for Object-Oriented Design (QMOOD) by using a set of nine properties established by Weyuker. These properties commonly using for investigating the effectiveness of the metric. The integration of two measuring methods (i.e. QMOOD and Weyuker) will provide new way for evaluating the software quality based on the inheritance context. The output of this research shows the extent of satisfaction of the inheritance metric in QMOOD against Weyuker nine properties. Further results proved that Weyker's property number nine could not fulfilled by any inheritance metrics. This research introduces a way for measuring software that developed using object-oriented approach. The theoretical validation of the inheritance metric presented in this paper is a small step taken towards producing quality software and in providing assistance to the software industry.